Correct and the file structures could be in an appendix.. There's a lot of other references to paths besides the executables.
Figuring out where this all is located and setting the partitions up is 1/2 the problem - if you're learning. tedc -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Derek Atkins Sent: Wednesday, April 07, 2004 3:56 PM To: Russ Allbery Cc: [EMAIL PROTECTED] Subject: Re: [OpenAFS] SUN Solaris package for Openafs. Russ Allbery <[EMAIL PROTECTED]> writes: > I think what we're hearing is not that this really bothers people > inherently, but that the documentation really needs to reflect the paths > so that people don't get confused. I think the paths can mostly be REMOVED from the documentation.. Or have a paragraph right at the beginning that explains how to find the right binary paths and add it to PATH. Granted, this requires changing the documentation, but that sounds like it would be a Good Thing. There is NO REASON that you need to specify "/usr/afs/bin/bos" in the documentation for every call. Admittedly you need to fix the BosConfig commands to point to the correct binary paths, but AFAIK that's the only place where full paths are important (well, and the location of the config files). -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH [EMAIL PROTECTED] PGP key available _______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info _______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
