From owner-freebsd-questions Sun Jul 14 22:43:47 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA01407 for questions-outgoing; Sun, 14 Jul 1996 22:43:47 -0700 (PDT) Received: from homer17.u.washington.edu (durang@homer17.u.washington.edu [140.142.76.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA01402 for ; Sun, 14 Jul 1996 22:43:45 -0700 (PDT) Received: from localhost by homer17.u.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA88490; Sun, 14 Jul 96 22:43:43 -0700 Date: Sun, 14 Jul 1996 22:43:43 -0700 (PDT) From: Ken Marsh To: dwhite@resnet.uoregon.edu Cc: questions@FreeBSD.ORG Subject: /etc/nologin file invunerability In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I tried booting with -s option, and found that I have few commands at my > > disposal (i.e., no man pages) and I am also denied access to the file > > /etc/nologin. "su" is also not available when I single-user boot. I can > > delete the file when logged in as root, but then it reinstates itself when > > I reboot. > > Oh, you have to key in "mount /" then "mount -a" to get your commands > back and get / back to read/write. > > > This is only one of many problems I have had, including no login prompt on > > boot, my atapi CD-ROM isn't recognized, my lpd daemon has to be > > re-activated manually with ever print..... it think all the problems are > > the result of using an atapi CD-ROM boot floppy from the 2.1.0 release to > > install from the Walnut Creek 2.0.5 CD. The install was not very clean. so i booted with "-s" and did the "mount /" and "mount -a". Then I removed the file /etc/nologin. When i rebooted, it had reappeared. It is just like before. I delete it, and next time it is there again. Ken