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

À̹®Èì   
   Á¶È¸ 5121   Ãßõ 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 4605/5664
2015-12   1439722   ¹é¸Þ°¡
2014-05   4901126   Á¤ÀºÁØ1
2004-01   8083   ±èÁ¤¿ì
2010-02   8083   ³ª³Ê¿ì¸®
2004-07   8083   ÀÓ½ÃÇö
2010-12   8084   ÀüÇüÁØ
2011-03   8084   classiccha
2004-05   8084   ±èÈ¿¼ö
2015-04   8084   ÁÒ½´¾Æ
2009-03   8084   Sico
2004-03   8084   Á¶±Ù»ó
2013-09   8084   ¸ÚÁø³Ñ
2004-06   8084   ¹ÚÂùÀÏ
2011-07   8084   ÀÌÁ¾Çöoph
2004-04   8084   Àü¼ºÈÆ
2004-03   8084   ±è±â¹ü
2013-11   8085   µÎ¸®¾È
2010-07   8085   ¿¹°ü½Å±Ô½Ä
2009-10   8085   ±è°Ç¿ì
2004-02   8085   À±µ¿Èñ
2018-09   8085   ¼ÛÁÖȯ
2013-10   8085   À¯È£ÁØ