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

À̹®Èì   
   Á¶È¸ 5151   Ãßõ 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 2991/5679
2014-05   4942949   Á¤ÀºÁØ1
2015-12   1479762   ¹é¸Þ°¡
2012-03   5150   °û¼øÇö
2014-10   5150   º¹ºÎºñ¸¸
2016-02   5151   yeondoo
2013-08   5151   À嵿°Ç2014
2014-02   5151   °¡ºü·Î±¸³ª
2013-05   5151   ÀÓ½ÃÇö
2017-01   5151   ¾Úºñ¾ðÆ®
2016-09   5151   ¸íÀÎ
2012-03   5151   ZEBE
2015-04   5151   ºü½Ã¿Â
2008-02   5151   ¿¬±Ô¼º
2017-10   5151   ÇãÀα¸¸¶Æ¾
2005-12   5151   Á¶´ë¿ø
2008-08   5151   ±èÇѱ¸
2012-11   5152   ¶Ñ¶Ñ±è´ë¿ø
2011-10   5152   ½ÂÈĴϵµÄì
2013-03   5152   ¸Ó¶óÄ«´Âµ¥
2016-04   5152   ÆíÇѼ¼»ó
2006-01   5152   ¼ÒÇöÁØ
2008-12   5152   ÀÌÀç´ö