Subject: Re: DAD verbosity
To: Chris G. Demetriou <firstname.lastname@example.org>
From: Darren Reed <email@example.com>
Date: 02/18/2000 02:59:30
In some email I received from Chris G. Demetriou, sie wrote:
> take a look at the way the autoconfiguration code works, when printing
> out info for an attached device.
> to print a single "fooM at barN: information here" line, part of
> that's printed by the generic autoconfig code, part is printed by the
> parent bus code, part by the child device code.
> you'd think you could make it simpler, e.g. have the "fooM at BarN" be
> printed by the generic code, then have the child code print out "fooM:
> information here", etc. as needed, but then what do you do with the
> "FOOBARBAZ at BarN not configured" messages (where you _have_ to have
> the parent bus print something), and i'm sure you could fix _that_
> some way, but you'd have some other issue to deal with.
This seems messy to me. Would it be worthwhile adding a buffer,
somewhere, which various parts could add information to and was
printed out once the `configure' was complete ? (I'm guessing,
without RTFS'ing, that the function which prints out "sd0" also
prints out the "\n").