It seems Justin T. Gibbs wrote: > >> In article <199903171103.naa13...@ceia.nordier.com> you wrote: > >> > Søren Schmidt wrote: > >> > > >> >> OK, easy enough, this is what I want to do: > >> >> > >> >> Boot from an ata disk on major# 30, device name "ad", plain and simple. > >> > > >> > I'd be inclined to handle this outside the boot code, by treating the > >> > passed in major# as describing the device rather than specifying > >> > the driver. > >> > >> Why not have the boot blocks pass in a device 'name' rather than a > >> major number. If the goal is to ditch major numbers entirely with > >> a properly working DEVFS, then using major numbers in the new boot > >> loader seems to be the wrong way to go. Until DEVFS is a reality, > >> the kernel will still need to perform a name to major number translation, > >> but it should be left up to the kernel. > > > >Because there's no way to work out a name either. > > If I explicitly say: > > 1:foobar(0,a)/kernel > > there certainly is a way to work out the name. Perhaps in the autoboot > case you'll have to guess, but it would be nice if the current boot > mechanism allowed user intervention as a way to boot a kernel with an > unknown bdev.
YES!! can we please have that ?? -Søren To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
