| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
is disabled or fails.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
where applicable. The main reason for this change is that
the location of make.conf is not constant and can be
modified via __MAKE_CONF. This change also improves
hyper-text linkage in our manpages.
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
|
|
| |
/boot.config or on the "boot:" prompt line via a "-S<speed>" flag,
e.g. "-h -S19200". This adds about 50 bytes to the size of boot2
and required a few other small changes to limit the size impact.
This changes only affects boot2; there are further loader changes
to follow.
|
|
|
|
|
|
| |
PR: docs/84198
Submitted by: Gary W. Swearingen
MFC after: 3 days
|
|
|
|
|
|
| |
Submitted by: Gary Allan <dragonfly@gallan.plus.com>
Obtained from: DragonFlyBSD
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
with -k option and never be used without kflag. This confuses
gcc because we set "kflag" at the same time with "kernel", but
the logic is not that apparant for gcc.
Since we can initialize "kernel" to NULL then know if "k" option
is set through determining whether it is still NULL, don't try
to have gcc to guess why we are connecting "kflag" with "kernel"
and use "kernel" directly in place of kflag.
Bump WARNS?= from 2 to 6
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Document better what the -C option means.
- The -c option is currently a no-op.
- The -D and -h options do not allow switching between
single/dual console modes and internal/video consoles.
(This used to be true for the old biosdisk boot code,
but now they just force the multiple consoles mode and
serial console, respectively.)
|
| |
|
|
|
|
| |
Reported by: ru
|
|
|
|
|
|
|
|
| |
and disklabel.5. Refrencing bsdlabel.5 is somewhat bogus as it is not
connected to the build and is mostly unwritten at this point.
Reported by: Matthias Andree <matthias.andree at web.de>
PR: docs/72020
|
|
|
|
|
|
| |
where boot.config needs to reside. Also change /kernel
to /boot/loader, as that is the apparent default now. This
man page probably requires more updates.
|
| |
|
|
|
|
|
|
| |
per letter dated July 22, 1999.
Approved by: core, imp
|
| |
|
| |
|
|
|
|
|
|
| |
doesn't have a process group, which can occur if you're working with
a custom init that doesn't set up a full tty context. Rather than
refusing to reboot, ignore ESRCH from the kill attempt in reboot(8).
|
|
|
|
| |
Neglected by: trhodes
|
|
|
|
| |
PR: 47015
|
| |
|
|
|
|
| |
Approved by: re
|
| |
|
|
|
|
| |
Approved by: re
|
| |
|
| |
|
|
|
|
| |
Spotted by: brandt@fokus.gmd.de
|
|
|
|
|
|
|
|
| |
when using '-p' with reboot, and the power down action failds, reboot
the system normally. The behaviour of 'halt -p' and of shutdown(8) is
unchanged.
Approved by: roberto
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
'-p' is used on the reboot(8) command line.
This is intended for use when you want to attempt a power down
action, but you want the system to reboot (not halt) if the
power down action fails.
This is typically useful when the power-off action performed by
the kernel consists in signalling an uninterrupted power supply
that it should shut down its inverter if mains power has not returned.
The behaviour of shutdown(8) and init(8) is not modified;
only the behaviour of invoking 'reboot -p' manually is
modified, and then only in the case when a power-down action
fails.
Sounded reasonable to: phk
Approved by: roberto (mentor)
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
nextboot functionality.
Reviewed by: jake (mentor)
|
|
|
|
|
|
| |
support. Also, hook it up to the build.
Approved by: jake (mentor)
|
| |
|
|
|
|
|
|
|
| |
is a loader configuration file and can be used for more than just a
kernel name.
Submitted by: Gordon Tetlow <gordont@gnf.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
around. If the kernel boots successfully, the record of this kernel
is erased, it is intended to be a one-shot option for testing
kernels.
This could be improved by having the loader remove the record of
the next kernel to boot, it is currently removed in /etc/rc immediately
after disks are mounted r/w.
I'd like to MFC this before the 4.6 freeze unless there is violent
objection.
Reviewed by: Several on IRC
MFC after: 4 days
|
|
|
|
|
| |
PR: docs/36267 (partial)
Submitted by: Thomas Quinot <thomas.cuivre.fr.eu.org>
|
|
|
|
|
|
|
| |
PR: i386/36016
Submitted by: Thomas Quinot <thomas@cuivre.fr.eu.org>
Reviewed by: rnordier
MFC after: 1 week
|
|
|
|
|
| |
Also drop a note about undocumented features that was intended to
cover the since-documented slice-selection syntax.
|
|
|
|
| |
Prodded by: ambrisko
|
|
|
|
|
| |
(This is more useful for 4.x where boot blocks can still load
kernels, modulo the PR kern/17422.)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This flag adds a pausing utility. When ran with -p, during the kernel
probing phase, the kernel will pause after each line of output.
This pausing can be ended with the '.' key, and is automatically
suspended when entering ddb.
This flag comes in handy at systems without a serial port that either hang
during booting or reser.
Reviewed by: (partly by jlemon)
MFC after: 1 week
|
|
|
|
|
|
| |
Binary builds that cannot handle this must explicitly set WARNS=0.
Reviewed by: mike
|
| |
|
| |
|