Date: Sat, 16 Oct 2004 20:24:03 -0500 From: "Conrad J. Sabatier" <conrads@cox.net> To: "Poul-Henning Kamp" <phk@phk.freebsd.dk> Cc: freebsd-current@freebsd.org Subject: Re: no echo console Message-ID: <20041016202403.7928c26d@dolphin.local.net> In-Reply-To: <19260.1097963444@critter.freebsd.dk> References: <16753.38774.621295.6356@ran.psg.com> <19260.1097963444@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 16 Oct 2004 23:50:44 +0200, "Poul-Henning Kamp" <phk@phk.freebsd.dk> wrote: > In message <16753.38774.621295.6356@ran.psg.com>, Randy Bush writes: > >> Does it depend on which shell you use for single-user mode ? > > > >uh, make the test you want clear, plz. i am fried today. > > > >root's shell is /usr/local/bin/bash (no comments, please:-) > > > >i am seeing the problem as root in multiluser. i don't spend > >much time in single abuser, so can't say. > > Ahh, that's different then. > > I'll hunt this one down tomorrow. I'm quite certain now that it's occurring after every run of portupgrade. I don't get the same if I cd to a port's dir and do a build; only if I use portupgrade. Weird. I have no idea what's going on. -- Conrad J. Sabatier <conrads@cox.net> -- "In Unix veritas"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041016202403.7928c26d>