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

À̹®Èì   
   Á¶È¸ 5233   Ãßõ 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 3020/5688
2015-12   1541275   ¹é¸Þ°¡
2014-05   5005998   Á¤ÀºÁØ1
2014-08   5234   À̴Ͻºii
2006-01   5234   ¼­ÅÂÈñ
2006-07   5234   ±è½Â·æ
2009-03   5234   ¾¾Çü
2006-06   5234   ¿ì½Â¿±
2018-12   5234   ha2mil
2008-07   5234   ¼³¼ºÂù
2013-07   5234   ±èÁ¦¿¬
2005-07   5234   ÃÖ¿¬½Â
2016-11   5234   ÆíÇѼ¼»ó
2005-07   5234   ¹ÚÁ¾´ë
2006-08   5234   À̹®Èì
2016-08   5235   ±è°Ç¿ì
2007-05   5235   À̵µ¼·
2015-05   5235   °Ü¿ï³ª¹«
2014-04   5235   ³ªºñz
2019-07   5235   LSSAH
2008-12   5235   ÀÓ½ÃÇö
2012-08   5235   ¹Ì¼ö¸Ç
2006-05   5235   À̼ºÈ¿