From: Wolfgang Weisselberg <weissel@netcologne.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Mandrake 8.1 and LVM
Date: Sat Dec 1 10:30:02 2001 [thread overview]
Message-ID: <20011201160437.C16319@tiger.bigcats.invalid> (raw)
In-Reply-To: <20011129190920.B23998@kluge.net>; from felicity@kluge.net on Thu, Nov 29, 2001 at 07:09:20PM -0500
Hi, Theo!
Theo Van Dinter (felicity@kluge.net) wrote 60 lines:
> My rule of thumb for disk layout on a server is:
> /boot - Small, usually 32-128MB, don't run out of space here.
You can also do a combined / and /boot. Give it enough space
and move everything where non-related changes happen away
from it. (128 to 256 MB should outlast your HD.) Non-LVM.
> / - I put /usr in here since there's no reason not to any
Personally I feel /usr really wants a separate partition.
You also may want partitions for /usr/src (if you have lots of
compiling/source code for the whole machine), and /usr/local
(if you use more than a few programs which are not on your
distribution). Sub-partitions are possible, depending on usage.
Long live LVM.
> /var - As someone's already stated, filling up /var can be a DoS.
If you have a news spool, put it on a separate partition --
it's just too different from size and lifetime compared to
/var. Unless you have a non-file/hardlink-based news system.
And then still move it out of the way.
If you have a WWW cache, that one might want a separate
partition as well -- and usually there's no need to backup
that cache.
> /tmp - Yet another possible DoS, don't allow user-writable areas
> to live on /. 128-512M should be sufficient, it's
> temporary space after all.
More -- especially with quotas. Sometimes people have to
download CD-Rom Images (e.g. .iso) and might be unable to put
them into /home.
Speaking of it -- /home probably wants a partition, too; and
regular backups.
-Wolfgang
next prev parent reply other threads:[~2001-12-01 10:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-29 15:53 [linux-lvm] Mandrake 8.1 and LVM Sarwer Zafiruddin
2001-11-29 16:01 ` mitch
2001-11-29 16:06 ` Steve Wray
2001-11-29 18:07 ` Theo Van Dinter
2001-11-30 1:59 ` Chad C. Walstrom
2001-11-30 2:40 ` Steve Wray
2001-11-30 14:18 ` Chad C. Walstrom
2001-11-30 15:53 ` mitch
2001-11-30 19:31 ` Chad C. Walstrom
2001-12-01 0:15 ` mitch
2001-11-30 16:00 ` Petro
2001-11-30 19:27 ` Chad C. Walstrom
2001-11-30 16:04 ` Steve Wray
2001-11-30 19:24 ` Chad C. Walstrom
2001-11-30 10:47 ` Theo Van Dinter
2001-11-30 11:37 ` Luca Berra
2001-11-30 12:02 ` svetljo
2001-12-02 8:24 ` Luca Berra
2001-12-01 10:30 ` Wolfgang Weisselberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-02 8:55 Luca Berra
2001-12-02 9:22 ` galia
[not found] <Pine.LNX.4.21.0111291810070.435-100000@sol.rune.org>
2001-11-29 17:12 ` Sarwer Zafiruddin
[not found] <Pine.LNX.4.21.0111291704150.435-100000@sol.rune.org>
2001-11-29 16:14 ` Sarwer Zafiruddin
2001-11-29 16:44 ` Steve Wray
2001-11-30 2:35 ` Luca Berra
2001-12-01 10:17 ` Brian J. Murrell
2001-11-29 7:58 Sarwer Zafiruddin
2001-11-29 11:15 ` Luca Berra
2001-11-29 15:04 ` Steve Wray
2001-11-29 15:16 ` Lars Kellogg-Stedman
2001-11-29 15:42 ` mitch
2001-11-29 15:56 ` Steve Wray
2001-11-29 19:09 ` Lars Kellogg-Stedman
2001-12-03 20:12 ` Mark van Walraven
2001-11-30 2:28 ` Luca Berra
2001-12-01 10:58 ` Brian J. Murrell
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=20011201160437.C16319@tiger.bigcats.invalid \
--to=weissel@netcologne.de \
--cc=linux-lvm@sistina.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.