As a few people on l-k know, I run my own custom Linux install on my
machines. I followed the same route as a few others, started out with a
Slackware install (version 3.4 was the last I installed) and gradually
recompiled everything as new versions came out, mutated verious scripts,
eventually I had a system that did not have one file in common with the
I've even come up with a crude install process that lets me take my base
installation and copy onto a new machine using NFS.
Coming from the Slackware world I made myself a set of boot and root
floppies. The boot one gets a custom kernel tailored for the machine that
I'm going to install on, the root is pretty generic, with just enough
tools to partition, format, mount, and copy.
Also following in Slackware's footsteps, I use a compressed ramdisk on my
root floppy. This has worked just fine until today.
I got a new Thinkpad, it doesn't have an internal floppy drive. Instead
it has a USB floppy. It can boot from the floppy just fine, I can get my
custom boot disk's kernel loaded. But when it comes to loading the root
image I run into trouble.
I've made a lot of headway today, but it has taken me 4 hours to get this
far and it is almost dinner time, so I figured I'd post here before I beat
my head too much more.
Obviously (but not to me initally) the USB floppy isn't a real floppy
controlled by a floppy controller, but it is a USB mass storage device.
Got the kernel seeing that much, finds a SCSI0 and has the floppy
attatched to it. Because it doesn't have a partition table, I'm assuming
the kernel is going to want me to mount /dev/sda. But I'm not certain,
cause I've never used a laptop running Linux let alone messed with a USB
floppy, so I'm feeling around rather blindly trying to pass the right
root= to the kernel in an attempt to get something mounted.
But then I run into more trouble, cause the normal parameters for mounting
a gziped root image from a floppy don't work with SCSI devices. For one
it won't wait for me to flop disks. I have fast fingers so that isn't a
problem, I can change disks while the kernel is booting. But I have a
feeling I'm barking up the wrong tree here.
I've seen the initrd option in the kernel config along with the other RAM
disk stuff. I have a feeling that is the path I'm going to need to go
down, but I've never delt with it before (I know Linus is gung-ho about
initrd from posts I've seen by him here). So I figure I'd better learn
about it sooner or later.
So anyway, this isn't super kernel releated, but I figured it was enough
that a post here wouldn't hurt too much (just this one has gone on longer
than I initially intended). I'm just looking for any pointers or ideas,
to what has become an interesting problem to me.
Thanks a lot,
-- Two penguins were walking on an iceberg. The first penguin said to the second, "you look like you are wearing a tuxedo." The second penguin said, "I might be..." --David Lynch, Twin Peaks
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Sep 30 2001 - 21:01:10 EST