Request ability to manually assign mountpoints to existing partitions.
ReemZ-nl opened this issue · comments
Title says it all really, I would love the ability to manually assign mountpoints to existing partitions, for example a separate /var (still heavily advised when using a SSD/HDD combination) and separate data partitions (like in my case in order to have data accessible from multiple installed operating systems). Apart from /, swap, /home and /var I have three separate data partitions with rather odd names I would like to access without having to mess with /etc/fstab later.
A similar request was made two months ago but that issue was closed after, I assume, adding the /home option. Instead of reopening that I was requested to open a new issue, so here it is.
Totally agree that it would be nice to be able to auto mount the windows partition as /windows without messing with fstab after the installation.
This basically is messing with the fstab after installation, through yet another tool.
I really don't want to enable users to override system mount points like /var, because it can go very, very wrong, such as not being able to boot or breaking journald completely.
"Still heavily advised" by whom? Where? What usecase? We're talking about a desktop system, not a server running MySQL :)
This hasn't seen activity in a long time, but I just came across this issue when trying to install Solus for the first time on a laptop. I would like to add my voice to the request for this feature. For years I have created separate partitions for /boot /var and /usr. I also have a separate partition /windows for the Windows installation that came on my company provided laptop, which I am required by my company to keep, alas.
With Ubuntu I have had to also have /boot/efi on a separate partition per their recommendation. RedHat used to recommend it for RHEL6 but apparently RHEL7 doesn't have this requirement. I assume Solus doesn't have this requirement since it isn't mentioned in the documentation, even for UEFI. This one probably doesn't need to be supported in the installer.
The use case for /boot according to RHEL is "Due to the limitations of most firmwares, creating a small partition to hold these is recommended. In most scenarios, a 1 GiB boot partition is adequate. Unlike other mount points, using an LVM volume for /boot is not possible - /boot must be located on a separate disk partition."
The use case for having /var on a separate partition is that if something causes a lot of disk usage in /var/log or /var/tmp you can insulate the rest of your filesystem from a possible disk full condition. This is something that is admittedly uncommon, but high risk to the system if it does happen. You can still diagnose what's going on and free up disk space if your system doesn't lock up.
Ubuntu also recommends having /var, /tmp and /home on separate partitions for people who have multi-user systems (like a family might), who have the disk space to do so.
People coming from other distributions who already have more mount points than / /home and swap are probably going to be used to the installer supporting their preferred partition and mount scheme. Allowing this, with appropriate UI warnings, provides flexibility for knowledgeable users while cautioning less experienced users. This works well in Ubuntu, for instance. Solus isn't Ubuntu, in a good way. mention this to support the point that they have been able to provide this flexibility without losing their reputation as an easy to use distro for home users.
I hope the Solus project will consider this request for the not too distant future.