access point in the neighbourhood).
Complete list of channel attributes and list of management information element
payload.
While here, use estrlcpy instead of strncpy.
From FreeBSD ifconfig and net80211
- Use errx(3) in the appropiate function rather than warn(4) and
returning EXIT_SUCCESS all the time.
- Remove another case where it checks the device passed string will be
the same than in bv_dev.
one in bv_dev, which in some drivers like arcmsr(4) it contains the
volume name.
While I'm here, fix the formatting output so that it fits with arcmsr(4),
like:
$ sudo bioctl -h arcmsr0
Volume Status Size Device
arcmsr0 0 Building 698G ARC-1210-VOL#00 RAID5 96% done
0 Online 234G 0:0.0 noencl <WDC WD2500YS-01SHB1 20.06C06>
1 Online 234G 0:1.0 noencl <WDC WD2500YS-01SHB1 20.06C06>
2 Online 234G 0:2.0 noencl <WDC WD2500YS-01SHB1 20.06C06>
3 Online 234G 0:3.0 noencl <WDC WD2500YS-01SHB1 20.06C06>
$
Don't change default to the boot volume until after we've found we aren't
doing -F.
For tool-fdisk enforce -F and use #defines to make code that can no
longer possibly execute compile.
it's still reasonable and some kernel code seems to assume it
(otherwise some inode numbers of directories could be corrupted).
XXX: not sure if odd e2fs_ipg is valid or not in ext2fs spec.
- initialize inode generation numbers with random numbers for NFS
like newfs(8) as man page said
XXX: sys/ufs/ext2fs/ext2fs_alloc.c:ext2fs_valloc() seems to override
these generated numbers.
- replace a magic number with a macro
- fix several printf format
- fix possble block sizes for zap_old_sblock()
- use err(3) rather than errx(3) + strerror(errno)
- fix a typo
- misc cosmetics
This is based on the newfs(8) command for ffs, but
most ext2fs specific part is written from scratch.
Tested on alpha, cobalt, i386 and sgimips with some disks and vnd(4),
and at least cobalt's firmware can load boot files from an ext2fs
E2FS_REV0 partition created by this native newfs_ext2fs(8) command.
Closes PR bin/16175.
and "BLK(S) MISSING IN BIT MAP #N" reports on newer ext2fs with
EXT2F_COMPAT_RESIZE feature by accounting blocks in EXT2_RESIZEINO.
XXX1: Should we account blocks allocated by all other reserved inodes?
XXX2: We should really check and fix EXT2_RESIZEINO accordingly.
this because we do have a working raidframe(4).
- Miscellaneous cleanups and make the code WARNS=4 compliant.
- Removed all stuff that doesn't apply to NetBSD.
riz