On 31-May-00 Chad W. Skinner wrote:
> I have been reading about HD partitioning for server systems and security
> and am wondering what others think about the topic. This is a somewhat
> personal topic as well since I am getting ready to reinstall my system.
>
> I have read that it is a good idea to have a boot partition and a root
> partition. As far as I can tell the only reason for this is to ensure the
> boot partition is below the 1024th Cylindar. Does anyone know if this is
> true?
I believe that this is the reason.
> The other recommended partitions are /, /var, /var/log, /home, /usr,
> /usr/local, /home and swap. The reasoning behind these as I understand it is
> as follow.
>
> /var - to store email, news and other variable information
> /var/log - to store log files (on a separate partition on
> email systems so as a syslog DOS attack can not
> drop email services)
> /usr - stores system wide programs (on redhat the RPM files)
> [mounted ro to prevent changes]
> /usr/local - all other applications on a separate partition limiting
> errors during updates. [mounted rw]
> /home - User personal files.
depending upon your needs, and usage of 3rd party software, you might also
wish to have a "/opt" - functionally /opt is like /usr/local.
> Does anyone know formulas to assist with the decision on how big to make
> each of these filesystems and does this seem excessive on a production
> server?
/usr will depend upon the installed system. can be anything from 500 mb on a
minimal system to 2gb on a system that unpacks the .src.rpc into
/usr/src/redhat, and then rebuilds the packages.
I used to do 1gb /usr partitions, and as of rh62, I find 1gb to be quite tight
on a mostly loaded system.
> Also where is the recommended place to create storage space for group
> projects, I am assuming /usr/local?
I wouldn't think so on this.
I would use /usr/local for locally installed packages, and header files,
packages which I/we have built locally. /usr/local will probably be between
a few hundred mb to half a gig, depending upon the availability of disk space.
for project space, I would encourage you to mount a separate partition. I've
worked in several large unix environments, and which the names of the auxiliary
partition has differed from company to company (or system administrator to
system administrator), the basic idea has been the same.
create a mountable partition, which will be several hundred mb per developer
(depending, of course, upon the disk requirements for development trees).
I've see it mounted as /home/WIP (as in Work In Progress), but you can name it
anything. underneate there, each developer will have a directory, and the
respective directory will be owned by the respective developer (with associated
group permissions - usually a common "project related" group). Developers will
either just cd to their WIP directory, or have a soft link from their home
directory, their choice.
> Is it a bad idea to move the web pages
> from /home/httpd/ to /usr/local/www?
no experiance, cannot comment.
regards,
-Greg
----------------------------------
E-Mail: Gregory Hosler <[EMAIL PROTECTED]>
Date: 31-May-00
Time: 16:15:10
Black holes are where God divided by zero.
----------------------------------
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
