Re: /boot

[Grant Grundler <grundler@parisc-linux.org>]

On Sun, Feb 27, 2005 at 12:00:25PM -0500, Harry Cochran wrote:
> Am I right that with /dev/sda1 mounted as /boot, if I am at say /var a
> cd /boot should go to the /dev/sda1 partition? If so, that /boot is empty as
> shown above.
> 
> Now for the bad news ... cd / and then cd boot which should bring me to the
> boot directory under the root is also empty.

No - "mount /dev/sda1 /boot" will overlay and hide the original contents
on /dev/sda3.

That's why we keep telling you to "mount /dev/sda1 /mnt" and then copy
the /boot contents to /mnt.

> Arrrg. Will an apt-get install
> kernel-image-2.6.8-2-32-smp reload /dev/sda1 with the files I need to boot?

Probably not. But "dpkg -i kernel-image-2.6.8-2-32-smp.deb" will.
(just get the name of the .deb file right)

> Assuming I can get a loadable kernel and initrd.img back on the /boot on
> /dev/sda1/, I guess I don't need --update-partitioned /dev/sda in palo.conf.
> Can you please confirm that?

You do need --update-partitioned /dev/sda in palo.conf.

> Also I did cd /var and then tried umount /boot and got "device is busy"
> still. What am I doing wrong?

It sounds like /boot is the original directory on /dev/sda3.
No one uses /boot for anything *except* palo to load vmlinux/initrd.

grant