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

À̹®Èì   
   Á¶È¸ 5389   Ãßõ 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 2966/5709
2014-05   5150717   Á¤ÀºÁØ1
2015-12   1685240   ¹é¸Þ°¡
2007-06   5389   Çѵμº
2007-09   5389   ¿À¼º±â
2011-12   5389   ±èÈ¿¼ö
2009-01   5389   À±³²¼ö
2013-11   5389   ÀÌÁöÆ÷Åä
2020-09   5389   È«¼ºÇàÁ¤»ç
2006-07   5389   ±è³²¼º
2016-12   5389   ±è°Ç¿ì
2007-09   5389   ±èÀ¶±â
2012-08   5389   À±Ä¡¿­
2017-02   5389   ¼­¹Ì
2007-11   5389   ÀÌÁ¾¿ø
2006-07   5389   ¹®Ãß±â
2019-05   5389   ¶¥¶¥
2016-01   5389   AplPEC
2005-11   5389   ¹ÚÁØ¿ë
2006-05   5389   Á¤¹ü
2019-11   5389   À嵿ÈÆ
2008-07   5389   È«Çöö
2019-05   5389   °­Çѱ¸