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

À̹®Èì   
   Á¶È¸ 5198   Ãßõ 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 4628/5687
2014-05   4989667   Á¤ÀºÁØ1
2015-12   1525649   ¹é¸Þ°¡
2017-09   4148   ¸â¹ö3
2008-11   5860   ¹Ú¿µ¼±
2012-03   6430   ÀϹÝÀ¯Àú
2018-12   3150   ĸƾ¾Æ¸Þ¸®Ä«³ë
2012-03   4936   Á¶¿î
2017-09   3392   polipilo
09-09   647   2CPUÃÖÁÖÈñ
2012-03   5617   ±è°Ç¿ì
2015-08   3786   ÃÖâÇö
2003-02   10868   À̳â¿ë
2018-12   5328   ĵÀ§µå
2003-02   12329   °­µ¿¿µ
2015-08   9403   2CPUÃÖÁÖÈñ
09-22   652   ÇÚÁî
2018-12   3015   Sikieiki
2016-09   7801   À̹ÌÁ¸ÀçÇÏ¡¦
2015-08   4546   °¡ºü·Î±¸³ª
2021-06   2982   ¯´Ô
2005-11   6230   ±èÇÑÁÖ
2020-02   12266   ityongsan