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

À̹®Èì   
   Á¶È¸ 5503   Ãßõ 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 4671/5729
2015-12   1790080   ¹é¸Þ°¡
2014-05   5265090   Á¤ÀºÁØ1
2013-11   8337   ±èµ¿¹Î
2004-03   8337   Çѵ¿ÈÆ
2010-09   8337   ¾Æ¸§´Ù¿î³ëÀ»
2010-04   8337   ºí·ç¿µ»ó
2011-11   8337   Landa
2004-02   8338   À̼ºÈ¿
2009-10   8338   Ǫ¸ªÀÌ
2011-12   8338   ±è°Ç¿ì
2013-05   8338   HEUo±è¿ë¹Î
2015-08   8338   izegtob
2003-07   8338   ¿À´ë¼·
2003-09   8338   ±èÇöÈ¿
2011-03   8339   ¹Ú»ó¹ü
2004-04   8339   È«µ¿±Ç
2004-05   8339   õ±â¼®
2010-08   8340   À±¿µµ·
2013-09   8340   Æ÷¿ì
2006-04   8340   ½É±Ô»ó
2004-03   8340   ÀÌÈ¿Áß
2004-01   8340   ¼Û»óº´