• Avid Amoeba@lemmy.ca
    link
    fedilink
    arrow-up
    13
    ·
    10 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.

  • setVeryLoud(true);@lemmy.ca
    link
    fedilink
    arrow-up
    6
    ·
    10 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.

  • KseniyaK@lemmy.ca
    link
    fedilink
    arrow-up
    8
    arrow-down
    2
    ·
    edit-2
    10 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.

  • Chewy@discuss.tchncs.deOP
    link
    fedilink
    arrow-up
    5
    ·
    10 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.