From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Gentoo as a production server - insecure?
Date: Mon, 16 Feb 2009 22:36:40 +0000 [thread overview]
Message-ID: <20090216223640.44844ab8@krikkit> (raw)
In-Reply-To: <loom.20090216T144624-896@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
On Mon, 16 Feb 2009 15:51:11 +0000 (UTC), James wrote:
> If the rub is really the gcc compiler, then do not have it installed;
> activate a remote partition with any such tools as gcc, coreutils
> and use them for admin things. Then unmount these (NFS or such)
> necessary system tools, when your not actively using them.
Or don't install them at all. Put all the toolchain packages
in /etc/portage/profile/package.provided or create a custom profile
without a toolchain in @system. Then build the packages on another
computer. If this is a production server, you'd want to test things
before installing on the live server, so build everything on the test
box and install on the server with emerge -K.
--
Neil Bothwick
ALZHEIMER.COM found . . . Out of . . . something . .
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-02-16 22:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 12:05 [gentoo-user] Mailing Lists Kaushal Shriyan
2009-02-16 12:26 ` Etaoin Shrdlu
2009-02-16 12:48 ` [gentoo-user] Gentoo as a production server - insecure? Johannes Frandsen
2009-02-16 13:50 ` Mike Kazantsev
2009-02-16 14:27 ` Mick
2009-02-16 15:51 ` [gentoo-user] " James
2009-02-16 22:36 ` Neil Bothwick [this message]
2009-02-20 8:36 ` Mick
2009-02-16 17:33 ` [gentoo-user] " Dirk Heinrichs
2009-02-16 20:15 ` [gentoo-user] " james
2009-02-16 20:27 ` Matt Harrison
2009-02-16 20:33 ` Dirk Heinrichs
2009-02-16 21:35 ` James
2009-02-16 15:11 ` [gentoo-user] Mailing Lists Dan Cowsill
2009-02-16 16:35 ` Hilco Wijbenga
2009-02-17 14:06 ` Dan Cowsill
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=20090216223640.44844ab8@krikkit \
--to=neil@digimed.co.uk \
--cc=gentoo-user@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