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

À̹®Èì   
   Á¶È¸ 5168   Ãßõ 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 2688/5683
2015-12   1492386   ¹é¸Þ°¡
2014-05   4955920   Á¤ÀºÁØ1
2015-04   5173   Áö³ª°¡´ÂÇàÀÎ
2008-04   5173   ÃÖÀç±Õ
2009-01   5173   À̼ºÁØ
2005-12   5173   ¿À»óÈÆ
2006-08   5172   Á¶¸í¼ö
2006-03   5172   ±èÇüÇÊ
2013-11   5172   º¸¹°¼¶
2017-12   5172   ¾Ïºê·Î½Ã¾Æ
2005-12   5172   ¹ÚÀç¼®
2006-06   5172   ¿ì½Â¿±
2016-08   5172   ³Ä¾Æ¾Æ¾Æ¾Ï
2007-04   5172   ¾çâ±Ç
2006-07   5171   ±Çµð¾Æ³ª
2006-01   5171   ¹Úµ¿¼·
2008-03   5171   ±èÇö¿ì
2016-09   5171   Á¤ÀçÈ£02
2005-09   5171   ¹Ú±¤´ö
2007-10   5171   ±¸¸í¼­
2016-05   5171   À¾³»³ë´Â¿Àºü
2006-02   5171   Áö¼º¿ì