On Aug 3, 2007, at 11:21 AM, James Carlson wrote:
> eric kustarz writes:
>> We would then have the following executables:
>> /usr/benchmarks/filebench/bin/filebench (executable perl script)
>> /usr/benchmarks/filebench/bin/go_filebench (isaexec link)
>> /usr/benchmarks/filebench/bin/{i386,amd64,sparcv9}/go_filebench
>> (executable binary)
>
> Whew.
>
> That's quite wordy, but if it works for you, it's ok by me.
Just have to put /usr/benchmarks/filebench/bin in your PATH :)
>
> It was the mix of /usr/benchmarks/<subdir> and /usr/lib/<stuff> that I
> found confusing. If it's like /usr/games or /usr/ucb, then binaries
> alone should go in /usr/benchmarks and the rest belongs in /usr/lib as
> you had it. If it's like /usr/demos, then just directories belong
> there.
>
> I'm not sure how clear the answer will be to users, but that's the
> clarification I was looking for.
Cool. Yeah there's basically two routes we can go (the so-called "to
bin or not to bin"):
1) /usr/bin/filebench (with private files in /usr/lib/filebench)
2) everything under /usr/benchmarks/filebench
Michael and Bart were very strong advocates of /usr/benchmarks
(looking to the future). Seems like a reasonable thing to me.
I'll update the PSARC case and send it out.
eric
