Title. Mainly asking for the library side, but PC cafe is also interesting to ask about.
Mainly since Windows 11 is 64-bit only, and it seems Windows 12 is going to subscription based on top of that, neither of which public libraries can afford tossing out computers and paying more in subscription fees than they make with overdue books.
My local library is only open for 2 days a week, due to a lack of funds for hiring more staff in the area. They use older Dell all in ones, and that just makes me think if they don’t have the money for being open 5 days a week, they don’t have the money to buy 4 new computers for the space.
Not even getting into the bigger libraries part of that system or the ones nearby. Some have 8 computers in groups, with 4 stations of groups.
So I was just wondering, if anyone has started or is aware of a Library/Public Computer focused linux-based OS? Perhaps one that allows immutable systems, and the library card system backed most use to enable end user access. Perhaps that’s a config file tucked away somewhere.
And I guess the PC cafe OS is interesting, simply due to the fact that Linux gaming has been making huge strides, and PC cafes are still popular in Japan, Korea, and China.
EDIT: I am not in control or assistance to the library, just looking if there’s a potential solution to libraries like mine. If I could give links to a library computer manager, or if I could give upstream bug reports to people making such software.
NixOS is immutable and highly reproducible, with the ability to rebuild identical systems with a declarative configuration file–including installed packages.
So in the case of multiple public computers, you would only need to create/maintain one configuration file that defines all of the user profiles, permissions, restrictions, settings, software packages, you name it.
It would without a doubt be what i’d choose for a fleet of public library computers. Extremely reliable and easy to setup to prevent tampering or misuse.
I wouldn’t. Relying on a cookie-cutter distro like NixOS is a recipe for disaster in the long run, IMO. I mean, sure, you could set it all up exactly how you want, but the next person coming in to replace you may not be familiar with NixOS. And there’s no guarantee you’d be around to train them - in my circles we call this the “getting run over by the bus” problem. More importantly, organisations need to be able to get reliable support - support from an actual organization they can count on, when shit hits the fan.
Choose an industry standard, well-supported distro like Debian/Fedora/OpenSUSE (or immutable variants like Fedora Silverblue/openSUSE MicroOS) deploy it using Kickstart/Preseed/Cobbler, and configure/maintain it using Ansible. If you’ve got large number of users to manage, use a centralized user/identity management system like FreeIPA or JumpCloid.
Don’t go for cookie-cutter distros unless you want to be their IT person forever.
What does “cookie-cutter” mean in this context?
It means DIY/hobbyist/niche.
If the config file is well documented, you don’t need to worry too much about that bus. And it isn’t several user accounts, it’s a computer that needs to be accessible to nearly everybody. Like said in other comments, a script to destroy everything on logout, and then add a configuration to logout on idle.
That’s not the point though, the point is about support.
The main issue is with cookie cutter distros like this is, things break, and when that happens, getting support can be a PITA. In fact I experienced this myself on more than a couple of occasions. Most recently, I ran a
nix-channel --updatewhich then brokenixos-rebuild switch. I couldn’t figure it out, asked online and they said nothing was wrong with my config, so I ended up restoring to a previous snapshot. This was just a VM btw so not a big deal, but I’d never run NixOS as my main, never mind putting it on user-facing machines in a public organization.The library won’t be able to find someone to support a random OS like “NixOS”. Just imagine putting out a job advert for that. Actually, they probably won’t be hiring a dedicated IT person in the first place, so they’ll reach out to some MSP and it’s highly unlikely they’ll be able to find some company willing to support it.
Just because you’re good and familiar with some obscure piece of technology doesn’t mean that it’s the right choice for an organization - because that’s how you build up technical debt. This sort of stuff happens all the time, I work for a MSP and often come across some adhoc DIY thing built by some random employee who left the company ages ago and now no one knows how it works, so they never maintained the thing and everyone’s scared to touch it lest it breaks something.
I agree that this is a good choice. But I doubt library staff will have the technical background to set this up. But if some local volunteer could do it, it would be a good option.
People couldn’t tamper with it even if they wanted to. Like literally how do I tamper with it??
-sincerely, trying to learn NixOS