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

À̹®Èì   
   Á¶È¸ 5201   Ãßõ 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 2686/5687
2015-12   1530139   ¹é¸Þ°¡
2014-05   4994202   Á¤ÀºÁØ1
2012-12   5201   ÇãÁøÇüALpha
2012-04   5201   ºÀ»ïÀÌ2
2006-10   5201   ³ëÇϼ®
2017-08   5201   ´ÃÆĶõ
2016-08   5201   ³Ä¾Æ¾Æ¾Æ¾Ï
2005-07   5201   ±èÁ¤¿í
2017-02   5201   ¼ÛÁøÇö
2006-08   5201   ÀåÁø¼ö
2006-02   5201   ¹ÚÀ§·Õ
2014-07   5200   À©µµ¿ì10
2023-06   5200   È£Á¶
2019-03   5200   annm
2014-02   5200   Ȳ¼ºÁø
2008-01   5200   ±¸¸í¼­
2005-12   5200   Á¤¹ü
2005-07   5200   ¹ÎÁ¤±â
2014-03   5200   À嵿°Ç2014
2014-08   5200   eorupa
2015-02   5199   ±èº´ÀÏ
2008-05   5199   ³ëÇϼ®