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

À̹®Èì   
   Á¶È¸ 5128   Ãßõ 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 4607/5666
2015-12   1448524   ¹é¸Þ°¡
2014-05   4910159   Á¤ÀºÁØ1
2008-02   4849   ±è¹Î¿í
2016-06   4290   Astarot
2008-02   9568   ±Ç¿ëÀÏ
2017-06   4147   ÀüÁ÷P¿¬±¸¿ø
2022-09   1235   ÁÒ½´¾Æ
2002-05   16969   ±è»óÇö
2011-09   8753   wo9abak1
2008-03   7586   ¹ÚÁØ¿ë
2016-07   3909   ¾ç¾ç2
2002-06   15371   ±è±Ç¼ö
2005-05   6249   Á¤¿µ±³
2008-03   5238   ±è»óÀÏ
2011-09   5148   Áö¸§ÆÒ´õ
2008-04   5682   ¼ÕÀçÈÆ
2002-07   14126   Á¤»ó¿ë
2011-10   5837   ¾Æ¸§´Ù¿î³ëÀ»
2018-10   13843   À¸¶óÂ÷Â÷Â÷
2017-06   3426   ¹«±â¸í
06-04   1277   sbg2005
2014-02   3581   ¹«¾Æ