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

À̹®Èì   
   Á¶È¸ 5407   Ãßõ 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 2985/5710
2015-12   1692016   ¹é¸Þ°¡
2014-05   5157731   Á¤ÀºÁØ1
2016-05   5406   À嵿°Ç2014
2007-03   5406   Çѵ¿ÈÆ
2008-09   5406   ÀÌ°æ¹Î
2006-03   5407   ±èÁø¼ö
2006-08   5407   ¹èÁ¤ÇÑ
2011-10   5407   ȲȥÀ»ÇâÇØ
2012-11   5407   ¶Ñ¶Ñ±è´ë¿ø
2016-12   5407   susemi
2006-08   5407   È«»óÈÆ
2008-06   5407   ÀÌÁ¾¹ÎCB
2006-06   5407   Á¤»ó¾ï
2007-10   5407   Á¶ÀçÇö
2008-09   5407   ÃÖâÇö
2017-09   5407   Á¶Áö¿¬
2009-02   5407   Çã°íÈÆ
2009-01   5407   À̼ºÁØ
2006-09   5407   ±èÀ±¼ú
2007-06   5407   ¼±Ã¶
2006-05   5407   À̼ºÈ¿
2008-03   5407   ±èÇö¿ì