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

À̹®Èì   
   Á¶È¸ 5518   Ãßõ 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 4677/5736
2014-05   5280130   Á¤ÀºÁØ1
2015-12   1804718   ¹é¸Þ°¡
2004-02   8354   À̼ºÈ¿
2010-07   8354   song05
2008-09   8354   ¹æÈ¿¹®
2011-08   8354   ±è½Å¿ì
2013-06   8354   ±è°Ç¿ì
2016-03   8354   izegtob
2004-05   8354   õ±â¼®
2004-02   8355   Á¤¿ø¿õ
2013-05   8355   HEUo±è¿ë¹Î
2011-02   8355   ±×±×
2010-03   8355   ¹Ú»ó¹ü
2012-11   8355   ±èÀºÈ£
2010-01   8355   ȲȥÀ»ÇâÇØ
2016-03   8355   ȸ¿øK
2010-04   8356   ±èÀå¿ì
2007-10   8356   ±èÈ«±æ
2013-10   8356   À¯È£ÁØ
2003-05   8356   °­¹Î
2011-04   8357   ±¼´Ù¸®±³
2004-07   8357   Á¤¿ø¿õ