[-] remram@lemmy.ml 4 points 2 months ago

If you're one of those people that think every product is better if there's "AI" on the box then sure. What you're describing is static analysis though, it is not new.

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

Keep in mind that a part of the filesystem will be reserved on creation. Here if I create a completely empty ext4 filesystem with:

truncate -s 230G /tmp/img
mkfs.ext4 /tmp/img
mount /tmp/img /mnt

Dolphin reports "213.8 GiB free of 225.3 GiB (5% used)"

screenshot

[-] 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 4 points 3 months ago

Did it write that playbook? Did you read it?

[-] remram@lemmy.ml 5 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 4 points 3 months ago* (last edited 3 months ago)

Go away. You're here pretending that Ubuntu only does security updates. You have never received a bugfix from Ubuntu? And I am the one who doesn't know what he's talking about?

Why do you insert yourself into conversations with other people? I am the one who's rude?

[-] 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 4 points 3 months ago

Maybe I'm not being clear.

I want to stagger updates, giving time to make sure they work before they hit the whole fleet.

If a new SSH version comes out on Tuesday, I want it installed to 1/3 of the machines on Tuesday, another third on Wednesday, and the rest in Friday. Or similar.

Having machines update on a schedule means I have much less frequent updates and doesn't even guarantee that they hit the staging environment first (what if they're released just before the prod update time?)

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

I invite you to re-read the second paragraph of my post.

You're just throwing things I already listed back at me. I mentioned a staging environment, I mentioned a schedule was a (bad) option.

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

Is there anything about staggered upgrades and staging environments in there? Because obviously I had read it before posting...

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

Hard disagree there. It is a tunnel, it is plenty fast if the intermediate node is close enough, and why would you want encryption at the IP layer.

It works great and gives me IPv6 that I otherwise wouldn't have with my ISP (Optimum), allowing me to connect to native IPv6 site and use all the IPv6 functionality I want (dedicated IPs for containers/VMs etc).

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

I have IPv6, Google just doesn't like my address.

view more: ‹ prev next ›

remram

joined 3 years ago