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

À̹®Èì   
   Á¶È¸ 5192   Ãßõ 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 3000/5686
2015-12   1518181   ¹é¸Þ°¡
2014-05   4982104   Á¤ÀºÁØ1
2008-04   5190   ÃÖÀç±Õ
2006-09   5190   ±èÅ¿ì
2006-06   5190   ¹ÚÁØ¿ë
2012-09   5190   HEUo±è¿ë¹Î
2017-09   5190   Àü¼³¼ÓÀǹ̡¦
2013-02   5190   ¼ºÅõºÒÆÐ
2005-07   5190   ±Ç¼ø±Ô
2015-10   5190   ±è¹ÎöGC
2017-07   5190   ±èȲÁß
2015-02   5191   ±èº´ÀÏ
2011-11   5191   ºÐ³ëÀÇ´Ù¿îÈú
2017-11   5191   witbox
2013-11   5191   º¸¹°¼¶
2012-04   5191   theÃ̳ð
2005-12   5191   ±ÇÈñ¼®
2015-04   5191   Áö³ª°¡´ÂÇàÀÎ
2017-11   5191   À嵿°Ç2014
2017-08   5191   ´ÃÆĶõ
2009-01   5191   À̼ºÁØ
2007-10   5191   ÀÌÁøÇü