On Fri, Jan 13, 2012 at 03:20:20PM +0200, Vitali wrote:
> On Fri, Jan 13, 2012 at 2:28 PM, Francois Pussault
> <fpussa...@contactoffice.fr> wrote:
> > I prefer to define my parts manualy like this
> > A / 256Mo
> > enough free space on the fastest disk in the machine
> >
>
> [cut]
>
> > When your /var will be full, it will not grow up, you have to purge some
> log
> > files (use logrotate or so will help), to purge read mails & print queues
> to
> > get free space.
> >
> > With a so huge /var 90% is anormal, you should already look for a logrotate
> > solution or choose a new partition map you will use on next update of the
> > machine.
> >
>
> After the installation procedure is over I relink the /tmp to /usr/tmp just
> mv /tmp /usr
> ln -s /usr/tmp /tmp
>
> Huge /var is need when I build mail servers under qmail which uses
> /var of course, and comparatively little /usr
> For DB servers (I compile Pg and My SQL's or LDAP by myself and
> install _everything_ into /usr/local/pgsql/*) I cut off a huge /usr
> partition, for example...
> Apache, which I also install into /usr/local/http/*, also assign a
> huge /usr partition.
Your systems sure are a pain for upgrading.... but if you are the only
one administrating them it is for you to waste your time like you want.
>
> There is one more philosophical side effect of this question - speed.
> The closer the partition is placed to the outer cylinders, the faster
> the data are read from it.
More a methaphysical question. On modern disks, the correspondence
between block/cyl number and physcial location is very blurred.
-Otto
