Most books and courses introduce Linux through shell commands, leaving the kernel as a mysterious black box doing magic behind the scenes. In this post, we will run some experiments to demystify it: the Linux kernel is just a binary that you can build and run.
  • dubyakay@lemmy.ca
    0·
    3 days ago

    On my arch install, all I have is vmlinuz-linux under /boot. How come there’s no further information appended like in the article?

    • ReversalHatchery@beehaw.org
      0·
      11 hours ago

      an arch user doesn’t know that!!

      so, that further information is the kernel’s version number. it helps to keep some older versions. but you didn’t set it up to include the version in the filename.

      és egyébként bojler eladó. processzorra cserélném.

    • atzanteol@sh.itjust.worksEnglish
      0·
      3 days ago

      Different distros vary a bit here, and it will differ if you’re on a system using efi.

      Sometimes /boot isn’t mounted by default (it’s not needed unless you’re updating a kernel). You may be seeing a symlink or placeholder there.

      If you’re using efi there will probably be /boot/EFI or something where your kernel is stored.

      • flying_sheep@lemmy.ml
        0·
        1 day ago

        The reason there’s no version in the filename is simply that Arch just doesn’t keep old kernels around.

        The vmlinuz-linux just gets replaced whenever you update the linux package and the old one is deleted immediately.

        • atzanteol@sh.itjust.worksEnglish
          0·
          17 hours ago

          That’s… Insanity. Keeping at least one old kernel is amazingly useful if you run into issues with an update.

          • flying_sheep@lemmy.ml
            0·
            11 hours ago

            I agree that it’s be useful, and I think you can just install e.g. the LTS kernel next to the regular one.

            But even without , the arch way isn’t insane either: when something kernel-related breaks, boot with a live system on USB and fix it.

            Case in point: I dimensioned the EFI partition too small, so at some point, me using the zen kernel (which comes with a backup kernel image) messed things up and I couldn’t boot a half-written kernel.

            then I

            1. created and booted a live USB stick,
            2. Mounted my / and /boot partitions manually into /mnt/root/ and /mnt/root/boot
            3. Bind-mounted the live system’s /dev and /proc into /mnt/root/{dev,proc}
            4. chrooted into /mnt/root (resulting in an environment using /dev and /proc from the live system and the rest from my system),
            5. Used regular package manager commands to uninstall the zen kernel and install the regular one, and finally
            6. rebooted into the now working system.

            It’s not crazy, it doesn’t take long, you just need to know how the system works. Upside is that nothing ever breaks permanently, everything is fixable (except hardware failure)

            • atzanteol@sh.itjust.worksEnglish
              0·
              7 hours ago

              But even without , the arch way isn’t insane either: when something kernel-related breaks, boot with a live system on USB and fix it.

              That is not a replacement for “arrow-key down during boot to select an older kernel”.

              I have a server with a RAID card and the kernel at some point introduced a bug with the driver that prevented that server from booting. So I select the older kernel at boot, get the system up and running, mark that kernel as the default until the bug is fixed.

              It’s not crazy, it doesn’t take long, you just need to know how the system works.

              I know how the system works very well thankyouverymuch. But that’s an insane option when having multiple older kernels is so easy to do and common.