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

À̹®Èì   
   Á¶È¸ 5096   Ãßõ 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 2985/5657
2014-05   4861050   Á¤ÀºÁØ1
2015-12   1406305   ¹é¸Þ°¡
2009-01   5114   ¹®¿µ½Ä
2016-05   5114   ¹Ú¸í±ÙTN
2007-01   5114   ¹ÚÂùÇõ
2007-05   5114   ÀÓ°æÈÆ
2006-10   5114   ¼ÛÀçÈÆ
2012-04   5114   ºÀ»ïÀÌ2
2007-11   5114   ±è½Ãö
2020-04   5114   ¸í¼ºÈ£
2006-06   5114   ¿ì½Â¿±
2005-12   5114   À̱æ¿ø
2008-03   5114   ¹ÚÁØ¿ë
2007-11   5114   ±èÁ¤ÈÆ
2005-11   5114   À±Á¾¿Ï
2014-08   5114   ȸ¿øK
2005-07   5114   À±Çö´ö
2007-04   5114   ±è´ë¼º
2006-01   5115   ÁöÇü±Ù
2006-08   5115   ÀåÁø¼ö
2013-06   5115   ¿À¼º±â
2017-09   5115   °ËÀºÄá