From: Hamish Moffatt <hamish@cloud.net.au>
To: linux-hams@vger.kernel.org
Subject: Re: Installing ham packages
Date: Fri, 24 Feb 2006 00:10:20 +1100 [thread overview]
Message-ID: <20060223131020.GB8873@cloud.net.au> (raw)
In-Reply-To: <43FD5C52.8080808@jnos.org>
On Wed, Feb 22, 2006 at 10:55:14PM -0800, Bill Vodall WA7NWP wrote:
> Ok --- where do they go.
>
> conversd goes in /opt/converd/(etc|bin...)
> aprsd
> jnos
> digi_ned
>
> etc?
[...]
> What's the gospel these days? Where should we be installing the ham
> packages and putting their configuration files?
You, as the system admin, are encouraged to install into /usr/local.
/usr is reserved for your distribution to use.
/opt is reserved for third party packages (although your distribution
might use them too). Or you could use it.
/usr/local is definitely reserved for you to install things directly
from source code.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2006-02-23 13:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 0:34 AX.25 for dummies Chris Hare, W5CDN
2006-02-21 16:20 ` Curt, WE7U
2006-02-21 17:28 ` Jeremy Utley
2006-02-21 18:06 ` Jack Sterba
2006-02-21 18:28 ` Chris Hare, W5CDN
2006-02-22 2:29 ` Curt Mills
2006-02-21 19:24 ` Jeremy Utley
2006-02-21 20:39 ` Jack Sterba
2006-02-21 19:22 ` Net2kiss - multiple ports Bill Vodall WA7NWP
2006-02-22 8:32 ` Richard Adams
2006-02-22 16:11 ` Bill Vodall
2006-02-23 6:55 ` Installing ham packages Bill Vodall WA7NWP
2006-02-23 13:10 ` Hamish Moffatt [this message]
2006-02-23 14:34 ` Bill Vodall
2006-02-23 15:39 ` LinuxNode (2) Luigi - IK5ZUK
2006-02-23 16:08 ` Brett Mueller
2006-02-23 20:04 ` Installing ham packages Curt Mills
2006-03-09 5:35 ` Serial extenion cable Bill
2006-03-09 14:58 ` Curt, WE7U
2006-03-09 15:24 ` Braddock
2006-03-09 15:30 ` Curt, WE7U
2006-03-09 17:13 ` Bill Vodall WA7NWP
2006-03-10 15:20 ` Serial extenion cable - now CONVAPRS Bill Vodall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060223131020.GB8873@cloud.net.au \
--to=hamish@cloud.net.au \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.