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

À̹®Èì   
   Á¶È¸ 5646   Ãßõ 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 4693/5752
2014-05   5380671   Á¤ÀºÁØ1
2015-12   1894998   ¹é¸Þ°¡
2011-06   8472   13579
2011-02   8472   ½É¹ÙÆ®
2004-03   8472   ÇϽÂÇù
2010-04   8472   ¹æoÈ¿o¹®
2009-05   8472   ¼Û½ÂÈ­
2015-06   8473   Àü¼³¼ÓÀǹ̡¦
2010-05   8473   ±èÁ¤Áß
2004-03   8473   Â÷Æò¼®
2012-11   8473   ±èÀºÈ£
2011-03   8473   ¸¶·Î±î²þ
2004-06   8474   ¿À½ÂÁØ
2012-12   8474   °æ¹ÚÇѽùÎ
2009-04   8474   ¿©ÁÖÀÌ»óµ·
2011-06   8474   yummy
2016-04   8474   Â÷ºÐÇϰÔÇÏÀÚ
2014-01   8474   ±èÀºÈ£
2015-12   8474   Macstall
2019-11   8474   ±èÁ¦¿¬
2004-11   8474   À̼ºÈ¿
2014-10   8474   õ¿Üõoo³ë¡¦