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

À̹®Èì   
   Á¶È¸ 5418   Ãßõ 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 2988/5710
2015-12   1695509   ¹é¸Þ°¡
2014-05   5161225   Á¤ÀºÁØ1
2005-07   5423   ¹ÚÁø±¹
2021-03   5423   ÇູÇϼ¼
2019-07   5423   ¹Ì³î»ç¶û
2008-08   5423   ±èÈ¿¼ö
2007-04   5423   ³²°æ¸²
2006-04   5423   ÀÌ»ó·æ
2009-01   5423   ±è¿µ¼ö
2011-10   5423   ¹æoÈ¿o¹®
2006-02   5423   ±èº´»ó
2008-12   5423   Á¶ÀçÇö
2015-08   5423   ½º¹«ÇÁ
2006-09   5423   ¼­¿øÅÃ
2016-09   5423   2CPUÃÖÁÖÈñ
2008-07   5423   ±èÀºÈ£
2012-07   5423   ÀÌÁöÆ÷Åä
2019-09   5423   °£Àå°ÔÀå
2012-10   5423   ƼŰ
2006-06   5423   ÀÌ»ó¿­
2009-01   5423   À̼ºÁØ
2006-09   5423   ¿ì½Â¿±