![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
How is it that we are the same person
Pronouns: They/Them
How is it that we are the same person
Heh no that’s the mushroom forager’s bible right there, going back many years, it’s assigned reading for mycology students and very reputable. It’s funny how much it looks ML generated, but it well predates ML image generation. For reference, he’s holding a flesh colored mushroom and a trumpet.
I don’t quite recall, but I think they were moved again to an office or something. No idea who was moving computers around and properly connecting them to the network, it wasn’t us (contracted IT). At least they put both this guy’s computers directly next to eachother. But nothing was labelled. I recall trying to get someone onsite to label the computers both times and I don’t think it ever happened lol.
I think another wrinkle was that most of the attorneys were at that time being migrated or already using a single remote desktop server in a Colo, so I don’t know why the customer got this guy a second remote computer. The owner had a tendency of just buying computers without consulting us, and this particular lawyer was a bit of a squeaky faucet with tech, and the RDS was… less than perfect. So that’s probably it.
I had a client at a law firm who moved to a different city, but continued to remote into his computer at work. At some point someone moved it to some other spot in the building so they could have someone else use his desk, and he continued to use it without issue.
Until one day it shut down, while he was in the middle of something very important and lawyery. No one at the firm was willing to look for it (as they were all lawyers), so we had to send a technician on site to just check each room until he spotted an old computer connected to power and Ethernet in the corner of a mail room.
Some months later it happened again, in a the middle of another important time sensitive lawyer thing. Except now he had two headless computers which he used both of (an old computer and a new one he was migrating to), and he still didn’t know where they were physically. Luckily there was a intern on site to do the search this time, but it took some time to figure out which was which when we did locate them.
The circle of lif.
Yeah I feel like that’s pretty squarely next to debian as traditional and open source.
Marxism-Leninism-Debianism ftw. But I also need thigh highs.
To me that looks like a fairly non-controversial perspective amongst leftists and communists (especially internationally). But that’s just my (communist) perspective.
I get where you are coming from, but this event is pretty much entirely the fault of Crowdstrike and the countless organizations that trusted them. It’s definitely a show of how massive outages are more likely when things are overly centralized and proprietary, and managed by big, shitty, profit driven organizations. Since crowdstrike operates in kernel space, it doesn’t matter which operating system it’s on, it can break it if it does something stupid. In fact they managed to break some redhat machines not too long ago, and some Debian machines not long before that. It’s just the impact wasn’t as far reaching as this recent utter fuckup, just because fewer critical machines were affected, so we didn’t hear about those smaller fuckups in the news.