On Fri, 13 Apr 2001, IS wrote:
> I mean besides the Linux native and swap partition for what reason should I
> make partitions for /boot /home /usr /var etc.
>
> Once you setup the filesystem with all those partions what happens with the
> size of the filesystems when I add a new disk to my RAID array and expand
> the diskspace?
Lots of reasons. It makes it easy to manage the different partitions, each
which has their own needs and characteristics. If you have different
partitions for these different directories, you can normally do management
of them without having to affect the rest of the system.
For example, /usr is intended for binaries and libraries and other static
files, thus it is often mounted read-only as a security measure.
On the other hand, /var is written to often, with critical data. It is
normally a good idea to use a journaling file system for /var, though
journaling would normally be uneccessary for a volume like /usr
(especially if it is mounted read-only).
Personally, I like putting /home on a different physical drive(s), often
on an external array, because that is where most of my user data is, and
in the event of a catostrophic system failure, I can normally bring up the
critical user data within a minute or two, simply by mounting the external
array on another machine.
Unix systems recognize that different applications and different system
components have different performance, security, and availability
requirements. Rather than encouraging administrators to do the easy thing
and throw one's entire C: drive on a RAID5 or RAID10 monster drive,
splitting applications across different filesystems lets us tune different
filesystems for different applications, all happily co-existing on the
same system.
thornton
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
