>Number:         3849
>Category:       bin
>Synopsis:       newfs does not initialize file system with random inodes
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jul  9 16:05:01 1997
>Last-Modified:
>Originator:     John Kohl
>Organization:
NetBSD Kernel Hackers `R` Us
>Release:        NetBSD-current, 1997/07/09
>Environment:
	
System: NetBSD pattern.arlington-heights.ma.us 1.2G NetBSD 1.2G (PATTERN) #14: Tue Jul 8 21:57:42 EDT 1997 jtk@pattern.arlington-heights.ma.us:/u4/sandbox/src/sys/arch/i386/compile/PATTERN i386


>Description:
	Other UNIXes I've used run fsirand automatically from newfs;
still others initialize the inodes as they build the file system with
"random" generation numbers.
	Shouldn't NetBSD do this automatically for ffs-style file systems?

>How-To-Repeat:
	newfs a vnd device, examine it with 'fsirand -p'
>Fix:
	
>Audit-Trail:
>Unformatted: