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

À̹®Èì   
   Á¶È¸ 5242   Ãßõ 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 2666/5689
2015-12   1544840   ¹é¸Þ°¡
2014-05   5009080   Á¤ÀºÁØ1
2012-01   5244   ¹æoÈ¿o¹®
2006-01   5244   ±è¿µ±â
2005-11   5244   ¹ÚÁØ¿ë
2008-11   5244   ±è»óÀÏ
2008-02   5243   ³ëÇϼ®
2008-03   5243   ÀÌ»óÈ£
2013-01   5243   ¼­¹öÀ¯Á®
2007-09   5243   ±è½ÂÈÆ
2015-05   5243   ÇϾá°í´Ï
2016-03   5243   Goldentooth
2006-06   5243   À̽ÂÇö
2013-07   5243   ȸ¿øK
2015-12   5243   ÀÌÇö±æ
2008-08   5243   °í¿µ¹Î
2005-09   5243   ȲÁ¤ÀÏ
2005-06   5243   À±È£¿ë
2008-11   5243   Á¶¿µ¼ö
2006-07   5243   ±è°Ç¿ì
2006-06   5243   À±º´±Ç
2007-04   5243   ÇÑâ¼ö