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

À̹®Èì   
   Á¶È¸ 5426   Ãßõ 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   1695704   ¹é¸Þ°¡
2014-05   5161405   Á¤ÀºÁØ1
2007-06   5424   ÇѸí¼ö
2008-08   5424   ÀÌÁ¤ÈÆ
2014-01   5424   ȸ¿øK
2006-09   5424   ±è¿µ¼ö
2007-01   5424   ÁÖÀαÇ
2006-10   5424   È«»óÈÆ
2006-03   5424   ·ùÀåÈ£
2006-10   5424   ÀÌ°üÈ£
2007-12   5424   À±È£¿ë
2007-08   5424   ÀÌâÁØ
2007-11   5424   ±èÁø¿ë
2008-05   5424   ±èÇö¿ì
2006-10   5424   ³ëÇϼ®
2006-01   5424   ÀåÇö¸ð
2015-02   5424   ³ª¸ô¶ó1
2007-04   5424   ¹æÈ¿¹®
2011-12   5424   ½ÂÈĴϵµÄì
2005-11   5424   °­¿µ½Ä
2008-02   5424   À̼ºÁØ
2006-09   5424   õÈñ½Â