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

À̹®Èì   
   Á¶È¸ 5172   Ãßõ 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 4627/5685
2014-05   4963394   Á¤ÀºÁØ1
2015-12   1499851   ¹é¸Þ°¡
2012-11   8126   ±èÀºÈ£
2011-04   8127   ±¼´Ù¸®±³
2004-04   8127   °í´ëÁØ
2013-10   8127   À¯È£ÁØ
2011-04   8127   Anonymous
2015-04   8127   ȯŸ
2011-04   8128   samuelmpÁؼº
2022-02   8128   Ãʱް³¹ßÀÚ
2012-12   8128   ±è°Ç¿ì
2018-02   8128   ³ª¶ó»ç¶û
2010-02   8128   ³ª³Ê¿ì¸®
2018-09   8128   °³¹é¼ö28È£
2004-07   8128   ÀÓ½ÃÇö
2013-06   8128   ±è°Ç¿ì
2016-11   8128   Çϴø¶·ç
2015-01   8129   icarusom1
2004-01   8129   ¼Û»óº´
2004-02   8129   ±èöȯ
2016-04   8130   Çê¶Ñ
2004-05   8131   ±èÈ¿¼ö