public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Advice/best practices for a new Gentoo installation
Date: Fri, 26 Feb 2010 11:54:13 -0600	[thread overview]
Message-ID: <58965d8a1002260954v37bc6293xd4b92d82183bd346@mail.gmail.com> (raw)

Hi, I'm building a new personal computer. I respect the opinion and
experience of the people on this list and am interested in anyone's
advice on the best way to set up my new Gentoo installation. Things
that you say "I wish I set mine up this way the first time..." or have
learned from experience how to do it right the first time already. :)

Some topics I'm thinking about (comments welcome):
- be aware of cylinder boundaries when partitioning (thanks to the
recent thread)
- utilizing device labels and/or volume labels instead of hoping
/dev/sda stays /dev/sda always
- initrd - I've never used one, but maybe it's needed if root is on
software RAID?
- grub/kernel parameter tips and tricks... i'm already using uvesafb,
and don't dual-boot with MSWin or anything, just Gentoo
- better partitioning scheme than my current root, boot, home (need
portage on its own, maybe /var as well?)
- some kind of small linux emergency/recovery partition? equivalent to
a liveCD maybe.
- best filesystem for portage? something compressed or with small
cluster size maybe.
- SSD vs 10000rpm vs big-and-cheap hard drive for rootfs/system files.
I lean toward the latter since RAM caches it anyway.
- omit/reduce number of reserved-for-root blocks on partitions where
it's not necessary.
- I have never used LVM and don't really know about it. Should I use
it? will it make life easier someday? or more difficult?
- Is RAID5 still a good balance for disk cost vs usable space vs data
safety? I can't/don't want to pay for full mirroring of all disks.

Or any other tips that apply to things which are difficult to change
once the system is in use.

It will be ~amd64 Gentoo using Intel Core i7 920 with 12GiB RAM. No
disks have been purchased yet.

Thanks



             reply	other threads:[~2010-02-26 17:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 17:54 Paul Hartman [this message]
2010-02-26 18:24 ` [gentoo-user] Advice/best practices for a new Gentoo installation Kyle Bader
2010-03-05 21:37   ` Paul Hartman
2010-02-26 19:22 ` Willie Wong
2010-02-26 19:38 ` BRM
2010-02-26 20:30 ` roundyz
2010-03-02  6:31 ` Frank Steinmetzger
2010-03-02  9:35 ` Alex Schuster
2010-03-02 10:10   ` Neil Bothwick
2010-03-02 14:43     ` Mick
2010-03-03 11:52     ` Alex Schuster
2010-03-03 12:27       ` Willie Wong
2010-03-03 16:34         ` Alex Schuster
2010-03-04 12:50           ` Walter Dnes
2010-03-03 12:30       ` Neil Bothwick
2010-03-03 16:03         ` Alex Schuster
2010-03-04 14:16           ` Alex Schuster
2010-03-04 14:17           ` Alex Schuster
2010-03-04 14:26           ` Alex Schuster

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=58965d8a1002260954v37bc6293xd4b92d82183bd346@mail.gmail.com \
    --to=paul.hartman+gentoo@gmail.com \
    --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