public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Stefan G. Weichinger" <lists@xunil.at>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: btrfs and gcc 4.9
Date: Sun, 09 Nov 2014 14:09:40 +0100	[thread overview]
Message-ID: <545F6794.9060105@xunil.at> (raw)
In-Reply-To: <loom.20141108T222935-144@post.gmane.org>

Am 08.11.2014 um 23:17 schrieb James:

> I'm trying to keep it as simple as possible (the old boot root swap 
> type of approach for btrfs is all I'm after for now. (simple).
> 
> I have several system to experiment on, so once I get it figured out,
> I'll try a more agressive set up. For now it's everything under
> /root/ with subvolumes created under /root partition ?
> 
> 
> /usr/local/  is the only thing I do special. The /home dir
> is just me. So I'm trying to keep this simple and get
> it working on 3 old boxes.. 

General rule(s) for subvolumes as I learned them:

* create them if you want to separate things logically

* use them if you want to use specific settings/parameters for specific
directories/subvols: for example compression, quotas ...

* use them if you want to use snapshots. A (btrfs-)snapshot is always
based on a subvolume so if you want to create snapshots for particular
areas you have to set them up as subvolumes in advance.

Splitting it into /boot, /, /home and maybe /distfiles (no compression
here ... ?) is a usual approach. Keeping it as simple as possible in the
start is a good idea. You can always add subvols later ... and move
things over ...


As I see the howto and the steps about booting:

http://wiki.gentoo.org/wiki/Btrfs_native_system_root#Embedding_an_initram_filesystem

I didn't do it that way but used dracut for the initrd ... the
ml-archives have some threads around learning this (combined with
systemd and LVM stuff back then I spent quite some time ...).

Canek's tool kerninst also helps here:

https://github.com/canek-pelaez/kerninst



  parent reply	other threads:[~2014-11-09 13:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-08 20:27 [gentoo-user] btrfs and gcc 4.9 James
2014-11-08 21:07 ` Stefan G. Weichinger
2014-11-08 21:09   ` Stefan G. Weichinger
2014-11-08 22:17   ` [gentoo-user] " James
2014-11-08 22:40     ` Neil Bothwick
2014-11-09  2:58       ` James
2014-11-09 10:04         ` Neil Bothwick
2014-11-09 13:09     ` Stefan G. Weichinger [this message]
2014-11-10  0:36       ` James
2014-11-13 18:12         ` Stefan G. Weichinger
2014-11-13 20:34           ` Stefan G. Weichinger
2014-11-24 21:40             ` Stefan G. Weichinger

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=545F6794.9060105@xunil.at \
    --to=lists@xunil.at \
    --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