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

À̹®Èì   
   Á¶È¸ 5372   Ãßõ 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 2726/5709
2014-05   5145529   Á¤ÀºÁØ1
2015-12   1679642   ¹é¸Þ°¡
2005-12   5371   À̽ÂÇÑ
2013-01   5371   ºí·¢
2016-06   5371   ÀÌÇØÂù
2017-02   5371   À嵿°Ç2014
2005-07   5371   ÃÖ¿¬½Â
2017-10   5371   ½Ãµµ´Ï
2021-12   5371   ¾ÈÇü°ï
2009-01   5371   Á¤¼ºÈÆ
2019-05   5371   ÂøÇÏ°Ô»ìÀÚ2
2019-05   5371   °­Çѱ¸
2006-02   5371   Áö¼º¿ì
2015-10   5371   ¼­¿ï»ç¶÷
2007-10   5371   ±èµ¿¼ö
2007-09   5371   ÀÌÁ¾¿ø
2015-08   5371   ¹Ì·ç°¡·ç
2021-02   5371   neo21s
2021-08   5371   ¿ì¸®4¶û
2020-08   5371   ÇູÇϼ¼
2006-12   5371   ±è´ë¼º
2016-12   5371   ¹Ú¹®Çü