Peter Wemm wrote:
>
> Lars Eggert wrote:
> > I'm playing with the networking code; by that time, the disks should have
> > been probed.
>
> Hmm.. driver or stack? If it is a driver, then why not just kldload it?
Stack.
> If you do a boot -v, you should see something like: 'creating disk ad0'
> and/or 'wd0' on RELENG_4 boxes, that is after interrupts are enabled and
> the minidisk layer can get to the disk partition info. It is probably too
> late for network stack stuff by then though as the stacks are initialized
> earlier. See sys/kernel.h for the SYSINIT ordering.
>
> Have a look at kern/kern_shutdown.c, setdumpdev(). Note the call to
> devsw->d_psize() - that gets the number of blocks in the partition.
> If you boot to multi-user you might be able to get these magic values
> and hardwire the bootstrap to set these values and dumpdev.
Ah, yes, I'll try that.
> However... there is a BIG difference between RELENG_4 and -current in this
> area right how. In RELENG_4, dev_t (and hence dumpdev) is a simple integer
> for the minor/major number.
I'm using 4.2-RELEASE+KAME, actually, since I depend on recent KAME/ALTQ
changes, which aren't in -STABLE or -CURRENT. (Side note: AFAIK KAME in
RELENG_4/CURRENT is still a version from 7/2000, and ALTQ isn't merged...
will that be updated anytime soon?)
> Seriously though, please thoroughly check out the KLD module option and see
> if you can get that to work somehow.
Unfortunately not an option...
--
Lars Eggert <[EMAIL PROTECTED]> Information Sciences Institute
http://www.isi.edu/larse/ University of Southern California
S/MIME Cryptographic Signature
