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

À̹®Èì   
   Á¶È¸ 5320   Ãßõ 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 2704/5701
2015-12   1645017   ¹é¸Þ°¡
2014-05   5108677   Á¤ÀºÁØ1
2012-05   5320   2CPUÃÖÁÖÈñ
2016-01   5320   ±èÈñ¿µ
2018-06   5320   mapoo
2012-02   5320   ¹Ú³²±Ô
2005-12   5320   ÀåÇö¸ð
2006-08   5320   Â÷µ¿È­
2012-09   5320   ±×¸°º¸ÀÌ
2006-07   5320   ±èÇö±¹
2012-03   5320   ¸¶ÀÌÄÚÄÚ
2013-09   5320   ¹ÚÇö±Ù
2013-01   5320   AKAÁö´Ï
2007-11   5320   ±è°ü½Ä
2008-07   5320   È«Çöö
2011-09   5320   ±¸¸í¼­
2007-04   5320   ±èÀ±¼ú
2008-05   5319   ³ëÇϼ®
2008-01   5319   ¼±¿ì±Õ
2005-10   5319   ±è´ë¼º
2005-12   5319   À̼ºÁÖ
2008-07   5319   ¹ÚÁø±¹