Thanks for your tips!
Fedora. It uses newer packages, but prioritizes stability. It also has a bit of a learning curve which will help ease you into the more complex linux concepts.
Good point. I might look at it. Do you know how it is in terms of bloatedness? Say I want one distro everywhere is Fedora good for servers too you think? I mean I guess there is only one way to truly find out and that is to test it.
Bloat is subjective. Fedora will be less bloated than Ubuntu, but will be more bloated than something you self install in Arch. But bloat isn't a bad thing in all cases either.
Desktop and Server use cases tend to have different expectations. Servers tend to prioritize base bones and unflinching stability. Desktop tends to want features and hardware compatability. There's a reason Debian is used for servers but Arch is used for desktop.
Fedora doesn't pop up much for servers because of it's 6 month release cycle. But another Red Hat distro, like Rocky or Alma would be a good fit for a server because of their extended release cycles and focus on stability above anything else.
Bloat is subjective. Fedora will be less bloated than Ubuntu, but will be more bloated than something you self install in Arch. But bloat isn't a bad thing in all cases either.
Desktop and Server use cases tend to have different expectations. Servers tend to prioritize base bones and unflinching stability. Desktop tends to want features and hardware compatability. There's a reason Debian is used for servers but Arch is used for desktop.
Thing is Debian (or pehaps I am thinking about Ubuntu or both) seems to have a lot of uhm kernel options enabled for such things as bluetoth, audio, keyboard, mouse etc. that I assume will never be used on a real server (unless some server software strangely depends on these very unserver-like things). I get the impression the in the olden golden age it was more common to have separate kernel settings for server and desktop but now since computers are so powerful they just leave it all in and dont have separate kernel configs for server releases of distros (if they even have server-specific distros at all).
I run all hobby projects on potatoes so RAM usage is very limiting a lot of the time for me.
Fedora doesn't pop up much for servers because of it's 6 month release cycle. But another Red Hat distro, like Rocky or Alma would be a good fit for a server because of their extended release cycles and focus on stability above anything else.
Aha,if its not mentioned often its probably for a good reason. Cool might look at Rocky and Alma then maybe. It would be convenient to have the some distro or at least very similar distros for server and desktop.
Debian stable is stable, but you may feel the obsolescence mounting before the next release. You can improve that a bit with back ports.
I think most of the Bluetooth etc. would be modules which don't load for lack of hardware. Now there is still stub code in the kernel to attach to the module but I suspect the cost of this is rather low.
(post is archived)