41–50 of 108 posts
Earlier quoted context omitted.
The 'target' moves slow so once you learn it, it all stays relevant forever. ... And it's very, very fun.
Does it offer performance advantages over NFS root?
Looks like ZFS is only used to store the image on the server, though. I was expecting this to be more interesting because of that.
Does zfs support error correcting instead of just finding (already) broken files? I have been waiting for such a feature for like 15 years now. Without it, zfs is just a fad and useless filesystem (all that complexity for NOTHING). ext2 for the win! still
--
0: https://klarasystems.com/articles/troubleshooting-zfs-common-issues-how-to-fix-them/rEFInd is _so_ much simpler: one efi entry, one text config file in the efi partition, nothing that needs to change when the kernel updates, and no massive pile of templating and moving parts to mysteriously break dumping you at an impenetrable grub “rescue” shell.
Earlier quoted context omitted.
or just copy the latest kernel to something like /vmlinux and /initramfs
Or use UKI and throw the current kernel to /efi/boot/bootx64.efi; there's plenty of solutions to sane bootloader/kernel management if you're willing to invest 15 minutes into the topic and not act like it's scary and complicated (it really is the opposite).
Friends don't let friends use grub. rEFInd is _so_ much simpler: one efi entry, one text config file in the efi partition, nothing that needs to change when the kernel updates, and no massive pile of templating and moving parts to mysteriously break dumping you at an impenetrable grub “rescue” shell.
> UEFI fixes that to some extent, but it’s a pain to maintain the UEFI entries manually and change them every time the kernel updates. … you don't have to update the UEFI entries every time the kernel updates. (I guess you might if you do like a kernel w/ CONFIG_EFI_STUB, and you place the new kernel under a different filename than what the UEFI boot entry point to then you might … but I was under the impression that…
Nice. I'm extra fond of ZFS backed network root filesystem, because it lets you put an OS on ZFS without needing to deal with ZFS support in that OS. (One of these days I want to try OpenBSD with its root on NFS on ZFS, either from Linux or FreeBSD.) Does anyone have an opinion on iSCSI vs NBD?
Pretty cool! You could also boot into an ephemeral minimal initrd that displays a selection menu instead of doing it in iPXE. That would grab the new kernel and initrd from the network and kexecs it without reboot.
Wouldn't that need a local disk?
"I didn’t want to get into the hassle of repartitioning everything that the boot loader works with both Linux & Windows." Hmmh? I haven't done so in years, but configuring multi-boot used to be considerably easier than disk-less operation.
The Debian installer is less than optimal for repartitioning. The Linux NTFS resizing code also has a tendency to trigger data corruption. Not really Linux' fault, but it's a good reason to do partitioning from inside of Windows, which can be a pain already. Another issue I've run into is Windows creating a very small (~300MiB) EFI partition that barely fits the Windows bootloader, let alone a Linux bootloader and ke…
If Linux corrupts someone files, it is 100% Linux's fault and is absolutely unacceptable.