[OpenAFS] SUN Solaris package for Openafs.

[Lester Barrows]

I'll have to second that. I was required to build a cell from scratch with 
whatever documentation available, if the paths had been changed it wouldn't 
have been nearly as pleasant an experience. Luckily, I was using the RH SRPMs 
with transarc paths and everything more or less made sense, with a bit of 
google and openafs-info on the side. If paths start jumping around on every 
platform (although they already have on OS X, and of course Windows is 
another world) it's going to be more difficult to maintain the documentation.

In my experience, good documentation is the difference between having to 
answer a question once or every time someone has the problem. As nice as the 
wiki is, I would have been lost if that's all I had to work with when I was 
bringing our cell up. The more accurate the docs are, the less likely new 
users are to ask questions which seem silly or obvious to longtime users. :-)

Regards,

Lester Barrows
Asani Solutions, LLC
Code IC Systems Group
NASA Ames Research Center

On Wednesday 07 April 2004 14:26, ted creedon wrote:
> >From my own learning experience non-transarc paths makes the IBM
>
> documentation extremely hard to follow. Fortunately the ./configure
> --with-transarc-paths in the make solves this  problem.
>
> tedc
>
> -----Original Message-----
> From: openafs-info-admin@openafs.org
> [mailto:openafs-info-admin@openafs.org] On Behalf Of Hendrik Hoeth
> Sent: Wednesday, April 07, 2004 2:01 PM
> To: openafs-info@openafs.org
> Subject: Re: [OpenAFS] SUN Solaris package for Openafs.
>
> Thus spake Derrick J Brashear (shadow@dementia.org):
> > Hopefully more than just you and me will speak up.
> >
> > Me, I use transarc paths;-)
>
> Of course I use transarc paths  ;)