this post was submitted on 09 Dec 2024
21 points (88.9% liked)
Open Source
31746 readers
126 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
what about Rhino (it is Ubuntu's unofficial rolling distro)?
I'm confused. Your OP seems to describe wanting something stable and "fault-tolerant," but then you go and ask about an unofficial rolling distro? I think you should figure out what your priorities are first.
i have priorities. And fresh software is higher priority that being ultra stable and fault tolerant. I used Tumbleweed which is a rolling release and it was perfectly stable. I would use SUSE server in no question, if it was free
I didn't mean to imply you didn't have priorities, just that a couple of them seemed to be conflicting. To me, what you described called more for reliability than cutting edge. I understand your concern with getting security updates expediently, but you can get those with less system stability risk using a more standard distro.
I haven't used a SUSE in a very long time, but as I recall Tumbleweed is an official product of theirs. I've not heard of Rhino until now, which gives me pause in considering it - let alone the fact it's not backed by a known significant team. There's nothing wrong with that, but when setting up a server like you're describing I'd rather it not require a significant amount of time at random once I've got it up and running, which is what can happen when relying upon less vetted software.
It's your choice, obviously. Rhino looks like it might make a nice desktop to play with, but I personally would really be hesitant to use it for a server because I just don't have the time to deal with problems at random - I've got enough of those already in my life. Your priorities are obviously different, and there's no denying the fact that even things going awry on your server can be a plus from a learning perspective. I would really be concerned with the project being abandoned since it's just a year old, tho.
Good luck whichever way you choose to go.