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

À̹®Èì   
   Á¶È¸ 5305   Ãßõ 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 2695/5698
2014-05   5091965   Á¤ÀºÁØ1
2015-12   1629164   ¹é¸Þ°¡
2020-07   5307   MinGi
2009-02   5307   Çã°íÈÆ
2018-12   5307   ºÎ»ê°ñµ¿Ç°
2005-09   5307   ±è¼ºÁø
2005-10   5307   ÀÌÀç¼®
2012-11   5307   Å×·¯¸®½ºÆ®
2007-11   5307   ±èÁø¿ë
2008-12   5307   ÀÓÁظð
2016-10   5307   ¹Ú¹®Çü
2008-01   5307   Â÷Àç±Ù
2006-05   5307   ±èº´¿ì
2007-06   5307   ±èÁ¾À²
2008-08   5307   ÀåÇö¸ð
2006-07   5307   ±èÇö±¹
2008-05   5307   Á¶¿µ¼ö
2021-04   5307   ½Ì±¹³¯°­µµ
2013-07   5307   ÀÌ°©ºÎ
2008-01   5307   ÀÌÈñ¿ø
2014-02   5307   ´Ùsº£ÀÌ´õ
2012-03   5307   Â÷Æò¼®