- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or # to comment.
There is no such thing as maintenance free hosting. There is just saving it all up for the eventual outage.
“I do not want to play sysadmin in my spare time.”
* proceeds to do a bunch of sysadminy things, but on a proprietary OS *
Huh…
Well, i get your snark but i disagree. To me, the annoying part of sysadminning is the “keeping things running” part. Doing them once is unavoidable.
Hey. I realise my comment may have come off as rude and made me sound like an asshole. It was not my intention to be disrespectful, apologies for that. The reason I posted that is because I read your post (thanks for taking the time to write and share it) and it left me a bit puzzled. I respect wanting something stable, familiar and that requires minimal maintenance, but you seemed to imply this is not possible with a more “traditional” NAS setup. Many of the points you raised about wanting an applliance-like experience are equally achievable on most Linux distros, with no license fees, and with a lot more flexibility, should you need it in the future (although I understand you don’t need or want it).
Take Debian for example (a.k.a. the world’s most boring distro, in a good sense). With the knowledge you demonstrated about the underlying services involved (BTRFS, Wireguard, etc), it would have taken you no more time to configure the same set of services on a minimal Debian install, it would also run rock-solid for many years, and updates would be entirely at your discretion (as they are with RouterOS). Plus, your pockets would be 50 EUR heavier. But for me, personally, by far the biggest avantage of going with Linux for a data storage solution like this is the possiblity of using ZFS.
Also, have this Debian meme:
Doing it once… how cute. You can always tell when someone only deals with enterprise level networking equipment. I’m not being critical, just realistic. Anything like this will eventually break. And in the weirdest ways imaginable.
I mean… It would work fine to use ROS for this, and truly, my mikrotik devices are definitely hands-off except updates and few rule adjustments, but this isn’t really any different from a Linux box. You have about as much initial config in a hardened immutable box as this.
The other thing is that mikrotik code isn’t open, which might be an issue for some.
I want to add that I respect this approach, it just seems like about as much work as any other roll-your-own solution.
Yeah, their GPL “compliance” is a disgrace.
My thinking was that while the initial setup time might be comparable, i’m banking on saving time with long-term maintenance. Most regular linux distributions have so many moving parts that often also change from one major version to the next. One could argue a bespoke minimal installation based on alpine or something would alleviate that, but at the cost of much more setup time (for me, at least). But i’m not saying my way is particularly the best; it’s just what works well enough for me.
Appreciate your words!
