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

À̹®Èì   
   Á¶È¸ 5321   Ãßõ 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 2998/5700
2015-12   1646114   ¹é¸Þ°¡
2014-05   5109806   Á¤ÀºÁØ1
2013-02   5321   motion
2016-12   5321   ÆÈÄÚ
2018-06   5321   mapoo
2012-02   5321   ¹Ú³²±Ô
2005-12   5321   ÀåÇö¸ð
2006-08   5321   Â÷µ¿È­
2005-12   5321   俵Áø
2008-08   5321   ÀÌÁ¦È£
2005-12   5321   À¯»ç¿ë
2012-03   5321   ¸¶ÀÌÄÚÄÚ
2013-04   5321   stone92±è°æ¹Î
2013-01   5321   AKAÁö´Ï
2005-09   5321   ±è¼ºÁø
2011-09   5321   ±¸¸í¼­
2006-06   5321   ÀÌ»ó·æ
2008-03   5322   ¹®º´Ã¤
2006-03   5322   ±èÁø¼ö
2015-06   5322   ¼ÛÁÖȯ
2006-06   5322   ÀÌ»ó¿­
2009-01   5322   À̼ºÁØ