Install the following applications, using whatever method is appropriate for your operating system: Devote the remainder of your disk to /home, as usage will likely grow rapidly if you have many users. Pretty much anything that belongs to your users, except for MySQL and PostgreSQL databases, will reside on /home. ![]() home: The home partition is where all of your domain users data, email, CGI scripts, logs etc. If users are expected to be heavy database users, you may opt to divide the remaining disk space between /var and /home. Depending on whether you will allow your domain users to use the database features, this partition may be between 2 GB and 10 or more GB. var: The /var partition is where system logs, various changing data, and MySQL and PostgreSQL databases are stored. Your OS vendor probably knows best what size this should be. boot: The /boot partition should be large enough to accommodate a few system kernels and initrd images. This partition should be at least 3.5 GB for most operating systems. : This partition is used for all of the operating system files, executables, and configuration files. Historically, multiple partitions were considered wise administrative policy, but most modern systems and backup utilities eliminate the reasons for utilizing multiple partitions. This layout spreads files across a few partitions, in order to facilitate usage some types of backup utility as well as making some types of administrative task easier (for example, installing larger disks for some partitions at a later time). Because of this, if you are using disk quotas, you probably want to make /home its own very large partition. In the case of mail delivery and processing, there are several very sneaky ways for this to cause failures of various types. Quotas apply to all files on a given partition, regardless of the directory. Note If you plan to use disk quotas, you should be aware of a few potential gotchas with this type of deployment. This is where all system and user data will go. : The remainder of the disk(s) should be devoted to /. boot: The /boot partition should be large enough to accomodate a few system kernels and initrd images. Swap: The swap partition should be at least twice the size of RAM on the system. Traditionally, "one big partition" was considered problematic from an administration standpoint, but most such issues have been resolved by modern filesystems, backup utilities, and improved hardware reliability. The system partition contains /home for users, /var for logs and databases, as well as all of the normal system executable files, documentation and libraries. In this partition layout, you will only have one system partition plus a swap partition and /boot partition. Other partition layouts may lead to incorrect configuration of filesystem quotas, but can be corrected after installation is completed if other partitioning schemes are preferred. Either partition scheme is supported by the Virtualmin Professional Installer. The partitions on your Virtualmin server should be allocated in one of the the following two ways, depending on your requirements and preference. If you are not extremely comfortable with your operating system, the services used in a hosting system, and performing various configuration tasks from the command line, you are advised to use the automatic installation on a Grade A supported operating system. ![]() ![]() This method, however, requires significantly more knowledge on the part of the person doing the installation, and a much larger time investment to insure that all necessary configuration is performed and all Virtualmin managed services are working correctly. Unlike the Automated Virtualmin Installation, to make use of this installation type, your OS does not need to be freshly installed, nor does it need to be a supported operating system.
0 Comments
Leave a Reply. |