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).
-
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
>
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
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 availa
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
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.
---
Scotty
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Tro
6 matches
Mail list logo
