Live data from Hacker News

Fedora 30

fedoramagazine.org

11–20 of 99 posts

Re: Fedora 30

#11

This is good distro for developers by developers. I wouldn't suggest it for everyday users though. There are too many beta quality bugs since it uses really bleeding edge releases.

If the 6-month release cycle is too frequent for you as a desktop user, consider using RHEL/Centos. In general Red Hat's distros are top-notch and easier to reason about than other distros.

What? The software in CentOS' official repositories is horribly outdated (aka 'stable', which is why it runs on many servers). Why should a desktop system run CentOS? I'd rather recommend Ubuntu or one of its descendants. They also have LTS versions, if stability is a concern, but are not as outdated as CentOS.

Re: Fedora 30

#12
post #6

Love this, switched today! Definitely the most easy to use distro out there and, especially in the case of Silverblue, the most modern by far (containers only!).

Silverblue is pretty incredible, but after a month of using it (Fedora 29) I did hit the occasional RPM I couldn't install because OSTree didn't support layering packages to that directory. It's also weird about third-party repos. I also wish more software was available as a Flatpak - unfortunately Ubuntu's mindshare means more developers are aware of the proprietary Snap format.

I'm super excited about it though and will keep using it every month, it finally solves the dependency problem most distributions run into.

Re: Fedora 30

#13
post #9

Earlier quoted context omitted.

F29 included bugs such as: -Cron jobs don't run -Package manager creates multi-gigabyte log files -Package manager crashes on systems upgraded from previous releases -GNOME crashes when switching to a virtual terminal and back -Default bluetooth config doesn't work for some devices -Ethernet runs at 10mbps instead of 1gbps https://fedoraproject.org/wiki/Common_F29_bugs

> -Default bluetooth config doesn't work for some devices Bluetooth (Bluez) is a trainwreck on any distro; even the version shipped with Ubuntu 18.04 (LTS!) is broken.

Not my experience. Or, if anything, bluetooth on Ubuntu works much better than on my Windows laptop (Lenovo).

Re: Fedora 30

#14
post #9
post #7

Earlier quoted context omitted.

What beta quality bugs?

F29 included bugs such as: -Cron jobs don't run -Package manager creates multi-gigabyte log files -Package manager crashes on systems upgraded from previous releases -GNOME crashes when switching to a virtual terminal and back -Default bluetooth config doesn't work for some devices -Ethernet runs at 10mbps instead of 1gbps https://fedoraproject.org/wiki/Common_F29_bugs

I think the Fedora community is pretty responsive when it comes to fixing bugs that are under their control, and the developers dogfood the desktop enough that they care about these things.

Also, Fedora gets new kernels all the time, and that often takes care of problems that sometimes persist in more "stable" distributions.

I have one mid-level issue per release, I figure, and it is usually patched within a couple of weeks.

I did have a bad experience upgrading from F27-29, so I've only been on F29 for maybe a month or so, and it has been smooth so far. I will probably wait a few weeks to a month to upgrade to F30 to increase my chances of a trouble-free transition.

Re: Fedora 30

#15
post #9

Earlier quoted context omitted.

F29 included bugs such as: -Cron jobs don't run -Package manager creates multi-gigabyte log files -Package manager crashes on systems upgraded from previous releases -GNOME crashes when switching to a virtual terminal and back -Default bluetooth config doesn't work for some devices -Ethernet runs at 10mbps instead of 1gbps https://fedoraproject.org/wiki/Common_F29_bugs

> -Default bluetooth config doesn't work for some devices Bluetooth (Bluez) is a trainwreck on any distro; even the version shipped with Ubuntu 18.04 (LTS!) is broken.

This is true, F29 just happened to ship with an extra-broken default config.

Though I have yet to see any BT implementation that isn't at least a little bit broken. Nobody actually conforms to the spec so you have to attempt to make your noncomforance work with the widest possible variety of other vendors' nonconformance and you'll always find device combinations that just don't work together.

Re: Fedora 30

#17
post #9
post #7

Earlier quoted context omitted.

What beta quality bugs?

F29 included bugs such as: -Cron jobs don't run -Package manager creates multi-gigabyte log files -Package manager crashes on systems upgraded from previous releases -GNOME crashes when switching to a virtual terminal and back -Default bluetooth config doesn't work for some devices -Ethernet runs at 10mbps instead of 1gbps https://fedoraproject.org/wiki/Common_F29_bugs

[deleted]

Re: Fedora 30

#18
post #9
post #7

Earlier quoted context omitted.

What beta quality bugs?

F29 included bugs such as: -Cron jobs don't run -Package manager creates multi-gigabyte log files -Package manager crashes on systems upgraded from previous releases -GNOME crashes when switching to a virtual terminal and back -Default bluetooth config doesn't work for some devices -Ethernet runs at 10mbps instead of 1gbps https://fedoraproject.org/wiki/Common_F29_bugs

Lot of dnf issues on that list. I find using dnf more reliable than using the gui software installer. That program is really buggy.

Re: Fedora 30

#19
post #12
post #6

Love this, switched today! Definitely the most easy to use distro out there and, especially in the case of Silverblue, the most modern by far (containers only!).

Silverblue is pretty incredible, but after a month of using it (Fedora 29) I did hit the occasional RPM I couldn't install because OSTree didn't support layering packages to that directory. It's also weird about third-party repos. I also wish more software was available as a Flatpak - unfortunately Ubuntu's mindshare means more developers are aware of the proprietary Snap format. I'm super excited about it though and…

Not to trn this thread into an argument about formats but snap isn't a proprietary format at all. It's a squashfs file with some metadata.

]and congratulations to Fedora!]

Re: Fedora 30

#20
Too bad they didn't get Sway 1.0 package in time for Fedora 30. That's the issue with non rolling releases, you miss the train and now we have to wait months.

I also tried out Silverblue, but it was super unpolished, not a lot of documentation, and there's rpms I couldn't get installed that I needed for work.

Fedora is still my favorite Linux distro for just getting things done. Red Hat is a focal point for kernel and systems developers so you know you're getting no frills quality.

Post reply on HN