From owner-freebsd-alpha Thu Mar 22 14:41:16 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 0D11737B719 for ; Thu, 22 Mar 2001 14:41:14 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2MMcxs02824; Thu, 22 Mar 2001 14:38:59 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103222238.f2MMcxs02824@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: 4.3beta status report In-reply-to: Your message of "Thu, 22 Mar 2001 17:33:54 EST." <15034.32210.922514.879843@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Mar 2001 14:38:58 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Question, why is all of a sudden a problem now, and it wasn't in 4.2? > > It was a problem in 4.2 apparently. Just not in 4.1 or prior. > I had a hard time beleiving it existed since I never run with a getty > on /dev/console.. We did a run around this in 4.0 or so; I can't believe that someone tried to put a getty on /dev/console *again*. What was discussed before was fixing sysinstall to enable a getty on /dev/ttyd0 *if* the install was being done on a serial console; this is the only sane way to go about it. Putting a getty on /dev/console screws up all sorts of things; most especially, non-serial-console installs and X. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message