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

À̹®Èì   
   Á¶È¸ 5045   Ãßõ 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 2650/5633
2015-12   1259343   ¹é¸Þ°¡
2014-05   4713338   Á¤ÀºÁØ1
2006-06   5045   ±è°Ç¿ì
2018-10   5045   ±è°Ç¿ì
2006-02   5045   ½ÅÀç»ó
2013-10   5045   ¸ÚÀïÀÌ
2008-12   5045   ÀÌ»óµ·
2006-01   5045   ³ªº´±æ
2019-01   5045   »ç¶ûÇ϶ó
2014-02   5045   À©µµ¿ì10
2011-09   5045   Áö¸§ÆÒ´õ
2009-01   5045   À±º´ÈÆ
2015-08   5045   ±èȲÁß
2015-12   5045   goodsense
2006-06   5045   ±èÇöÈ£
2005-10   5044   ¿ì½Â¿±
2007-09   5044   ¹æÈ¿¹®
2005-12   5044   ¹ÚÁ¾´ë
2007-01   5044   Á¶À翵
2012-05   5044   ½ÂÈĴϵµÄì
2011-12   5044   ±èÈ¿¼ö
2007-10   5044   ¹ÚÁ¾¿ë