home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.admin
- Path: sparky!uunet!munnari.oz.au!cs.mu.OZ.AU!munta.cs.mu.OZ.AU!zs
- From: zs@munta.cs.mu.OZ.AU (Zoltan Somogyi)
- Subject: Re: Vendors Considered Evil (Re: Perl use over NFS)
- Message-ID: <9224419.3248@mulga.cs.mu.OZ.AU>
- Sender: news@cs.mu.OZ.AU
- Organization: Computer Science, University of Melbourne, Australia
- References: <1992Aug27.180847.15448@kakwa.ucs.ualberta.ca> <1992Aug28.145234.17625@news.eng.convex.com> <1992Aug28.155801.14501@sei.cmu.edu> <1992Aug28.180137.22861@ra.msstate.edu> <1992Aug28.183918.22664@sei.cmu.edu>
- Date: Mon, 31 Aug 1992 09:23:16 GMT
- Lines: 23
-
- kochmar@sei.cmu.edu (John Kochmar) writes:
- >You've gotta be kidding, right? You're not advocating that perl be
- >placed in /usr/bin so that scripts you pick up from who-knows-where
- >will run without modification, right?
-
- No, that's not why you want it.
-
- I am regularly using several machines from several vendors. On all these
- machines except one, my home directory is NFS mounted, so that I see the
- same files when I log in. I have a ~/bin/sgi subdirectory, a ~/bin/sun4 etc,
- as well as a ~/bin/scripts. Whatever I put into ~/bin/scripts should work
- the same on every machine. This is true for scripts whose interpreters
- are in known standard locations, such as /bin/sh and /bin/awk*. It does
- not work if different machines put perl in different directories. Instead,
- I have to make several copies of the script and put them in ~/bin/<arch>,
- with the usual double maintenance problem if I ever need to fix or enhance
- the script.
-
- *: actually, for reasons best known to themselved SGI put awk in /usr/local/bin,
- causing this very problem.
-
- Zoltan Somogyi <zs@cs.mu.OZ.AU>
- Department of Computer Science, University of Melbourne, AUSTRALIA
-