Question About Partitions
I've used many different distributions (Ubuntu/Kubuntu, Mint, Sabayon and Zenwalk mostly) and have always had my partition scheme for the Linux part as:
Swap / But when looking at installing Arch Linux in the installation guide it lists you should have: Boot Partition Swap Partition Root Partition /home Partition For one is the root and boot partitions really necessary? And secondly what is a root partition anyway? (Isn't the the partition of / I had above call the root partition. And wouldn't that also be where my home directory would be. So before I was basically putting the two together?) I know what the boot partition is but I've just never used one before. |
Quote:
Quote:
Quote:
On a simple install, you can have / , /boot and /home all on the same partition. It will run. Swap uses a different file system, and as far as I know has to be on a separate partition. |
This also allows you to specify different mount options in fstab. Such as ro for /boot and nodev,nosuid,noexec etc. for others. It is pretty convenient to be able to wipe out everything except for user files
|
Quote:
Use this scheme: 1. System root (/): all system directories. About 20 GB at present. 2. Swap: twice the amount of system RAM. 3. A data partition that uses up all the rest of the drive space. Very simple. An argument can be made for a /home partition, so you can reinstall Linux without having to back up and restore (although backing up is very wise). In such a plan, the third large partition could be labelled /home, and have extra directories under the /home directory for large data archives as well as the normal user directories. |
Quote:
|
Quote:
A hypothetical system with two partitions will fail if one of the partitions fills, regardless of how much space remains on the other partition. It gets worse with more partitions -- the probability that one partition will fill before the others is very high and becomes higher as the number of partitions increases. This is not rocket science. Imagine a special, self-defeating car with four fuel tanks -- if any of the four tanks empties before the others, the car suddenly stops on the freeway, regardless of how much fuel remains in the other tanks. That is what having multiple partitions does for system reliability. Partitions can be justified, but all such schemes should be weighed against their drawbacks. Quote:
Your argument seems to be that, if the drive isn't used to its full capacity, then there's no problem. Even that is a shaky premise, but it argues for something with no upside -- where is the advantage of splitting the drive up into isolated blocks of storage? A system partition separate from a user partition makes sense -- you can install a new version of Linux without having to back up and restore. A swap partition makes sense. That's three ... after that, it stops making sense. I think many people assume multiple partitions make sense, but without actually thinking through the implications and the risks. Someone will surely argue that a multi-partition system is like a multi-engine airplane, but for this "airplane", it falls out of the sky as soon as any of its engines fails. This, by the way, is why Charles Lindbergh turned down a multi-engine plane to fly across the Atlantic in 1927 -- he discovered the plane couldn't stay airborne on one engine, so he realized one engine was actually safer (fewer things to go wrong). Incidentally, a team of flyers in a multi-engine plane disappeared without a trace at about the same time. Pardon my digression. Again, it's not rocket science -- more partitions only decrease system reliability. |
Thank you, I see what you're saying. But is there no security gained by ro/nodev/nosuid mount options?
|
Quote:
|
Quote:
|
In fact you can setup just one large partition and also have a swap file if you need it. This would not be a good idea if you plan on upgrading your system instead of complete wipe and reinstall. But, I'm just saying it's possible and it saves space, it's what I do. You don't even need swap usually, only if you edit large images or load large files into RAM that may slow the system to a crawl without swap space.
|
Quote:
|
Quote:
the simple work-around for this problem was to have a small ext2 partition for /boot, and that always seemed worthwhile to me in the case that you didn't know what distro and which fs type you were going to use next. Quote:
Quote:
/ is the root of the filesystem. You will have one of these whatever you do. You may or may not have other things (such as /home) on this partition; if you have a separate /home partition, then /home will be on that separate /home partition, if you don't, it won't. You will always have /home, the only question is whether it is on its own partition or not. For most purposes, it looks exactly the same, whether you have the home partition separate (eg, you can cd up and down the tree without ever noticing the difference) or not. With the separate home partition, you do have the concern whether the separate home partition is filling up, and so, as a minimum, you should watch out for that. When you come to re-install or upgrade you distro version, however, having home separate does give the advantage that you can preserve this partition while clearing the others. This has the potential to be easier and save time, but does not obviate the requirement for a back-up, in case things go wrong. Of course, you do not 'need' convenience, so it is not necessary to do this. |
/
/home these are the basic partitioning I use And I do add a 2x ram swap as well even though I don't think I ever use it. |
I agree with others here. /,/home, and swap should be all you need.
|
Sorry, you didn't state this explicitly, but everyone (& I include myself) seems to be giving you advice assuming that the question concerns a desktop system; if this is a server, then the advice would get a bit more involved.
|
All times are GMT -5. The time now is 04:50 AM. |