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

À̹®Èì   
   Á¶È¸ 5176   Ãßõ 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 4627/5686
2014-05   4969544   Á¤ÀºÁØ1
2015-12   1505854   ¹é¸Þ°¡
2023-05   2280   À̸ŸÁ·®2
2015-12   12202   ±ô¹Ú±ô¹Ú°¡
2020-06   3442   µðÁöÀ¯
2013-02   5596   ¶Ñ¶Ñ±è´ë¿ø
2016-12   3768   ¿À¼º±â
2018-01   3950   ½É¹ÙÆ®
2013-02   5462   ±è»óÀÏ
2018-02   6586   ¾Æ¶ó¾ß
2018-02   3839   PCMaster
2019-04   7447   Waterticket
2010-01   10272   ¿ÀÁØÈ£5
2010-01   17844   ³ª³Ê¿ì¸®
2023-06   1754   Ȧ¸¯0o0
2013-03   11237   HEUo±è¿ë¹Î
2014-09   13893   õ¿Üõoo³ë¡¦
2014-10   6367   ¹æoÈ¿o¹®
2016-12   5050   NeOpLE
2014-10   4513   ±Ã±Ý¿Í
2019-04   6761   2CPUÃÖÁÖÈñ
2016-12   4251   ±è¿µ±Õ