Sigh…

git revert HEAD
echo \*.json.\* >> .gitignore
git commit

My primary laptop is a Lenovo T495s. I’m a big fan because my requirements for a laptop aren’t particularly demanding, but while a 5 year old Ryzen 7 is a bit aged, I’d hardly consider it underpowered, at least for my (and many others) needs. Laptops like this can easily be found in great condition and under $200. I spent a little more after a new nvme and maxing out ram.

This is the real problem.

Far too many people with rooted phones having no business with a rooted phone, installing whatever from wherever with no regard to the security implications.

At least people with root on a Linux system, by default, are going to be more knowledgeable in that regard.

Back in my day, /dev/hda was the primary master, hdb was the primary slave, hdc was the secondary master and hdd was the secondary slave.

Nothing ever changed between reboots. Primary/secondary depended on which port the ribbon cable connected to on the motherboard, and primary/secondary master/slave was configured by a jumper on the drive itself.

Archwiki is also one of the best consolidated sources of information on Linux, too, whether you run arch or not (I run arch, btw).

Contrast to circa 1997, and I got dual boot and mounting my windows drive figured out. Hadn’t found out about non-root users yet.

I asked in EFnet #linux about how to start x. The answer I was given was rm -rf /. I said Thanks and rebooted to Linux.

Ladies and gentlemen, that is not the correct answer. The correct answer was startx. The answer I was given fucked both my Linux and my windows drives.

Yeah WiFi seems to always be the biggest pain in the ass, and it’s still way easier than it was 15 years ago.

Haven’t had a single laptop with an issue, personally (though I only have bought Lenovo laptops in the past 7 years or so, but in that time I’ve bought 3). I’ve got one (really cheap) WiFi dongle I’ve had on my HTPC that had been a pain. Had I taken the time to choose the other really cheap one that had a different chipset, it would’ve worked out of the box. Oh well.

Einstein Says is arguably a much better template.

You sound like someone who doesn’t want to save 10 minutes of work every day because it might cost you half an hour every month.

All I hear is FUD.

I have a couple scripts running in containers. I’m too lazy to do a proper CI build and I only run it on one system anyway so I just got pull and docker build. Sorry if i offend you.

Though if i keep this up I’ll probably just start to use my generic python container and commit a shell script to docker run with . mounted to /project or something, and set the entry point to pip install project/requirements.txt; python project/main.py.

Sorry but IMO that’s FUD.

The reliance on it legitimately prevents the issues that it’s likely to cause. It’s made to be both idempotent and ephemeral.

Give an example of a Python project. You make a venv and do all your work in there. You then generate a requirements with all the versions pinned. You start build a container on a pinned version of alpine, or Ubuntu, or w/e. Wherever possible, you are pinning versions.

With best practices applied, result is that the image will be functionally the same regardless of what system builds it, though normally it gets built and stored on a registry like Docker Hub.

The only chance a user has to screw things up is in setting environment variables. That’s no different than ever before. At least now, they don’t have to worry about system or language-level dependencies introducing a breaking change.

If it’s an open-source project, usually the dockerfiles are available for reading.

Do you audit every line of code that you run in production? If you are trying some new python/django/sql app, are you reviewing all that?

I’d assume with a python based project, you’d be able to at least look at requirements and tell there’s something that sets off red flags. And you are either familiar/trust the maintainer, or you are reviewing the actual python itself?

Beyond that, the dockerfile is essentially just installation instructions for getting it running on a virgin system of X distribution. I wouldn’t call that a black box.

If the container isn’t part of an open source project, then this is a moot point then. The project itself is a black box.

My office has official chat (teams) and unofficial chat (Mattermost).

I don’t think there’s anything wrong with having a more casual discussion platform at work, which is what Mattermost had become.

Friendly reminder that open source projects don’t just need coders contributing to them.

Technical writers are very appreciated.

Same. I remember getting interested in Linux in like 1997 or so, and it seemed like RedHat was preferred for newbies.

Of course, what were the alternatives then? It was basically Slackware (or Suse), Debian, and RedHat (or Caldera). There was no RHEL or Canonical or SElinux back then. It was a different time.

Hell one of the language packs for installing RedHat was “Redneck”. It was a gimmick to demonstrate localization options.