Date: Sun, 17 Dec 2000 22:45:38 -0800 From: Doug Barton <DougB@gorean.org> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: John Baldwin <jhb@FreeBSD.ORG>, current@FreeBSD.ORG Subject: Re: test/review: /dev/console logging patch Message-ID: <3A3DB292.B297D5C2@gorean.org> References: <25628.977121324@critter>
next in thread | previous in thread | raw e-mail | index | archive | help
Poul-Henning Kamp wrote:
>
> >>>
> >>> This patch is for the printf(9), log(9) & /dev/console stuff.
> >>> The result is that you can watch the output from /etc/rc in
> >>> your /var/log/messages.
> >>
> >> Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: Doing
> >> additional network setup:
> >> Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: ntpdate
> >> Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: ntpd
> >> Dec 17 13:00:27 <console.info> Master /boot/kernel/kernel: portmap
> >> Dec 17 13:00:27 <console.info> Master /boot/kernel/kernel: .
> >
> >The '.'s are simple and not too cluttery. Fixing the console to line buffer
> >what it sends to log(9) is a better fix, IMO.
>
> I specifically decided not to do this because I want to be able to
> see stuff like:
>
> echo -n "Press return to avoid disaster: " > /dev/console
> read < /dev/console
>
> Of course one could add timeouts and what's not, but then imagine
> the case of two programs writing on /dev/console at the same time...
*nod* I wasn't sure that the buffering was the best suggestion, which
is why I preferred making the messages from /etc/rc* more meaningful. :)
Doug
--
"The most difficult thing in the world is to know how to do a thing
and
to watch someone else do it wrong without comment."
-- Theodore H. White
Do YOU Yahoo!?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A3DB292.B297D5C2>