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

À̹®Èì   
   Á¶È¸ 5362   Ãßõ 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 2725/5708
2014-05   5143856   Á¤ÀºÁØ1
2015-12   1678001   ¹é¸Þ°¡
2006-04   5361   ¾ÈâÁØ
2006-08   5361   Á¤ÀÇÇÑ
2005-07   5361   ÃÖ¿¬½Â
2016-01   5361   sensekuh
2005-07   5361   ¹æÈ¿¹®
2005-11   5361   ¹ÚÁØ¿ë
2006-08   5361   ÀüÅÂÁØ
2016-10   5361   Çϳë±è»ó°í
2014-07   5361   Á¤Ã¢Áø
2007-12   5361   ±ÇÇõÀÏ
2016-12   5361   ´ÃÆĶõ
2007-01   5361   À̺À·Ä
2015-09   5361   °³¹é¼ö28È£
2016-11   5360   ¹Ð¿ì
2007-09   5360   ±èÇö¿ì
2006-07   5360   ±Çµð¾Æ³ª
2017-12   5360   MPerformance
2008-07   5360   ÇÑÁø¿ì
2008-01   5360   ¹®Á¤ÁØ
2008-09   5360   ±èµ¿¹ü