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

À̹®Èì   
   Á¶È¸ 5187   Ãßõ 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 4669/5686
2015-12   1514976   ¹é¸Þ°¡
2014-05   4978855   Á¤ÀºÁØ1
2008-03   5713   ±è¿ë¼ö_
2003-10   10031   ÀÌÇÐÇö
2006-08   5188   À̹®Èì
2004-05   8029   ¼ÛÈ­½Ä
2007-07   5400   °ûÅ¿µ
2005-04   6345   ±è´ëÆò
2007-12   5227   Çѵ¿ÈÆ
2008-01   5418   ¹ÚÇö±Ù
2008-10   7349   ¹Úº´¿í
2005-11   5793   ½ÅÀ¯È£
2006-03   5475   ³ëÇü¼®
2006-05   6230   ±èÁø¿ë
2003-11   10375   ¹ÚÀÌ¿õ
2006-08   5549   ¼Û¿µ¿À
2004-04   8443   °­Áø¼®
2005-06   5799   ¿¹º´±â
2005-12   5333   ¼Ûµ·Èñ
2006-01   5182   äÀ±¼º
2007-02   4710   Àü¿ä¼Á
2005-12   5339   ¼Û¿µÈÆ