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

À̹®Èì   
   Á¶È¸ 5429   Ãßõ 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 2975/5710
2015-12   1695735   ¹é¸Þ°¡
2014-05   5161430   Á¤ÀºÁØ1
2012-08   5426   ¹Ì¼ö¸Ç
2017-01   5426   ¾Úºñ¾ðÆ®
2018-10   5426   ±×³ÉÁß
2012-02   5426   À嵿°Ç2014
2008-07   5426   ¹æÈ¿¹®
2005-10   5426   ÀÌÀç¼®
2006-03   5426   ·ùÀåÈ£
2007-08   5426   ÀÌâÁØ
2016-08   5426   DoubleSH
2007-11   5426   ±èÁø¿ë
2008-09   5426   ÀåÇö¸ð
2014-06   5426   Áö±ÛÁö±Û
2015-04   5426   ºü½Ã¿Â
2008-05   5426   ±èÇö¿ì
2018-03   5426   ÿ½ÃÀÇ·¥Æĵå
2014-03   5426   ¹ÙÀÌ·¯½º1
2006-01   5426   ÀåÇö¸ð
2006-03   5426   ¹ÚÁ¾´ë
2005-12   5426   Á¶½ÂÇö
2017-01   5426   Çϼ¿È£ÇÁ