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

À̹®Èì   
   Á¶È¸ 5378   Ãßõ 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 2737/5709
2014-05   5146027   Á¤ÀºÁØ1
2015-12   1680200   ¹é¸Þ°¡
2006-02   5378   Áö¼º¿ì
2007-08   5378   ±èÇö¿ì
2008-12   5378   Á¤ÀºÁØ
2006-01   5378   ÀÌÃæÈÆ
2017-02   5378   ¸ðÀÚ¶õÆ®
2006-06   5378   ÀÌ»ó·æ
2021-08   5378   ¿ì¸®4¶û
2006-06   5378   À±º´±Ç
2020-08   5378   ÇູÇϼ¼
2018-05   5378   ÀϷиӽºÅ©
2015-04   5378   ½ºÆ¿·¯½º
2006-06   5378   À±È£¿ë
2016-07   5378   ±è°Ç¿ì
2007-03   5378   Çѵ¿ÈÆ
2008-02   5378   ±èÁ¾¼º
2007-01   5378   À̰ǹÎ
2017-01   5378   LINKINPARK
2006-01   5378   äÀ±¼º
2015-09   5378   °³¹é¼ö28È£
2014-07   5378   2CPUÃÖÁÖÈñ