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

À̹®Èì   
   Á¶È¸ 5105   Ãßõ 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 4601/5660
2015-12   1416008   ¹é¸Þ°¡
2014-05   4876863   Á¤ÀºÁØ1
2019-11   3064   ºñºñBB
2022-03   3063   JJ½Ã½ºÅÛ
2017-10   3063   ÀÓÁø¿í
2015-12   3063   ÀåÃ浿ºê·Î¡¦
2017-07   3063   psj1050
2015-03   3063   ±èÀ¯Áß
2019-01   3063   nelson1945
2017-04   3063   Tu7885
2018-10   3063   ĵÀ§µå
2017-07   3063   Èĸ®±â
2020-03   3063   GoverZG
2019-01   3063   ¹è»ó0¿ø
2014-04   3062   ¹Ú¹®Çü
2018-08   3062   dreamer74
2016-04   3062   ¹Ì¼ö¸Ç
2020-04   3062   ÀüÁø
2020-05   3062   ¸Ó¶óÄ«´Âµ¥
2017-04   3062   pika
2019-12   3062   ºí·ç¿µ»ó
2019-10   3062   Àâ½Ä