Revert "newsyslog(8): Comment out zstd support for now."

This reverts commit b4fcc362a220df584355e7fae6974e113e4caf3a.

Fix typo in various licenses: merchantibility -> merchantability

pciconf(8): Do actually enable the -e and -B options.

Handling them was added in d650e2183cf9557d58c726150ef990202fc85b98 but
for some reason they were neither added to getopt() nor documented.

Doc

pciconf(8): Do actually enable the -e and -B options.

Handling them was added in d650e2183cf9557d58c726150ef990202fc85b98 but
for some reason they were neither added to getopt() nor documented.

Documentation was taken from FreeBSD.

show more ...

Fix -Wundef in some code imported from NetBSD.

libaura: Do not initialize va_list args twice

- Fixes a segfault in the installer right after
"Begin Installing files".

Reported-by: @swildner

usr.sbin/autofs: Fix absolute path when creating a mountpoint

from freebsd 63640b2f552c0476f50484635eb9888eafcd22dc

FreeBSD finally fixed a bug I reported in 2017,
in a bit different way from a wor

usr.sbin/autofs: Fix absolute path when creating a mountpoint

from freebsd 63640b2f552c0476f50484635eb9888eafcd22dc

FreeBSD finally fixed a bug I reported in 2017,
in a bit different way from a workaround in DragonFly and NetBSD.
Apply FreeBSD fix in place of 108ed43a1e5e7ff8f890085e206d970562bf4a7c.

show more ...

Use %U for URIs within reference blocks in various manual pages.

libaura: Limit device/mount point comparison to PATH_MAX

libaura: Restore local variable name 'args'.

- For consistency's sake across the tree where 'args' or 'ap'
are widely used.

libaura: Restore fspred CVD Id.

- It is still important for some people.

libaura: Remove unused variable

Reported-by: daftaupe

libaura: Several fixes to fs predicates

- Make is_program() a bit more precise.
- Fix is_device()
- Simplify the code a bit.
- Regression tests now pass.

Test case

libaura: Several fixes to fs predicates

- Make is_program() a bit more precise.
- Fix is_device()
- Simplify the code a bit.
- Regression tests now pass.

Test case Result
--------------------------------------------------------------------------------
usr.sbin/installer/libaura/dict1/dict1 PASS
usr.sbin/installer/libaura/dict2/dict2 PASS
usr.sbin/installer/libaura/dict3/dict3 PASS
usr.sbin/installer/libaura/fspred1/fspred1 PASS

show more ...

Revert "Fix various mistakes (s/it were/it was/) in manual pages."

This reverts commit e4adeac153e9f588eff22befbf196d2fd3444bc3.

Fix various mistakes (s/it were/it was/) in manual pages.

usr.sbin/fstyp: Fix exfat detection

from FreeBSD ddf61156132b610915325769cbb93ea11be0d433

usr.sbin/fstyp: Sync with NetBSD

usr.sbin/fstyp: Minor fix for HAMMER2

usr.sbin/fstyp: Don't assert(0) for invalid HAMMER1/2 ondisk

Given purpose of fstyp, don't kill the process for invalid ondisk.
Just fail HAMMER1/2 detection.

Fix some -Wjump_misses_init warnings (found by clang).

Remove obsolete dev_mkdb(8)

The devname(3) has long been updated to determine the device name via
the 'kern.devname' sysctl provided by devfs(5). The dev.db created by
dev_mkdb(8) is thus unused an

Remove obsolete dev_mkdb(8)

The devname(3) has long been updated to determine the device name via
the 'kern.devname' sysctl provided by devfs(5). The dev.db created by
dev_mkdb(8) is thus unused and obsolete. So remove dev_mkdb(8) as well
and update relevant parts.

show more ...

sys/vfs/hammer2: Add initial multi-volumes support for HAMMER2

This commit adds initial multi-volumes support for HAMMER2. Maximum
supported volumes is 64. The feature and implementation is similar

sys/vfs/hammer2: Add initial multi-volumes support for HAMMER2

This commit adds initial multi-volumes support for HAMMER2. Maximum
supported volumes is 64. The feature and implementation is similar to
multi-volumes support in HAMMER1.

