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

À̹®Èì   
   Á¶È¸ 5325   Ãßõ 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 4644/5702
2015-12   1652344   ¹é¸Þ°¡
2014-05   5116881   Á¤ÀºÁØ1
2015-12   3254   jabez033
2017-04   3254   ¿À¼Ò¸®
2015-12   3254   ¾Þ¾Þ¾Þ
2014-03   3253   ±¼´Ù¸®±³
2020-08   3253   Ä«·½
2018-03   3253   ¿À»óÈÆ
2024-01   3253   ½Å¿ì¼·
2020-08   3253   agegold
2018-11   3253   FreeBSD
2019-04   3253   ¼ÇÇѸÆÁÖ
2017-06   3253   ±è°Ç¿ì
2019-12   3253   ½ÅÀº¿Ö
2019-05   3253   ¼­¿ï»ç¶÷
2017-10   3253   ºí·ç¿µ»ó
2020-04   3253   ÇÑ°­ÇÑ»´ºä
2020-04   3253   ¿¥ÇÃ
2017-07   3253   ÄÚÄí
2021-07   3253   ½Ã°ñ³ëÀÎ
2014-04   3252   ¹æoÈ¿o¹®
2019-02   3252   Win31