Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!ucsd!network.ucsd.edu!hp-sdd!ncr-sd!ncrcae!sauron!wescott
From: wescott@Columbia.NCR.COM (Mike Wescott)
Newsgroups: comp.sys.ncr
Subject: Re: Avoid single user on cold boot
Keywords: single-user init-n
Message-ID: <2089@sauron.Columbia.NCR.COM>
Date: 28 Mar 90 22:16:33 GMT
References: <482@vela.acs.oakland.edu>
Sender: news@sauron.Columbia.NCR.COM
Reply-To: wescott@micky.Columbia.NCR.COM (Mike Wescott)
Organization: E&M-Columbia, NCR Corp, W Columbia, SC
Lines: 30

In article <482@vela.acs.oakland.edu> bminnebo@vela.acs.oakland.edu (Brian P. Minnebo) writes:
> [...] What I would like is for the boot procedure to go into multi
> user as the default.

> Is there any method to set this up or is it fixed in the hardware?

It's not done by hardware (or firmware).  Try changing the inittab entry
marked initdefault.  From inittab(4):

	initdefault
	    Scan the entry only when init is initially
	    invoked.

	    Init uses this entry, if it exists, to determine
	    which run-level to enter initially: init takes the
	    highest run-level specified in the rstate field
	    and uses that as its initial state. If the rstate
	    field is empty, it is interpreted as 0123456 and
	    so init enters run-level 6.

	    Also, the initdefault entry can use s to specify
	    that init starts in the SINGLE USER state.
	    Additionally, if init does not find an initdefault
	    entry in /etc/inittab, then init requests an
	    initial run-level from the user at reboot time.


--
	-Mike Wescott
	 mike.wescott@ncrcae.Columbia.NCR.COM