- 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

Fix usr.bin/ and usr.sbin/ build with a 64-bit ino_t.

Original code by: Gleb Kurtsou

Mark global functions and/or variables in snapinfo(8) static where possible.

This allows compilers and static analyzers to do more thorough analysis.

mdoc: consistently spell our email addresses <foo@FreeBSD.org>

Reviewed by: ru

Mark ftwv as __unused. This compare function does not need it.

Imagine a situation where:

# ls -ld /mnt/{foo,bar}
drwxr-xr-x 3 root wheel 512 Mar 16 06:56 /mnt/bar
lrwxr-xr-x 1 root wheel 3 Mar 16 12:10 /mnt/foo -> bar

# grep /mnt/foo /etc/fstab
/dev/da1 /mnt/foo ufs rw 0 0

Which means, we give symbolic link as a mount point to mount(8), but mount(8)
use realpath(3) before mounting the file systems, so we get:

# mount | grep /dev/da1
/dev/da1 on /mnt/bar (ufs, local)

Before the commit:

# snapinfo /mnt/foo
usage: snapinfo [-v] -a
snapinfo [-v] mountpoint
# snapinfo /mnt/bar
/mnt/bar/snap

This commit makes snapinfo(8) to first realpath(3) the given mount point and
now we have:

# snapinfo /mnt/foo
/mnt/bar/snap
# snapinfo /mnt/bar
/mnt/bar/snap

Pass special device to the ufs_disk_fillout() function, instead of mount
point path. This way we properly handle the case when file system listed
in /etc/fstab was unmounted and another file system was mounted on the
same mount point.

Fix version number when the feature was added.

Spotted by: ceri
MFC after: 1 day

snapinfo -- show snapshot location on UFS file systems

Glanced over by: kan
Review by: ru (snapshot.8)
MFC: TBD