triangulation

trilateration actually (^0_0)

In terms of modern shells being more complex in general: yes and no. modern shells pretty much always use some kind of electronic fusing, sometimes multiple kinds of electronic fuses. back then they had bombs, mines and grenades with literal clockwork inside and electronics was still very rare. also fuses and primary charges were not easy to produce reliably.

throw off the yolk

lol

Indeed. atetheonion might contain a bunch of idiocy, but i would not be offended by being included there just because i was sceptical of something.

It’s just the basic posix shell syntax. It just looks weird because they are using lots of library functions and in-place substitutions. also apparently the function, to translate a system path to something grub will understand, is an ELF binary 0_o

check the GRUB_CMDLINE_LINUX key in /etc/default/grub it should contain the info about any subvolume. if it does not then there might be another grub config hook that is used by Fedora to add that info. If you want to be able to change subvol names without having to touch the grub config you might also want to switch to using subvolid instead of subvol keys on the kernel command line, because the id will stay the same after a rename (this could backfire though if you assign functions to certain names like “fallback” etc.).

Edit: found the hook that adds the kernel command line option for btrfs subvolumes. in /etc/grub.d/10_linux there is this bit of code:

case x"$GRUB_FS" in
    xbtrfs)
        rootsubvol="`make_system_path_relative_to_its_root /`"
        rootsubvol="${rootsubvol#/}"
        if [ "x${rootsubvol}" != x ]; then
            GRUB_CMDLINE_LINUX="rootflags=subvol=${rootsubvol} ${GRUB_CMDLINE_LINUX}"
        fi;;
    xzfs)
        [skipped for brevity]
        ;;
esac

so it seems it is always looking at the subvol name of the currently mounted root fs.

this is extra tricky because they did not specify the exact kernel. mainline could be any of the kernels tagged as stable that you can build from linus’ git tree. i know that in the past you could run a mainline linux on intel 368 chips but today you probably can not because official support was dropped a while ago.

instead of putting a grub config in /boot/grub you could also try embedding it directly with grub-mkimage. you would need to point to the grub config that you have with -c and add all the needed modules as extra arguments at the end.

it is possible that the grub image you installed is just not looking for the config file at the right place.

or maybe try putting the grub.cfg in the same directory as the grubx64.efi

no i was just adding that to explain that grub needs special steps to work with secure boot enabled. if secure boot is off you can ignore that part.

is secure boot enabled in the firmware? It is possible that you have a signed grub binary installed but the module signing is not yet rolled out. Edit: my mistake: if you are using grub with shim then all the necessary modules need to be baked into the grub binary. maybe grub was not installed correctly?

woah this is awesome!

maglevs need classical wheel systems anyway because there might be a power outage, so simply having wheels that are compatible with the local rail system is a brilliant idea.

add in a tiny propulsion system so they can use the normal tracks at low speed without the help of the maglev tracks and you can sort of blend the two systems together in critical locations like switches and train stations.