You can’t really blame a shortage of DRAM without acknowledging that you caused the shortage by pre-ordering two years worth, and allocating it only to data center customers. Louis Rossman has a few good takes on it. One is the, “I’m suing Samsung” video. The recent Gamer’s Nexus piece where he’s talking with that unboxing YouTuber is pretty spot on too.

That means you remember the thrill of getting the Diamond Multimedia Viper SVGA card (or similar)and being able to “crank up” the resolution beyond 800x600.

Or:

Set Blaster= A220 I5 D9

Enjoy your day, fellow vintage builder.

That’s not Linux, though; that’s docker.

Many of us started running Windows Server and endpoints, but in my case, the cost and substandard tools turned me away. I was running A DLNA server and using WDS (yes, very overkill for home, but fun to learn for work), but then I found TrueNAS (then called FreeNAS) running on BSD. I now run a simple share from there and Kodi on my (Linux and Android) user endpoints. I don’t bother with imaging anymore, and use dd for backups to my NAS. My Firewall runs OPNSense (BSD) and I run OpenWRT on two TrendNet WAPs.

I’ll never go back to MS. It’s just not a welcoming platform from my perspective. Don’t even get me started on .NET or the various and sundry “redistributables” constantly required by every tool you try to use.

my distaste for MS grew

This is a natural progression. Inescapable.

That’s a really good point. At that point, we’re just talking about a voluntary answer, right? I’m more concerned about the API exposed to the world, so patching that away was what I was thinking.

So MX Linux (which, last I checked already had an alternative to systemd) should follow suit as a derivative of antiX, right?

ETA: I went from MX to Nobara last spring when my RX 9070 needed new Mesa to work (as opposed to a black screen), but I’d be happy to go back. It was super stable.

ID verification brought to you by Wegets Hakktalot. Where information security didn’t make it to the budget.

I would like a package you could easily install on any distro that patches age verification out of the system. I’m not switching distros (yet) for this, as much as I also am not on board with the concept of OS-level compliance with mass control and censorship.

No worries. I use Voyager. I don’t think I’ve ever cross posted, but I think it works. I see others doing it all the time

In case your client just spins trying to load the content like mine did:

Over the past few months, our former payment provider Nexi S.p.A. (“Nexi”) requested access to private data, which we understood to be specifically the usernames and passwords of our supporters. We have refused this request. All our attempts to clarify Nexi’s request, or to understand how their need for such information was necessary and legal, were met with what we consider to be vague and unsatisfactory explanations relating to a general need for risk analysis. > > Subsequently, we found ourselves unable to receive credit card donations through Nexi’s system. In the afternoon of 10 March, we were further informed that our contract had been cancelled a few days prior on 7 March, due to our supposed failure to meet their deadline to fulfil their request. This deadline was not communicated to us beforehand, despite us having been Nexi’s customer for the past 15 years. This is completely crazy! As 450 supporters are affected, that is a huge amount of donations that were cut off!

Here’s what they said:

Like many of you, we were surprised by the news last week, and questions quickly followed about our position on this matter. We just have to wait to see how this will develop for FOSS and Linux in general. It isn’t easy for us to make a clear statement on it at this moment, because this decision involves not only the distros but also DE/WM environments, software packages and mirror networks. Like Arch, we don’t have any infrastructure to track how many users download or install our system, let alone who is running Endeavour on their machines. Besides the fact that it goes against FOSS fundamentals, we simply don’t have the manpower or resources to take on this near-impossible task.

Also, in creating this law, not a single person or entity from the FOSS world was represented or heard, and there is still a window of opportunity open to address the concerns for open source software and Linux/Freebsd systems before the law takes effect. After the news dropped, the OSI, FSF, and Linux Foundation must have realised their mistake in not reacting in time and hopefully will come into action for the many distributions and other FOSS projects, like us, that don’t have Californian or US legal representation. So, all eyes are on them, because Colorado and the rest of the world are next… We are not blaming any of the organisations mentioned by the way. We are just pointing out that the law isn’t set in stone, yet.

I don’t update my Keepass db often enough to need syncing. Maybe every other week or so I just pull the latest backup from my desktop from backblaze b2 to my phone, or if I change something on the phone, I send a copy to myself using signal “note to self.” Then I manually merge the databases.

Pretty low-tech.

Though development seems to have ceased for a few years now

No. A Mac becomes a non-personal computer. And NPC…?

Isn’t VirtualBox an Oracle property now? Fuck VirtualBox.

Lol! I’m glad you picked on that. I won’t badmouth them, but the user experience does that for them. That guy from the party must hate himself, haha

I was at a party about fifteen years ago. A guy introduced himself and we gabbed for a few minutes. Then he asked what I do for work (IT sysadmin at the time) and I told him and asked the same. He said he was in sales for a tech company. I asked which one, and he stepped close and whispered, “Oracle.” I could see he was prepared for me to bring the hate. He saved himself when he told me he was actually leaving for a gig at Dell. Later, I learned from the host that he made that part about leaving up because he felt bad. I later learned he went to work for Nutanix. Poor guy hated his own employer, and it was obvious.

Good catch. I don’t usually see SAS as /dev/sd* so I assumed. Almost the same cables, though *usually better made.

I second this. SATA cables are cheaply made and can present issues that seem to indicate drive failure.