- Copy stable/10 (r259064) to releng/10.0 as part of the
10.0-RELEASE cycle.
- Update __FreeBSD_version [1]
- Set branch name to -RC1

[1] 10.0-CURRENT __FreeBSD_version value ended at '55', so
start releng/10.0 at '100' so the branch is started with
a value ending in zero.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Move the check whether the clear flag is set. This has 2 advantages

- When operating on a core file (-M) and -c is specified we don't clear
the message buffer of the running system.
- If we don't have permission to clear the buffer print the error message
only. That's what Linux does in this case, where this feature was ported
from, and it ensures that the error message doesn't get lost in the noise.

Discussed with: antoine, cognet
Approved by: cognet

Bump .Dd for recent content change.

Reported by: delphij

Add support for 'dmesg -c' which clears the dmesg buffer after it has
been printed. This provides compatibility with other *nix systems
(including Linux).

While here use stdbool booleans for 'all'.

PR: bin/178295
Submitted by: Levent Serinol <lserinol@gmail.com>
Reviewed by: will

Add missing static keywords for global variables to tools in sbin/.

These tools declare global variables without using the static keyword,
even though their use is limited to a single C-file, or without placing
an extern declaration of them in the proper header file.

Switch the default WARNS level for sbin/ to 6.

Submitted by: Ulrich Spörlein

Avoid moving onto a new line while testing if there is a syslog priority
in the buffer. This isn't exactly the patch that Stephen submitted, but
is based on one of his suggestions.

PR: 93841
Submitted by: Stephen Montgomery-Smith <stephen@math.missouri.edu>
MFC after: 2 weeks

WARNS=6 cleanup:

- signed/unsigned conform.
- Better initialization of nlist[]. I think we should have
something like NLIST_NULL instead of the current (ugly)
form...

Print a usage message if a non-option is specified.
MFC after: 3 weeks

Don't add integers to void pointers.

Remove advertising clause from University of California Regent's license,
per letter dated July 22, 1999.

Approved by: core, imp

Not too much point specifying -N but not specifying -M.

Further simplify the code for printing the message buffer:
- Ensure that the buffer ends with "\n\0" to avoid special cases
and allow the use of strtol().
- Use strvisx() on each complete line instead of character by
character.

Submitted by: bde
MFC after: 1 week

Don't print the oldest line in the message buffer if the buffer is
full, since that line is almost always incomplete. Make the parsing
of <%d> lines more strict.

Also simplify the logic a little:
- Start off by making the buffer linear so that we don't have to
deal with it wrapping around (suggested by bde).
- Process line by line rather than byte at a time.

Replace the code for reading and writing the kernel message buffer
with a new implementation that has a mostly reentrant "addchar"
routine, supports multiple message buffers in the kernel, and hides
the implementation details from callers.

The new code uses a kind of sequence number to represend the current
read and write positions in the buffer. This approach (suggested
mainly by bde) permits the read and write pointers to be maintained
separately, which reduces the number of atomic operations that are
required. The "mostly reentrant" above refers to the way that while
it is now always safe to have any number of concurrent writers,
readers could see the message buffer after a writer has advanced
the pointers but before it has witten the new character.

Discussed on: freebsd-arch

bufpos is used in size_t contexts, so make it one.

These are WARNS=2 clean, try to keep them that way.

s/filesystem/file system/g as discussed on -developers

Include <nlist.h> for nlist interfaces instead of depending on namespace
pollution in <kvm.h>.

The .Nm utility

o Remove __P
o Use ANSI function definitions
o mark usage() as __dead2

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

Reviewed by: mike

mdoc(7) police: compute the exact tag width.

Add mention of /var/run/dmesg.boot.

Yes, this isn't really the right place for it. No, it really can't
remain undocumented.

add -a to usage()

Submitted by: Ashley Penney <ashp@unloved.org>
MFC after: 3 days

mdoc(7) police: removed HISTORY info from the .Os call.

Update the dmesg man page to reflect the recent changes to dmesg.

Reviewed by: ru

Use the kern.msgbuf sysctl to get the message buffer on a running
kernel, and remove setgid kmem, which is not needed any more.

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

Set the default manual section for sbin/ to 8.

Backout -a restriction hack.

Requested by: rwatson

Restrict -a to root only.

PR: bin/25337

Fix hard sentence break introduced in previous commit.

Add a -a option to show the entire message buffer.

mdoc(7) police: use the new features of the Nm macro.

Remove obsolete /dev/drum references

Reviewed by: alex, asmodai, billf

$Id$ -> $FreeBSD$

Use an error message that more clearly indites(sp?) an out-of-sync
kernel+userland when that is the case.

PR: bin/7414

Use .Pa for filenames. Use .Bl/.El in FILES section. Remove unused #includes.

Make the size of the msgbuf (dmesg) a "normal" option.

compare return value from getopt against -1 rather than EOF, per the final
posix standard on the topic.

Revert $FreeBSD$ to $Id$

Make the long-awaited change from $Id$ to $FreeBSD$

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.

Who would have though that dmesg didn't understand message buffers?

Fixed the following bugs:
- the buffer was reprinted endlessly when msg.bufx == 0 and (for a
different reason) when msg.bufx == 1.
- the last byte of the buffer wasn't printed except in the the infinite
loop cases.
- the comment about walking the buffer didn't match the (correct) code.
- minor -Wall and style bugs.
Not fixed:
- excessive newline processing which hid the non-printing of the last
byte of the buffer.

Add relevant files to the FILES section
Submitted by: Julian H Stacey

Add #include <err.h>.

Add setlocale LC_CTYPE

Converted 'vmunix' to 'kernel'.

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.

This commit was generated by cvs2svn to compensate for changes in r1558,
which included commits to RCS files with non-trunk default branches.