arc-1220¿¡¼­ RHEL as4 up3¸¦ »ç¿ëÇÒ¶§, Ä¿³Î ¾÷µ¥ÀÌÆ®½Ã...

À̹®Èì   
   Á¶È¸ 5183   Ãßõ 9    


arc ·¹À̵å ÄÁÆ®·Ñ·¯¿¡¼­ RHEL as4 up3À» »ç¿ëÇÒ¶§,
¼³Ä¡½Ã linux dd·Î µå¶óÀ̹ö¸¦ ¼³Ä¡ÇÏ´õ¶óµµ

¼³Ä¡°¡ ³¡³­ ÈÄ, Ä¿³Î ¾÷µ¥ÀÌÆ®¸¦ ½Ç½ÃÇÏ°Ô µÇ¸é,
"/"ÆÄƼ¼Ç ¹× °¢ ÆÄƼ¼Ç ¹× À̹ÌÁö¸¦ ¸ø ã°Ô µÇ´Âµ¥,
(»õ Ä¿³Î ¹öÁ¯¿ë µå¶óÀ̹ö¸¦ ãÁö ¸øÇÏ´Â Çö»ó)

ÇØ°á ¹æ¹ýÀÔ´Ï´Ù.

Q-10180608 – We are currently running the kernel version "2.6.9-34.EL.x86_64". When we try to make an automated Red Hat Network upgrade to the "2.6.9-34.0.2.EL-x86_64" kernel (one which fixes a security hole with core dumps), the system will not boot using the updated kernels. Here's what happens.
Requested and Answered by Vincent on 10-Aug-2006 (36 reads)
Areca other customer has found things work fine even for the new Update4 release (2.6.9-42.EL) if you do a few things BEFORE you do the upgrade:

a. Before they want to isntall 2.6.9-34.0.2EL, do a
mkdir -p /lib/modules/2.6.9-34.0.2EL/updates
cp /lib/modules/2.6.9-34.EL/updates/*
/lib/modules/2.6.9-34.0.2EL/updates

b. now install the new 2.6.9-34.0.2EL kernel RPM

c. When the RPM installs, it will create the required mkinitrd for booting which will work just fine.


À§ÀÇ ³»¿ëÀº areca»çÀÇ Áö½Ä¹ðÅ©(?) ÀÇ ³»¿ëÀÔ´Ï´Ù.



ªÀº±Û Àϼö·Ï ½ÅÁßÇÏ°Ô.


QnA
Á¦¸ñPage 4627/5686
2014-05   4975281   Á¤ÀºÁØ1
2015-12   1511447   ¹é¸Þ°¡
2020-03   3123   °Ü¿ï³ª¹«
2017-07   3123   ¼ºÅõºÒÆÐ
2020-04   3123   ¿¥ÇÃ
2017-09   3123   Çã´Ï¿µÈ£
2014-04   3122   ¹Ú¹®Çü
2021-03   3122   ¿ø»óÇö
2015-06   3122   ±è»ó¹Î
2017-05   3122   µþ±â´ëÀå
2015-03   3122   ±èÀ¯Áß
2019-05   3122   ¸á¶û²Ã¸µ
2015-07   3122   ½½·çÇÁ
2015-03   3122   ÄÄÁö±â
2019-04   3122   È︶
2019-04   3122   ¼ÇÇѸÆÁÖ
2018-12   3122   ¾ç½Ã¿­
2014-04   3122   ¹Ú
2018-01   3122   ÇÞ»ìÇѽºÇ¬
2017-04   3122   ¹äÇѳ¢
2019-12   3122   ±èȲÁß
2022-03   3121   µðÁöÀ¯