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

À̹®Èì   
   Á¶È¸ 5160   Ãßõ 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 2689/5682
2014-05   4952369   Á¤ÀºÁØ1
2015-12   1488919   ¹é¸Þ°¡
2014-02   5161   °¡ºü·Î±¸³ª
2006-04   5161   ½Åõȣ
2013-05   5161   ÀÓ½ÃÇö
2017-11   5161   jore
2008-03   5161   ±èÇö¿ì
2021-12   5161   ¹Î»çÀå
2014-04   5161   ½É¿ìö
2020-12   5161   ȣȣÈÄ
2014-03   5161   2CPUÃÖÁÖÈñ
2006-06   5161   ±èÁÖ¿µ
2005-12   5161   À̽ÂÇÑ
2007-06   5161   À̱æ¿ø
2012-10   5161   ±Ç¿ÀÁØ
2006-05   5161   ±è¿ìÅÃ
2005-12   5161   Á¶´ë¿ø
2006-08   5161   À̹®Èì
2015-03   5160   ¹Ú»ó
2017-01   5160   ¾Úºñ¾ðÆ®
2012-03   5160   ZEBE
2006-04   5160   ±è¼º½Ä