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

À̹®Èì   
   Á¶È¸ 5430   Ãßõ 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 2973/5710
2015-12   1695750   ¹é¸Þ°¡
2014-05   5161440   Á¤ÀºÁØ1
2009-05   5425   Ggrpia
2014-07   5425   Á¤Ã¢Áø
2006-07   5425   È«µ¿±Ç
2008-09   5425   ÀÌ°æ¹Î
2008-06   5425   ¹ÚÁßÇÊ
2007-08   5426   ³ëÇϼ®
2006-06   5426   ÃÖÁÖÈñ
2006-01   5426   ÇѼºÁØ
2007-12   5426   ±Ç¿ÀÁØ
2015-06   5426   °¥¸¯Çªµå
2009-01   5426   ±è¿µ¼ö
2017-06   5426   ÀϷиӽºÅ©
2006-08   5426   Á¶¸í¼ö
2007-09   5426   ±èµ¿¹ü
2007-09   5426   ¹æÈ¿¹®
2012-08   5426   ¹Ì¼ö¸Ç
2014-07   5426   ¼¼°¡»õÅÏ
2017-01   5426   ¾Úºñ¾ðÆ®
2018-10   5426   ±×³ÉÁß
2015-08   5426   Àü¼³¼ÓÀǹ̡¦