Filebench [PSARC/2007/448 FastTrack timeout 08/16/2007]

[James Carlson]

eric kustarz writes:
> Bart mentioned that he would like more than just a single executable  
> in the libmicro directory.  Something like:
> /usr/benchmarks/libmicro/libmicro (executable)
> /usr/benchmarks/libmicro/README
> /usr/benchmarks/libmicro/libmicro.tar.gz

If there's a reasonable man page, what would be in the README?

I'm really hesitant to ask what's in that tar.gz file.  That doesn't
look like a way to deliver packaged software.  :-/

If there's a good case to be made that directories would be needed
here, then I'm ok with it, but I don't quite see anything that
establishes that case.  That's particularly true given that the
"extra" stuff is tucked neatly away in /usr/lib/ where it won't hurt
anyone.

Perhaps a more complete explanation of /usr/benchmarks would help.

> > 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.
> 
> Whatever the ARC/manpage experts think is the right way is a-ok with me.

Given that it's a segregated collection of software, I think a
segregated set of man pages makes some sense.

It'll need a new /usr/man/man.cf entry, and should likely have some
sort brief Intro(1BENCH) page.

-- 
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