A Raspberry Pi 3b is about as plug-and-play with wifi and audio out as you can get, for $35 usd. 64-bit, Arch ARM has an image for it, the support and community are the absolute best you can get in an SBC, pretty much anything you could possibly want to do with it will have a blog writeup guide that sonebody's already done. If a 4-core 1GHz processor and 1GiB of memory are suitable for the software you want to run, that'd be my go-to.
Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
Yeah, this sounds perfect. Someone else suggested the 3B+ as it also has a WiFi module. It's not than powerful enough; it's literally going to be sitting on a shelf connected to the AUX input of a dual-speaker radio thing we got for xmas one year, and running snapclient and little else.
Rpi 3B+ (not 3B, no wifi on that one) or the Pine quartz64 B should work. Both have Arch Linux for Arm support, wifi, and a 3.5mm audio jack
Beautiful, thanks. That's a solid suggestion.
You don't want Arch since it isn't designed for embedded. The best option of the top of my head would be the Pine64 Ox64
I want Arch because I'm currently most familiar with it; it's what's running on everything else in my house. Mine is the sort of brain that purges information that I don't use, and the worst case for me is some little box running somewhere in the house with a distro I'm not familiar with which develops a hiccup. Then I have to spend a day with a browser trying to figure out the special snowflake commands needed to troubleshoot and fix whatever went wrong. Because it's invariably a dependency issue, and that's invariably specific to the distro package manager, and that's dicking around with tools I never use because that distro is running on exactly one of the 9 computers I maintain and I usually never touch it.
If you've seen one Linux you've seen them all. The big difference is that busybox is much more lean
This is absolutely not true. Package managers make a huge difference. There's a big difference between rolling release distros and non. Some distros don't use systemd, and dinit is vastly different from s6. Distros that use NetworkManager have different tools and processes for getting online than ones that use connman, which are different than netctl.
In fact, the only time Linux distros act the same is when they share parentage. Ubuntu is mostly Debian (but is still pretty different), and EndeavourOS is mostly interchangeable tool-wise with Arch. But even then, if you are familiar with Arch and get dropped into Artix - which derives from Arch - you're mostly fucked.
I have to hard disagree with you on that point. LFS is nothing like CentOS in any way that matters.
Except anything that is widely used follows the same system. Everyone uses systemd and package managers work fundamentally in the same way. (Not that you would want to use a package manager or systemd in a embedded context)
Arch is not going to fit in a cheap device. Those devices have limited flash that has limited writes and your ram is going to be limited. You want a static system that only has what you need. You can build a system with buildroot that will fit in a few mb of flash.