Subject: Re: partition bookkeeping
To: Greywolf <greywolf@starwolf.com>
From: Bill Studenmund <wrstuden@nas.nasa.gov>
List: tech-kern
Date: 09/22/1999 16:15:12
On Wed, 22 Sep 1999, Greywolf wrote:
> Are we going to continue dumbing down this thing, or what? I agree
> that we will need a /dev/disk or something similar directory, but
> I do NOT think that we should go further down than that -- it's just too
> cumbersome. /dev/$BUSTYPE/$PERIPHTYPE/cXtXpX is just fscking
> ludicrous. Not to mention, hard to type repetitively (and I've
> had to do that).
I agree fully!
> If you're worried about devices switching locations, WIRE DOWN YOUR
> DAMNED DEVICES and be *done* with it. [Profuse apologies here
> for assuming that everyone uses source -- I'm sure that this is
> a patent lie; nonetheless, I find it hard to believe that there
> are that many people incapable of compiling a new kernel for reasons
> of disk space.]
>
> As far as the root device goes, using Ignatios' idea of mounting /kern and
> referencing /kern/rootdev as a valid device makes a WHOLE lot of sense.
> You'll at least be able to put yourself back together without too much
> grief.
The only thing I found was that /kern/rrootdev (which'd be needed for
fsck'ing) didn't seem to always show up for me. I'm not sure why..
> Should we (do we?) have a peripheral scanner which will configure
> a kernel with wired down devices followed by the generic devices
> and (optionally) attempt a rebuild?
>
> If we don't, is someone already working on it?
>
> If nobody's working on it, I'll be glad to take a stab at it...
Someone was working on it, but I don't know how it's doing. I think you're
right that we need it. :-)
Take care,
Bill