"Matthew N. Dodd" wrote:
> > Agreed. I like what I see there. Maybe it is time to hoist something
> > like that into bus_subr.c
> Lets define exactly what we want before we start our charge.
> What should be printed?
> device ID
> attachment point
> resource reservation
> device additional
> When should it be printed?
> bootverbose levels?
Years ago I provided diffs to the kernel boot to report some probes Before
as well as after, so one could see which probe was about to hang, - more use
than which probe was last to pass. Idea was rejected as some thought it
was too verbose, but Nobody (me included) thought of having a
bootverbose levels switch to hang on it on. ... Nice Idea !
Some Computer mags reccomend MS-* users to keep a boot flop for Linux or BSD,
as we provide much more diagnostics than MS*, Before-probe-announcements
would make it more valuable still. Imagine if the more competent of the MS
crowd actually wanted to keep a FreeBSD boot floppy around :-)
Julian
Julian H. Stacey http://www.freebsd.org/~jhs/
Considering Linux ? Then also consider the 2000+ free packages for FreeBSD.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
