Matthew Ahrens writes: > This project delivers the following executable perl script: > /usr/benchmarks/filebench/filebench
Not mentioned here is that this seems to establish a precedent for a directory called /usr/benchmarks, with subdirectories for each benchmark. It seems to be akin to /usr/demo/ (is that right?), but the semantics are somewhat unclear, as it seems unlikely that anyone would deliver more than handful of executables in any directory, and likely that it's just a single file per directory. Are there other things that might fit here? Future plans? An update to filesystem(5) to describe this new hierarchy would be helpful. > User Commands filebench(1) > > NAME > filebench - framework of workloads to measure and compare > filesystem performance Nit: since it's on a non-default path, I think this man page should include the full path. Would it make sense to have a new subsection (say, 1BENCH) to collect these man pages together? Otherwise, I think it seems a little odd to have things in section 1 that aren't going directly into /usr/bin. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
