Mailinglist Archive: opensuse (2217 mails)

< Previous Next >
Re: [opensuse] Best Disk Layout
  • From: Aaron Kulkis <akulkis3@xxxxxxxxxx>
  • Date: Wed, 19 Sep 2007 03:08:38 -0400
  • Message-id: <46F0CAF6.5000203@xxxxxxxxxx>
Carlos E. R. wrote:
Hash: SHA1

The Wednesday 2007-09-19 at 12:43 +1200, Robin Klitscher wrote:

Given that space will not be a problem of itself (two SATA 320 GB disks,
non-RAID), what layout would make sense?  I want to do individual partitions
for /, /boot, and /home; but what about others?  What about /usr, or /var?
What are the plusses and minuses involved (a lot of Net afficionados refer to
these but don't explain what they are)?

Opinions or advice will be gratefully received.   Thank you.

There is a discussion of this in the SuSE admin book - I forget the correct name now, but you have the rpm - if you don't find the piece, I'll try to find a link to the chapter I mean tomorrow.

That section is so outdated it's not even funny. It's written as if 2 GB of disk
space is something only wildly profitable corporations would buy.

You don't really need those partitions if you don't know why you would need them ;-)

BAD advice.

So if I don't know why something is under the hood of my car, I should just
take it off of my engine????

However, you can get some speed gain by having, say, / in one disk and /usr in other, or by having the swap space distributed on both disks (same priority). Then, If you have a web/ftp server, you might think of separating /srv to its own partition (same motivation as for /home).

There are many considerations for doing such things, but normally there is no need; unless you know you need them, in which case you wouldn't be asking - which is another way of saying what I wrote two paragraphs above ;-)

You can simply leave space unpartitioned and decide later.

- -- Cheers,
       Carlos E. R.

Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Made with pgp4pine 1.76


To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups