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

À̹®Èì   
   Á¶È¸ 5555   Ãßõ 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 4722/5740
2015-12   1823969   ¹é¸Þ°¡
2014-05   5307860   Á¤ÀºÁØ1
2003-01   12420   Á¶¿µÁø
2006-08   5764   ¹®»ó¼ö
2004-09   7956   ±èº´¿í
2008-04   5892   À̱Ôâ
2002-08   15060   ±è±âÈÆ
2005-07   5974   ÇϽÂÀ±
2002-09   13337   ±è¼ö¿µ
2003-05   11438   ÀüÇüÈÆ
2004-07   7833   ¹ÚÂù¹Î
2004-10   7305   ÀÎÄ¡µ¿
2004-11   7359   ¹Ú¹Î¼®
2007-09   5269   ¹Ú¼öÇö
2007-10   6538   ¹æÈ¿¹®
2008-03   6017   ±è¿ë¼ö_
2003-10   10202   ÀÌÇÐÇö
2006-08   5556   À̹®Èì
2004-05   8242   ¼ÛÈ­½Ä
2007-07   5792   °ûÅ¿µ
2005-04   6542   ±è´ëÆò
2007-12   5687   Çѵ¿ÈÆ