Am Donnerstag, dem 06.10.2022 um 11:48 +0200 schrieb Enrico Zini:
>
> my laptop runs with a default partition layout created by Debian
> Installer 4 years or so ago:
>
> Device Start End Sectors Size Type
> /dev/nvme0n1p1 2048 1050623 1048576 512M EFI System
>
On Fri, 2022-10-07 at 07:13 +0200, Enrico Zini wrote:
> On Thu, Oct 06, 2022 at 06:16:56PM +0200, Michael Biebl wrote:
>
> > Can you clarify? Is the new intramfs generated in /boot or generated outside
> > of /boot but copied to /boot under a different name so it can be replaced
> > atomically?
>
Hi,
Am Fri, Oct 07, 2022 at 07:13:12AM +0200 schrieb Enrico Zini:
> On Thu, Oct 06, 2022 at 06:16:56PM +0200, Michael Biebl wrote:
>
> > Can you clarify? Is the new intramfs generated in /boot or generated outside
> > of /boot but copied to /boot under a different name so it can be replaced
> >
On Thu, Oct 06, 2022 at 06:16:56PM +0200, Michael Biebl wrote:
> Can you clarify? Is the new intramfs generated in /boot or generated outside
> of /boot but copied to /boot under a different name so it can be replaced
> atomically?
> I assume this is done for robustness reasons. Maybe, if space
On Thu, 6 Oct 2022 17:14:56 +0200 Michael Biebl wrote:
> Am 06.10.22 um 16:23 schrieb Diederik de Haas:
> > That doesn't change my perspective that the fundamental aspect of /boot
> > being too small should be addressed (directly) and not try to workaround
> > it.
>
> Agreed. But automatically
Am 06.10.22 um 11:48 schrieb Enrico Zini:
(somehow a bit more space is needed during install than is used at the
end)
Can you clarify? Is the new intramfs generated in /boot or generated
outside of /boot but copied to /boot under a different name so it can be
replaced atomically?
I assume
Am 06.10.22 um 16:23 schrieb Diederik de Haas:
That doesn't change my perspective that the fundamental aspect of /boot being
too small should be addressed (directly) and not try to workaround it.
Agreed. But automatically resizing existing partitions on a running
system will probably not be
On Thursday, 6 October 2022 16:23:27 CEST Diederik de Haas wrote:
> That doesn't change my perspective that the fundamental aspect of /boot
> being too small should be addressed (directly) and not try to workaround
> it.
With workarounds I was thinking of using a better compression scheme
Hello,
El jue., 6 oct. 2022 12:03, gregor herrmann escribió:
> On Thu, 06 Oct 2022 11:48:42 +0200, Enrico Zini wrote:
>
> > ## /etc/initramfs-tools/initramfs.conf
> >
> > # makes somewhat smaller initrd files and buys some time
> > COMPRESS=zstd
> >
> > # makes definitely smaller
On Thursday, 6 October 2022 15:41:52 CEST Ben Hutchings wrote:
> > my laptop runs with a default partition layout created by Debian
> > Installer 4 years or so ago:
> >
> > Device StartEnd Sectors Size Type
> > /dev/nvme0n1p120481050623 1048576 512M EFI System
>
The vmlinuz is usually small. The initrd can be quite big.
Regards
On Thu, 2022-10-06 at 11:48 +0200, Enrico Zini wrote:
> Hello,
>
> my laptop runs with a default partition layout created by Debian
> Installer 4 years or so ago:
>
> Device StartEnd Sectors Size Type
> /dev/nvme0n1p120481050623 1048576 512M EFI System
>
On Thu, 2022-10-06 at 11:48 +0200, Enrico Zini wrote:
> Device Start End Sectors Size Type
> /dev/nvme0n1p1 2048 1050623 1048576 512M EFI System
> /dev/nvme0n1p2 1050624 1550335 499712 244M Linux filesystem
> /dev/nvme0n1p3 1550336 1000214527 998664192 476.2G
On Thu, 06 Oct 2022 11:48:42 +0200, Enrico Zini wrote:
> ## /etc/initramfs-tools/initramfs.conf
>
> # makes somewhat smaller initrd files and buys some time
> COMPRESS=zstd
>
> # makes definitely smaller initrd files, but breaks boot if
> # dependencies are not computed
Hello,
my laptop runs with a default partition layout created by Debian
Installer 4 years or so ago:
Device StartEnd Sectors Size Type
/dev/nvme0n1p120481050623 1048576 512M EFI System
/dev/nvme0n1p2 10506241550335499712 244M Linux filesystem
15 matches
Mail list logo
