this post was submitted on 15 Jul 2023
131 points (99.2% liked)

Linux

48372 readers
951 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

Like most people, I entered COVID as a normal hobby geek with a Linux server I played around with and a healthy hardware habit with a side of home automation and DD-WRT. I emerged from COVID enrolled in college, now with two servers (one new build, one rebuilt from my first one), two Pi, multiple instances of Home Assistant (one dedicated) and putting sensors on everything a sensor could go on and rewiring switches for wifi control of overhead fans, flashing every compatible router I could find on Amazon Warehouse with DDWRT in my home for an ad hoc mesh network (no, it didn't work, but I didn't care) while cabling everything to switches and creating a really hilarious network deathtrap tripping hazard, a massive media library (discovered Handbrake and making multiple resolutions) and a Sonos home theatre system. And yes, played an unhealthy amount of Animal Crossing and got an NVIDIA Shield Pro for streaming and Plex, as you do. I'm sure everyone can relate.

SBC's were the natural escalation; I had credit card bills to pay off and that's going to take a while.

I gatewayed with Pi like ten years ago but it took off during Later COVID when I noticed my credit score and started testing it as a NAS, Media Server (later: Cassiope Media Server, my second end to end Linux build), then got into learning about the kernel itself. I already had an Odroid (Home Assistant Blue) so why not go on, so project-based SBCs seemed healthy; I had a reason for buying one. This led to more Pi's--as I couldn't use Kernel Pi (Eurydice) for it and Andromeda Pi was masking my personal network, then I needed one for a Pihole (Iphigenia, Hecuba), which is how I ended up with a BeagleBone Black (Medusa) for an Open Thread Border Router. Still pretending I wasn't just collecting them like cats, I networked them together and just enjoyed looking at them and making them matching banners with figlet with the excuse I was learning how to do network-wide deployments over SSH (true) and learn Debian OS (technically, I am doing that) and started PoEing things (my credit card bills may not be getting lower, no).

The count stands at a total of 9: one (1) Pi Zero W, one (1) Pi Zero 2 W, one (1) Raspberry Pi 4B 4G, two (2) Raspberry PI 4B 8G, one (1) Odroid N2+, one (1) Beaglebone Black, one (1) PocketBeagle, and one (1) BeaglePlay. (Other: two Linux machines, Watson and Cassiope). Yes, they all have names and technically, each is associated with a project. The BeaglePlay's (Circe) associated project is 'create my own documentation on what it does because Beagles don't document'.

So which ones do you use, why, origin story, feelings: go.

(I'm moving in a week and half my hardware is being packed. I'm about to have to take down my network and Home Assistant and may be freaking out. I'm not sure I know where any light switches are here, either.)

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 1 year ago

I consider SBCs drastically overhyped these days. RaspberryPi was nice enough when it was released a decade ago, but these days you can just get a Beelink or similar miniPC, which is much more capable and often even cheaper. It doesn’t have the GPIO, but even if you need that, you are generally better served with a cheap MCU connected to USB.

I would put it another way; they're ideal for You Have One Vital Job Only projects; Home Assistant and Pihole are my two specific,, but robotics, a router, even a dedicated NAS would be a use case. I could run a lot of things on a mini PC with a hypervisor--soon, I shall start be experimenting with that--but One Vital Job Only projects are ones that do their thing without me ideally ever noticing them other than maintenance, if that makes sense. And even more important, things I should not tinker with because they're just fine, which is why I ended up building a second, dedicated Media Server/media ripping/encoding/NAS machine; once I did that, I finally had a stable media library I could access for more than a month at a time before I got An Idea That Would Be Fun and Oops Time To Reinstall (seriously; before I built that machine, I had to run my media and plex from a Pi (aka One Vital Job) because if I put it on my main machine, I'd tinker it to death; hence, separate everything. I am basically hiding the cookies from a three year old and I am the three year old).

Tentatively--and this applies to a much smaller population--they're perfect for deconstructing the Linux kernel and operating systems in general because you get to work at a reduced scale. I have the repository for the Pi kernel in my bookmarks and go to just read through it and get familiar when I have some time or if I remember something I want to look for (my usb wifi dongle testing project was invaluable for how much kernel homework I had to do, it's hilarious). I know and can write in basic C++, I know how to compile, but I still don't pretend to understand the kernel; with the Pi's scale, though, I can grasp it, if that makes sense. I can recognize the structure and begin to get how things fit together. I can even--tentatively--find specific parts, identify drivers, especially when it comes to specific removable hardware where it's fairly obvious and easy to follow (following actual driver files....that's in progress). My goal before I die is to be able to read and follow the entire kernel end to end; I think I'm going to need to look into the benefits of reincarnation or cryogenics admittedly, but hope springs eternal.

(BeagleBones--if nothing else--has seriously upped my game on Figure It Out For Yourself. Which yes is a very me-specific use case, requires more homework to get context than literally every class I'm taking combined including TCP/IP class, and I literally don't have time to do in more than sprints, but did lead to me literally being able to making my first Universal New Install Checklist (covers every Linux operating system I've ever used including all my personal configurations and scripts, in order, with all exceptions) and my first foray into creating an auto-install-and-configure script I can run on a new machine. Yes, those Beagles had me doing a clean install that many times. No idea what I'm doing there and I really wish there was a universal template for that.)

Having said that, I haven't jumped into MiniPC/hypervisor culture so I am up for changing my mind the minute I make the leap. And seriously, this thread has moved it actively up my priority list, which I did not see coming, so thank you for that.