From: "Christoph" <christoph23@charter.net>
To: linux-newbie@vger.kernel.org
Subject: Install location(s)
Date: Mon, 8 Apr 2002 14:29:51 -0500 [thread overview]
Message-ID: <007a01c1df33$c2ee2e40$8c01a8c0@wild.net> (raw)
In-Reply-To: m3ofgui987.fsf@wobble.eth.net
Apologies if this is a stupid question. And apologies for all
the stupid questions that are sure to come from me in the
weeks to follow. :p I take heart that since this is a newbie
list, I'm sure that you guys have fielded plenty.
In any case, my question: where should you typically install
new software? For example, I'm getting ready to look into
and install Samba on my Linux (RH 7.2) box. I've DL'd it
already and have been reading the documentation but have
yet to make and install it. So, where should it (and anything
else I plan to install) go to make it easier to manage and
administer?
thnx,
Christoph
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2002-04-08 19:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 13:57 a simple browser G Anna
2002-04-08 16:30 ` Elias Athanasopoulos
2002-04-08 16:32 ` Pierre Rousselet
2002-04-08 19:29 ` Christoph [this message]
2002-04-08 21:02 ` Install location(s) Pierre Rousselet
2002-04-09 6:02 ` a simple browser cr
2002-04-09 12:46 ` ichi
2002-04-09 15:54 ` Sean Rima
2003-03-12 7:02 ` pshook
2003-03-12 12:30 ` Rodrigo Gesswein
2003-03-12 12:57 ` Mateusz Łoskot
2003-03-12 14:39 ` James Miller
2003-03-12 14:54 ` Mateusz Łoskot
2003-03-12 15:06 ` Carl
2003-03-12 15:54 ` Mateusz Łoskot
2003-03-12 18:28 ` James Miller
2003-03-12 19:16 ` Haines Brown
2003-03-13 8:10 ` ichi
2003-03-13 1:25 ` Haines Brown
-- strict thread matches above, loose matches on Subject: below --
2002-04-08 20:10 Install location(s) Ray Olszewski
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='007a01c1df33$c2ee2e40$8c01a8c0@wild.net' \
--to=christoph23@charter.net \
--cc=linux-newbie@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.