1. ondisk changes
=================
This commit bumps volume header version from 1 to 2, and adds four new
volume header fields using reserved fields in version 1. Other ondisk
structures are unchanged.
* "volu_id" - volume id from 0 to 63, where 0 represents root volume.
* "nvolumes" - number of volumes. All volumes have same the same value.
* "total_size" - sum of "volu_size" in volumes. All volumes have the
same value.
* "volu_loff[HAMMER2_MAX_VOLUMES]" - A 512 bytes table which contains
start offset of max 64 volumes within "total_size". All volumes have
the same value.

Version 1 volume header has 0 for above fields, so HAMMER2 internally
treats "nvolumes" as 1, and "total_size" as "volu_size" to be able to
handle version 1 and 2 transparently.

All volumes have 4 headers, but only root volume ones are relevant.
Non-root volume headers have their own unique "volu_id" and "volu_size",
but other fields are unimportant and never used. Non-root volume headers
have sroot blockset[i] whose type is HAMMER2_BREF_TYPE_INVALID. Non-root
volume headers don't have boot/aux area, so freemap area start from
offset 0. Non-root volume headers are readonly and never updated after
creation. This means non-root volumes are just extra storage to extend
fs size and internally make up a single virtual volume whose size is
"total_size".

It currently doesn't automatically upgrade an existing version 1 fs to
version 2. Only newly created fs becomes version 2 for now.

2. volumes layout
=================
Basically similar to HAMMER1. A first block device argument provided for
newfs_hammer2(8) becomes the root volume, and if specified remaining
devices extend "total_size" as non-root volumes. All volumes except for
the last one have 1GiB (freemap level1) aligned "volu_size".

This means each volume's start offset within "total_size" is also 1GiB
(freemap level1) aligned. The start offsets of volumes are stored in
volu_loff[HAMMER2_MAX_VOLUMES]. Each volu_loff[n] (0 <= n < nvolumes)
represents start offset of volume n within "total_size". Unused volumes
have -1 for volu_loff[n].
e.g. If a fs consists of 1 volume, volu_loff[0] has 0 and rests have -1.
e.g. If a fs consists of 3 volumes, x GiB root volume, y GiB volume,
and z GiB volume, volu_loff[0] has 0, volu_loff[1] has x, volu_loff[2]
has x+y, and rests have -1.

Low level I/O function in HAMMER2 uses this linear offsets table to
determine a device vnode to use and relative offset within the device
vnode, for a given blockref's "data_off". This is different from HAMMER1
where logical offset had embedded volume id bits (i.e. there were holes
in logical address space). HAMMER2 needs this table to support multi-
volumes without changing current logical offset mechanism.

Unless all volumes are specified and mountable, mount_hammer2(8) fails
like it failed in HAMMER1. This also applies to other userspace commands
which require volumes specification, except for fstyp(8).

3. userspace commands
=====================
Basically same as or similar to HAMMER1.
* newfs_hammer2(8) takes a list of block device paths as argv[].
* mount_hammer2(8) takes block device paths or names in "a:b:c:..."
format.
* hammer2(8) takes block device paths or names in "a:b:c:..." format for
directives which require volumes specification. This commit also adds
"volume-list" directive and an ioctl command HAMMER2IOC_VOLUME_LIST,
which are similar to the one in HAMMER1.
* fsck_hammer2(8) takes device paths or names in "a:b:c:..." format.
* fstyp(8) takes device paths in "path1:path2:path3:..." format.

4. limitations
==============
* hammer2(8) "info" directive ignores multi-volumes block devices.
* hammer2(8) "growfs" directive doesn't support multi-volumes fs.
* fstyp(8) is unable to find PFS label via -l option if the PFS inode or
its parent indirect blocks are located beyond root volume.
* hammer2(8) doesn't support "volume-add" and "volume-del" directives
which existed in HAMMER1, and there is currently no plan to support.

show more ...

usr.sbin/fstyp: Minor HAMMER1 fixes

usr.sbin/fstyp: Minor HAMMER2 fixes

build - Fix building new sources on older systems

* Fix compile errors when doing a new buildwolrd on an old
base system.

top, vmstat, who, rwhod - Use CLOCK_UPTIME to calculate uptime

* Use CLOCK_UPTIME to calculate the system uptime instead of
subtracting current real time from boot real time, which could
get muf

top, vmstat, who, rwhod - Use CLOCK_UPTIME to calculate uptime

* Use CLOCK_UPTIME to calculate the system uptime instead of
subtracting current real time from boot real time, which could
get muffed up by setting the time.

show more ...