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

À̹®Èì   
   Á¶È¸ 5170   Ãßõ 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 2993/5683
2015-12   1493263   ¹é¸Þ°¡
2014-05   4956782   Á¤ÀºÁØ1
2008-09   5169   ÃÖâÇö
2008-03   5169   ±èÁÖ¿µ
2006-11   5169   Ȳ¼±°ü
2014-04   5169   ½É¿ìö
2018-11   5169   ¹ÚÁß¼®
2012-12   5169   ¹Ú¼º¸¸
2005-12   5169   À̽ÂÇÑ
2007-06   5169   ¹Ú³ª¶ó
2006-04   5169   ±èÀ±µ¿
2008-10   5169   À̹®Èì
2012-10   5169   ±Ç¿ÀÁØ
2016-03   5169   dreamer74
2005-12   5169   Á¶´ë¿ø
2014-12   5170   ¿¥ºê¸®¿À
2017-02   5170   ±èÇö¿ì1
2017-04   5170   Tu7885
2018-09   5170   ÀÌÈñÁÖ
2006-08   5170   È«¼ºÁø
2014-10   5170   º¹ºÎºñ¸¸
2009-02   5170   ¹Ì³à¿ÍÈ®°í¡¦