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

À̹®Èì   
   Á¶È¸ 5126   Ãßõ 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 5547/5665
2015-12   1444463   ¹é¸Þ°¡
2014-05   4906004   Á¤ÀºÁØ1
2006-07   7179   ÀÌÈ£µ¿
2010-02   9976   ¿Õ¿ëÇÊ
2020-07   3653   ÀüÁø
2018-03   8273   ±è¹ÎöGC
2020-07   2413   ºÐ´ç±èµ¿¼ö
2020-07   4453   ¸¸¹«¶óºñ
2013-04   35706   °¡ºü·Î±¸³ª
2019-04   4551   Àü½ÂÀ±
2020-07   3301   ¸¸¹«¶óºñ
2014-10   5549   ³ªºñz
2006-08   5127   À̹®Èì
2017-01   6798   ¿Ï¼Ò½É³²
2010-03   7395   ¹èÁÖ±Ô
2014-10   4271   Ç®·Îµå½Ã½ºÅÛ
2017-01   4865   ¼ÛÁÖÇü
2018-03   7250   Ÿ¸·
2004-01   9566   Àü¼ºÈÆ
2021-12   1964   ¯´Ô
2004-01   8393   ¹ÚÂùÀÏ
2019-05   3140   ¸¶½ºÄÚÆ®