Date: Sun, 14 Jul 1996 23:12:31 -0700 From: David Greenman <davidg@root.com> To: Ken Marsh <durang@u.washington.edu> Cc: dwhite@resnet.uoregon.edu, questions@FreeBSD.ORG Subject: Re: /etc/nologin file invunerability Message-ID: <199607150612.XAA02199@root.com> In-Reply-To: Your message of "Sun, 14 Jul 1996 22:43:43 PDT." <Pine.A32.3.92a.960714224002.138091A-100000@homer17.u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
>> > 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. Sounds like someone is playing a trick on you. /etc/nologin is normally created by the shutdown command and is normally removed in the system startup script /etc/rc. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607150612.XAA02199>