Re: HEADS UP: UFS2 extended attribute changes will be committed tomorrow
On Mon, Nov 21, 2022 at 10:10:57PM -0800, Chuck Silvers wrote: > yes, there should be a way to tell sysinst to create UFS2ea rather than UFS2 > (or vice-versa if we make UFS2ea the default in sysinst). this was on my > list of outstanding issues but I think I was thinking that Martin would > take care of it (since he's been the one doing most of the sysinst changes > for a long time now). at any rate, either Martin or I will add this. I will add it soonish. Martin
Re: HEADS UP: UFS2 extended attribute changes will be committed tomorrow
On Fri, Nov 18, 2022 at 09:09:22AM +0100, Matthias Petermann wrote: > Hello Chuck, hello all > > I have done some tests with a current build. I did a complete > reinstallation. I noticed a few small things that I would like to point out. > Some of the things are probably not caused by the current commit, I just > want to mention them in the context from a user's point of view: > > - UFS2 seems to be the default in Sysinst when FFSv2 is selected. I did not > find a selection to explicitly choose UFS2ea. A new installation with UFS2ea > enabled FFSv2 as root filesystem is currently only possible via a detour > (conversion via fsck in single user mode). Would an addition of sysinst be > desirable here? yes, there should be a way to tell sysinst to create UFS2ea rather than UFS2 (or vice-versa if we make UFS2ea the default in sysinst). this was on my list of outstanding issues but I think I was thinking that Martin would take care of it (since he's been the one doing most of the sysinst changes for a long time now). at any rate, either Martin or I will add this. > - A FFSv2 with UFS2 (without ea) can be mounted without error message with > the option "posix1eacls". Only when trying to manipulate an ACL with setfacl > you get an error message "Operation not supported". Is this due to the fact > that the mount command generally does not check in advance whether the > addressed file system supports the options or does not know about them, or > is this a place where the magic bytes still have to be updated? that was an oversight. I think that it would be best to fail the mount if the fs being mounted cannot support a requested mount option like this. I'll add a check for that (though it may be a while before I can get to this). > - The mount option "posix1eacls" (I think there was a second ACL related > one?) is missing in the man page mount(8). I feel like I've seen this before > in a man page...was I looking for it in the wrong place? the other ACL option is "nfs4acls". I would have thought that mount options specific to certain file systems would go in the manpage for that file system's mount command (mount_ffs in this case), but it looks like some options that apply only to one file system type are documented in mount.8. however, most file-system-type-specific mount options and arguments are documented only in their respective mount_foo.8 manpages, and I think this is the better practice to follow. I'll add the acls options to mount_ffs.8 and see about moving some of the text in mount.8 to the appropriate mount_foo.8. > - The new fsck option "-c" to convert from UFS2 to UFS2es and vice versa is > missing in the man page fsck(8) as you noted in your later mail, this is documented only in the fsck_ffs manpage since it only applies to fsck_ffs and not the fs-independent fsck wrapper program. thanks for your feedback! -Chuck
daily CVS update output
Updating src tree: P src/distrib/sets/lists/base/shl.mi P src/distrib/sets/lists/debug/mi P src/distrib/sets/lists/debug/module.mi P src/distrib/sets/lists/man/mi P src/distrib/sets/lists/modules/mi P src/distrib/sets/lists/tests/mi P src/doc/CHANGES P src/etc/mtree/NetBSD.dist.tests P src/lib/lua/Makefile U src/lib/lua/libm/Makefile U src/lib/lua/libm/libm.c P src/sbin/gpt/gpt.c P src/sbin/gpt/resizedisk.c P src/share/man/man3lua/Makefile U src/share/man/man3lua/libm.3lua P src/share/man/man4/Makefile U src/share/man/man4/bmx280thp.4 P src/share/man/man4/iic.4 P src/sys/arch/hp300/dev/rd.c P src/sys/arch/hp300/dev/rdreg.h P src/sys/arch/hp300/stand/common/if_le.c P src/sys/arch/hp300/stand/common/rd.c P src/sys/arch/x86/include/specialreg.h U src/sys/dev/i2c/bmx280.c U src/sys/dev/i2c/bmx280reg.h U src/sys/dev/i2c/bmx280var.h P src/sys/dev/i2c/files.i2c P src/sys/dev/sysmon/sysmon_envsys_tables.c P src/sys/fs/union/union_vfsops.c P src/sys/modules/Makefile U src/sys/modules/bmx280thp/Makefile U src/sys/modules/bmx280thp/bmx280thp.ioconf P src/sys/netinet/ip_output.c P src/sys/sys/envsys.h P src/tests/lib/Makefile U src/tests/lib/lua/Makefile U src/tests/lib/lua/Makefile.inc U src/tests/lib/lua/libm/Makefile U src/tests/lib/lua/libm/h_lualibm.c U src/tests/lib/lua/libm/lualibm.lua U src/tests/lib/lua/libm/t_lualibm.sh P src/tests/sbin/fsck_ffs/t_extattr.sh P src/tests/sbin/gpt/t_gpt.sh P src/usr.sbin/envstat/envstat.8 P src/usr.sbin/envstat/envstat.c Updating xsrc tree: Killing core files: Updating file list: -rw-rw-r-- 1 srcmastr netbsd 42802111 Nov 22 03:03 ls-lRA.gz
Automated report: NetBSD-current/i386 build failure
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2022.11.21.22.01.33.
An extract from the build.sh output follows:
File is obsolete or flist is out of date ?
--
./usr/libdata/debug/usr/tests/lib/lua
./usr/libdata/debug/usr/tests/lib/lua/libm
= end of 2 extra files ===
*** Failed target: checkflist
*** Failed commands:
${SETSCMD} ${.CURDIR}/checkflist ${MAKEFLIST_FLAGS}
${CHECKFLIST_FLAGS} ${METALOG.unpriv}
=> cd /tmp/build/2022.11.21.22.01.33-i386/src/distrib/sets &&
DESTDIR=/tmp/build/2022.11.21.22.01.33-i386/destdir MACHINE=i386
MACHINE_ARCH=i386 AWK=/tmp/build/2022.11.21.22.01.33-i386/tools/bin/nbawk
CKSUM=/tmp/build/2022.11.21.22.01.33-i386/tools/bin/nbcksum
DB=/tmp/build/2022.11.21.22.01.33-i386/tools/bin/nbdb
EGREP=/tmp/build/2022.11.21.22.01.33-i386/tools/bin/nbgrep\ -E HOST_SH=/bin/sh
MAKE=/tmp/build/2022.11.21.22.01.33-i386/tools/bin/nbmake
MKTEMP=/tmp/build/2022.11.21.22.01.33-i386/tools/bin/nbmktemp
MTREE=/tmp/build/2022.11.21.22.01.33-i386/tools/bin/nbmtree
PAX=/tmp/build/2022.11.21.22.01.33-i386/tools/bin/nbpax COMPRESS_PROGRAM=gzip
GZIP=-n XZ_OPT=-9 TAR_SUFF=tgz
PKG_CREATE=/tmp/build/2022.11.21.22.01.33-i386/tools/bin/nbpkg_create
SED=/tmp/build/2022.11.21.22.01.33-i386/tools/bin/nbsed
TSORT=/tmp/build/2022.11.21.22.01.33-i386/tools/bin/nbtsort\ -q /bin/sh
/tmp/build/2022.11.21.22.01.33-i386/src/distrib/sets/checkflist -L base -M
/tmp/build/2022
.11.21.22.01.33-i386/destdir/METALOG.sanitised
*** [checkflist] Error code 1
nbmake[2]: stopped in /tmp/build/2022.11.21.22.01.33-i386/src/distrib/sets
1 error
nbmake[2]: stopped in /tmp/build/2022.11.21.22.01.33-i386/src/distrib/sets
nbmake[1]: stopped in /tmp/build/2022.11.21.22.01.33-i386/src
nbmake: stopped in /tmp/build/2022.11.21.22.01.33-i386/src
ERROR: Failed to make release
The following commits were made between the last successful build and
the failed build:
2022.11.21.21.24.00 brad src/share/man/man4/Makefile,v 1.730
2022.11.21.21.24.00 brad src/share/man/man4/bmx280thp.4,v 1.1
2022.11.21.21.24.01 brad src/distrib/sets/lists/debug/module.mi,v 1.22
2022.11.21.21.24.01 brad src/distrib/sets/lists/man/mi,v 1.1756
2022.11.21.21.24.01 brad src/distrib/sets/lists/modules/mi,v 1.156
2022.11.21.21.24.01 brad src/sys/dev/i2c/bmx280.c,v 1.1
2022.11.21.21.24.01 brad src/sys/dev/i2c/bmx280reg.h,v 1.1
2022.11.21.21.24.01 brad src/sys/dev/i2c/bmx280var.h,v 1.1
2022.11.21.21.24.01 brad src/sys/dev/i2c/files.i2c,v 1.125
2022.11.21.21.24.01 brad src/sys/dev/sysmon/sysmon_envsys_tables.c,v 1.14
2022.11.21.21.24.01 brad src/sys/modules/Makefile,v 1.273
2022.11.21.21.24.01 brad src/sys/modules/bmx280thp/Makefile,v 1.1
2022.11.21.21.24.01 brad src/sys/modules/bmx280thp/bmx280thp.ioconf,v 1.1
2022.11.21.21.24.01 brad src/sys/sys/envsys.h,v 1.39
2022.11.21.21.24.02 brad src/usr.sbin/envstat/envstat.8,v 1.67
2022.11.21.21.24.02 brad src/usr.sbin/envstat/envstat.c,v 1.103
2022.11.21.21.29.32 brad src/doc/CHANGES,v 1.2932
2022.11.21.21.29.32 brad src/share/man/man4/iic.4,v 1.35
2022.11.21.22.01.32 christos src/distrib/sets/lists/base/shl.mi,v 1.942
2022.11.21.22.01.32 christos src/distrib/sets/lists/debug/mi,v 1.392
2022.11.21.22.01.32 christos src/distrib/sets/lists/man/mi,v 1.1757
2022.11.21.22.01.33 christos src/distrib/sets/lists/tests/mi,v 1.1234
2022.11.21.22.01.33 christos src/etc/mtree/NetBSD.dist.tests,v 1.197
2022.11.21.22.01.33 christos src/lib/lua/Makefile,v 1.8
2022.11.21.22.01.33 christos src/lib/lua/libm/Makefile,v 1.1
2022.11.21.22.01.33 christos src/lib/lua/libm/libm.c,v 1.1
2022.11.21.22.01.33 christos src/share/man/man3lua/Makefile,v 1.8
2022.11.21.22.01.33 christos src/share/man/man3lua/libm.3lua,v 1.1
2022.11.21.22.01.33 christos src/tests/lib/Makefile,v 1.35
2022.11.21.22.01.33 christos src/tests/lib/lua/Makefile,v 1.1
2022.11.21.22.01.33 christos src/tests/lib/lua/Makefile.inc,v 1.1
2022.11.21.22.01.33 christos src/tests/lib/lua/libm/Makefile,v 1.1
2022.11.21.22.01.33 christos src/tests/lib/lua/libm/h_lualibm.c,v 1.1
2022.11.21.22.01.33 christos src/tests/lib/lua/libm/lualibm.lua,v 1.1
2022.11.21.22.01.33 christos src/tests/lib/lua/libm/t_lualibm.sh,v 1.1
Logs can be found at:
http://releng.NetBSD.org/b5reports/i386/commits-2022.11.html#2022.11.21.22.01.33
Automated report: NetBSD-current/i386 test failure
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: sbin/gpt/t_gpt:resize_2part The above test failed in each of the last 4 test runs, and passed in at least 26 consecutive runs before that. The following commits were made between the last successful test and the failed test: 2022.11.20.11.57.02 mlelstv src/sbin/gpt/destroy.c,v 1.14 2022.11.20.11.57.02 mlelstv src/sbin/gpt/gpt.c,v 1.83 2022.11.20.11.57.02 mlelstv src/sbin/gpt/gpt.h,v 1.44 2022.11.20.11.57.02 mlelstv src/sbin/gpt/resizedisk.c,v 1.19 Logs can be found at: http://releng.NetBSD.org/b5reports/i386/commits-2022.11.html#2022.11.20.11.57.02
Re: Installation of liblua fails
My attempt: as NetBSD wont boot from stick or even ISO (neauveu cant
initialise X server), I thought, I do a virtual machine distribution
built and it ends up in install liblua {Error 1}; no hint, nothing.
What to do?
If you want to make the system boot and it's not booting because of
nouveau, then you can disable nouveau by using the boot menu to drop to
the command line:
userconf disable nouveau
boot
When you've got a booted system, you can edit /boot.cfg to disable nouveau
like so:
menu=Boot normally:rndseed /var/db/entropy-file;userconf disable nouveau;boot
John
