Jason Thorpe writes:
> On Wed, 09 Jul 1997 18:46:54 GMT 
>  laine@MorningStar.Com (Laine Stump) wrote:
> 
>  > >fsirand(8) had a serious bug that would cause it to damage file
>  > >systems larger than 4GB.  I've fixed this, and the change should show
>  > >up in tonight's update.
>  > 
>  > 1) Was this a problem in 1.2G?
> 
> Yes... of course, since we're still at 1.2G, it's now fixed in 1.2G :-)

Sorry, I meant specifically the snapshot in /pub/NetBSD/arch/i386 that
is called 1.2G. I didn't know -current still had that name.

> You can, of course, only update the fsirand(8) program itself if you
> want to run it on your file systems.  Or, you won't have a problem if
> you don't run fsirand(8) on them.
> 
> fsirand(8) is a program that randomizes the inode generation numbers on
> ffs file systems.

Thanks. If I had bothered to RTFM before sending my message, I probably
wouldn't have needed to send it...