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

À̹®Èì   
   Á¶È¸ 5571   Ãßõ 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 4684/5743
2014-05   5323054   Á¤ÀºÁØ1
2015-12   1838482   ¹é¸Þ°¡
2013-06   11150   ¿ì¾Ó»Ñ¾Ó
2014-11   4164   ÇÏ´ÃÇÏ´Ã
2017-01   4406   PCMaster
2006-10   5608   ÀåÁø¼ö
2004-03   8969   ±è¿ìÅÃ
2014-11   3519   ÇÏ»ó¿í
2017-01   4031   LINKINPARK
2019-05   3585   ȲÁø¿ì
2006-11   5898   ¼Õ»ó¿í
2018-04   6021   ±è°Ç¿ì
2018-04   4006   epowergate
2019-05   2739   ºñ¿¤À̺ê
2017-01   5418   Ãʺ¸IT
2018-04   8374   ÄðÄðÄð
2006-11   5419   Çã¿í
2014-12   5552   ¹Ù¶ó±âIÀ̵¿¿Ï
2013-07   6681   À̱ԹÎ
2010-07   9521   ÀÌÀÏ·Î
2013-07   5156   ¿Õ¿ëÇÊ
2020-08   3057   GPGPU