

I run projects inside Docker on a VM away from important data. It allows me to test and restrict access to specific things of my choosing.
It works well for me.
Anything and everything Amateur Radio and beyond. Heavily into Open Source and SDR, working on a multi band monitor and transmitter.
#geek #nerd #hamradio VK6FLAB #podcaster #australia #ITProfessional #voiceover #opentowork
I run projects inside Docker on a VM away from important data. It allows me to test and restrict access to specific things of my choosing.
It works well for me.
Some of it is still in a museum.
I’m fluent in Dutch and at no point in the supplied link is there any reference to eating anything.
Attempted murder, torture, court, death, body parts being sold, heart being cut out and displayed for years, yes … eating, not so much.
Hands up if you have done this at least once in your life…
The SCSI solution requires making sure that you have the right terminator connector because of course there’s more than one standard … ask me how I know … I think the Wikipedia article on SCSI says it best:
As with everything SCSI, there are exceptions.
There’s a reason why there’s only privileged write access to /dev/sda.
If you run unknown software as root on any computer you get to experience first hand the impact of: “fuck around and find out”.
I can absolutely guarantee that you are not the only person to have spent quality time getting to know the intimate backwaters of a codebase tracking down a bug that you introduced whilst tracking down a bug.
Source: I’ve been writing software for over 40 years.
About that.
Just because I’ve done it this way and haven’t had issues, doesn’t mean it’s the best or only way.
You dared to ask a question and the tools to explore answers are readily available.
This is how we as a society make progress.
Please don’t feel like my experience is the final answer to your question … my experience tells me that this is rarely … if ever … the case.
So … please … explore!
If you genuinely attempting to quantify this, you can create a swap file of any size right there on your drive. You could iterate and test every setting for every scenario. You could even change settings dynamically if you wanted to.
That said, I leave it to the kernel to figure out and over the past 25 or so years that’s been fine.
I’m assuming you’re familiar with Asahi Linux?
It’s still very much a work in progress.
https://asahilinux.org/docs/platform/feature-support/overview/
At the moment I’m bridging the gap by using homebrew, UTM, ssh into local hardware and shortly remote desktop on EC2.
It’s far from ideal, but that’s where I found myself after my x86 iMac died last year, so I feel your pain.
I’m not sure if you’re being sarcastic, observant, or something else. There have been many a meal where I was asked what I wanted to eat and it’s rare that I go beyond the words “surprise me”, knowing full well that the person asking would eat the same as I was offered, making the “surprise”, less of a risk and more of an adventure.
In this case, OP asked a completely unanswerable question to which there was absolutely no reasonable answer, since we know nothing about the person, their interests, their experience, the hardware they have access to, or anything remotely resembling a needs analysis.
So, even my answer, generic and random as it might appear, was based on how I use a computer, namely, to be productive. I’ve been using them for over 40 years, mostly like that, with some sojourns into art and personal expression, not nearly worthy of public scrutiny, but not specifically “productive” as such.
So … what were you attempting to say?
Whatever you need to be productive.
So … six months and nobody notices?
What’s the problem?
Thank you. Glad I’m not alone in this quest with that kind of history.
My current desktop is Wheezy inside a VM - also across several platforms, but VMware, by design , doing the heavy lifting.
Anything of note, essentially everything except Audacity, is running on a Bookworm Docker host with X11 forwarding and reverse mount sshfs, so all the container “sees” is the directory I give it.
I’ve made several attempts to move away from Wheezy, but there’s too many scripts in my ~/bin directory to make that simple.
The “fresh paint smell” experience for me comes from a docker pull or docker build, but it does require hardware capabilities that died eight months or so ago, when my 64 GB RAM iMac died. No data loss, just endless frustration.
At the moment I’m exploring EC2 on demand. I suspect that for the $10k I previously spent on hardware, I can always have the latest on tap, but I’m still trying to get real-time audio editing to not be a weekly disaster. Getting closer, but not quite there yet.
I’ll have a squiz at NixOS, seems like an interesting approach.
Much obliged for sharing your experience!
Unfortunately I can’t run Debian on my M3 MacBook Air :-(
Wow, that brings back memories. Forgot about the whole Palm thing. That was a wild ride at the time.
Thank you!
I got a T-shirt from Mozilla in the early 1990’s and foolishly wore it to death. My Linux tie pin is somewhere, but I’m sure that my penguin tie has died, as have the Debian Potato CDs with boot disks for x86, PowerPC and SPARC.
Forgot about BeOS (and NetBSD for that matter), and wonder what came of BeOS.
With?