Re: Problem during the reboot phase (netinst mage 2004-05-16)

[Richard Hirst <rhirst@levanta.com>]

On Wed, May 19, 2004 at 10:13:43AM +0200, Joel Soete wrote:
> 
> > -- Original Message --
> > Date: Tue, 18 May 2004 18:09:25 +0100
> > From: Matthew Wilcox <willy@debian.org>
> > To: Joel Soete <jsoe0708@tiscali.be>
> > Cc: ste@stex.opensolution.net, debian-hppa@lists.debian.org
> > Subject: Re: Problem during the reboot phase (netinst mage 2004-05-16)
> > 
> > 
> > On Tue, May 18, 2004 at 09:21:23AM +0200, Joel Soete wrote:
> > > Just replace '2/boot/vmlinux' by the actual '2/vmlinux-2.4.26-64-smp'
> in
> > > palo.conf and re-run palo so that the boot cmd line will be updated and
> > the
> > > auto boot on works fine
> > 
> > Umm.  Palo follows symlinks,
> Yes, but according to Stex report: "...I found out tonight is that there
> is no simbolic link [...] /vmlinux
> which points to /boot/vmlinux-..."  it missed :(

symlinks are in /boot for hppa, so you should see a symlink
/boot/vmlinux pointing to /boot/vmlinux-<version>.

> > so 2/vmlinux is what we should have,
> > not 2/boot/vmlinux or 2/vmlinux-2.4.26-64-smp.
> > 
> Yes depending if we implement or not a deicated fs for /boot ?

If /boot is a dedicated fs, then use 2/vmlinux (assuming boot
is partition 2).  If /boot is part of the root fs, use
1/boot/vmlinux (assuming / is partition 1).

Richard