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

À̹®Èì   
   Á¶È¸ 5249   Ãßõ 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 2675/5691
2015-12   1552108   ¹é¸Þ°¡
2014-05   5016648   Á¤ÀºÁØ1
2007-09   5248   ±è½ÂÈÆ
2008-02   5248   Àü±ÙÇö
2008-09   5248   À±Ä¡¿­
2006-08   5248   ÀüÅÂÁØ
2006-06   5248   ±ÇÈñ¼®
2014-08   5248   ±è½ÂÇö1
2015-01   5247   Ǫ¸¥ÇϴþƷ¡
2013-01   5247   ¼­¹öÀ¯Á®
2005-12   5247   ¹Úµ¿¼·
2007-11   5247   ±èÁø¿ë
2008-08   5247   ÀÌÁ¦È£
2008-08   5247   °í¿µ¹Î
2005-11   5247   ¹ÚÁØ¿ë
2019-04   5247   LSSAH
2015-11   5247   ¹Ì¼ö¸Ç
2006-08   5246   È«»óÈÆ
2008-03   5246   ÀÌ»óÈ£
2005-10   5246   È«Á¾¿î
2006-05   5246   À̼ºÈ¿
2017-09   5246   °ËÀºÄá