I recall having a band like that, there were two or three removable sections closest to the watch on each side, those may have been removed already if they aren’t there.
I recall having a band like that, there were two or three removable sections closest to the watch on each side, those may have been removed already if they aren’t there.
You’d probably get better conversations at selfhosted I know some folks there run *bsd network appliances. NASs, firewalls, etc.
Jokes on you, I’m supposed to be doing stuff.
With my step kid I’ve basically just told him I’m not making anything else for him if he doesn’t like what I made. If he won’t eat it, he can have fresh vegetables and/or last night’s leftovers instead. I give him some options before I start cooking, so he knows and has some say in what dinner is.
The exception is if I make something that’s objectively gross. I’ve had a few frozen package dinners that looked good but were outright nasty and made sandwiches instead.
I used both tumbleweed and leap for a bit and they really are good. I’m actually using tumbleweed on a home server right now and it’s been a champ. But…
My biggest gripe is opensuse seems to use different package names than any of the other distros for basic packages. I had to install a package that used capitals in the package name, and coming from mostly debian based distros, that made me rationally angry when trying to find the package I needed. I think it was network-manager or something that’s usually installed by default and I wanted something familiar.
Online directions for setting something up usually has deb and/or fedora rpm directions, which is usually just some difference in package names and the equivalent install command, searching the base package will let you figure it out. I had very few issues following debian/Ubuntu directions and translating them for fedora. Opensuse is always non-existent so you always need to translate those directions for opensuse, which is usually like doing it for fedora until you run into point (1).