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

Re: 2.4 kernel



Wow. Thanks. So the file format is basically like that of lilo or at least
close to it?

To set MacOS up with lilo, it would something like this?

other = /dev/hda1   
  table = /dev/hda
  label = MacOS


On Mon, 9 Oct 2000, Ethan Benson wrote:

> On Tue, Oct 10, 2000 at 12:09:25AM +0000, Cameron Berkenpas wrote:
> > Not really, quik != bootx
> > 
> > Where can I find some docs on quik? Does it allow me to boot without
> > having macos? I'd love to remove  MacOS, as it crashes more than windows.
> 
> yes quik does not require macos, it is a real OpenFirmware bootloader.
> 
> to configure quik setup a /etc/quik.conf something like this:
> 
> timeout=20
> partition=2
> 
> image=/boot/vmlinux-2.2.17
> 	label=linux
> 	root=/dev/hda2
> 	read-only
> 
> image=/boot/vmlinux-2.4.0-test9
> 	label=test
> 	root=/dev/hda2
> 	read-only
> 
> do not point image= entries at symlinks, this does not work reliably
> with quik it appears (however all my experience is second hand, over
> irc, email etc, i have no oldworld machines to work with)
> 
> partition= should be the partition number of your root partition,
> basically the number in the /dev filename, ie: /dev/hda3 == partition=3. 
> 
> after you have your /etc/quik.conf run /sbin/quik then change the
> OpenFirmware boot-device variable to your hard disk, you can find this
> out like so:
> 
> ofpath /dev/hda
> 
> add a 0 to the end of the output from ofpath, so say you got /pci/blah/@0:
> you would use /pci/blah/@0:0 
> 
> ofpath is in the yaboot package, you will need the one out of
> proposed-updates.
> 
> nvsetenv works like so
> 
> nvsetenv boot-device '/pci/blah/@0:0'
> 
> reboot your machine and pray to the Holy Penguin that it will work ;-)
> (oldworld OF is rather broken and quik suffers from this) 
> 
> note however that many oldworld machines cannot display OpenFirmware
> console on your monitor, so you have to use a serial terminal to see
> the quik boot: prompt.  if you machine is capable of displaying to the
> monitor you can *usually* enable this by running:
> 
> nvsetenv output-device screen
> nvsetenv input-device keyboard
> 
> input-device should always work, so you could probably enter quik
> commands blind if need be, im not sure on that.  some machines also
> don't have a valid screen alias so you need to find the real OF path
> to your video hardware, i can't really help you there.  (wonder around
> /proc/device-tree/) 
> 
> if all works well and you are satisfied that quik will work to your
> satisfaction you can delete all your macos partitions along with all
> those useless driver partitions littering up the partition table.  
> 
> -- 
> Ethan Benson
> http://www.alaska.net/~erbenson/
> 



Reply to: