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

À̹®Èì   
   Á¶È¸ 5216   Ãßõ 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 4629/5687
2014-05   4997135   Á¤ÀºÁØ1
2015-12   1533025   ¹é¸Þ°¡
2010-08   8146   ±è°Ç¿ì
2009-10   8146   psj1050
2011-02   8146   ¹Ú
2006-07   8146   ¿ÁÁ¾¼®
2017-07   8147   ¼ÛÁøÇö
2004-06   8147   À±Ä¡¿­
2011-04   8147   samuelmpÁؼº
2010-01   8147   ÀÌ¿µ±Ô
2015-04   8147   ÁÒ½´¾Æ
2004-02   8147   ¹Ú¿µ·Ï
2010-04   8147   Á¶Àç°æ
2012-11   8147   ±è°Ç¿ì
2004-02   8147   ±è¿ë¼ö
2004-05   8148   ±è½ÂÇö
2004-07   8148   ÀÓ¼öȯ
2018-06   8148   ÀǷӰԻ츮¶ó
2011-01   8148   ÀÚ»ê°ü¸®
2015-02   8148   ŸÀÌÈ£
2004-03   8148   ±èµ¿Çö
2004-07   8149   ÃÖâÇö