On Wed, Aug 07, 2024 at 01:50:39AM +0200, David Uhden Collado wrote:
> > The rationale is that the installer is not able to make a reasonable
> > guess about
> > how you plan to use the system. It knows the minimum required filesystem
> > sizes, and if you have a moderate amount of extra disk it has rules on how
> > to allocate the extra.
> >
> > But if you have an extremely large amount of extra space there's no way to
> > tell what you have planned for it. Are you going to run a database? Maybe
> > the extra space should go into /var. Or better yet, use that extra space to
> > make a new filesystem like /var/mariadb or /var/postgresql. Or maybe you
> > are setting up a web server and you'll want /var/www enlarged. Maybe you
> > will want the extra space in an entirely new directory like /nfs.
> >
> > If the installer can't reasonably guess, it is better to leave the space
> > unused
> > as it's easy to add space somewhere if you have extra, but hard if you
> > don't.
> > The idea here is to start with sane defaults, not immediately paint you into
> > a corner.
>
> 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.
It's also possible to tweak the auto partitioned proposal when
installing. Choose the appropriate option ((E)dit auto layout) and use
the R command to resize the partition sizes you don't like. If you
shrink or grow a partition, the partitons after it wil be moved. You
can also delete or add partitions in that step.
-Otto
