boot disks 2.3.5

red: use the install floppies to create a new root floppy which contains the module required marked to be loaded, and then go into the install sequence? If so, then how does one achieve this? Many thanks for your time - as I said, things are looking very good indeed. Matthew -- Matthew Sackman Nottin

Re: boot disks 2.3.5

wrote: > On Fri, Jun 15, 2001 at 10:00:28PM +0100, Matthew Sackman wrote: > > > However, one thing comes to mind: if one is installing to, say, a hardware RAID > > array, which appears to linux as a single SCSI drive, but requires a module > > loading, then how do you do

boot floppies drivers disk(s)

ib/modules/[kernel-version]. This is fine, but does the drivers disk have an FS of it's own, or should I copy the tar.gz of the modules directly to the disk with a dd command? Thank you in advance, and my apologies if this is not quite the right mailing list. Matthew -- Matthew Sackman Nott

Re: boot floppies drivers disk(s)

On Sat, Sep 15, 2001 at 03:42:33AM -0800, Ethan Benson wrote: > On Fri, Sep 14, 2001 at 11:20:50PM +0100, Matthew Sackman wrote: > > Hi Guys, > > > > I'm customising the bootfloppies 3.0.13 1.44 images for my own installation > > and have replaced the kernel on

Re: boot floppies drivers disk(s)

On Sat, Sep 15, 2001 at 03:35:13PM -0800, Ethan Benson wrote: > On Sat, Sep 15, 2001 at 11:55:23AM +0100, Matthew Sackman wrote: > > On Sat, Sep 15, 2001 at 03:42:33AM -0800, Ethan Benson wrote: > > > > > > the split images are in a special format, use the floppy_spli

Re: Capturing install screenshots

ve system). You just chroot it as normal. Get the install disks, work out which disk contains the binaries, and hunt around until you actually find the one that launches the install sequence - if you do it from an xterm then you can snapshot as much