DataMuseum.dk

top - metrics - download

    Length: 2281 (0x8e9)
    Types: TextFile
    Notes: UNIX file
    Names: »reboot.2v«

└─⟦26887b7e0⟧ Bits:30009717 Comet 32 harddisk image
    └─⟦28c352965⟧ »/a« UNIX Filesystem
        └─⟦this⟧ »usr/man/man2/reboot.2v« 

TextFile

.ig
	@(#)reboot.2v	2.1	7/1/84
	@(#)Copyright (C) 1983 by National Semiconductor Corp.
..
.TH REBOOT 2V
.SH NAME
reboot \- reboot system or halt processor
.SH SYNOPSIS
.nf
.B #include <sys/reboot.h>
.PP
.B reboot(howto)
.B int howto;
.fi
.SH DESCRIPTION
In a SYS32 environment,
.I reboot
is used to cause a system reboot, and in the event of
unrecoverable system failure, it is invoked automatically.
.I Howto
is a mask of options passed to the bootstrap program.
The system call interface permits only RB_HALT or RB_AUTOBOOT
to be passed to the reboot program.
When neither of these options (e.g. RB_AUTOBOOT) are  passed, 
the system is automatically rebooted
from file \*(lqvmunix\*(rq in the root file system of partition 0
in a processor specific way;
it is determined by the setting of the
front switch pack switches 3 and 4.
If both switches 3 and 4 are 
.BR ON ,
the processor will enter the
.B ROM
monitor which will select the bootstrap device.
.PP
The bits of
.I howto
are:
.TP
RB_HALT
the processor is simply halted; no reboot takes place.
The CPU locks out all interrupts and executes the WAIT instruction.
.TP
RB_ASKNAME
Interpreted by the bootstrap program itself, causing it to
inquire as to what file should be booted.  Normally, the system is
booted from the file \*(lqxx(0,0)vmunix\*(rq without asking, where
.I xx
is determined by a code in register
.I r7
(which is known as
.I devtype)
at entry to the bootstrap program.  The code corresponds to the
major device number of the root file system, i.e. \*(lqmajor
of the rootdev\*(rq.
Currently, the following values of
.I devtype
are understood:
.RS
.br
.ns
.IP
.nf
0	disk
1	tape
.fi
.RE
.IP
Thus if
.I r7
contained a 0, the system
.RS
.IP
.B dc(1,0)vmunix.
.RE
.IP
would be booted.
This switch not available from the system call interface.
.TP
RB_SINGLE
Normally, the reboot procedure involves an automatic disk consistency
check and then multi-user operations.  This prevents the consistency
check, rather simply booting the system with a single-user shell on
the console, from the file system specified by
.I r7.
This switch is interpreted by the
.IR init (8)
program in the newly booted system.
This switch is not available from the system call interface.
.SH "SEE ALSO"
crash(8), halt(8), init(8), reboot(8)