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

À̹®Èì   
   Á¶È¸ 5177   Ãßõ 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 4627/5686
2014-05   4971219   Á¤ÀºÁØ1
2015-12   1507501   ¹é¸Þ°¡
2004-08   7253   Á¤¸¢
2007-10   6164   ³²±ÃÀϳ²
2007-11   5499   ¹Úº´Èñ
2005-03   6966   À¯ÁöÈÆ
2006-02   6039   Á¤ÇÑ°æ
2004-11   6858   ¹Î°æ¼·
2005-03   6750   ÀÌÁ¾Çõ
2002-10   11490   ¼­¿µ¹«
2005-10   5820   ÀÌâ¼®
2003-04   10787   Á¶Çö±Ô
2003-06   9463   Á¤±¸½Â
2003-08   9100   Á¤±âÁ¾
2006-04   5566   ÀåÁø¿ì
2006-05   5568   Á¶À±¼º
2006-06   5230   °­¼ºÁø
2008-03   5561   ÇÑŵ¿
2008-04   5916   ÀÌ»óµ·
2003-09   8027   À±Ä¡¿­
2007-03   4954   ¹ÚÁØ¿ë
2007-06   5231   ÀÌ»óµ·