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

À̹®Èì   
   Á¶È¸ 5338   Ãßõ 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 4689/5707
2015-12   1669328   ¹é¸Þ°¡
2014-05   5134356   Á¤ÀºÁØ1
2008-10   4980   ¼Õ¼®¿ì
2007-09   4913   Á¤µµ¿µ
2005-06   6420   ½ÅÀ¯È£
2005-06   6466   ±è¿ëÁÖ
2008-12   5535   ¼ÛÈ­½Ä
2006-01   5826   ÀÌÁ¤¼®
2006-12   5963   Á¤¼Ûȯ
2008-02   5878   ¹æÈ¿¹®
2005-05   5924   ÇϽÂÇù
2002-09   12675   Á¶¿µ¹Î
2006-05   5639   ±èµµÇå
2006-10   5246   Áø¿øÀç
2007-12   6014   ¼­µ¿±¹
2008-04   5849   ÀÌ»óµ·
2002-07   13798   ±èº´Ã¶
2003-01   12273   Á¶¿µÁø
2006-08   5494   ¹®»ó¼ö
2004-09   7843   ±èº´¿í
2008-04   5714   À̱Ôâ
2002-08   14883   ±è±âÈÆ