From: Barry.SCHWARTZ@chemoelectric.org
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Re: Upgrading from amd64 to ~amd64.
Date: Wed, 19 Oct 2005 11:06:19 -0500 [thread overview]
Message-ID: <20051019160619.GA4185@crud.crud.mn.org> (raw)
In-Reply-To: <pan.2005.10.19.15.35.39.239558@cox.net>
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
Duncan <1i5t5.duncan@cox.net> writes:
> Of course, part of that probably has to do with something else you
> mention, that whole apache-php-subversion thing. That implies the purpose
> of your installation is server related, and servers traditionally run more
> conservative settings, DEFINITELY so if they are publicly accessible or
> mission critical.
No, it's all very local. The only reason for running Apache is to use
a web-based application on my own box, just for me. I use amd64 for
that because ~amd64 often is broken at the ebuild level, due to all
the software independencies.
--
Barry.SCHWARTZ@chemoelectric.org http://www.chemoelectric.org
Esperantistoj rajtas skribi al Barijo.SXVARCO@chemoelectric.org
'And now we're going to go try to comfort people in that
part of the world.' -- Bush, referring to the southeastern U.S.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-10-19 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 2:50 [gentoo-amd64] Upgrading from amd64 to ~amd64 Toby Fisher
2005-10-18 3:09 ` Barry.SCHWARTZ
2005-10-18 3:15 ` Mark Knecht
2005-10-18 3:55 ` Richard Freeman
2005-10-18 11:09 ` [gentoo-amd64] " Duncan
2005-10-18 15:58 ` Scott Stoddard
2005-10-19 15:25 ` [gentoo-amd64] " Duncan
2005-10-18 20:25 ` [gentoo-amd64] " Barry.SCHWARTZ
2005-10-19 15:35 ` [gentoo-amd64] " Duncan
2005-10-19 16:06 ` Barry.SCHWARTZ [this message]
2005-10-18 20:29 ` [gentoo-amd64] " Barry.SCHWARTZ
2005-10-18 15:28 ` [gentoo-amd64] " Peter Humphrey
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=20051019160619.GA4185@crud.crud.mn.org \
--to=barry.schwartz@chemoelectric.org \
--cc=gentoo-amd64@lists.gentoo.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