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

À̹®Èì   
   Á¶È¸ 5035   Ãßõ 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 2648/5626
2014-05   4697276   Á¤ÀºÁØ1
2015-12   1243344   ¹é¸Þ°¡
2016-09   5036   º°À̹ÀÜ
2015-02   5036   ³ª¸ô¶ó1
2016-12   5036   ÀÌÇϳª
2007-11   5036   ÀÌÀÏ·Î
2019-01   5036   »ç¶ûÇ϶ó
2009-04   5036   ÀϹÝÀ¯Àú
2020-03   5036   CircuitBoard
2012-03   5036   Â÷Æò¼®
2008-01   5036   Á¤Çö¹®
2006-06   5036   ±èÇöÈ£
2006-07   5036   ÇѺ´ÁØ
2005-10   5036   À±È£¿ë
2007-12   5036   ±ÇÇõÀÏ
2006-08   5036   À̹®Èì
2020-09   5035   ¾È°³¼Ó¿µ¿ø
2016-07   5035   ÇÞ»ìÇѽºÇ¬
2008-07   5035   ±è½ÂÇö
2006-05   5035   ÀÌÇö±Ô
2013-06   5035   ¿À¼º±â
2006-12   5035   À±È£¿ë