| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
with a trailing zero-width space: `e.g.\&'.
|
|
|
|
|
|
|
| |
Avoid using parenthesis enclosure macros (.Pq and .Po/.Pc) with plain text.
Not only this slows down the mdoc(7) processing significantly, but it also
has an undesired (in this case) effect of disabling hyphenation within the
entire enclosed block.
|
| |
|
| |
|
|
|
|
|
|
|
| |
not -tag. Instead, put a period after the error messages to aide
those using dumb terminals not capable of properly displaying markup.
Requested by: ru
|
|
|
|
|
|
|
| |
the former makes it more obvious as to there the error message starts
and the explanation begins.
PR: 26431
|
| |
|
|
|
|
|
|
|
| |
may not be (un)loaded.
PR: 23350
Submitted by: Gordon Tetlow <gordont@bluemtn.net>
|
| |
|
|
|
|
| |
Submitted by: bde
|
|
|
|
| |
PR: 20974
|
|
|
|
|
| |
of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.
|
|
|
|
|
| |
PR: docs/14449
Submitted by: James FitzGibbon <james@targetnet.com>
|
|
|
|
|
|
|
|
|
| |
assumption that only getty processes can be managed. Describe the
SysV-like ability to keep arbitrary long-running processes alive
using a non-device first field in /etc/ttys.
PR: 12767
Submitted by: Peter Jeremy <peter.jeremy@alcatel.com.au>
|
|
|
|
|
|
|
| |
init(8) cannot decrease securelevel. The manual page explains this
and single_user() doesn't try to downgrade kernel to insecure mode.
Reviewed by: bde (manual page)
|
| |
|
|
|
|
| |
literally.
|
|
|
|
|
| |
Requested by: peter
Reviewed by: des, billf
|
|
|
|
|
|
| |
While I'm here, fix some typos in the manpage.
Requested by: des
|
|
|
|
|
|
|
|
|
| |
or halt and turn the power off if sent SIGUSR2.
PR: 5451
Submitted by: Leif Neland <leifn@image.dk>
Reworked by: ru
Reviewed by: -hackers
|
|
|
|
|
| |
about fdisk and securelevel 2.
PR: docs/7785
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
(a) Note that the default securelevel value is -1, in -current and -stable.
(b) Mention kernel sysctl variable that controls securelevel.
(c) Add warning the `fsck' will fail if securelevel >= 2.
(d) Suggest end of /etc/rc as the right place to raise securelevel.
and one spelling fix.
PR: 2850
|
|
|
|
|
| |
Add sample /etc/rc.shutdown (which is just a shell for now).
Submitted by: Ollivier Robert <roberto@keltia.freenix.fr>
|
|
|
|
|
|
| |
system is running in secure mode.
Obtained from: NetBSD PR# 3299
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.
|
| |
|
|
|
|
|
|
|
| |
match reality.
Say that secured devices `may not be opened for writing' instead of
`are read-only'.
|
|
|
|
|
|
| |
man pages up to mdoc guidelines and fix some minor formatting glitches.
Also fixed a number of man pages to not abuse the .Xr macro to
display functions and path names and a lot of other junk.
|
|
|
|
|
| |
halt before) if init is sent an interrupt signal. This is necessary
for <CTL><ALT><DEL> to do the right thing if enabled.
|
|
Note: XNSrouted and routed NOT imported here, they shall be imported with
usr.sbin.
|