>>> In other words, find something
>>>else to clean up.
>>Yeah, like all the stuff that's been written to /dev/null over the years.
>>It must really be piling up. :;
> Wait until some doofus creates a package remove script that
> removes /dev/null and it gets created as a normal file.
I've told this story before, but maybe it's time for a repetition.
A colleague of mine added user "oracle" to group "sys", so that he could run
jobs that both dumped his Oracle databases and (via ufsdump) some related ufs
filing systems (/dev/rdsk/* devices having group=sys and group read access).
This was in the era when the /dev directory had group=sys and group-*write* access.
When he next ran the Oracle installer, and was asked where he wanted some diagnostic
output sent, he specified "/dev/null" (perfectly standard practice).
Sometime later he observed various strange effects, which in due course he traced
to the fact that /dev/null was now a regular file with curious contents.
It turned out that the Oracle installer had helpfully removed the "old" /dev/null
and recreated it. If it had failed, of course, it would not have complained, but
just used the existing /dev/null as intended.
There's probably a moral, but it may be difficult to say exactly what it is.
Email: cet1 [at] cam.ac.uk