From: Kyle Bader <kyle.bader@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Advice/best practices for a new Gentoo installation
Date: Fri, 26 Feb 2010 10:24:43 -0800 [thread overview]
Message-ID: <854dca5c1002261024k48b17392r8b59098a987b2938@mail.gmail.com> (raw)
In-Reply-To: <58965d8a1002260954v37bc6293xd4b92d82183bd346@mail.gmail.com>
> - be aware of cylinder boundaries when partitioning (thanks to the
> recent thread)
+1
> - utilizing device labels and/or volume labels instead of hoping
> /dev/sda stays /dev/sda always
+1
> - initrd - I've never used one, but maybe it's needed if root is on
> software RAID?
It's not technically needed and boot times are faster without them.
I'm a fan of statically compiled kernels too but that's more to
prevent malicious LKMs.
> - 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?)
putting portage on it's on partition is a good idea imo, I usually use
reiserfs because it handles large amounts of small files well.
> - some kind of small linux emergency/recovery partition? equivalent to
> a liveCD maybe.
I usually keep a bootable usb in my bag for recovery, which also works
if there is a problem with the disk/raid.
> - best filesystem for portage? something compressed or with small
> cluster size maybe.
reiserfs
> - SSD vs 10000rpm vs big-and-cheap hard drive for rootfs/system files.
> I lean toward the latter since RAM caches it anyway.
SSDs can make things snappier for boot times. Having lots of ram for
disk cache eliminates the benefit after booted since ram is even
faster than a SSD.
> - omit/reduce number of reserved-for-root blocks on partitions where
> it's not necessary.
I never get close to filling my disks so never have bothered with this
> - 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?
I'm not a fan, if you don't plan on changing your partition sizes I
don't see a lot of utility in adding the extra layer of complexity.
> - 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.
It's better than no raid but as you probably know it will only allow
for a single disk failure. Getting drives from different lots (but
same geometry) is recommended.
--
Kyle
next prev parent reply other threads:[~2010-02-26 18:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 17:54 [gentoo-user] Advice/best practices for a new Gentoo installation Paul Hartman
2010-02-26 18:24 ` Kyle Bader [this message]
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=854dca5c1002261024k48b17392r8b59098a987b2938@mail.gmail.com \
--to=kyle.bader@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