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

À̹®Èì   
   Á¶È¸ 5103   Ãßõ 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 4558/5659
2015-12   1410694   ¹é¸Þ°¡
2014-05   4865394   Á¤ÀºÁØ1
2006-11   4784   À̼ºÁØ
2006-11   4882   ÀÌÀç¼±
2006-11   7972   ¾ÈâÁØ
2006-11   4817   °­°æ¸ð
2006-11   4228   ¹Ú¼ºÀÏ
2006-11   4973   ÀÌ»ó¿­
2006-11   4651   À±È£¿ë
2006-11   5411   ³ëÇϼ®
2006-11   5123   À¯È£ÁØ
2006-11   4803   Á¤¸íÇö
2006-11   4576   ±èÇѱ¸
2006-11   5024   ÃÖ°ÇÁÖ
2006-11   4690   Á¤ÁÖȯ
2006-11   4575   Á¤Ã¢ÈÆ
2006-11   4941   ±è½ÂÅÂ
2006-11   8388   ±è»ó¿ìAP
2006-11   4524   ÃÖ°æ¹Î
2006-11   4895   ÀåÁø¼ö
2006-11   4861   ¹ÚÁØ¿ë
2006-11   6521   ÀåÁø¼ö