Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that.
I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!
It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means: -No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
7. Content should match the theme of this community.
-Content should be Mildly infuriating.
-At this time we permit content that is infuriating until an infuriating community is made available.
...
8. Reposting of Reddit content is permitted, try to credit the OC.
-Please consider crediting the OC when reposting content. A name of the user or a link to the original post is sufficient.
...
...
Also check out:
Partnered Communities:
Reach out to LillianVS for inclusion on the sidebar.
All communities included on the sidebar are to be made in compliance with the instance rules.
image caption: A Microsoft Windows screen showing "Active Hours" with start time set to 12 AM and end time set to 12 AM and an error that says "Choose an end time that's no more than 18 hours from the start time".
Linux "reboots" every program and service it updates separately.
So the only update that needs a reboot is one of the kernel, which doesn't happen often.
With Enterprise Linux, you can update the kernel without a reboot, too.
Can't confirm. Linux hasn't complained and I don't remember Firefox complaining. Maybe it doesn't happen with the flatpak
I have zypper ps -s as part of my update script so I personally notice through that when something needs to be restarted. It's pretty rare to have to do an actual reboot. A lot of the software stores notify if you need to restart. I've seen it on Discover and GNOME Store (?) at least
Obviously there's a small handful of things that would require a reboot, but unlike Windows, the vast majority of programs in user space don't require reboots on update.
There's also the fact that restarting Windows to update is a much slower and more disruptive experience than restarting Linux.
Okay, that's not true. Glancing at dbus sideways will result in a reboot. But in systems free of systemd and all its entourage of shit, that's still true.
OK my bad, I don't run systemd.
dbus is 4 years older than systemd, thus proving once again that systemd haters have no idea what they're talking about.
my next laptop is going to be linux anyway :)
Sad you included this misinformation in your otherwise good comment. Linux fundamentally works different and you can often update binaries as well as the kernel without rebooting.
And even if you couldn't, that's 100% a user problem. Every distro I've ever seen makes it clear as day when you do need to restart, so this is 100% a user issue. But I guess people will also complain if their OS forces them to reboot (like this post), so... 🤷🏼♂️
On my box updating firefox and then restarting it won't even launch the new version because NixOS knows I'm logged in and won't just change things in my environment. But unless there's a kernel update yes
nixos rebuild switchfollowed by logging out and logging in is equivalent to rebooting as it will automatically shut down and restart all system services, I think even systemd itself. Modulo some wibbles around kernel modules but those fall under kernel updates in my book.Contrast Ubuntu, which really likes to prompt your for reboots. The difference between a distro primarily for desktop use and one that can also do desktop because also devops want a desktop. Hey I could spin up 1000 cloud instances of my desktop with a couple of keystrokes isn't that impressively useless :)
I don't know what Windows needs to do to get as good of a state as Linux but you rarely need to do a full reboot as you seemingly are forced to do on Windows.
It does tell me. Zypper tells it outright and you'll get a list with zypper ps -s. But like said, it's very rare that you need to actually reboot. Restarting apps or services suffices.
Don't know what's up with that. With Windows it nagged about rebooting constantly. Seemingly every update. Meanwhile Linux can be just fine without, some stuff you need to restart but actual reboot is much rarer.
ROFL
If Microsoft really cares for more users keeping their system updated they should fix their update process.
While some updates require a reboot on other OSes for them to take effect they don't require work during the reboot maximizing the downtime.
Which is on top of the work done before rebooting, on the background, unprompted, destroying system performance.
With windows pro you can use Group Policy to disable them completely actually, though it’s obv not a good idea
Open Group Policy Object Editor. Navigate to Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Update. Set Configure Automatic Updates to Disabled.
Mine doesn't reboot on it's own and I don't recall ever changing any settings to prevent it other than messing with the thing OP is talking about which wouldn't let me turn it off. I get nag screens daily after a while but it never actually restarts. Maybe one of my applications prevents it or something.
I don't think that was it because it was nagging me every day for a few weeks until I finally got a free weekend to deal with the updates. I have a ton of shit going all the time and restarting is kind of a chore.
Yeah no for Linux at least.
laughs in
needs-restarting -sIt's weird that RPMs have been restarting apps affected by library updates for decades and you still haven't clued-in. You new?
Turning off or rebooting your computer isn't good for it.
(It's not as bad as turning it on, of course, but once you've made that mistake you should leave it on.)