From owner-freebsd-current Wed May 14 10:32:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA22496 for current-outgoing; Wed, 14 May 1997 10:32:36 -0700 (PDT) Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA22488 for ; Wed, 14 May 1997 10:32:31 -0700 (PDT) Received: from labs.usn.blaze.net.au (local [127.0.0.1]) by labs.usn.blaze.net.au (8.8.5/8.8.5) with ESMTP id DAA01114; Thu, 15 May 1997 03:32:16 +1000 (EST) Message-Id: <199705141732.DAA01114@labs.usn.blaze.net.au> X-Mailer: exmh version 2.0gamma 1/27/96 To: Michael Hancock Cc: freebsd-current@freebsd.org Subject: Re: RELENG_2_2 In-reply-to: Your message of "Mon, 12 May 1997 19:54:18 +0900." X-Face: (W@z~5kg?"+5?!2kHP)+l369.~a@oTl^8l87|/s8"EH?Uk~P#N+Ec~Z&@;'LL!;3?y Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 15 May 1997 03:32:14 +1000 From: David Nugent Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 3) You won't be able to login to your computer if you don't have > /etc/login.conf. Huh? This should certainly not be true. If so, it is a bug, and I'd very much like to hear the details. FWIW, I just tried it on a 2.2 box AND on a 3.0 box with very recent builds from each branch that include the recent login.conf changes - both login and su worked fine without /etc/login.conf present, with only a syslog complaint that there's no default or root class (which is intentional). What problems are you experiencing? If there's some gotcha there that I haven't considered, I'd certainly like to clear it up as soon as possible. The lack of this file is NOT intended to make the system unusable, not in -current, and not in 2.2 either. Regards David