From: "Phillip Ames" <phillip.ames@uconn.edu>
To: linux-newbie@vger.kernel.org
Subject: Advice about packages
Date: Wed, 1 Oct 2003 17:18:28 -0400 [thread overview]
Message-ID: <002901c38861$8ef4d0c0$0da16389@hyperion2> (raw)
Hi,
I'm relatively new to using Linux on a daily basis and I was looking for
some information about what the "trends" are for production Linux
machines. I installed RedHat 9, and have mucked about with rpm and
thought that packages were the greatest thing since sliced bread.
However, in the course of my reading and playing I've noticed that many
places recommend that the binary executables actually be compiled by
your machine (with all its kernel options, etc.) which is sensible.
Everything is well when I ./configure them and then "make install" but
if there is an update to a particular product it seems very inconvenient
to upgrade versions. An example is the Apache httpd server - 1.3.xx
stores its served files in /var/www/html/ and the actual httpd daemon in
/usr/bin. Apache 2, however, sets the DocumentRoot as
/usr/local/apache2/htdocs/ and the binaries in /usr/local/apache2/bin/.
I know it's just a simple matter of changing the DocumentRoot entry in
the httpd.conf file for served documents but is there a better/easier
way to go about upgrading the binaries? Or is the de facto standard to
simply run ./configure --with-prefix=/usr/bin? Any advice would be
appreciated. Thanks,
-Phil
-
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 reply other threads:[~2003-10-01 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 21:18 Phillip Ames [this message]
2003-10-01 21:42 ` Advice about packages James Miller (office)
2003-10-02 6:58 ` Nathan Clayton
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='002901c38861$8ef4d0c0$0da16389@hyperion2' \
--to=phillip.ames@uconn.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox