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

À̹®Èì   
   Á¶È¸ 5053   Ãßõ 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 4577/5636
2014-05   4729803   Á¤ÀºÁØ1
2015-12   1275958   ¹é¸Þ°¡
2019-06   2935   ¶¥ºÎÀÚ
2018-07   2935   ¼ÛÁÖȯ
2019-05   2935   ¹Ý¼º¸¸
2020-07   2935   ÄËƲ¸®12
2017-10   2935   Æ丣¼¼¿ì½º
2016-02   2935   ÆíÇѼ¼»ó
2021-02   2935   ½Å»ç¿ä
2021-02   2935   ÇູÇϼ¼
2020-10   2934   galaxyfamily
2018-11   2934   ¸ð½º¿ùµå
2020-07   2934   »õ·Î¿îÂ÷¿ø
2018-11   2934   ½ÅÀº¿Ö
2023-10   2934   ¹ÎÈ£¾ç
2019-06   2934   ½´ÆÛÂ÷Àú
2023-10   2934   ±èȲÁß
2019-03   2934   ±èÁ¦¿¬
2017-05   2934   ¶óÈ¥
2017-10   2934   Àü»êoa
2020-11   2934   °¡À»ÇÞ»ì71
2015-01   2934   ±èÈÆ1