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

À̹®Èì   
   Á¶È¸ 4990   Ãßõ 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 1077/5604
2015-12   1082533   ¹é¸Þ°¡
2014-05   4531915   Á¤ÀºÁØ1
2005-07   5428   ÇϽÂÀ±
2002-09   12720   ±è¼ö¿µ
2003-05   11088   ÀüÇüÈÆ
2004-07   7505   ¹ÚÂù¹Î
2004-10   6866   ÀÎÄ¡µ¿
2004-11   6956   ¹Ú¹Î¼®
2007-09   4608   ¹Ú¼öÇö
2007-10   6095   ¹æÈ¿¹®
2008-03   5461   ±è¿ë¼ö_
2003-10   9860   ÀÌÇÐÇö
2006-08   4991   À̹®Èì
2004-05   7861   ¼ÛÈ­½Ä
2007-07   5154   °ûÅ¿µ
2005-04   6178   ±è´ëÆò
2007-12   4995   Çѵ¿ÈÆ
2008-01   5180   ¹ÚÇö±Ù
2008-10   7108   ¹Úº´¿í
2005-11   5597   ½ÅÀ¯È£
2006-03   5291   ³ëÇü¼®
2006-05   6016   ±èÁø¿ë