On 8/8/24 02:39, Eric Furman wrote:
On Wed, Aug 7, 2024, at 8:44 PM, Justin Yates Fletcher wrote:
On Wed, 2024-08-07 at 01:50 +0200, David Uhden Collado wrote:
Now I understand the rationale. It might be beneficial for the
installer
to offer multiple templates when selecting the automatic partitioning
option. These templates could cater to various common use cases,
making
the process more convenient and often eliminating the need for manual
disk partitioning.
The difficult problem is that there is no good definition of "common
use cases". I'm sure that the problems I use my computers to solve are
different than yours.
The default way of setting up the partitions assumes that you have done
your homework.
For example, the installer gives you the option to manually partition
or manually adjust after an auto partition layout. If you don't know
what you want then just manually create a root and swap and have fun!
But when you do so then you also lose some of the extra protections
(nodev, wxallowed, nosuid, etc) that the auto partitioning sets up by
default.
It always amazes me when people ask for stuff like this.
The defaults exist for a reason.
It's not like the Devs didn't think about this stuff.
OBSD has always expected its users to think.
If you want to step outside the defaults then you
better damn well know what you are doing.
Don't ask for anything to help you with it.
It's the single biggest thing I HATE bout MS.
It's always trying to think for you and it is
ALWAYS wrong.
Changing allocations for system functions makes no sense 99% of the time. Only
/home and /var/www should (normally) contain user files which
might need large partitions.
Automatic installation gives /home most of large drives anyway,
If the system has a second disk drive, /etc/fstab can point at that
drive touching nothing else.
A trivial advantage of moving /home is that reinstalls or installs of
new OS versions can simply wipe the root drive clean.
Of course, do a backup first anyway.
