Bug 1635

Summary: MILO doesn't follow symlinks in any useful way.
Product: [Retired] Red Hat Linux Reporter: Peter Jones <pjones>
Component: distributionAssignee: Cristian Gafton <gafton>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 6.0CC: jbj, msw
Target Milestone: ---   
Target Release: ---   
Hardware: alpha   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-03-21 14:42:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Peter Jones 1999-03-20 01:34:01 UTC
The default kernel path (so far) is /boot/vmlinuz-2.2.3-5 ,
and there's a symlink to /boot/vmlinuz .   MILO does really
bad things if you point it at /boot/vmlinuz ;  We probably
need to have vmlinuz be a real file (when we install a new
version, make the old one vmlinuz.old and _copy_ the new one
to vmlinuz) and fix the documentation to reflect this.

Comment 1 Cristian Gafton 1999-03-21 14:42:59 UTC
No way, the proposed vmlinuz handling is a disaster waiting to happen
as far as packaging goes.

I propose to get rid of all references to /boopt/vmlinuz and tell
people to use the real names. If anybody likes vmlinuz, he/she can do
that on their own.

Comment 2 mchampig 1999-10-29 14:56:59 UTC
Another reason to dump the use of /boot/vmlinuz is that aboot
can't follow symlinks either from SRM. I've seen this bite quite
a few people. The safest is to use the full pathname under *all*