Answer the question
In order to leave comments, you need to log in
What is the best way to partition drives for Mint?
There is a home PC with Xeon E5462 and 8GB DDRII.
It has two disks:
Answer the question
In order to leave comments, you need to log in
What is there to think? You allocate twice the amount of RAM for the swap partition, 50 gigs for the system, and the rest for the hamster. Mount the hard disk in /hdd as a single piece.
If it doesn’t [wait, temporarily merge the hamster on the hdd, quickly rearrange the system with repartitioning as you like and return the hamster. Minute business.
However, lately I have not carried the system and the hamster into different sections at all. In fact, everything is divided into swap and the rest.
UPD.
Forced to correct.
If you have an SSD, I think it makes no sense to have a separate swap partition. You can get by with a file.
With a permanently attached HDD, it makes no sense (IMHO) to even separate /home from the system. Less hassle.
We do everything on the SSD in one partition, mount the HDD in / hdd and live - we don’t know grief.
Swap is allocated by the size of the RAM in the /tmp/swap. If there is not enough, you can increase the quotas.
Oh, I always do this, also a 120 ssd:
under the root 20gb
under swap = ram
under var = 16-18GB
the rest under home, ~ 50 remains there.
And a couple of gigs in unallocated, so that ssd is not buggy
You can also put var on hdd, but I don’t think it’s buzzing
Allocate the entire ssd disk for the bcache disk cache (read-write) and on top of it btrfs or, if there is enough RAM, as a regular zfs cache (read-only). Instead of partitioning the disk into dos partitions, cut btrfs/zfs volumes, with very flexible space usage.
It makes sense to move / and / home to separate volumes, it’s not worth highlighting the OS partitions personally, as it was 10-20 years ago. Later, place the swap partition inside one of the btrfs / zfs volumes, disabling the cow chips and others for it.
The division into volumes makes sense for flexible control of the occupied space and can be managed.
ps if uefi is used (and it is most likely used), then you will need a uefi boot partition and a regular dos mbr or gpt boot sector.
sda - ssd, sdb - hdd
sda1 - 110Gb cache
sda2 - 10Gb protection area for cheap ssds (not from glitches, but from a strong drop in performance)
sdb1 - 100mb - uefi boot
sdb2 - remaining disk space bcache+btrfs/zfs
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question