[vox] Re: Shwaine's custom Boot Disks
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[vox] Re: Shwaine's custom Boot Disks
I'm following the Linux Bootdisk HOWTO. The HOWTO gives a couple
of options at some points, so here's what I did at those points.
the LILO option in it to install the kernel. I used a ramdisk in
build the root file system. I also custom-built the kernel and fine-
the root file system so both can fit on a 1600k formatted floppy
/dev/fd0u1600). The problem is not with the booting. It boots just
just always says "RAMDISK: Couldn't find valid ramdisk image at 397"
(397 is the KERNEL_BLOCKS variable mentioned in the HOWTO) once
it gets to the point of trying to load the root system. I'm wondering
problem is using 1600k formatting instead of 1440k. I haven't yet tried
specifying the disk geometry in LILO to check that. I really don't have
many other files I can pare down to get it to fit into 1440k. Oh,
is a Slackware -current (downloaded June 18th) system using the
2.2.19 kernel. I have scripts to create the disk that I could post, but
they are rather long.
> On Sat, 23 Jun 2001, ME wrote:
> > On Fri, 22 Jun 2001, Shwaine wrote:
> > I meanwhile will be retreating to day 3 of my battle with homegrown
> > root/boot disks, pondering why the howto instructions work for two
> > seperate disks but blow up like a big stink bomb when using one
> > disk.
> Asking some obvious questions here:
> If you are making a single boot disk installation system, I assume you
> have a root.bin file image saved on the same boot floppy as the
> a copy of the kernel and a way to load the kernel on that floppy. Yes?
> You should probably use a minix filesystem for your root.bin image
> can be hady to use the loopback interface to modify the image. You did
> Last, the readmes often say to write the root.bin image directly
> floppy device (/dev/fd0). Obviously, if this was done, it would
> the boot sector and first parts of the booting floppy\ and render it
> useless. For this reason the root.bin should be save on the floppy
> a file, and you should copmpress it with something like gzip before
> storing it on the floppy.
> My recollection of making custom boot floppies for different distros
> bit hazy. If you could refer to the document you are using, I might be
> able to offer some more suggestions on things to check.
> I seemed to recall you made the minix filesystem as an image and
> all you wnated in the root fs on that image. Then you compress
> with gzip (dont know if they ever included bzip2 supprt). If gzip
> try gzip --best filename. Then you rename the file to root.zip
and copy to
> the same floppy as the kernel disk *but* as a file, not written
> to the device. Then a command line boot arguement handed to the
> linux kernel may include root=root.bin (if LOADLIN.EXE is used, for
> example.) This should cause the preload of the root.bin file with the
> kernel and avoid it asking you to insert the root.bin floppy.
> Now-a-days, it is becoming increasingly difficult to make universal
> floppies with linux and all of the modules needed, and a root filesystem
> all on one floppy. It is however, still posible to compile your
> with only the minimal options needed by you, no modules, and still
> to et a minimal root filesystem in image format all on one floppy. :-)
> Ages ago I made custome debian boot floppes for 2.0 and 2.2 kernels
> network installation with pcmcia cards not supported under the
> boot floppies, but supported with the latest pcmcia-cs. Now-a-days,
> a custom bootable boot CD is the better solution. :-)
> One of these days, I might make a dual boot linx/dos CD-ROM if I feel
> tremendiously insane.
> Anyway, more info on your issues would be helpful...
Shwaine the Wandering Arch of Malevolence