CollapseOS used to emulate the Z80 using... libz80, i think it was called? lib6502 is also a thing.
jaredj
joined 2 years ago
Sure, go ahead :)
The Gemini capsule is yet to be done, but the wallpapers are available at https://j.agrue.info/wallpapers/
This post inspired me to go find the tiling wallpapers I made 20 years ago. I almost made a pull request about it, but then decided not to, because it's GitHub. My wallpapers used to be on my own website, and now I'm going to make a Gemini capsule and put them up on that.
Yeah, I did one for my Dactyl Manuform and just oversized it by a couple millimeters and stuck Amazon bubbly envelopes on the inside. The bottom of each half is flat, the same shape, and rubberized, so the covers just go over the top, I clap the bottoms together (tee hee?), and chunk the whole thing in a lunch bag that barely fits. It stays together without slipping and without any attachment between the two cover halves. Janky but it's worked for years.
That's beautiful!
I 3d-printed a hard box for my Fourier. https://gitlab.com/jaredjennings/fourier-box. (wince, there is no photo nor even an STL in that repository.) I wanted it to fit in my backpack with a laptop and books, so it holds the two halves side by side, not stacked. I had to print it in two pieces and friction-weld them together. That sounds fancy, but it just means you take a piece of filament, put it in a Dremel chuck, and draw on your model. Wherever you push down, the friction makes the end of the filament melt. Then I put on some Sci-Grip 4 (dichloromethane), which further solvent-welded the joint.
If you wanted to make one like this for your cepstrum, you'd need to do it in more pieces because that's larger than a Fourier. Your case would end up to be the size of a laptop. You might not want that.
They are made (I think) to be implementable - even, to give implementors some flexibility. Then everybody goes and buys a tool to do it, and not that well. I thought 15 years ago that security configuration was a (voluminous) subset of system configuration and system administration, ripe for automation and rigorous documentation - not something to pay a different vendor for. But the market says otherwise. When you can split some work across a whole team, or even into a separate company, instead of glomming it into one job, that's worth money to businesspeople.
The C128 has a Z80 too ;) I don't reckon there was an SX128 though
Oh, like refusing to parse $5. That would be good. Thanks for looking!
Uhhmmmm... "sold for 00"? What part of the software in between this headline and my browser is parsing $5 (which clearly has no value at that moment), and why is it working on input it isn't intended to? What variables would exist and be interpolated into the title if they were to happen in a post title? Is this a known issue? An issue with the bot? An issue with Lemmy?
Do people get messages when you @ them? @krogoth@infosec.pub @jerry@infosec.pub @shellsharks@infosec.pub I don't want to report this post - it's a fine post - but I do want infosec.pub to be safe and secure.
I have heard that there is some arrangement whereby you run FreeBSD on your hardware, with Linux in a bhyve virtual machine; you hand your physical wireless card into the VM, where LInux's drivers can talk with it; and route packets from the main system through it. -- Ah, https://blog.desdelinux.net/en/wifibox-the-project-that-allows-you-to-use-linux-wifi-drivers-in-freebsd/
To try to set up such a thing as your first entry into a BSD might be frustrating, but if you kept on until it worked, you would definitely have dived deep. (Dove? Doven? Diven?)
I'm a long-time Linux user now using FreeBSD on my home server. The first few times I looked at BSDs, they seemed old and stale, like nothing was happening there, and the coreutils were less comfortable to use because they were missing some switches. But what I've learned is that FreeBSD builds incrementally, without undermining itself, and my own understanding of it can do the same. What I've learned about previous versions of FreeBSD is more likely to still be true about the next version of FreeBSD.
BSD people often mention how the BSD in question is built as a whole, not cobbled together as a distribution. This difference can be stated far more quickly than it can be fully understood: like a culture, of which you gather a nuanced understanding from a broad survey of its literature, rather than a movement, whose goals are painted in broad strokes by a manifesto.
Anyway, welcome! My experience has been that #freebsd on libera.chat is more lively during US daytime hours than later at night. The Handbook is definitely your first documentation stop. ZFS, with its snapshots and replication, seems to be the most-hailed feature of FreeBSD; DTrace didn't even make the top 10, but when I didn't understand why NFSv4+Kerberos was failing, it was indispensable. Have fun!