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

À̹®Èì   
   Á¶È¸ 5425   Ãßõ 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 2740/5710
2014-05   5161403   Á¤ÀºÁØ1
2015-12   1695699   ¹é¸Þ°¡
2005-11   5423   ±èº´»ó
2005-07   5423   Á¶¿ëÁÖ
2009-03   5423   ±ÇÈñ¼®
2005-09   5423   ±è¼ºÁø
2016-12   5423   ½Ãµµ´Ï
2006-04   5423   ÀåÀÎÂù
2012-11   5423   Å×·¯¸®½ºÆ®
2015-01   5423   ±¸ÇüÈ°¿ë°¡
2016-05   5423   NAS°íÀå³µ´Ù¡¦
2016-11   5423   ±è°Ç¿ì
2018-11   5423   ·ù·ù·ù
2015-01   5423   ±èÀ±¼ú
2006-10   5423   ³ëÇϼ®
2014-03   5423   ¹ÙÀÌ·¯½º1
2006-09   5423   À±Á¾¿Ï
2006-03   5423   ¹ÚÁ¾´ë
2006-08   5423   ±èÁö¼º
2014-06   5423   ±èÀÍÅÂ
2008-07   5423   ¹ÚÀ§·Õ
2008-09   5423   Çѵ¿ÈÆ