[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Root symlink to /boot/vmlinuz

Hi there!

There was an similar thread on debian-user some days ago:

On Sat, Mar 02, 2002 at 12:10:39PM -0500, dman wrote:
> On Fri, Mar 01, 2002 at 08:29:47PM -0800, Craig Dickson wrote:
> | Dumb question: why does Debian like to have a symlink, /vmlinuz,
> | pointing to the kernel image in /boot? Does some program depend on being
> | able to find the kernel at /vmlinuz? Would something break if I simply
> | deleted this symlink?
* snipped *
> Remove the existing symlink and create /etc/kernel-img.conf with the
> following contents :
> ~~~~~~~~~
> # create symbolic links in / ?
> do_symlinks = No
> ~~~~~~~~~
> to prevent kernel-image packages from (re)creating that symlink every
> time.
> -D

On my system (alpha, LX164 Board, Alpha-Bios) things are somewhat

I'v created boot floppies potato/alpha (2.2r4) and then I've installed
the basic system directly from the Internet.  This worked out good, but:

A package I dont know creates this symlink:
...  Dec 10 21:28 /vmlinuz -> boot/vmlinuz-2.2.18pre21-generic

This is WRONG, since df -T:
/dev/sda1    msdos       11208      3812      7396  34% /boot

The long filename wasn't long any more!  As far as I know the bios of
this machine _needs_ a msdos fs to boot the kernel.  The bios tries to
look like NT 3.5 :( As a result I am only able to use 8.3 names for
different kernels.  Where to fix such a problem in the distrib?

During installation I watched another error: some "autodection"
installs EB164 as milo.  That doesnt work, have to copy LX164 manually.

Later on I watched an _enormous_ clock drift. As suggested elsewhere
on this list I installed a new one 2.2.19.  I was in an hurry and
doesn't find kernel-package with dselect.  Handrolling the new kernel
shows some "strange" behaviour:
/usr/src/kernel-source-2.2.19/{vmlinux,System.map} instead of
arch/alpha/boot, kernel not zipped.  Not really a problem but: Is it
neccessary to use kernel-package? One more manual to read...

The other side: The update to 2.2r5 shows no problems, a great work
was done by debian.org.  How can I contribute?  Things are far from
running smooth on this machine.  Internet access is provided through
an other box, to cut off problems I should debianize it too.


Reply to: