Remove svn:mergeinfo from the releng/10.0 branch.

After branch creation from stable/10, the stable/10 branch mergeinfo
was moved to the root of the branch.

Since there have not been any merges from stable/10 to releng/10.0
yet, we do not need to track any of the existing mergeinfo here.

Merges to releng/10.0 should now be done to the root of the branch.

For future branches during the release cycle, unless otherwise noted,
this change will be done as part of the stable/ and releng/ branch
creation.

Discussed with: peter
Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

- 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

Adapt to the fact that minidumps are now on by default.

PR: 177188

Document that you can use -v along with -l.

Noticed by: pjd

Add an option to display the current dump device via dumpon -l.

MFC after: 2 weeks

Switch the default WARNS level for sbin/ to 6.

Submitted by: Ulrich Spörlein

Whitespace and style nits.

With minidumps, the dumping partition could be smaller than physical
memory, so checking the size of the partition is not necessary.

Tested by: kris

It has not been possible to specify a dumpdev in loader.conf since 2002,
so don't raise false hopes here.

- Mention the size of the additional header

PR: docs/85867
Submitted by: dinoex
MFC after: 1 week

Sort sections.

Promote mediasize and physmem to uintmax_t when comparing them.

Whitespace nit.

dumpon builds cleanly at WARNS level 6.

Verify that the specified device is at least as large as hw.physmem.

Wrap some long lines (no content changes)

`off' is a keyword, not a parameter name.

Obtained from: DragonFly

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

Approved by: core, imp

style.Makefile(5):
Use WARNS?= instead of WARNS=.

Bring the dumpon(8) man page closer to reality:

- dumpon utility has not used kern.dumpdev sysctl
since rev. 1.14 (sbin/dumpon/dumpon.c) when phk@
updated it to use the DIOCSKERNELDUMP ioctl [1]
- remove obsolete reference to sysctl(3)

While I am there, fix two style nits:

- use .Nm instead of `dumpon'
- change NOTES to IMPLEMENTATION NOTES, to bring
it in line with recommended section headings in
mdoc(7)

Original patch by: Martin Faxer <gmh003532brfmasthugget.se> [1]

PR: docs/39293
Approved and Reviewed by: des (mentor), re (scottl, bmah)

Use __FBSDID() to quiet GCC 3.3 warnings.

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

Improve wording even more.

Replace the 'at least the amount of physical memory + 64K' with a better
explanation in regards to sizing the dump device.

The .Nm utility

unbreak build: include string.h for strcmp prototype.

Update dumpon manual page to explain single/multi-user usability

PR: 36465
No Objections from: ru

Rename DIOCGKERNELDUMP to DIOCSKERNELDUMP as it strictly speaking
is a "set" not a "get" operation.

Sponsored by: DARPA & NAI Labs.

Move generic disk ioctls from <sys/disklabel.h> to <sys/disk.h>.

Sponsored by: DARPA & NAI Labs

Here follows the new kernel dumping infrastructure.

Caveats:

The new savecore program is not complete in the sense that it emulates
enough of the old savecores features to do the job, but implements none
of the options yet.

I would appreciate if a userland hacker could help me out getting savecore
to do what we want it to do from a users point of view, compression,
email-notification, space reservation etc etc. (send me email if
you are interested).

Currently, savecore will scan all devices marked as "swap" or "dump" in
/etc/fstab _or_ any devices specified on the command-line.

All architectures but i386 lack an implementation of dumpsys(), but
looking at the i386 version it should be trivial for anybody familiar
with the platform(s) to provide this function.

Documentation is quite sparse at this time, more to come.

Sponsored by: DARPA, NAI Labs

Details:

Dumpon now opens the device and uses ioctl(DIOCGKERNELDUMP) to set it
to be the dumpdevice. When "off" is set, /dev/null is used.

o __P
o Strict ANSI declarations.
o return (foo);
o main (int, char *[])

CG hard sentence breaks.

Submitted by: ru

Don't use `you'.

Submitted by: ru

Allow dump device be configured as early as possible using loader(8) tunable.
This allows obtaining crash dumps from the panics occured during late stages
of kernel initialisation before system enters into single-user mode.

MFC after: 2 weeks

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

Reviewed by: mike

Typo.

Remove whitespace at EOL.

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

Include missing header files which define functions for which gcc has
builtins (e.g., exit, strcmp).

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

Set the default manual section for sbin/ to 8.

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

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

* Clarify text on choosing a dump device
* Remove the text which states only devices with minor number 1 can be used
- this is no longer true.
* Mention that dumpon(8) cannot be used to capture dumps from panics during
kernel initialization.
* /dev/wd -> /dev/ad

PR: 19848
Submitted by: Udo Erdelhoff <ue@nathan.ruhr.de>
Reviewed by: sheldonh

Remove unused #include.

Back out the new advice introduced in the previous commit, which at
least one reviewer is now unhappy with, since it contains incomplete
and misleading advice that is not easy to correct.

The net effect of this commit and the previous commit is to simply
remove all discussion of setting dumpdev to catch crash dumps
prior to entering user mode.

Update instructions for setting the dump device prior to multi-user
mode.

Reported by: dcs
Submitted by: asmodai

The dumpon sysctl only accept cdevs thse days.

Submitted by: bde

Accept both types of devices to work with older kernels too
Fix confusing message

Convert dumpon to work on character devices instead of block devices.

NB: You may need to change your /etc/rc.conf!

$Id$ -> $FreeBSD$

Use current names for swap devices.

PR: docs/11708
Submitted by: Matthew D. Fuller <fullermd@over-yonder.net>

Sort cross references.

Capitalize at the start of sentence. Add rcsid. Remove unused #includes.
Use `dumpon' instead of argv[0].

Correct manual page, based on feedback from Bruce Evans.

Reviewed by: Bruce Evans <bde@freebsd.org>

Manual page fix: add cross references, refer to ``dumpdev'' variable in
"/etc/rc.conf".

PR: 6117
Submitted by: Mark Mayo <mark@vmunix.com>

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.

Use the .Fx macro where appropriate.

Fixed some minor formatting problems to silence manck some more.
Corrected some bogus cross references to man pages that we don't/won't
have and either deleted them, or found a more appropriate man page
that we do have. Various other minor changes to silence manck.

Manck is currently down to about 200 lines of errors, down from
the 500 - 600+ when I started all this.

Remove trailing whitespace.

My utility to specify where you want crash dumps to go. More user
and kernel support to follow.