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

À̹®Èì   
   Á¶È¸ 5093   Ãßõ 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 4595/5654
2015-12   1387461   ¹é¸Þ°¡
2014-05   4842818   Á¤ÀºÁØ1
2012-05   8041   ±èµ¿½Ä
2009-11   8042   ÀϹÝÀ¯Àú
2004-05   8042   È«¼ºÈ£
2004-01   8042   ÀÌÁ¾¹Î
2010-10   8042   ºí·ç¸ð¼Ç
2003-09   8042   Á¤ºÀ¿ø
2009-01   8042   ±èº´¿À
2010-06   8042   ¹Ì³à¿ÍÈ®°í¡¦
2010-06   8043   Á¶¸í¼ö
2011-12   8043   ±è°Ç¿ì
2015-08   8043   Á¶¸í¼ö
2010-07   8043   ±èÄ¡
2006-07   8043   ¿ÁÁ¾¼®
2010-01   8044   corean
2004-06   8044   ÀÌÀåÀç
2004-01   8044   À̽ÂÇö
2004-04   8044   ¹Ú¿ë¼±
2010-08   8044   ³ª³Ê¿ì¸®
2010-07   8044   song05
2010-06   8044   ¼öÆÛ¸Ç1