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

À̹®Èì   
   Á¶È¸ 5300   Ãßõ 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 4639/5697
2014-05   5084692   Á¤ÀºÁØ1
2015-12   1621877   ¹é¸Þ°¡
2010-07   8205   ±èÁ¤Áß
2013-06   8205   ±è°Ç¿ì
2009-10   8205   º¸½½ºñ³»¸®¡¦
2004-08   8205   ¹®Áöȯ
2012-08   8205   ¹Ì¼ö¸Ç
2016-05   8206   amplifier
2004-07   8206   ÀÌ°æ´ö
2004-01   8206   ±èµ¿Àº
2010-12   8206   ´Ù·ÕÀÌ
2004-04   8206   ¾ÈÁ¾¿õ
2019-02   8207   ´ÃÆĶõ
2009-03   8207   Sico
2013-04   8207   ¹Ú¼º¸¸
2004-04   8207   ¹Ú¼º¼®
2004-07   8207   ±èöȯ
2010-12   8207   À¯È£ÁØ
2011-01   8207   ¸±·ç
2016-11   8208   Jjun
2013-10   8208   ¹Ú¹®Çü
2004-01   8208   ±è´ö±â