svn commit: r365643 - head/bin/cp

[Scott Long]

>> normal means before devfs can be mounted.  However, several people have
>> looked and found no evidence on their system. This means there's something
>> special / unique to Rod's setup that's generating them (assuming it isn't a
>> simple chroot without devfs). What that is, and how they come to be, hasn't
>> been explained in enough detail to reproduce. That's what people are asking
>> Rod about: how do we get there? How did it happen? Once we know those
>> answers, we can fix it.
> 
> Problem is these are being found in after the fact analysis,
> so "getting there" is going to be hard.  I'll try to collect
> better data such as inode contents and dates and see if I 
> can correlate that to system install time, or some time during
> the systems life time.
> 
> Given what kib, and ian have said I am starting to suspect
> that this may be occuring during the install process, the
> dates on the null inode and a find of the oldest inode on
> the disk should correlate that next time I see one of these.
> 
> If I could easily reroduce it we would not be having
> this conversation, it would of been fixed.
> 

I just tested 11.2, 11.4, 12.0, 12.2 releases (or betas), and the most recent 13.0
snapshot.  I tested both UFS and ZFS installs to a local disk, used the stock
images, default bsdinstall options, stock everything.  After each install I mounted
the disk onto another system and examined the contents of the root filesystem.
In no case did I find any files in the /dev directory.  If there were previous bugs
with files being written to /dev during install, they’re long gone.  I’m going to
consider this problem closed and/or unique to Rod and his usage patterns.  Any
further extraordinary claims will need to be accompanied by extraordinary
proof.

Thanks,
Scott