From owner-freebsd-hackers Sun Sep 12 20:54: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt014nb6.san.rr.com (dt014nb6.san.rr.com [24.30.129.182]) by hub.freebsd.org (Postfix) with ESMTP id B08C814D91 for ; Sun, 12 Sep 1999 20:54:05 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt014nb6.san.rr.com (8.9.3/8.8.8) with ESMTP id UAA09362; Sun, 12 Sep 1999 20:53:59 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37DC7556.82A77322@gorean.org> Date: Sun, 12 Sep 1999 20:53:58 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0912 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Rodney W. Grimes" Cc: Dag-Erling Smorgrav , hackers@freebsd.org Subject: Re: How to prevent motd including os info References: <199909130217.TAA31971@gndrsh.dnsmgr.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rodney W. Grimes" wrote: > It dawned on me what can be done. Look, we get all the kernel printf's > from the dmesg output saved in a buffer and pull that out later with > syslog, looks like we could just slip a pipe fitting into /dev/console > that copies all it's output into the mesgbuf as well, until we smack it > wth the ballpean and tell it to stop doing that (Either getty lanching the > login: on ttyv0 could cause this, or something at the end of /etc/rc). > > What do you think of that idea? I think that's a fine idea, and it's a lot cleaner than mine for a number of reasons. Completely beyond me to code, but very nice from the design standpoint. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message