Bug 1635 - MILO doesn't follow symlinks in any useful way.
MILO doesn't follow symlinks in any useful way.
Product: Red Hat Linux
Classification: Retired
Component: distribution (Show other bugs)
alpha Linux
high Severity high
: ---
: ---
Assigned To: Cristian Gafton
Depends On:
  Show dependency treegraph
Reported: 1999-03-19 20:34 EST by Peter Jones
Modified: 2008-05-01 11:37 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-03-21 09:42:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Peter Jones 1999-03-19 20:34:01 EST
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 09:42:59 EST
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 10:56:59 EDT
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*

Note You need to log in before you can comment on or make changes to this bug.