Re: LILO 21.6-2
>>"Brian" == Brian May <bam@debian.org> writes:
Brian> Somebody else recently said that kernel-image packages no longer
Brian> maintain these symlinks (at least that was my understanding).
Brian> (or perhaps it is now a user configurable item?)
Why is it that posting to a public forum is seen as a superior
method compared to actually reading manual pages? Here are excerpts
from two man pages that show the extents of the configurability of
image locations (one of these is lrevant to compile time, the other
to install time configurations).
manoj
======================================================================
kernel-img.conf (5):
image_in_boot:
Set to Yes if you want the kernel image vmlinuz in
/boot rather than the default /. defaults to No.
do_symlink
By default, the kernel image post installation
script shall create or update the /vmlinuz and
/vmlinuz.old symbolic links. This is true if a
/vmlinuz link already exists, however, in absence
of /vmlinuz, the script looks to see if this con-
figuration file exists. If it does not, the config-
uration scripts asks the user whether to create the
symbolic link, and stashes the answer in a newly
created /etc/kernel-img.conf. If the configuration
file already exists, and if this option is set to
No, no symbolic link is ever created. This for peo-
ple who have other means of booting their machines,
and do not like the symbolic links cluttering up
their / directory. Defaults to Yes.
no_symlink
Whether to use symlinks to the image file. Mutu-
ally exclusive to reverse_symlink. Can be used
with image_in_boot. If set to Yes, the image is
placed in vmlinuz (instead of /boot/vmlinuz-
X.X.XX). The old vmlinuz is moved to vmlinuz.old
unconditionally. (Normally, that is only done if
the version of the new image differs from the old
one). This restricts you to two images, unless you
take additional action and save copies of older
images. This is for people who have boot on a sys-
tem that does not use symbolic links (and say, they
use loadlin as a boot loader). This is a Hack.
Defaults to No.
reverse_symlink
Whether to use reverse symlinks (that is, the real
file is the one without the version number, and the
number version is the link) to the image file.
Mutually exclusive to no_symlink. Can be used with
image_in_boot. Just like no_symlink, except that
the /boot/vmlinuz-X.XX is symbolic linked to the
real new image, vmlinuz. This too restricts you to
just two images unless father action is taken. The
older symlinks are left dangling. This is for peo-
ple with boot on umsdos, and who can't see the link
in dos, but do want to know the image version when
in Linux. This is a Hack. Defaults to No.
image_dest
If you want the symbolic link (or image, if
move_image is set) to be stored in elsewhere than /
set this variable to the dir where you want the
symbolic link. Please note that this is not a
Boolean variable. This may be of help to loadlin
users, who may set both this and move_image
Defaults to / This can be used in conjunction with
all above options except image_in_boot, which would
not make sense. (If both image_dest and
image_in_boot are set, image_in_boot overrides).
move_image
Instead of creating symbolic links to (or, is
reverse_symlinks is set, from) image_dest, the
image is moved from its location in /boot into
image_dest. If reverse_symlinks is set, /boot
shall contain a symbolic link to the actual image.
This option can be useful to people using loadlin,
who may need the image to be moved to a different,
dos partition. This variable is unset by default.
do_bootloader
If set to NO, this prevents the postinst from run-
ning the boot loader. The user may still be asked
to create a floppy, unless do_bootfloppy is also
set to NO. Defaults to Yes.
relative_links
If set to yes, the kernel image postinst script
shall go to extra ordinary lengths to ensure that
the symbolic links are relative. Normally, the sym-
bolic links are relative when it is easily deter-
minable that relative links shall work. efaults to
No.
======================================================================
kernel-pkg.conf (5):
no_symlink
Whether to use symlinks to the image file. Can be
over-ridden by the environment variable NO_SYMLINK
Mutualy exclusive to reverse_symlink. Can be used
with image_in_boot. The image is placed in vmlinuz
(instead of /boot/vmlinuz-X.X.XX). The old vmlinuz
is moved to vmlinuz.old unconditionally. (Normally,
that is only done if the version of the new image
differes from the old one). This restricts you to
two images, unless you take additional action and
save copies of older images. This is for people who
have boot on a system that does not use symbolic
links (and say, they use loadlin as a boot loader).
This is a Hack. Defaults to undefined (optional)
reverse_symlink
Whether to use reverse symlinks (that is, the real
file is the one without the version number, and the
numberd version is the link) to the image file. Can
be over-ridden by the environment variable
REVERSE_SYMLINK Mutualy exclusive to no_symlink.
Can be used with image_in_boot. Just like no_sym-
link, except that the /boot/vmlinuz-X.XX is sym
linked to the real new image, vmlinuz. This too
restricts you to just two images unless futher
action is taken. The older symlinks are left dan-
gling. This is for people with boot on umsdos, and
who can't see the link in dos, but do want to know
the image version when in Linux. This is a Hack.
Defaults to undefined (optional)
--
For my son, Robert, this is proving to be the high-point of his
entire life to date. He has had his pajamas on for two, maybe three
days now. He has the sense of joyful independence a 5-year-old child
gets when he suddenly realizes that he could be operating an
acetylene torch in the coat closet and neither parent [because of the
flu] would have the strength to object. He has been foraging for his
own food, which means his diet consists entirely of "food" substances
which are advertised only on Saturday-morning cartoon shows;
substances that are the color of jukebox lights and that, for legal
reasons, have their names spelled wrong, as in New Creemy
Chok-'n'-Cheez Lumps o' Froot ("part of this complete
breakfast"). Dave Barry, "Molecular Homicide"
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Reply to: