“Only Microsoft® Outlook for Windows™ is secure, use that application for read the email on your computer”

Ok, I’m on linux, that means I won’t be reachable on the work email.

  • lawks@aussie.zone
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 days ago

    I hope you’re joking about uptime. Sure, you can do that, but you’re not getting updates if you don’t restart programs (and the whole machine when you get a new kernel). Add the needrestart package, or your distro’s equivalent. It’ll tell you what’s running outdated binaries. What are you running that doesn’t update the kernel in two months?

    • ITGuyLevi@programming.dev
      link
      fedilink
      English
      arrow-up
      0
      ·
      22 hours ago

      I also had to downvote man, it isn’t hard to swap the kernel and does not need a normal reboot (or at least what most people consider a reboot).

      I’ve had to swap the kernel on mission critical servers before and as debian is my distro of choice, I use kexec and the “reboot” happens faster than most people would notice (about a second or so for the switch then maybe 3-5 seconds before everything is back up). A full reboot (anything that forces you to sit through BIOS/UEFI/Grub/etc.) is very rarely needed in my experience.

      • lawks@aussie.zone
        link
        fedilink
        English
        arrow-up
        0
        ·
        17 hours ago

        That’s an odd reason to downvote. kexec still shuts down the entire userspace. It’s in no way related to ‘just applying updates’. It’s literally using Linux to boot another Linux to minimise downtime by skipping hardware init. It is not something a typical distro does by default, and would also reset uptime. Just because it’s fast, doesn’t make it not a reboot. Bottom line is if you’re seeing two months of continuous uptime, and you think you’ve fully updated your kernel in that time, not just live patched critical bugs, you’re practically guaranteed to be wrong. And if you’re using kexec, you should know that.

        • ITGuyLevi@programming.dev
          link
          fedilink
          English
          arrow-up
          0
          ·
          14 hours ago

          Your comment seemed to recommend people reboot their system, there is no reason to fully reboot. Much in the same way as a hdd is just a database, the kernel is just another part of the OS, no need to restart the whole system for one piece… That feels like the corporate logic of ‘Just reimage it’ no matter what the issue when the issue could be solved without wiping everything.

    • tigerhawkvok@startrek.website
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 day ago

      Lol. I downvoted you for tone, no need to be so fragile over internet points. Your post is tonal whiplash and condescension.

      • techmaster7d@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 day ago

        It sounds like you are the one being too sensitive. I see nothing wrong with the tone or message. Also, they are not being fragile over internet points, you are the one bringing that here. So in this case, I down voted you for your ignorance and condescension.

      • lawks@aussie.zone
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 day ago

        I wasn’t trying to admonish (at least until they doubled down), otherwise I wouldn’t have put in the helpful advice. Your downvote was there before my edit, so it had no discernible tone when you did, that was your own assumption.

      • ITGuyLevi@programming.dev
        link
        fedilink
        English
        arrow-up
        0
        ·
        22 hours ago

        You really can! Just make sure you load the new kernel to memory and switch over to it with something like kexec. Otherwise you’ll keep using the old one that is sitting in RAM.

      • lawks@aussie.zone
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 day ago

        Oh shit, you were serious. In that case, you’re not qualified to run Linux. You’re never running the new kernel if you don’t reboot

        uname -a
        

        To see what you’re really running on, then compare that to the latest installed by your package manager (I’m assuming you’re not compiling because … indications). Live patches aren’t the full gamut of updates, either.

        Edited typos.