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

À̹®Èì   
   Á¶È¸ 5412   Ãßõ 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 2987/5710
2014-05   5160080   Á¤ÀºÁØ1
2015-12   1694328   ¹é¸Þ°¡
2018-10   5412   s±èÁ¾È­z
2009-02   5412   Çã°íÈÆ
2009-01   5412   À̼ºÁØ
2008-06   5412   ¹æÈ¿¹®
2008-03   5412   ±Ç¿ÀÁØ
2008-10   5412   ÀåÅÂÁÖ
2015-10   5412   °Ü¿ï³ª¹«
2009-03   5412   ±ÇÈñ¼®
2005-11   5412   äÀ±¼º
2016-05   5412   ¹èº´·Ä
2006-10   5412   ¼ÛÀçÈÆ
2005-09   5412   ±è¼ºÁø
2016-10   5412   °Å´Ï³×
2008-07   5412   ¹æÈ¿¹®
2005-10   5412   ÀÌÀç¼®
2006-08   5412   ¿ÀÇü±Ù
2006-04   5412   À±È£¿ë
2006-10   5412   ³ëÇϼ®
2014-03   5412   ¹ÙÀÌ·¯½º1
2006-08   5412   À±Á¾¿Ï