Okay, so the title might be a little misleading. I waved goodbye to Windows in favor of Linux (obligatory "I use Arch, btw") some time ago. Given that my personal laptop's hardware was of the 2016 era, I just couldn't run Windows very well any longer. Not that I wanted to anyway. I opted for an Arch-based distribution called CachyOS, set it up once, and didn't fiddle with it at all. It worked great! But as the aging hardware continued to cause problems, it became apparent that it was time to mov...
Lessons on laying out the 404 Media zine using a relatively weird setup—on Linux, using Affinity, with the help of the Windows translation layer WINE.
Saving this one for posterity since I seem to run into something like this once every couple of months. Really gotta get a Mac for my next dev machine. sudo apt update && sudo apt upgrade -y # Since you mention that you have set your user to be root: sudo sh -c 'echo "[user]\ndefault=root" > /etc/wsl.conf' wsl.exe -l -v # Confirm your distribution name for the following command: wsl.exe --terminate Ubuntu Credit to this StackOverflow answer.
I’ve always taken an liking to dwm. For a very short period of time, I actually daily drived it, because I had no other laptops other than my sadly underpowered server, and sucklessware did the job (kind of). My reason for hackintoshing, and preferring macOS in general is the top tier design mixed with your normal everyday UNIX utilities, like good old zsh, cp, and ssh. No bullshit like whatever the fuck PowerShell is.
In what I hope will be the last entry in the "Brent learns the basics of VM provisioning" series, I finally moved to using Hashicorp's Vagrant yesterday. I'm glad I took the time to mess around in VirtualBox itself first - I always like understanding what I'm working with before I move to abstractions - but Vagrant makes it significantly easier. Vagrant sets up SSH in your VM by default, which is a nice time-saver, and generally makes the process of automating VM setup quick and easy. Behold: 1
OK, quickly discovered that I was less brilliant than I thought yesterday. It appears that for the functionality I wanted (both the ability to SSH into the VM and to port forward from my local machine to an application running on the VM) I need to use a NAT and not a bridge network. I spent a while struggling with this and discovered that to assign your VM to the standard 10.0.2.* range and successfully connect to the internet, a NAT drive should be your first network adapter. I'd initially had
I discovered recently that RHEL has a free developer license, something that could have saved me a lot of trouble if I'd known it earlier. Since I do a lot of work in RHEL I've wanted to have a virtual environment that mimics it - I had been working in WSL, but I think having to work with VirtualBox VM does a better job of replicating the experience of working on it in production. You'll need to get a RHEL Developer License to download the necessary ISO image. You can pretty much roll with the
Forget WINE; a weirdly fascinating technique to make Photoshop work on Linux involves chopping up a remote access client into a windowing interface. It’s wild, but it kinda works.
The periodic Rust-induced conflicts happening with the Linux kernel hint at underlying generational problems facing the project. And it’s already led a prominent maintainer to quit.
Let's learn how to set up our own private network for secure self-hosted services.
Let's learn how to set up our own private network for secure self-hosted services.
Let's learn how to set up our own private network for secure self-hosted services.
Let's learn how to set up our own private network for secure self-hosted services.
du -cha --max-depth=1 / | grep -E "M|G" From this StackOverflow answer - ncdu is also a good tool for this, allegedly, but its output didn't really seem to have any correlation to the actual folders on my server. I feel like I have to do this once a year because of storage issues and always forget, so hopefully this serves as a reminder going forward. Turns out snap is the culprit, as per usual. In a fit of pique I uninstalled snap and all of its files, and lo and behold I'm able to finally upd
My recent Linux experience has been pretty awesome thanks to Bazzite. It may represent the frontier of OS experiences.
The just-released elementary OS 8 is interesting, but it has a problem—its impressive but prescriptive interface paradigm has to live in an ecosystem of power users. Who blinks first?
Our technology should be good enough to work across operating systems now. The best way to test that is by using literally every platform. Which is what I plan to do.
Curious about customizing your terminal experience? Here's how I do it.