Re: Standard place for Bash Scripts

2005-09-30 Thread John Hasler
Stephen R. Laniel writes: > If you want them to be available to all users, I suspect the canonical > answer would be /usr/bin. Don't put local software in /usr/bin. It may collide with something installed by the package manager. Put it in /usr/local/bin. That's what it's for (except on BSD). -

Re: Standard place for Bash Scripts

2005-09-30 Thread Alvin Oga
On Fri, 30 Sep 2005, Stephen R Laniel wrote: > On Fri, Sep 30, 2005 at 07:47:14AM -0400, Scott Fitzgerald wrote: > > I was wondering if there was a standard place for bash scripts. A > > convention or "normal place" where they can be placed to be turned into a > > command, accessable to all use

Re: Standard place for Bash Scripts

2005-09-30 Thread John Hasler
Scotty writes: > I was wondering if there was a standard place for bash scripts. A > convention or "normal place" where they can be placed to be turned into a > command, accessable to all users. /usr/local/bin, of course. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a su

Re: Standard place for Bash Scripts

2005-09-30 Thread Stephen R Laniel
On Fri, Sep 30, 2005 at 07:47:14AM -0400, Scott Fitzgerald wrote: > I was wondering if there was a standard place for bash scripts. A > convention or "normal place" where they can be placed to be turned into a > command, accessable to all users. If you want them to be available to all users, I su

Re: Standard place for Bash Scripts

2005-09-30 Thread michael
On Fri, 2005-09-30 at 07:47 -0400, Scott Fitzgerald wrote: > I was wondering if there was a standard place for bash scripts. A > convention or "normal place" where they can be placed to be turned into a > command, accessable to all users. /usr/local/bin but users will have to ensure that's in th