[-] remram@lemmy.ml 12 points 1 month ago* (last edited 1 month ago)

I have never met anyone refer to "screen off" as "sleep".

https://en.wikipedia.org/wiki/Sleep_mode

The terms everybody else are using are: "sleep" = "suspend to RAM" = "S3" and "hibernation" = "suspend to disk".

[-] remram@lemmy.ml 5 points 3 months ago* (last edited 3 months ago)

I feel you, but on the other hand if every single community member tries to help, even if they have no idea or don't understand the question, this is not great.

Anybody can ask Google or an LLM, I am spending more time reading and acknowledging this bot answer than it took you to copy/paste. This is the inverse of helping.

The problem is not "the loop"(?), your (LLM's) approach is not relevant, and I've explained why.

[-] remram@lemmy.ml 5 points 3 months ago

What was "the point"? From my perspective, I had to correct a fifth post about using a schedule, even though I had already mentioned it in my post as a bad option. And instead of correcting someone, turns out I was replying to a bot answer. That kind of sucks, ngl.

[-] remram@lemmy.ml 7 points 3 months ago

Thanks, that sounds like the ideal setup. This solves my problem and I need an APT mirror anyway.

I am probably going to end up with a cronjob similar to yours. Hopefully I can figure out a smart way to share the pool to avoid download 3 copies from upstream.

[-] remram@lemmy.ml 6 points 3 months ago

Using scheduling is not a good option IMO, it's both too slow (some machines will wait a week to upgrade) and too fast (significant part of machines will upgrade right away).

It seems that making APT mirrors at the cadence I want is the best solution, but thanks for the answer.

[-] remram@lemmy.ml 7 points 3 months ago

Making multiple mirrors seems like the best solution. I will explore that route.

I was hoping there was something built into APT or unattended-upgrades, I vaguely remembered such a feature... what I was remembering was probably Phased Updates, but those are controlled by Ubuntu not by me, and roll out too fast.

[-] remram@lemmy.ml 5 points 3 months ago

So you can test the updates before fixing production.

My question is how to do that with APT.

[-] remram@lemmy.ml 5 points 3 months ago

No, I'm asking how to have unattended-upgrades do that.

41
submitted 3 months ago* (last edited 3 months ago) by remram@lemmy.ml to c/linux@lemmy.ml

I am using unattended-upgrades across multiple servers. I would like package updates to be rolled out gradually, either randomly or to a subset of test/staging machines first. Is there a way to do that for APT on Ubuntu?

An obvious option is to set some machines to update on Monday and the others to update on Wednesday, but that only gives me only weekly updates...

The goal of course is to avoid a Crowdstrike-like situation on my Ubuntu machines.

edit: For example. An updated openssh-server comes out. One fifth of the machines updates that day, another fifth updates the next day, and the rest updates 3 days later.

[-] remram@lemmy.ml 7 points 3 months ago

... and feel endless pain from whatever they did to the scrollbars. Seriously, wtf.

[-] remram@lemmy.ml 5 points 3 months ago

I don't know, I recently got a 2-in-1 laptop, and was surprised to see that KDE works great. Got Onboard as on-screen keyboard. Screen rotation works great. Glad I didn't have to run Gnome on that machine.

[-] remram@lemmy.ml 8 points 1 year ago

How many real teachers per student though? Is this just an excuse to have even less human support, because "we have 10 AIs per student"?

What does a ratio even mean in this case, the AIs are not separate.

[-] remram@lemmy.ml 16 points 1 year ago

For whatever reason, to this day I get a 403 error on http://google.com/ from IPv6. https://www.google.com/ works through.

Sometimes it's not your side that is broken.

view more: next ›

remram

joined 3 years ago