begin quoting John Oliver as of Wed, Mar 21, 2007 at 11:45:19AM -0700:
> I have VMware Server running on my newest server, and want to create a
> template VM that I can copy and use for different purposes. I want to
> use a partitioning scheme that will give me the greatest flexibility to
> be able to use LVM to resize partitions as needed.
A VM probably doesn't need much in the way of filesystem structure,
and if it's using LVM for resizing, even less.
> What file systems should get their own partitions, and about what size?
> I always make /var it's own partition.
For two reasons: (a) so log files can't fill up all of your disk, and
(b) it can be mounted noexec.
> I'm sure /sbin should probably
> be on it's own.
I've always considered /sbin to be an essential part of /, along with
/etc, as it (a) doesn't change and (b) contains the stuff you need
for a minimal system.
> /tmp?
If you're in the habit of filling the disk with temp files (as I am),
then yes.
> /home seems like a good idea.
Yes, as that way user-data can persist across significant upgrades.
> /root Anything
> else? What do you use for partitions, and how much space do you
> allocate to relatively fixed ones like /sbin?
My most frequent technique is to install just about everything to a
single partition, use "du" to establish the sizes of the various
major pieces (/, /usr, /var, /opt, /usr/local, /home, etc.) and
use that as a map for baseline format, apply a multiplier, and then
I reformat and reinstall.
You want to leave lots of room in /var ('cuz that's where log files
live and grow), /opt and /usr/local ('cuz that's where the stuff
you add to the system goes), and /home ('cuz your data is actually
the important stuff on the machine).
However, I haven't done this in ages. For VM instances, I go with
a single partition (except for Zones).
--
I like tempfs, not because I need swap, but I like to grow /tmp.
Stewart Stremler
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
