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

À̹®Èì   
   Á¶È¸ 5031   Ãßõ 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 2648/5626
2014-05   4693612   Á¤ÀºÁØ1
2015-12   1239875   ¹é¸Þ°¡
2008-02   5034   À̱æ¿ø
2006-04   5034   ±è¿ìÁø
2016-12   5034   ¾Óµå·¹ÁØ
2012-09   5034   ±èÁöȯ1
2012-12   5034   ¿©ÁÖÀÌ»óµ·
2011-11   5033   ºÐ³ëÀÇ´Ù¿îÈú
2013-10   5033   ¹è°íÇÁ°í°¡¡¦
2005-12   5033   ±è³²¼º
2008-07   5033   ±è½ÂÇö
2006-06   5033   ¹Ú¿ë¼±
2006-03   5033   °û¼±È£
2006-01   5033   Á¶±Ôö
2016-03   5033   ¹Ì¼ö¸Ç
2006-09   5033   ±è¿µ¼ö
2017-04   5033   ¹«¾Æ
2006-04   5033   À±È£¿ë
2015-09   5033   ¸ùź
2006-01   5033   ¾ÈâÁØ
2019-01   5033   »ç¶ûÇ϶ó
2015-09   5033   ¸Þ°¡³¯¹é