Re: Booting on a hfs partition for oldworld
Ethan Benson wrote:
>
> > What exactly is happening with quik? Is it telling OF to read an ext2 partition
> > for the kernel? That doesn't make much sence, since OF doesn't know about
> > ext2. Does the kernel need to be on a hfs partition on the hard drive?
>
> quik has ext2 filesystem support built into itself, so happens is
> this:
>
> OF loads the boot block from the root partition, this boot block
> contains a blocklist for the quik second stage which is in
> /boot/second.b (on the ext2 root filesystem) once second stage is
> loaded its executed and reads the ext2 filesystem to find
> /etc/quik.conf which is parses to find the image name it should load
> (the kernel) normally /boot/vmlinux-2.2.18 or whatever. it then reads
> the kernel off the ext2 root filesystem and executes it and passes
> control to it. from which point on linux has taken over and brings
> the system up.
>
Great, Although, this makes me wonder. Why don't we just create a hfs partition
with a blessed system file like we do with the hfs boot disk?
> > I have tried it with one partition, the kernel on / and it still won't boot.
> > I've tried a /boot partition with no booting.
>
> quik expects /boot to NOT be its own partition, i think its possible
> to make it work that way but i don't reccommend it. the other thing i
> have observed is quik might not work with symlinks reliably, so i tell
> people to specify a full path to the real kernel image in
> /etc/quik.conf the kernel image should be in /boot and /boot should
> be on the / partition which is ext2fs.
Yeah, I found that out the hard way. The debbootstrap wouldn't even tell you
why it couldn't "make debian boot directly from the hard disk"... Although I
did find some docs that said quik needs the kernel on the same partition as
/etc. The symlink problem is new though, to me at least.
>
> > I am also getting conflicting information. In the debian install docs I need to
> > run "nvsetenv `ofpath /dev/sda3`" which would be correct for me, but ofpath
> > isn't even on the boot floppy! I had to chroot into /target and setup apt-get
> > to download and install yaboot.
>
> you have older boot floppies then, ofpath should be on 2.2.19 and new
> boot floppies. the base system that comes with 2.2.19 boot floppies
> also has the current yaboot package which has ofpath.
>
> > Can anyone help solve some of these problems?
>
> you using current documentation with obsolete boot floppies. download
> current boot floppies (2.2.19 or later).
>
> --
> Ethan Benson
> http://www.alaska.net/~erbenson/
>
Great, I just mirrored the archive a week ago. When did this new set go in?
Will it actually let you make a boot floppy now?
I have had to go through the process of hfs-boot-floppy => debian-install-root
=> mount drives on /target => chroot /target..... to be able to work in the
system.
If it won't make a boot floppy for me, how do I make one? I noticed the kernel
is 2.5 MB in my /boot after the initial install, so I won't be able to use that
one... maybe the one on the hfs boot floppy would work... Any ideas?
Mike
Reply to: