From owner-freebsd-current Sun Dec 17 22:49:30 2000 From owner-freebsd-current@FreeBSD.ORG Sun Dec 17 22:49:27 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id ED2B137B400; Sun, 17 Dec 2000 22:49:26 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eBI6nNf26102; Mon, 18 Dec 2000 07:49:23 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Doug Barton Cc: John Baldwin , current@FreeBSD.ORG Subject: Re: test/review: /dev/console logging patch In-Reply-To: Your message of "Sun, 17 Dec 2000 22:45:38 PST." <3A3DB292.B297D5C2@gorean.org> Date: Mon, 18 Dec 2000 07:49:23 +0100 Message-ID: <26100.977122163@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A3DB292.B297D5C2@gorean.org>, Doug Barton writes: >> >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. :) Just for the record: There is no support for green "OK" messages in my patch :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message