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

À̹®Èì   
   Á¶È¸ 5272   Ãßõ 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 3016/5700
2014-05   5047783   Á¤ÀºÁØ1
2015-12   1584079   ¹é¸Þ°¡
2006-07   5273   ±è°Ç¿ì
2016-11   5273   ÆíÇѼ¼»ó
2005-07   5273   ¼ÒÇöÁØ
2006-04   5273   ¹ÚÂù¹Î
2006-06   5273   ±ÇÈñ¼®
2006-08   5273   À̹®Èì
2016-04   5273   ÁöÁ¸ÄÄÇ»ÅÍ
2016-08   5274   ±è°Ç¿ì
2005-11   5274   ½Åµ¿À±
2006-08   5274   Á¶¸í¼ö
2006-08   5274   È«»óÈÆ
2008-02   5274   ³ëÇϼ®
2006-02   5274   ÀÌÀ±
2006-09   5274   ¿ì½Â¿±
2008-07   5274   Á¶ÀçÇö
2008-10   5274   ÀåÅÂÁÖ
2020-06   5274   AMD7nm
2014-10   5274   ±è°Ç¿ì
2005-11   5274   À嵿±â
2006-01   5274   ¹ÚÁ¾´ë