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

À̹®Èì   
   Á¶È¸ 5238   Ãßõ 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 3021/5688
2014-05   5007167   Á¤ÀºÁØ1
2015-12   1542966   ¹é¸Þ°¡
2008-01   5237   ±èµ¿¼ö
2017-02   5237   »õÃÑ
2020-07   5237   ¿µ»êȸ»ó
2008-08   5237   ±èÇѱ¸
2008-05   5238   ³ëÇϼ®
2014-08   5238   À̴Ͻºii
2006-06   5238   ÀÌÁ¤È­
2005-09   5238   °­°æ´ö
2008-06   5238   Çѵ¿ÈÆ
2023-03   5238   NiteFlite9
2016-11   5238   ÆíÇѼ¼»ó
2006-03   5239   ¹é±âµ¿
2017-08   5239   º¸¶ó¸Å
2012-12   5239   ¿¡½ºÆijÄ
2006-05   5239   ±è´ë¼º
2005-10   5239   È«Á¾¿î
2006-08   5239   À̱æ¿ø
2014-01   5239   ȸ¿øK
2009-04   5239   ÀÓÁ¾¿­
2016-01   5239   ȲÀ¯½Ä