That’s…an opinion that is not backed by any facts at all. What in the world are you talking about with “bloat” 🤣
So you’re a newbie, and making lots of wild claims and taking awfully opinionated positions in this thread all over the place. I don’t think you want help, so just be on your way 👍
This…is not accurate. Not being pedantic, just correcting the misunderstanding so you know the difference.
LTS releases are built to be stable on pinned versions of point release kernel and packages. This ensures that a team can expect to not have to worry about major changes or updates for X years.
Rolling Releases are simply updating new packages to whatever versions become available when released. Pretty much the opposite of an expected stable release for any period of time.
Doesn’t have anything to with “forced reinstall” of anything. If you’ve been having to fully reinstall your OS every time a new LTS is released, you are kind of doing extra unnecessary work.
Well, to be honest, you’re choosing the two most difficult distros to manage.
It sounds like you’re kind of new to the area…why not just use Fedora?
Would be helpful hearing about WHY you want to switch if you’re already happy.
There are certain utilities, but it’s generally not useable.
Also most games where k/m would give you an edge over touch controls run detection and ban accounts anyway.
Yes, but don’t think you’re going to be automatically playing games with a keyboard and mouse if they don’t already support that 🤣
Interesting. I’m assuming an engineer found a specific use-case for a major performance gain that makes this permanent change a benefit for all.
Guessing this is dimensional database or vector related for some “AI” applications because this is a fairly normal tweak for enterprise backend DB machines to implement.
They are DevKits, as someone else mentioned. Very literally described as such.
Don’t be upset when you get exactly what they state by ignoring their own words.
8GB it more than enough to run whatever desktop. Probably not game, but any desktop distro is fine.
Mint doesn’t use Gnome or KDE, which is why devs generally steer clear. It’s best to be coding and running the thing the most number of users will be experiencing.
People in here like to hate, but there’s a damn good reason. The majority of the people who are vocal about distribution choice aren’t contributors, long-time users, or experts in the field. A lot of us who are just want a simple, quick installing, porting, “out of the way” (no heavy customizations) and functional distro with a large user base, and a solid team behind it. This means it’s not going to immutable, and it’s not going to to be by Canonical.
A lot of us use Fedora for this exact reason.
As others have stated, it’s probably because you’re activating the network from an IP that is defined as being in another time zone in between two locations. This can sometimes happen with certain VPN configurations as well.
Here’s some info on debugging a bit further to help determine if this is the issue: https://www.linuxtechi.com/sync-time-in-linux-server-using-chrony/
And here’s how to force a time zone if needed: https://www.cyberciti.biz/faq/howto-linux-set-time-zone-per-user-basis/
I’m aware of what it is. This is a Fedora Server install that shouldn’t have it enabled by default because it generally only fits the use-case of home users. Someone installing the default package list in an enterprise setting would not want this enabled.
I even checked to be certain, and it is not enabled by default.
Doesn’t matter. Your machine going to another is not simply due to mdns running. In fact, I doubt that’s a default package selection in Fedora Server for security reasons, but I could be wrong.
Run dig [whateverhostname] from your machine, and then check /etc/systemd/resolved.conf on the server and see if something with MulticastDNS is enabled. Don’t see why that would ever exist as a default.
Your router is doing that, not Fedora Server.
It simply does not work. Tested across 10 machines for fun with different hardware compilations. The only ones that don’t cause a problem are the outmoded GTX chips. Simply does not work for DC-grade hardware whatsoever.
I was hoping this could be pivoted to a more open detection and download system for general use, but it’s not even close.
I continue to contribute in the most minor way to both, and it’s very true that Hughes LARGELY runs this repo. This is becoming a problem, especially since the majority of companies do not contribute, though they use the upstream just like everyone else.
If Amazon, Google, Dell, Hetzner, Equinox, DR, DO…etc all paid their fair share, they’d be able to pay honest contributors just simply for making what is already available MORE readily available. That’s what this project is about.
On the hardware manufacturer side: AMD, Nvidia, Intel, Realtek…etc are also not chipping in.
This is a CRUCIAL project for larger adoption for home users. Yes, most enterprise-sized companies manage their own semver releases for firmware, but they still use these tools. They should contribute, not only because it’s the right thing to do, but a miniscule amount of money for them to do so to ensure the same people making this such a success can continue to do so.
Need the specific Thinkpad model #. Should be on the bottom.
systemctl --failedand see if you get anything there