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

À̹®Èì   
   Á¶È¸ 5330   Ãßõ 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 4648/5706
2015-12   1665132   ¹é¸Þ°¡
2014-05   5130303   Á¤ÀºÁØ1
2011-01   8234   ±è½Â±Ç
2004-03   8234   ±èµ¿Çö
2014-12   8235   ÂÄÀμº
2011-02   8235   ºÒ°¡¸¶ÅÁ
2010-07   8235   µ¥À̺ñµå
2010-01   8235   ȲȥÀ»ÇâÇØ
2013-10   8235   ¹è°íÇÁ°í°¡¡¦
2010-01   8236   corean
2011-03   8236   NiteFlite9
2016-10   8236   MikroTikÀÌÁø
2008-09   8236   ¹æÈ¿¹®
2004-06   8236   °­Á¤Çõ
2004-07   8236   Á¤Ä¡¹Î
2004-03   8237   ±èÄ¡ÈÄ
2009-11   8237   ÀϹÝÀ¯Àú
2010-04   8237   ±èÀå¿ì
2013-06   8237   ´Ù·ÕÀÌ
2004-01   8237   ±èµ¿Àº
2004-07   8237   º¯±âÈ«
2004-02   8237   ¿À¼º¿í