public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Intel Atom: architecture, distcc, crossdev and compile flags
Date: Thu, 13 Dec 2012 08:06:25 +0000	[thread overview]
Message-ID: <20121213080625.649dc5ba@digimed.co.uk> (raw)
In-Reply-To: <50C8C1AF.4010506@binarywings.net>

[-- Attachment #1: Type: text/plain, Size: 675 bytes --]

On Wed, 12 Dec 2012 18:41:03 +0100, Florian Philipp wrote:

> >> I personally see no reason for encrypting root as there is nothing of
> >> interest in there.  
> > 
> > No passwords in /etc? The main reason I encrypt / is that wicd keeps
> > its passwords in /etc.
> >  
> 
> I substitute with symlinks to /var/lib/*, /srv/* or similar.

I used to do that, although I linked to /home/etc, but I found myself
adding more and more and worried about missing something important. So I
decided to learn how to create an initramfs and now have all but /boot
(and sometimes /usr) encrypted.


-- 
Neil Bothwick

Top Oxymorons Number 5: Twelve-ounce pound cake

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-12-13  8:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11 17:36 [gentoo-user] Intel Atom: architecture, distcc, crossdev and compile flags Frank Steinmetzger
2012-12-11 19:40 ` Norman Invasion
2012-12-11 20:20 ` Florian Philipp
2012-12-12  1:40   ` Frank Steinmetzger
2012-12-12  8:16     ` Florian Philipp
2012-12-12  9:40       ` Neil Bothwick
2012-12-12 17:41         ` Florian Philipp
2012-12-13  8:06           ` Neil Bothwick [this message]
2012-12-14 22:29       ` Frank Steinmetzger
2012-12-13 18:24     ` Volker Armin Hemmann
2012-12-11 20:23 ` Joseph
2012-12-12  8:32 ` Walter Dnes

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=20121213080625.649dc5ba@digimed.co.uk \
    --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