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

À̹®Èì   
   Á¶È¸ 5163   Ãßõ 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 2691/5682
2014-05   4952964   Á¤ÀºÁØ1
2015-12   1489487   ¹é¸Þ°¡
2007-06   5161   À̱æ¿ø
2007-11   5161   Á¤¿µÃ¶
2015-04   5161   pingguworld
2006-05   5161   ±è¿ìÅÃ
2007-07   5161   ³²±ÃÀϳ²
2016-02   5160   yeondoo
2014-12   5160   ¿¥ºê¸®¿À
2013-03   5160   ¸Ó¶óÄ«´Âµ¥
2016-03   5160   Sgtsteam
2007-09   5160   ¹æÈ¿¹®
2016-09   5160   ¸íÀÎ
2005-11   5160   ±è³«Ã¶
2018-01   5160   ½Öcpu
2017-03   5160   µ¿ÇàÅ¥ºê
2008-02   5160   ¿¬±Ô¼º
2011-12   5160   ±èÈ¿¼ö
2006-08   5160   ±èÁö¼º
2006-10   5160   °­¼ºÁø
2012-07   5160   MikroTikÀÌÁø
2018-09   5160   ÀÌÈñÁÖ