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

À̹®Èì   
   Á¶È¸ 5217   Ãßõ 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 3012/5687
2014-05   4997803   Á¤ÀºÁØ1
2015-12   1533677   ¹é¸Þ°¡
2016-06   5217   ÀÌÈñÁÖ
2008-01   5217   ¹®Á¤ÁØ
2006-08   5217   ¹èÁ¤ÇÑ
2006-06   5217   ±èÁø¼®
2006-01   5217   ÀÓ¿µ¼ö
2006-05   5217   ±è¿µ±â
2008-12   5217   ±èÈñÁ¾
2008-05   5217   ¹æÈ¿¹®
2015-01   5217   Ǫ¸¥ÇϴþƷ¡
2006-08   5217   ³ëÇϼ®
2013-07   5217   ÀÌ°©ºÎ
2005-11   5217   ¼ÕÁØ»ó
2005-11   5218   À̼ºÈ£
2015-03   5218   µ·ÅÚÆÄÆÄ
2008-01   5218   À±È£¿ë
2012-03   5218   ¹æoÈ¿o¹®
2020-02   5218   heck
2007-05   5218   ±èÇå¿í
2008-02   5218   ¿À»óÈÆ
2022-07   5218   ¹ÎÁöÆÄÆÄ