I found it tiresomely political and strangely dogmatic way too much of the time. I didn’t get the impression that there was a wide cross-section of people on there.
Real talk, I want to try Guix but I have not successfully installed it on any hardware, including VMs. This includes with nonguix for proprietary drivers and stuff. I can never get past install, it always just craps out on some substitution thing. Am I just stupid?
Howdy. I have a “homeserver” that I’d like to actually start using. What’s currently keeping me from it are… Permissions.
I have TrueNas Scale running on top of Proxmox, and I can’t for the life of me not access NFS Shares from other VMs (specifically a Debian VM that I use as Docker Host) that I host in Proxmox. Plox hlp.
Arch is the only person who has been in my house for the last week and i have no clue how he is going about it and he has no clue how it is affecting him or how he feels and how it is affected me
What is something Linux related that you’ve learned recently?
As a meta question, could this work as an additional (or alternate) recurring discussion question? It felt similar in intent, to encourage people to keep learning / asking questions and chances are that if someone learned something then others will benefit from the information (or correct them)
After 26 years of using Linux, I did my first baremetal “immutable” distro install last week.
My youngest son is starting school and instead of the Chromebooks that they recommend, I took a chance and installed Fedora Silverblue on a $200 Lenovo “student-rugged” class laptop. Everything works and he hasn’t had any issues so far. He gets access to the same student platform as the other students through Chrome, but then I can install Minetest and Tux Paint and GCompris as well.
The older kids run Debian stable for years now, but if this works out, I might transition them over next semester.
I learned how a kernel actually loads a program and switches between them by using timer interrupts and interrupt vectors that point to specific locations in memory to resume execution from. Not specifically Linux related, but I'm trying to learn more computer science, and it just clicked for me two weeks ago. I've been programming microcontrollers for ten years, but those are monolithic programs, and while I knew what interrupts were and have used them, I never understood how an OS actually runs multiple things while staying in control. Now I do. About time I understood a core concept of these machines that have been here all 42 years of my life.
It's one of those "aha!" moments like when I realized classes and structs are just data types like any other in C++ when I was starting off programming and can be used like them. OOP became fun after that.
I remember when the mapping of virtual memory segments clicked for me. I think i said out loud, “that’s so clever!”. Now it just seems so fundamental to managing memory for user space applications, but I hadn’t thought about how it was done before.
I love the old Mac Pros and even built a trashcan setup for Debian a few years ago. But TBH, they use a lot of electricity for the processing power they provide. If you already have one or can get one for free, great, use it. Linux runs great. But I wouldn’t go to OWC and buy something that would be outperformed by a fanless, low TDP machine these days.
kbin.life
Oldest