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

À̹®Èì   
   Á¶È¸ 5208   Ãßõ 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 2683/5687
2014-05   4996036   Á¤ÀºÁØ1
2015-12   1531947   ¹é¸Þ°¡
2008-06   5206   ±èÁÖ¾È
2014-07   5206   ¼¼°¡»õÅÏ
2014-02   5206   ÀÌÁöÆ÷Åä
2015-11   5206   ±è°Ç¿ì
2008-03   5206   ¹ÚÁØ¿ë
2005-07   5206   ±èÁö¿µ
2013-09   5206   ȲȥÀ»ÇâÇØ
2017-01   5206   Áú¹®Çлý
2009-08   5205   ¹Ú¹®Çü
2017-12   5205   3cpu
2006-11   5205   ±è³²¼º
2016-05   5205   NAS°íÀå³µ´Ù¡¦
2014-10   5205   À嵿°Ç2014
2018-01   5205   PeerTree
2005-11   5205   Á¤À翬
2011-09   5205   Áö¸§ÆÒ´õ
2012-11   5205   inquisitive
2020-12   5205   À嵿°Ç2014
2020-07   5205   ¿µ»êȸ»ó
2007-03   5205   Çѵ¿ÈÆ