Penguin
Diff: DrivePartitioning
EditPageHistoryDiffInfoLikePages

Differences between current version and revision by previous author of DrivePartitioning.

Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History

Newer page: version 10 Last edited on Sunday, November 28, 2004 10:26:28 am by AristotlePagaltzis
Older page: version 8 Last edited on Thursday, February 12, 2004 9:43:07 am by JohnMcPherson Revert
@@ -1,54 +1 @@
-For a thorough explanation of partitioning, read HowToPartition (from the [Linux ] Documentation Project) .  
-----  
-If you a looking for a tool to re-partition a drive that is already in use (and you don't want to lose the data on the partitions), you could use the proprietary (but very good) PartitionMagic, or the [Free] tool parted(8).  
-----  
-Recently people have been asking about drive partitioning schemes for new Linux installs. Here is what I recommend:  
-  
-__hda1 /boot (32-64MB)__  
-  
-Historically lilo (the LinuxLoader) could not read past 1024 cylinders. Hence people created their first or second partition as /boot. Now lilo doesn't have this problem but it is still a good idea because it enables you to mount your /boot as read-only protecting your all important kernel from being accidentally blown away by careless fingers. Also with the increasing trend of using GRUB as a boot loader you should probably stick to using ext2 on your /boot. Seperating out /boot lets you use ext3 or some other more advanced FS on your root (/) partition.  
-  
-__hda2 swap (128-256MB)__  
-  
-Older Linux kernels could not use more than 128MB of swap in a single swap space. New kernels do not have this limitation. But you shouldn't have more than about 256MB of swap (128MB is probably enough really). If you find yourself running into swap a lot you should buy more RAM. Swap is not a substitute for RAM. It is a saftey zone so that your system doesn't run out of RAM and kill running processes. It is also used as a place to swap out rarely used chunks of ram (ie all those mingetty's you still have running while you're in X).  
-  
-__hda3 / (1-4GB)__  
-  
-Root. On a workstation this is where everything gets chucked. The biggest area of your root partition will be /usr or /opt. How big you make this partition all depends on what apps and packages you will be installing.  
-  
-__hda4 (extended)__  
-  
-Your extended partition. PC hard drives are ass and can only support 4 primary partions. So you 4th primary becomes your extended partion which covers the entire remaining portion of your disk.  
-  
-__hda5 /usr/local (1-2GB)__  
-  
-This is where you can build and install packages from source tar balls. Everything outside of /usr/local should be managed by your package management tools (rpm, debs, etc).  
-  
-__hda6 /home (the rest of the drive)__  
-  
-All your user accounts, warez, pr0n, mp3s etc. :) This is good layout for a personal workstation as it ensures that all your user data is on another partition safe from OS upgades.  
-  
-  
-Servers on the other hand should have a slightly different layout. Generally they also have the following partitions:  
-  
-__/tmp /var/tmp (265-512MB or whatever your feel is adaquate/sufficient for your situation)__  
-  
-The system tmp directories are nice places which everyone can write too. This is actually fairly dangerous. You should use mount options to ensure that people can not create executable files int he tmp dirs. Removing sgid and suid perms is good too.  
-  
-The mount flags of interest are noexec, & nosuid. See the mount(8) man page for more info on this.  
-  
-__/var (512MB-1GB or whatever your feel is adaquate/sufficient for your situation)__  
-  
-The variable data area is where logs are stored. They are important files for system auditing and monitoring. You should take as many steps as possible to protect these files. You should also make sure there is always enough space on /var for your log files to continue being written to. Other areas like /var/spool or /var/imap should have their modes/attributes changed to try and ensure there is no data lost on server failures. For this you might want to investigate the sync mount option and the chattr command ( see chattr(1) ).  
-  
-__/usr (whatever your feel is adaquate/sufficient for your situation)__  
-  
-To add additional protection to your applications from system crackers you can mount your /usr partition readonly.  
-  
-  
-I hope these tips help people make better decisions about how they partition their system's hard disks.  
-  
-----  
-Here's a mini howto someone wrote on swap: http://www.xenotime.net/linux/swap-mini-howto.txt  
-----  
-CategoryDiskNotes  
+Describe [DrivePartitioning ] here