“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.
“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.
As the only Linux guy in my shop, I just wait for their apps/updates to completely brick things and until the place is practically on fire, and when the moment is right, I just start complaining.
“My operating system is SO BORING. TWO MONTHS UPTIME AND IT JUST FUCKING WORKS. 650 updates and I don’t even need a restart. NOTHING I DO BREAKS IT. ARRRRGH IT IS SOOOO BOOOORINNNNG.”
Every now and then it’s fun to throw a symlink back to C: in your documents file. Cyber loves it when you backup everything to your OneDrive.
Having always been the only Linux guy at many places early in my career, I’ve finally pivoted to running the show with my last job change.
Boy, are we currently developing a long term concept with open source all over it. Supporting hosting on open source platforms is a requirement for new products and has cost two vendors their contracts so far.
I am raining fire on that passive, whiny attitude of can’t-do-anything-about-it slavery to locked down platforms in medium sized companies and the numbers, robustness to costs say I’m right.
BROTHER
We keep the lable maker next to the coffee maker.
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
needrestartpackage, 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?Edit: Lol, downvoting won’t fix your machines or your ignorance. That’s @tigerhawkvok@startrek.website and @Reygle@lemmy.world, so far.
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.
That’s an odd reason to downvote.
kexecstill 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 resetuptime. 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 usingkexec, you should know that.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.
Why are you spreading misinformation? I know what
kexecdoes, I use it on hypervisors and other non-virtualised bare metal servers, it’s great. However you’re seriously mistaken, it’s not just the kernel. From the OS’ point of view, the entire system reboots. Systemd (or whatever you’re using) goes through the whole shutdown sequence, every program & service stops, everything without an enforced graceful termination procedure gets killed rather than waited for, every user is logged out. It’s not continuous uptime, you’re still rebooting the entirely separate kernel. You have conflated speed with ‘swapping’, and I don’t think you know howkexecworks. Based on your doubling-down response, I’m not convinced you’ll learn, either.And you’re trying to shift the goalposts by putting words in my mouth: “fully reboot”. There’s no way the top level commenter is using
kexecif they think they have the new kernel fromapt full-upgrade, etc., when they didn’t even seem to know what running an outdated binary was (running process using an unlinked inode).So yes, I do recommend people reboot; via
kexecis fine, but it’s still a reboot. If you don’t usekexec, and most desktop/laptop users don’t, that is a full reboot.Lol. I downvoted you for tone, no need to be so fragile over internet points. Your post is tonal whiplash and condescension.
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.
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.
A person can install kernel updates and just not restart.
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.
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 -aTo 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.
Hehe you do you, but you should probably also run
fwupdmgrevery now and then ;) block those Microsoft CA certificatesI haven’t had a Windows update break anything in over a decade. Not at home, not in two sysadmin roles.
What are you running, Windows XP devoid of updates?
Then you’ve not been paying a lot of attention, or accidentally held back an awful lot of updates.
I don’t hold back at home, just allow middle-of-the-night updates and the occasional reboot. At work I used WSUS to hold off on updates until I could read the news, let them stew a week unless it was a critical security update.
I did doge that monster CRM breaking update at work, but again, that was over 10 years ago.
Look, I can’t fight the hivemind. Lemmy is convinced that Windows is in a constant state of broken. I’ve had my home Windows install since Win10, same SSD, across 4 PCs, haven’t had an OS issue for years. Lemmy will say this is not possible. And then go on to post questions about busted Linux drivers.
I think part of the disconnect is people seeing manufacturer Windows installs as the Windows experience. At home and work, I only install from a clean ISO, so I dodge almost all the crap people bitch about.
I’ve had every Linux desktop I installed in the last decade, except Mint, commit suicide after a few weeks to months due to borked updates. Every single one.
YMMV.
(Sure, they where salvagable, but that’s not the point: Linux too has its upgrade and dependency bullshit. That is my point. Linux is not immune to bad updates.)
True, all things ARE fallible, BUT Linux (I mean real Linux, example- Fedora/Debian) I’m NOT including things like Arch/etc- does not threaten to self destruct for millions of people every other Tuesday due to untested vibe-coded updates. Last Tuesday they pushed KB5132061 and broke printing for several tens of thousands of people.
Yeah, a few weeks ago even Copy Paste got nuked by an update, so either he’s not updating or doesn’t really use his computer.
It is the same with me. If an update breaks stuff for 0.01 % that still means 10’000 will be affected.
Yeah, that one update hit everyone on my office at the same time so I think it was pretty severe
Broken in Excel, which is not an operating system last I checked.
Nope, system-wide.
There’s been two WINDOWS updates that have broken copy paste in excel:
(KB5002914) And (KB5002934)
And there’s been two WINDOWS updates that have broken clipboard history, which isn’t all of the system but if you did have it activated it broke the clipboard entirely:
KB5058411 and KB5061526
Apparently also build 26200 of win 11 also had clipboard issues system-wide (deleting clipboard after a second until a restart).
All of these were this year, and all of these were Windows updates.
No, he/she is correct. You are just exaggerating and being obtuse.