*BSD News Article 53772


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.uwa.edu.au!classic.iinet.com.au!swing.iinet.net.au!news.uoregon.edu!chi-news.cic.net!usc!howland.reston.ans.net!Germany.EU.net!zib-berlin.de!news.tu-chemnitz.de!irz401!uriah.heep!not-for-mail
From: j@uriah.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Wantted: meaning of boot flags
Date: 31 Oct 1995 00:15:49 +0100
Organization: Private FreeBSD site, Dresden.
Lines: 36
Message-ID: <473mb5$8hl@uriah.heep.sax.de>
References: <470g0o$coa@shore.shore.net>
NNTP-Posting-Host: uriah.heep.sax.de
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

<witr@spooky.rwwa.com> wrote:
>Could someone please post the meaning of all of the
>boot flags?

I finally revamped the man page for boot(8) recently.

Here's the section about flags.

                      -abcCdhrsv
                           Boot flags:
                                 -a    ask for the device to install as root
                                       file system during kernel initialisa-
                                       tion
                                 -b    do not automatically reboot after shut-
                                       down or crash
                                 -c    run UserConfig to modify hardware pa-
                                       rameters for the loaded kernel
                                 -C    boot from CDROM
                                 -d    enter the DDB kernel debugger (see
                                       ddb(4))  before configuring any device
                                       (except the system's console)
                                 -h    toggle serial/graphics console
                                 -r    do not establish the root directory of
                                       the file system hierarchy on the device
                                       where the boot file is being loaded
                                       from
                                 -s    boot into single-user mode; if the con-
                                       sole is marked as ``insecure'' (see
                                       ttys(5)),  the root password must be
                                       entered
                                 -v    be verbose during device probing
-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)