Remove residual blank line at start of Makefile

This is a residual of the $FreeBSD$ removal.

MFC After: 3 days (though I'll just run the command on the branches)
Sponsored by: Netflix

rescue,nextboot: Install nextboot as a link to reboot, rm nextboot.sh

Reboot now emulates the nextboot shell script completely. Retire the
nextboot.sh script and install the link. Retain the same ma

rescue,nextboot: Install nextboot as a link to reboot, rm nextboot.sh

Reboot now emulates the nextboot shell script completely. Retire the
nextboot.sh script and install the link. Retain the same manual page,
since there's enough differences between nextboot and reboot that
talking about nextboot would likely be confusing in nextboot.8

The nextboot.sh script no longer exists, so doesn't need to be fixed up
to create rescue. However, now we need a link from nextboot to reboot.

Sponsored by: Netflix
Reviewed by: kevans
Differential Revision: https://reviews.freebsd.org/D43831
Differential Revision: https://reviews.freebsd.org/D43843

show more ...

sbin: Remove ancient SCCS tags.

Remove ancient SCCS tags from the tree, automated scripting, with two
minor fixup to keep things compiling. All the common forms in the tree
were removed with a perl

sbin: Remove ancient SCCS tags.

Remove ancient SCCS tags from the tree, automated scripting, with two
minor fixup to keep things compiling. All the common forms in the tree
were removed with a perl script.

Sponsored by: Netflix

show more ...

Remove $FreeBSD$: one-line sh pattern

Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/

Merge the projects/release-pkg branch to head.

This allows packaging the base system with pkg(8), including
but not limited to providing the ability to provide upstream
binary update possibilities f

Merge the projects/release-pkg branch to head.

This allows packaging the base system with pkg(8), including
but not limited to providing the ability to provide upstream
binary update possibilities for non-tier-1 architectures.

This merge is a requirement of the 11.0-RELEASE, and as such,
thank you to everyone that has tested the project branch.

Documentation in build(7) etc. is still somewhat sparse, but
updates to those parts will follow.

Sponsored by: The FreeBSD Foundation

show more ...

Explicitly add more files to the 'runtime' package.

Sponsored by: The FreeBSD Foundation

IFH@204581

Port the remaining apps in sbin/ to utmpx; only reboot(8).

Merge from head at r201628.

# This hasn't been tested, and there are at least three bad commits
# that need to be backed out before the branch will be stable again.

Let init(8) and reboot(8) use utmpx to log wtmp entries.

logwtmp() gets called with the raw strings that are written to disk. For
regular user entries, this isn't too bad, but when booting/shutting

Let init(8) and reboot(8) use utmpx to log wtmp entries.

logwtmp() gets called with the raw strings that are written to disk. For
regular user entries, this isn't too bad, but when booting/shutting
down, the contents get rather cryptic.

Just call the standardized pututxline().

show more ...

MFC @199204

Switch the default WARNS level for sbin/ to 6.

Submitted by: Ulrich Spörlein

Do not install boot_i386.8 on all architectures.

The kernel specified in main() of reboot(8) will be initialized
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

The kernel specified in main() of reboot(8) will be initialized
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

show more ...

Share the i386 boot manual page.

Hook the new nextboot(8) manpage up to the build.

Add a nextboot script to make it easier to control the loader nextboot
support. Also, hook it up to the build.

Approved by: jake (mentor)

Default to WARNS=2.
Binary builds that cannot handle this must explicitly set WARNS=0.

Reviewed by: mike

Use ${MACHINE}, it works with cross-builds.

Constify and set WARNS=2.

Submitted by: Mike Barcroft <mike@q9media.com>

- Backout botched attempt to introduce MANSECT feature.
- MAN[1-9] -> MAN.

Removed the boot_*(8) man pages for machines we don't support:
hp300, sparc, tahoe, and vax

Totally revamp the man page, update to the state of affairs.

Make a link from boot_${ARCH}.8 to boot.8, so people will get what
they expect when asking "man boot".

I think David will lynch me when

Totally revamp the man page, update to the state of affairs.

Make a link from boot_${ARCH}.8 to boot.8, so people will get what
they expect when asking "man boot".

I think David will lynch me when i'm requesting this to go into 2.1... :-)

show more ...

Install aliases "fasthalt" and "fastboot" for halt and boot respectively.
This is for "backwards compatibility". Documented these aliases in the
manual page.

Convert to our man installation style. Also fixed long-standing bug
in `fastboot'/`fasthalt' in which the interpreter would hang around
after `reboot' or `halt' is run, causing an irritating ``Kille

Convert to our man installation style. Also fixed long-standing bug
in `fastboot'/`fasthalt' in which the interpreter would hang around
after `reboot' or `halt' is run, causing an irritating ``Killed'' message.

show more ...