From owner-freebsd-current Sat Oct 13 7:10:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 87F6D37B401 for ; Sat, 13 Oct 2001 07:06:19 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 7BF0C14C2E; Sat, 13 Oct 2001 16:06:17 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Doug Barton Cc: freebsd-current@FreeBSD.ORG Subject: Re: Strike three, you're out References: <3BC67CBD.1DAAC031@DougBarton.net> <3BC7EA21.15F43811@DougBarton.net> From: Dag-Erling Smorgrav Date: 13 Oct 2001 16:06:16 +0200 In-Reply-To: <3BC7EA21.15F43811@DougBarton.net> Message-ID: Lines: 33 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Doug Barton writes: > Dag-Erling Smorgrav wrote: > > Remove UCONSOLE from kernel config. This has been discussed to death > > several times on the lists. > So your suggestion is just not to use that feature? I have to say that > I don't really like that answer. :) Is this something you think is just > impossible to fix? It's very difficult to fix. The problem is that printf() is used in the strangest parts of the deepest bowels of the kernel, but if a process grabs the console with TIOCCONS, printing something to the console causes the process that grabbed it to be woken up, which is a bad idea if, for instance, printf() was called from within mi_switch() (as is the case for those "microuptime() went backwards" messages). > My examination of what I could find in the lists > seems to indicate that this bug affects more than must xconsole, it also > presents problems during install. Yes, sysinstall uses TIOCCONS to redirect the console to ttyv1. > > Create /etc/host.conf (-CURRENT uses nsswitch.conf instead, and > > /etc/rc will bitch, but just ignore that) > *slaps forehead* D'oh! That makes total sense, thanks for the tip. > Warner, does this sound like something that should go into UPDATING? I'm wondering if actually the correct solution might be to have /etc/rc generate host.conf at boot time from the contents of nsswitch.conf. I'll see if I can cook up an awk script to do that. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message