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

À̹®Èì   
   Á¶È¸ 5115   Ãßõ 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 4557/5662
2014-05   4889052   Á¤ÀºÁØ1
2015-12   1428002   ¹é¸Þ°¡
2006-11   5077   ¹®º´±â
2006-11   4633   ¹®º´±â
2006-11   4756   Á¤¸í±â
2006-11   4672   ÃÖâÇö
2006-11   4600   ¹èµ¿°ü
2006-11   8258   ¿À»óÈÆ
2006-11   4781   ±èÇѱ¸
2006-11   4493   ¼­À±¼±
2006-11   6143   °­¼ºÁø
2006-11   4693   ÀÌÁ¾¿ø
2006-11   6902   ±è»óÁø
2006-11   6503   ±è»óÁø
2006-11   4695   °ûÅ¿µ
2006-11   4797   ±è´ë¼º
2006-11   6804   ³²¼º·æ
2006-11   4603   õÈñ½Â
2006-11   5062   ±Çµð¾Æ³ª
2006-11   4783   ±èÇѱ¸
2006-11   4451   ¹æÇõÁØ
2006-11   4238   À±È£¿ë