In my freshman year of computer science our main computer lab was filled with Sage IV machines. Basically a Motorola 68k series with 4 or 5 serial terminals. Most people were writing Pascal code or using a simple word processor. But god forbid you were on there with someone taking assembly language. Because they could write really stupid code with super tight loops that never allowed any other code to run, and the only thing you could do was reboot. So if you hadn’t saved your code you were fucked.
So I never purposely wrote really bad code that would overwrite unprotected shared memory with random quotes from Marvin from HHGTG to mess with other people. I would never do that. That would have been unethical and shit… 🤔
I did learn a lot of basic hardware and operating systems though so there’s that.
I ended up ripping the HDDs and putting them on my server, then proceeded to share the drives as normal. My docker containers now use them perfectly fine. IDK wtf Synology is doing but it’s cumbersome AF.
I’m kinda weird for this one. I started with arch a long time ago, and ended up distrohopping because I borked my install. Everything else had problems for me eventually, including Ubuntu and Debian. At this stage, if you can figure out iwctl you’re good to go. This enables me to have a system up and running quickly in which I feel I have no restrictions on my abilities as a developer.
archinstall will do proprietary drivers for you, works great for me.
Isn’t archwiki one of the most comprehended wikis for Linux distros out there? If anything, the arch-wiki (to me) has often too many answers for the same problem than the other way around.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.