Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Red Hat 7.2 disk partioning
- Thread starter NEFJ
- Start date
Hi,
This is one of those issues that is frequently debated and you'll find various schools of thought. If you were running a production (or otherwise important) system then there are good arguments for putting different parts of the directory tree on physically different drives and/or using raid, lvm, etc.
However, unless you need that kind of resilience, you are probably best off keeping it fairly simple and having a scheme like this:
swap : double your physical ram
/boot : approx 32mb unless you want to have a lot of different kernels to boot from at the same time, in which case increase the size accordingly.
/ : You need approx 3.4 gb for an 'everything' install and about 1.2gb for a 'workstation' install, i.e just for the packages without any spare space. So, either way, you would need as much extra space as you can get for your own files, new packages in the future, etc.
If you want to break '/' down into multiple partitions, obvious candidates for separate partitions are /home (if you have a lot of users or put your own stuff mostly there) and /usr .
For an install on a 1.1gb drive, you'll have to do a custom install and reduce the number of packages accordingly. Ultimately, linux can be put on a single floppy disk although the functionality is somewhat reduced !
Hope this helps
This is one of those issues that is frequently debated and you'll find various schools of thought. If you were running a production (or otherwise important) system then there are good arguments for putting different parts of the directory tree on physically different drives and/or using raid, lvm, etc.
However, unless you need that kind of resilience, you are probably best off keeping it fairly simple and having a scheme like this:
swap : double your physical ram
/boot : approx 32mb unless you want to have a lot of different kernels to boot from at the same time, in which case increase the size accordingly.
/ : You need approx 3.4 gb for an 'everything' install and about 1.2gb for a 'workstation' install, i.e just for the packages without any spare space. So, either way, you would need as much extra space as you can get for your own files, new packages in the future, etc.
If you want to break '/' down into multiple partitions, obvious candidates for separate partitions are /home (if you have a lot of users or put your own stuff mostly there) and /usr .
For an install on a 1.1gb drive, you'll have to do a custom install and reduce the number of packages accordingly. Ultimately, linux can be put on a single floppy disk although the functionality is somewhat reduced !
Hope this helps
Guest_imported
New member
- Jan 1, 1970
- 0
ifincham, how about /var? Where do you recommend document root files like html stuff to reside? Sometimes I hear /home, sometimes /var.
Hi,
It all depends how you prefer to lay it out and, to some extent, the way you do backups.
Redhat take the view that stuff like html files that don't belong to a 'real' user should be placed in /var (e.g. /var/ Apache) rather than somewhere under /home . I'd tend to agree with that but, then again, if you had set up Apache virtual hosts and people were uploading their own content you'd probably point their document root at somewhere under their $HOME directory.
The only directories you must have at all times on the '/' partition are :
/
/bin
/dev
/etc
/lib
/sbin
Anything else can be on another physical partition, a remote nfs mount, or any other filesystem type supported . Also, remember you can start with everything in '/' then move bits onto other partitions later. For example, you could get a new drive, create a ext2/3 partition and copy everything from (e.g.) /var to that partition then edit /etc/fstab so that your new partition was mounted at boot time as /var. Its a bit more fiddly in practice but you get the idea.
Regards
It all depends how you prefer to lay it out and, to some extent, the way you do backups.
Redhat take the view that stuff like html files that don't belong to a 'real' user should be placed in /var (e.g. /var/ Apache) rather than somewhere under /home . I'd tend to agree with that but, then again, if you had set up Apache virtual hosts and people were uploading their own content you'd probably point their document root at somewhere under their $HOME directory.
The only directories you must have at all times on the '/' partition are :
/
/bin
/dev
/etc
/lib
/sbin
Anything else can be on another physical partition, a remote nfs mount, or any other filesystem type supported . Also, remember you can start with everything in '/' then move bits onto other partitions later. For example, you could get a new drive, create a ext2/3 partition and copy everything from (e.g.) /var to that partition then edit /etc/fstab so that your new partition was mounted at boot time as /var. Its a bit more fiddly in practice but you get the idea.
Regards
I'm playing with RH7.2 at home this weekend, trying to set up a with MySQL and PHP (typical eCommerce stuff). What I chose for my 4.3gb EIDE was:
My reasoning was: I need /usr for the system and databases, and /var contains the website w/content. Swap is small because the machine's only got 64Mb RAM.
So far, still no luck getting to Apache from other machines on the LAN -- I suspect the firewall software is blocking port 80. Must track down the .conf file for it...
Chip H.
Code:
/ 384Mb
/boot 47Mb
/usr 1396Mb
/home 510Mb
/var 1639Mb
and
swap 188MbMy reasoning was: I need /usr for the system and databases, and /var contains the website w/content. Swap is small because the machine's only got 64Mb RAM.
So far, still no luck getting to Apache from other machines on the LAN -- I suspect the firewall software is blocking port 80. Must track down the .conf file for it...
Chip H.
Hi,
To administer the rh 7.x firewall just do '/usr/sbin/lokkit' as root and allow inbound port 80 or set the lan interface as trusted. It writes ipchains commands (without the 'ipchains' itself) into /etc/sysconfig/ipchains . You should restart firewall after making changes :
/etc/rc.d/init.d/ipchains restart
Regards
To administer the rh 7.x firewall just do '/usr/sbin/lokkit' as root and allow inbound port 80 or set the lan interface as trusted. It writes ipchains commands (without the 'ipchains' itself) into /etc/sysconfig/ipchains . You should restart firewall after making changes :
/etc/rc.d/init.d/ipchains restart
Regards
ifincham -
Thanks for the tip. But it turned out that the httpd.conf still had "localhost" for the ServerName. Replaced it with the IP address, and all was well.
Tried to get Dreamweaver 4 to connect to it with WebDAV -- I'm not 100% the DAV module was compiled into Apache -- I'll check it tonight. I'll also have to check the init.d script to make sure httpd is being started with the correct -D option.
Chip H.
Thanks for the tip. But it turned out that the httpd.conf still had "localhost" for the ServerName. Replaced it with the IP address, and all was well.
Tried to get Dreamweaver 4 to connect to it with WebDAV -- I'm not 100% the DAV module was compiled into Apache -- I'll check it tonight. I'll also have to check the init.d script to make sure httpd is being started with the correct -D option.
Chip H.
I had a tech from Red Hat helping me set up partitions on my system. He suggested 500 meg for swap file (I have 521 Meg ram in server) and the rest as /. That way you won't have to worry about running out of space. (We are using hardware raid with 36 gig available.) So far, this has worked really well.
Dan
Dan
- Status