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

À̹®Èì   
   Á¶È¸ 5482   Ãßõ 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 3011/5724
2014-05   5239852   Á¤ÀºÁØ1
2015-12   1765311   ¹é¸Þ°¡
2008-06   5523   ±èÁöȯ
2015-08   5523   ½½·çÇÁ
2008-06   5524   ¹æÈ¿¹®
2006-04   5524   ¹ÚÂù¹Î
2022-07   5524   cho609495
2006-02   5524   ÀÓ´ëÁß
2014-07   5524   º¸³ë´Ô
2016-10   5524   ¹Â¶ó
2015-11   5524   ÀÌ»¡Ã»Ãá
2016-07   5524   audacity
2015-01   5524   ±èÀ±¼ú
2018-08   5524   ddeell
2008-07   5524   Àü¸íö
2007-01   5524   ¹ÚÇö±Ù
2016-10   5524   ȸ¿øK
2006-03   5524   °û¼±È£
2018-10   5524   ¿©ÇØiÀÌ»óº¹
2012-03   5525   ±è°Ç¿ì
2006-05   5525   ±è´ë¼º
2006-01   5525   ÃÖ¿ë¼®