

real men write their code one bit at a time with a laser pointer and a fiber optic network cable
Or you could just use zig which is better at compiling C than C (the second it supports the espressif chips I’m never touching C again)
real men write their code one bit at a time with a laser pointer and a fiber optic network cable
Or you could just use zig which is better at compiling C than C (the second it supports the espressif chips I’m never touching C again)
I get very far by just keeping a set of folders for each piece of equipment in a git repo.
Pictures, etc, and sometimes the PDF manual if I bother.
The difficult part here is being consistent over time - making sure you mark down when you bought things, serial numbers, etc. a proper website/app will force you to do this, but there is flexibility in having whatever convention you like most
Strongly agree. A guide for dead simple setups would be incredibly useful (e.g. gsuite as idp, oauth for a single app).
It took me a few days to get that basic setup working, and a few days more to improve it. But once it was up, it was rock solid.
Keycloak might seem a little daunting to start with, but is basically glue between your idp (ldap) and whatever apps need to authenticate.
Many cloud providers (the cheap ones in particular) will put patches on top of the base distro, so sometimes root always gets a password. Even for Ubuntu.
There are ways around this, like proper cloud-init support, but not exactly beginner friendly.
Once upon a time, I accidentally created a folder named “~” in my home folder (the company provided scripting framework would inconsistently expand variables, so the folder had a ton of stuff inside it).
I ran “rm -rf ~” and only panicked when I started to wonder why it wasn’t taking too long.
Good news is that it only managed to get halfway through my local checkout of aosp before I stopped it. Bad news was that it nuked most of my dotfiles.
Holy propaganda batman!
The list of articles on that website is…extremely focused on one subject only.
Locks are only held during system calls. Process termination is handled on the system call boundary.
You’re projecting windows kernel insanity where it doesn’t belong.
What the duck Microsoft bullshit is this?
There is no concept of locked files in extfs, much less inside the kernel. Resource locks and unkillable processes is some windows bullshit that no sane operating system would touch with a ten foot pole.
Since when is immutability controversial? Linus called out the Google patches as badly designed with massive code quality issues for good reason. Theo described OpenBSDs approach to it and it is truly a simply concept with good security ramifications.
BGP isnt just Turing complete, It’s Cthulhu complete