home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.next.sysadmin:4938 comp.unix.admin:4783
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!crdgw1!ge-dab!puma.ATL.GE.COM!rsnyder
- From: rsnyder@atl.ge.com (Bob Snyder)
- Newsgroups: comp.sys.next.sysadmin,comp.unix.admin
- Subject: Re: Vendors Considered Evil (Re: Perl use over NFS)
- Message-ID: <1992Aug30.215306.12595@puma.ATL.GE.COM>
- Date: 30 Aug 92 21:53:06 GMT
- References: <1992Aug28.155801.14501@sei.cmu.edu> <1992Aug28.180137.22861@ra.msstate.edu> <1992Aug28.183918.22664@sei.cmu.edu>
- Sender: news@puma.ATL.GE.COM (USENET News System)
- Organization: GE Aerospace, Advanced Technology Labs
- Lines: 24
-
- In article <1992Aug28.183918.22664@sei.cmu.edu> 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?
- >
- >I got the same response from someone else in private mail. Since I
- >don't make a habit of picking up a script and running it without
- >checking it over, I don't see changing the #! at the beginning to be
- >that big a deal.
-
- That's fine if you are the only user of the system. If you are the only one
- using your machine, stick perl in /usr/local/software/thats/really/neat, and
- even put sh wherever you want too.
-
- But when you have a multi-user environment, and new users coming in, they
- expect that programs will be in certain commonly known locations, like sh
- and perl. I don't neccesarily like where it goes, but that is where most
- people expect to find it.
-
- Bob
- --
- Bob Snyder, Computing Services, GE Aerospace, Advanced Technology Labs
- rsnyder@atl.ge.com, (609) 866-6672, FAX: (609) 866-6397, DialComm 8*777-6672
-