- Copy stable/10@296371 to releng/10.3 in preparation for 10.3-RC1
builds.
- Update newvers.sh to reflect RC1.
- Update __FreeBSD_version to reflect 10.3.
- Update default pkg(8) configuration to use the quarterly branch.

Approved by: re (implicit)

MFC r287396:

It's 2015, and some people are still trying to use fdisk and then
go asking what debug flags to set for GEOM to make it work. Advice
them to use gpart(8) instead.

Something similar should probably done with disklabel,
but I need to rewrite the disklabel examples first.

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

Sweep man pages replacing ad -> ada.

Approved by: re (blackend)
MFC after: 1 week
X-MFC note: stable/9 only

Remove superfluous paragraph macro.

Be as explicit as possible when describing relation between the -m mask
argument and slices. Adjust example for the same reason.

Submitted by: Valentin Nechayev <netch netch kiev ua>
MFC after: 3 days

Allow boot0cfg to force a PXE boot via boot0 on the next boot.
- Fix boot0 to check for PXE when using the pre-set setting for the
preferred slice.
- Update boot0cfg to use slice 6 to select PXE. Accept a 'pxe' argument
instead of a number for the 's' option as a way to select PXE as well.

Submitted by: Andrew Boyer aboyer averesystems
MFC after: 2 weeks

Remove a note about disabling of GEOM protection mechanism.
boot0cfg should work without such hack.

MFC after: 3 days

Add reference to gpart(8).

MFC after: 3 days

Extend the geom-related info and put in the NOTE section, not
in BUGS, as this is a feature.

Bump the date, as it was forgotten in previous commits and the
page has had significant changes recently

Another, hopefully final set of changes to boot0 and boot0cfg.

boot0.S changes:

+ import a patch from Christoph Mallon to rearrange the various
print functions and save another couple of bytes;

+ implement the suggestion in PR 70531 to enable booting from
any valid partition because even the extended partitions that
were previously in our kill list may contain a valid boot loader.
This simplifies the code and saves some bytes;

+ followwing up PR 127764, implement conditional code to preserve
the 'Volume ID' which might be used by other OS (NT, XP, Vista)
and is located at offset 0x1b8. This requires a relocation of the
parameter block within the boot sector -- there is no other
possible workaround.
To address this, boot0cfg has been updated to handle both
versions of the boot code;

+ slightly rearrange the strings printed in the menus to make
the code buildable with all options. Given the tight memory
budget, this means that with certain options we need to
shrink or remove certain labels.

and especially:

make -DVOLUME_LABEL -DPXE the default options.

This means that the newly built boot0 block will preserve the
Volume ID, and has the (hidden) option F6 to boot from INT18/PXE.
I think the extra functionality is well worth the change.

The most visible difference here is that the 'Default: ' string
now becomes 'Boot: ' (it can be reverted to the old value
but then we need to nuke 1/2 partition name or entries to
make up for the extra room).

boot0cfg changes:

+ modify the code to recognise the new boot0 structure (with the
relocated options block to make room for the Volume id).

+ add two options, '-i xxxx-xxxx' to set the volume ID, -e c
to modify the character printed in case of bad input

PR: 127764 70531
Submitted by: Christoph Mallon (portions)
MFC after: 4 weeks

"-b /boot/mbr" is redundant, /boot/mbr is the default boot code for fdisk(8).

Pointed out by: ru

- Revert previous revision, it was incorrect
- Add an example using fdisk instead

Pointed out by: ru
Submitted by: Warren Block <wblock@wonkity.com>
MFC after: 3 days

Document /boot/mbr (non-interactive boot block)

PR: doc/111840
Submitted by: Warren Block <wblock@wonkity.com>
MFC after: 1 week

Document how to make boot0cfg work on mounted disks.

Sort sections.

Added the EXIT STATUS section where appropriate.

boot0 defaults to packet mode.

mdoc(7) fixes.

Document boot0sio and note that it requires modem handshake to work.

Spelling nit.

Get rid of duplicates.

Add an example of how to use the -m option that clarifies how the bits in
the mask correspond to slice numbers. Also, clarify the description of the
existing example.

Requested by: Larry Rosenman <ler@lerctr.org>

The .Nm utility

Remove references to the update/noupdate flag from the description
and examples of the "-s" option, since these two features operate
completely independently of each other.

Reviewed by: obrien

The man page is VERY WRONG about using "-o noupdate" with -s.
So fix it, and add an example using -s.

Trivial language fixes.

PR: 38015
Submitted by: Chris Pepper <pepper@mail.rockefeller.edu>

mdoc(7) police: utilize the new .Ex macro.

mdoc(7) police: s/BSD/.Bx/ where appropriate.

fdisk(8): document the default for -b, add xref to boot0cfg(8).
boot0cfg(8): add FILES section.

Reviewed by: rnordier

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

remove trailing periods from SEE ALSO.

Use Fx macro wherever possible.

Reflect new packet option default.

Mark a path up with Pa.

Whitespace-only change: apply normal line breaking style.

Provide correct information regarding "packet" option default.

PR: 20936
Originated by: obrien

Allow people to set the default boot slice with boot0cfg.

PR: 18923
Submitted by: Ian Dowse <iedowse@maths.tcd.ie>
Reviewed by: jhb
Approved by: rnordier

$Id$ -> $FreeBSD$

Implement -m option to enable/disable slices.

Finish implementing "setdrv" option. This is intended to be used
(with care) in those instances where boot0 is not passed the
correct drive number by the PC BIOS. (The symptoms are a
"F5 Drive 0" line, even though the current drive is drive 0.)

Make various minor corrections.

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

Add boot0cfg: this installs/configures the `boot0' boot manager. A
CLI utility to do this has been requested by a few people.