You are not logged in.
Pages: 1
Any reason the installer uses 100MB for the /boot partition by default? Seems very odd and makes it impossible to have multiple kernels available.
Offline
Any reason the installer uses 100MB for the /boot partition by default? Seems very odd and makes it impossible to have multiple kernels available.
Yes. It's a design decision by the author.
As with any other (unsupported) installer, by using such a thing, you agree to the settings the author(s) impose on you.
If you want a customized installation and not something that other people impose on you, don't use this (or any other) installer and install Arch the "classical" way.
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
Take the above with a grain of salt. The installer is supported like any other installation methods documented on the wiki (e.g. the installation guide, archboot, systemd-firstboot etc.), the "impose" argument is ridiculous to anyone who read the archinstall readme, and there's no reference this kind of thing is a "design decision". Best you open an issue on github instead.
Last edited by Alad (2021-08-04 12:26:20)
Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
Offline
Obedience towards redmond
(Ie. it likely just re-uses the partition scheme it finds and tha is likely the one put there by windows)
Quick glance at the guided profile "example" it doesn't touch an existing partition scheme at all.
Online
Offline
on my system:
drwxr-xr-x 6 root root 1.0K Dec 18 10:06 grub # 12.5 MB
-rw------- 1 root root 36M Dec 18 10:14 initramfs-linux-fallback.img
-rw------- 1 root root 13M Dec 18 10:14 initramfs-linux.img
-rw-r--r-- 1 root root 4.6M Jun 8 2021 intel-ucode.img
-rw-r--r-- 1 root root 10M Dec 18 10:14 vmlinuz-linux
2 initramfs is plenty, and still plenty of space for multiple kernels until you reach 100MB. or am i missing something?
Last edited by Dieter@be (2021-12-19 02:09:17)
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
You're missing that I for example do not use compressed initramfs images, since the decompression actually takes longer than reading an uncompressed image from my NVMe SSD.
$ ls -lh /boot
insgesamt 74M
drwxr-xr-x 3 root root 4,0K 27. Jan 2020 EFI
-rwxr-xr-x 1 root root 59M 18. Dez 02:38 initramfs-linux-zen.img
-rwxr-xr-x 1 root root 4,6M 8. Jun 2021 intel-ucode.img
-rwxr-xr-x 1 root root 11M 18. Dez 02:38 vmlinuz-linux-zen
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
Okay so it sounds like 100MB is enough for many/basic installations, but not enough for non-standard ones with multiple kernels. No default will ever be perfect for everyone. Alad's suggestion seems to make sense, bring up on the bugtracker to see what the developers think. Perhaps it should be easily configurable during installation, if it isn't currently. I haven't tried the installer myself.
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
I just stumbled upon this right after doing a fresh install(also accidentally deleted my windows partition thank god that was fresh too) with the default/suggested disk layout. My /boot was made 500MB. The most recent .iso (2021.12.01).
Offline
Sorry for the lack of responses.
There is no design decision in terms of `/boot` other than when we create it. Which is now default to 500MB as Ipv mentions.
The only time we can't facilitate this is when Windows is the one that creates the boot sector, which it does by creating a ~100MB small partition.
100MB will work, if you use vanilla `linux` kernel and can live without a `-fallback` initramfs. But it will spit out a warning every time you regenerate a initramfs.
We don't dare to implement magic functions to resize this limitation, but instead we've implemented a warning stating that the user has to resize the partition manually first.
Until there's a safe tool that can reliably resize the partition without consequences, this is the best we can do for now. Hope that's ok.
Offline
Pages: 1