Re: misc/57877: /etc/mtree/set.* is not automatically tested and doesn't always match installation

[Taylor R Campbell <riastradh%NetBSD.org@localhost>]

The following reply was made to PR misc/57877; it has been noted by GNATS.

From: Taylor R Campbell <riastradh%NetBSD.org@localhost>
To: gnats-bugs%NetBSD.org@localhost, netbsd-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: misc/57877: /etc/mtree/set.* is not automatically tested and doesn't always match installation
Date: Thu, 25 Jan 2024 23:47:07 +0000

 Amazingly, only two files are troublesome in these tests, according to
 the i386 testbed:
 
 https://releng.netbsd.org/b5reports/i386/2024/2024.01.25.19.12.49/test.html=
 #usr.bin_mtree_t_sets_set_base
 
    check_mtree
    Fail: incorrect exit status: 2, expected: 0
    stdout:
    dev/pts:=20
            permissions (0755, 0555)
    ./var/run/named missing
 
    stderr:
 
 I think we can just:
 
 1. fix the permissions on dev/pts in src/etc/NetBSD.dist.base, since
    it never makes sense for userland to write to files here --
    /dev/pts is always intended to have ptyfs mounted; and
 
 2. delete var/run/named from src/etc/NetBSD.dist.base, since it gets
    deleted on every boot by rc.d/clearcritlocal (which is presumably
    why it's reported missing here), so anything that relies on
    /var/run/named at boot has to recreate it anyway.
 
 
 P.S.  OOPS: mtree lives at /usr/sbin/mtree, so this test should have
       been put at tests/usr.sbin/mtree, not tests/usr.bin/mtree.