/dev/null affected by unlink process, which is not good and leads to hiding null from devfs tree.
It must be immunable to unlinking
Fix:
unknown :(
How-To-Repeat:
please run this small script (part of one configure script)
------------------
#!/bis/sh
cat >conftest.cpp <<EOF
int main() { return 0; }
EOF
gcc -o /dev/null conftest.cpp
------------------
after gcc ends node /dev/null will be absent and not autorecovered to
available state.

I can't replicate this on a recent 9-CURRENT installation: running 'g++ -o
/dev/null conftest.cpp' (gcc gives an error) as a normal user does nothing,
and as root it just updates the permissions to add execute permission.
--
Bruce Cran

I've just started poking around the PR's to try to learn and help out, =
and this one looked like a good first try..
Sure enough, as root on 9.0 -CURRENT I can "rm /dev/null" and it does =
unlink and is missing. However, I just recreate it with mknod /dev/null =
c 0 6 .. the behavior is identical on 8.2-RELEASE.
Am I missing something here? Is there some kind of new default behavior =
that should be implemented here?=20=