hi ya braxton
On Wed, 17 Dec 2003, Braxton Neate wrote:
> I tend to agree with you that Adding more partitions, doesn't make the
> system more manageable.
yup.. it does make it more manageable per se
but it does allow you the luxury of fixing the system if ti goes bonkers
by having / be 128MB or 256MB instead of lots-n-lots of disk that has
to be clean before it can boot itself
> One partition I forgot to mention in my post was /boot, a lot of people
> recommend having the kernel on a separate partition. I'm guessing this
> wouldn't exceed 10MB but 50MB is probably a safe size.
the simplest install ... ( relatively sane way )
<swap> partition of some size
<rest of disk>
-- no other partitions --
-- why bother w/ partitions -- if one wants it simple
-- and this 2 partition scheme usually isntall itself by
default(?) so no typing/thinking is needed ??
-------
and getting back to making things messy:
/boot is NOT needed, unless the "kernel" is about the 1024 cylinder
boundry
- a left over artifact like swap == 2x real memory
( if one has 4GB of memory, in a large PC, does that mean
( we need 8GB of swap ?? ... nah.. not many apps need that
( much memory other that oracle and cae/cad simulations
( and bunch of special apps
and if you did have /boot ... how many 1MB sized kernels
does that /boot partition hold ???
1GB /boot implies about 1,000 kernels +/- :-)
( assuming you dont put anything else there )
if one is wondering about /boot ... it's more important toponder
the reasons for /tmp as a separate partition
c ta
alvin
> After pondering a few reply's I'm thinking of the following:
> /boot - 50MB
> / - 23GB (remembering that /usr & /home etc. will be directory's
> underneath this)
> /var - 15GB (will contain logs, websites, and SQL data)
> SWAP1 - 1GB
> SWAP2 - 1GB
>
> Apparently the kernel can balance loads between 2 swap partitions like
> it can with multiple processors, so it would make sense to have 2 1GB
> partitions rather than a 1 2GB partition. However this machine rarely
> swaps.
>
> Another question which arises is should I partition the disk in any
> particular order i.e. does it mater if / is hda1 or hda5?
>
> Thanks for everyone's replies!
>
> -Braxton
>
> -----Original Message-----
> From: David Z Maze [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 17 December 2003 1:59 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Web server Partitions
>
>
> "Braxton Neate" <[EMAIL PROTECTED]> writes:
>
> > I know this is a question that gets asked a lot, but googling around I
>
> > can't seem to find a good answer. I'm re-installing a web/sql server
> > which currently has one large root partition and a swap partition.
> > This is obviously not the best setup.
> >
> > I'm wondering what other people would recommend in the way of
> > partitioning?
> >
> > The server is a 2x 800mhz PIII with 512MB RAM and a 40GB hard drive.
>
> It depends on your exact needs. Assuming you have no normal interactive
> users, I'd probably set it up as
>
> /var/www -- "big enough", maybe 10-15 GB
> /var/lib/postgres (or whever) -- "big enough", maybe 10-15 GB
> swap -- 0.5-1 GB
> / -- Whatever's left
>
> On this sort of system, the main benefits you get from partitioning are
> fault isolation: if something gets confused on your root filesystem, and
> fsck can't recover it, you haven't lost your data. Alternatively, if you
> decide to reinstall the system, this partitioning scheme lets you
> reinstall software but keep data. If you have a substantial amount of
> built-from-source software, you might also consider a partition for
> /usr/local for similar reasons.
>
> Adding more partitions, in my experience, doesn't make the system more
> manageable; a common thing to happen is to install the system with a
> small /var partition and then later realize that using APT is painful
> because it wants lots of space in /var/cache/apt. Or you make /usr too
> small, or /tmp too small, and run into problems later on.
>
> --
> David Maze [EMAIL PROTECTED]
> http://people.debian.org/~dmaze/
> "Theoretical politics is interesting. Politicking should be illegal."
> -- Abra Mitchell
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
