Re: [Cooker] DrakX / LILO / MBR

2001-06-06 Thread David Eastcott
On Wednesday 06 June 2001 10:56, you wrote: > Michael Brown <[EMAIL PROTECTED]> writes: > > Forget it if you want; it's just an option that I came across a need for > > yesterday (for boring reasons that I won't go in to), and I thought I may > > as well contribute the patch that implements it, si

Re: [Cooker] DrakX / LILO / MBR

2001-06-06 Thread Michael Brown
On 6 Jun 2001, François Pons wrote: > > Forget it if you want; it's just an option that I came across a need for > > yesterday (for boring reasons that I won't go in to), and I thought I may > > as well contribute the patch that implements it, since it's such a simple > > change. > We will add a o

Re: [Cooker] DrakX / LILO / MBR

2001-06-06 Thread François Pons
Michael Brown <[EMAIL PROTECTED]> writes: > Forget it if you want; it's just an option that I came across a need for > yesterday (for boring reasons that I won't go in to), and I thought I may > as well contribute the patch that implements it, since it's such a simple > change. We will add a onM

Re: [Cooker] DrakX / LILO / MBR

2001-06-06 Thread Michael Brown
On Tue, 5 Jun 2001, Pixel wrote: > > Is there any way to tell DrakX's auto-install mode to install LILO onto > > /dev/hda1 instead of /dev/hda ? I've looked through the code and the > > nearest option I can find seems to be > well, you could use > bootloader => { boot => 'hda1' }, Not quit

RE: [Cooker] DrakX / LILO / MBR

2001-06-06 Thread Eaon
> Not possible generally as NT partition has to be formatted fat32. > > François. > NT? FAT32? Um, no? :-) NT can't read FAT32. FAT16 only, or NTFS. Win2K can do FAT32, but NT can't.

Re: [Cooker] DrakX / LILO / MBR

2001-06-06 Thread François Pons
Michael Brown <[EMAIL PROTECTED]> writes: > You can install lilo to /dev/hda1 (or other partition) instead of /dev/hda > and then a 'standard' DOS MBR will happily boot lilo if the lilo partition > is marked active. (Tried and tested). At the moment, DrakX will always > overwrite a DOS MBR. Th

Re: [Cooker] DrakX / LILO / MBR

2001-06-06 Thread Pixel
Michael Brown <[EMAIL PROTECTED]> writes: > Is there any way to tell DrakX's auto-install mode to install LILO onto > /dev/hda1 instead of /dev/hda ? I've looked through the code and the > nearest option I can find seems to be well, you could use bootloader => { boot => 'hda1' }, [...]

Re: [Cooker] DrakX / LILO / MBR

2001-06-06 Thread Michael Brown
On 6 Jun 2001, François Pons wrote: > > > >Is there any way to tell DrakX's auto-install mode to install LILO onto > > > >/dev/hda1 instead of /dev/hda ? I've looked through the code and the > > > >nearest option I can find seems to be > > > >$o -> {bootloader}{crushMbr} > > > >which, if set to 1

Re: [Cooker] DrakX / LILO / MBR

2001-06-06 Thread François Pons
Michael Brown <[EMAIL PROTECTED]> writes: > > >Is there any way to tell DrakX's auto-install mode to install LILO onto > > >/dev/hda1 instead of /dev/hda ? I've looked through the code and the > > >nearest option I can find seems to be > > >$o -> {bootloader}{crushMbr} > > >which, if set to 1, c

Re: [Cooker] DrakX / LILO / MBR

2001-06-05 Thread Michael Brown
On Tue, 5 Jun 2001, Blue Lizard wrote: > >Is there any way to tell DrakX's auto-install mode to install LILO onto > >/dev/hda1 instead of /dev/hda ? I've looked through the code and the > >nearest option I can find seems to be > >$o -> {bootloader}{crushMbr} > >which, if set to 1, causes LILO to

Re: [Cooker] DrakX / LILO / MBR

2001-06-05 Thread Blue Lizard
Michael Brown wrote: >Is there any way to tell DrakX's auto-install mode to install LILO onto >/dev/hda1 instead of /dev/hda ? I've looked through the code and the >nearest option I can find seems to be > >$o -> {bootloader}{crushMbr} > >which, if set to 1, causes LILO to install onto /dev/hda b

[Cooker] DrakX / LILO / MBR

2001-06-05 Thread Michael Brown
Is there any way to tell DrakX's auto-install mode to install LILO onto /dev/hda1 instead of /dev/hda ? I've looked through the code and the nearest option I can find seems to be $o -> {bootloader}{crushMbr} which, if set to 1, causes LILO to install onto /dev/hda but if set to 0 causes LILO to