• Avid Amoeba@lemmy.ca
    link
    fedilink
    arrow-up
    100
    arrow-down
    3
    ·
    7 months ago

    I love this! Not only for the comedic value, but throwing kernel oopses on-screen when they can’t be easily captured when unprepared would be of great help in solving system problems. Unlike the cryptic messages Windows displays, Linux kernel messages are quite useful.

  • ChewyOP
    link
    fedilink
    arrow-up
    66
    arrow-down
    2
    ·
    7 months ago

    Some Highlights:

    • A new component “systemd-bsod” has been added to show logged error messages full-screen if they have a “LOG_EMERG” log level. This is intended as a tool for displaying emergency log messages full-screen on boot failures. Yes, BSOD in this case short for “Blue Screen of Death”. This was worked on as part of Outreachy 2023. The systemd-bsod will also display a QR code for getting more information on the error causing the boot failure.

    • Hibernation into swap files backed by Btrfs are now supported.

    • Support for split-usr has been removed.

    • KiranWells@pawb.social
      link
      fedilink
      arrow-up
      4
      ·
      7 months ago

      Actually looking forward to the btrfs swapfile hibernation; I have tried setting it up on my machine before but the documentation was never clear on whether it would work (or why mine wasn’t).

    • Vilian@lemmy.ca
      link
      fedilink
      arrow-up
      41
      ·
      7 months ago

      i totally understand if they named it bsod just for the meme, it’s funny also they could make an option to change de color :b

      • Julian@lemm.ee
        link
        fedilink
        English
        arrow-up
        51
        ·
        7 months ago

        Correct me if I’m wrong but isn’t this basically just better error reporting? It’s not like it’s gonna crash more often, it will just actually show log info if something catastrophic happens.

        • kpw@kbin.social
          link
          fedilink
          arrow-up
          46
          ·
          7 months ago

          No, there is a random crash every six hours now to increase familiarity.

          • Laser@feddit.de
            link
            fedilink
            arrow-up
            8
            ·
            7 months ago

            Unfortunately this only affects boot messages, not normal system operation, for that you still get core dumps and kernel panics / oops

        • ikidd@lemmy.world
          link
          fedilink
          English
          arrow-up
          10
          ·
          7 months ago

          A BSOD that gave you a clue about why it happened would be a welcome change.

          • Vilian@lemmy.ca
            link
            fedilink
            arrow-up
            4
            ·
            7 months ago

            that’s the goal, they also gonna implement the QR code, but not like the crappy of QR code on windows(that send you to a suppirt page with a dozen of possible sulution, where nothing work), the qr code is going translate to the kernel panic message, i liked, i can scan the qr code and search the error on my cell

  • Krafting@lemmy.world
    link
    fedilink
    arrow-up
    38
    arrow-down
    1
    ·
    7 months ago

    I just wish they would use another name for it, it’s linux here no need to copy windows slang! Or use another color! (I hope they’ll update it to make it a customizable color)

    • palordrolap@kbin.social
      link
      fedilink
      arrow-up
      25
      ·
      7 months ago

      Fun fact: The Windows BSOD colour was as easy as adding a couple of lines to a .INI file for a long time. Then, as they tend to do, they made it more difficult, but it was still possible. Third party tools were written to do the work.

      Very recent MS Windows I have no idea about. My search-fu is failing me.

      Anyway, my point is that the “two lines in a config file” method would be nice.

      Knowing systemd though, it’ll be “send some kind of message into a /proc pseudo-file”, or a sub-sub-sub-command of one of the many systemd* commands which ultimately does the same thing.

    • r00ty@kbin.life
      link
      fedilink
      arrow-up
      11
      ·
      7 months ago

      Yeah, Linux should have taken the guru meditation from the Amiga! (I know VirtualBox already copied it mind you)

  • KseniyaK@lemmy.ca
    link
    fedilink
    arrow-up
    30
    arrow-down
    3
    ·
    edit-2
    7 months ago

    I hope this isn’t going to be the default. I know, the average granny might prefer to have a BSOD with a QR code, but I think a lot of the people who are more tech-savvy, like me, would prefer to see log messages when booting because then you could see which service failed and why or why it’s all of a sudden taking so long to boot. That’s also why I choose not to have a splash screen when booting.

    Anyways, this BSOD thing doesn’t apply to me because I use Gentoo with OpenRC.

  • Infiltrated_ad8271@kbin.social
    link
    fedilink
    arrow-up
    25
    arrow-down
    2
    ·
    7 months ago
    • Hibernation into swap files backed by Btrfs are now supported.

    So, with btrfs on ssd, is there any use case for a swap partition?

      • bdonvr@thelemmy.club
        link
        fedilink
        arrow-up
        5
        ·
        7 months ago

        I think what they mean is that you can just make a swap FILE instead, which you can grow and shrink as needed. No need to mess with partitioning.

        • Infiltrated_ad8271@kbin.social
          link
          fedilink
          arrow-up
          1
          ·
          7 months ago

          Yep. In fact my comment seemed so clear to me that I assumed it was some kind of joke, but looking at the votes, maybe swapfiles aren’t as well known as I thought.

            • wmassingham@lemmy.world
              link
              fedilink
              arrow-up
              4
              arrow-down
              1
              ·
              edit-2
              7 months ago

              I’m not sure what that post is meant to show, if swap isn’t “disk RAM”. That post even concludes:

              Swap […] provides another, slower source of memory […]

              • lemmyvore@feddit.nl
                link
                fedilink
                English
                arrow-up
                1
                arrow-down
                2
                ·
                7 months ago

                Um, you really need to read the entire phrase and not pick out only what you want from it. 😃

                Swap can make a system slower to OOM kill, since it provides another, slower source of memory to thrash on in out of memory situations

                It means that if you try to use it as a source of memory, when you run out of actual RAM it will make your system almost completely unresponsive due to disk thrash, instead of allowing the kernel to just kill the process that’s eating your RAM. So you’ll just end up hard-booting system.

                • wmassingham@lemmy.world
                  link
                  fedilink
                  arrow-up
                  1
                  arrow-down
                  1
                  ·
                  7 months ago

                  Yes, and that’s a good thing if you don’t want it to start killing processes. You have that extra time/space to deal with the out-of-memory condition yourself.

                  Or you can ignore that condition and continue using the system in a degraded state, with swap as “disk RAM”.

    • rotopenguin@infosec.pub
      link
      fedilink
      English
      arrow-up
      5
      ·
      7 months ago

      Do you mean that you don’t have to find the LBA of the extents of your swap file, and put that into a kernel argument anymore?

      Cuz that is a nasty, skanky hack.

      • Infiltrated_ad8271@kbin.social
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        7 months ago

        I’ve never heard of that, it’s beyond me. So it’s an increased risk when tweaking the kernel? As an average home user it’s all right?

  • rotopenguin@infosec.pub
    link
    fedilink
    English
    arrow-up
    19
    ·
    7 months ago

    I don’t think it’s going to do a whole lot of good when the whole KMS/DRM falls over.

    (okay I haven’t had that for a few months now. But i am still traumatized)

  • setVeryLoud(true);@lemmy.ca
    link
    fedilink
    arrow-up
    5
    ·
    7 months ago

    Good idea, stupid name.

    Excellent for causing FUD.

    No, this will not increase the amount of kernel panics you see. It just makes them more informational to the average person. Technical folks can disable it, non-technical folks won’t know how to enable it, so on by default it is.

  • AutoTL;DR@lemmings.worldB
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    3
    ·
    7 months ago

    This is the best summary I could come up with:


    Ahead of the holidays systemd 255 has debuted as stable and comes with systemd-bsod as a “Blue Screen of Death” service capable of displaying full-screen error messages on Linux.

    This is intended as a tool for displaying emergency log messages full-screen on boot failures.

    The systemd-bsod will also display a QR code for getting more information on the error causing the boot failure.

    • Systemd’s bootctl will now show whether the system was booted from a Unified Kernel Image (UKI).

    • systemctl will now automatically soft-reboot into a new root file-system if found under /run/nextroot/ when a reboot operation is invoked.

    • A new option “SurveFinalKillSignal” has been added to skip the final SIGTERM/SIGKILL spree on shutdown in order to survive soft-reboot operation.


    The original article contains 490 words, the summary contains 123 words. Saved 75%. I’m a bot and I’m open source!