Live data from Hacker News

Why You Should Use Tumbleweed

rootco.de

21–30 of 68 posts

Re: Why You Should Use Tumbleweed

#21
post #12

That does sound pretty cool. Who owns Suse again? Do they have a social contract? How's their democratic decision making? Do they properly separate non-free software from their free packages? - Debian User.

and one question that doesn't get answered by that link - yes, we properly separate non-free software from our free packages

"Who Owns It" seems to be a company owned by a company floated on the stock markets. But with excellent community input.

That company is apparently actually making money selling at-least-mostly-free software, while supporting the properly-free openSuse.

Is that about right?

That's probably better than being Shuttleworth's toy.

Looks easily enough forked if needed.

I think I'd feel weird about going back to a OS supported by a for-profit rather than a charity, but that test suite does sound top.

I may give it a go for a while at least, next time I have to reinstall.

Cheers for making me pay some attention to it ;)

Re: Why You Should Use Tumbleweed

#22
This does all sound quite compelling. Somehow OpenSUSE has fallen under my radar, I've been an Arch user for a few years, and Gentoo user before that, and I'd only ever be interested in rolling distros, but I wasn't aware that OpenSUSE had Tumbleweed for this.

I did find dependency conflicts all too common on Gentoo, and keeping the system up to date was a frequent struggle. I've not had any major issues with Arch recently, and any that occur are usually fixed by doing a full system upgrade, but they do occur from time to time. I'd be interested to see how SUSE differs.

One thing I've noticed when doing a quick bit of reading on your Wiki - it sounds like you can't update Nvidia drivers from the package manager in Tumbleweed, and it has to be done manually. It also sounds like this process has to be done any time you update the kernel or X. This sounds like quite a pain - manually installing the nvidia drivers isn't exactly complex, but it's a number of manual steps that I'd rather not have to go through outside of the package manager every time I do a system update. Am I missing something here, or is this the case?

It also sounds like it supports installing with sysvinit rather than systemd, which is a rarity these days, and might appeal to some people.

Re: Why You Should Use Tumbleweed

#23
post #22

This does all sound quite compelling. Somehow OpenSUSE has fallen under my radar, I've been an Arch user for a few years, and Gentoo user before that, and I'd only ever be interested in rolling distros, but I wasn't aware that OpenSUSE had Tumbleweed for this. I did find dependency conflicts all too common on Gentoo, and keeping the system up to date was a frequent struggle. I've not had any major issues with Arch re…

nvidia drivers - we don't recommend them because we have a habit of adding kernels quicker than NVIDIA can keep up with their proprietary drivers

If you really want to use them, I'd recommend the dkms drivers we have in OBS https://en.opensuse.org/SDB:NVIDIA_the_hard_way#Further_read...

And yes, I believe if you want you can install with sysvinit, though we are primarily a systemd distribution first (with extensive sysvinit compatibility.. people still love those runlevels)

Re: Why You Should Use Tumbleweed

#24
Things that prevented me from using OpenSuSE:

1. no single letter user name allowed in the installer

2. yast rewriting config files

3. I couldn't get the partitioning tool to do what I tried which is plain simple /boot plus encrypted swap and root.

Re: Why You Should Use Tumbleweed

#25
With the recent announcement of Neon by KDE, and the rising popularity of Arch, and Fedora trying to get more modular (with multiple release versions) I can't help but feel the market is way oversaturated, but everyone is bringing something to the table better than everyone else. If we had a unified distro set rather than bascially four reimplementations of the same thing, we could be seeing a lot more momentum towards desktop Linux's adoption.

In general, there are two users of desktop distros:

A. Professionals and grandparents, who want stable, unchanging systems with long support. Think your SUSE Leap, your RHEL, your Ubuntu LTS, your Debian Stable, and kind-of-not-really Manjaro.[1]

B. Enthusiasts, developers, power-users, and gamers(!) who want the latest and greatest software. These are the SUSE Tumbleweed, Debian Testing, Ubuntu-nonLTS users (with a ton of PPAs), Fedora Rawhide, and Arch users. They don't want unstable software, they just want to get new stuff when the makers actually release it rather than have computers frozen in time - which in practice, no other OS actually does.

Nobody else is trying to ship an OS that intentionally holds back upstream released new releases, unless you consider the tiered versions of OSX / Windows / Android like that, except their availability is more based on your willingness to spend money / upgrade your device to get them than them just being delayed.

[1] I think there might be a schism between these two even further - grandparents probably want Neon style desktops just because individual distros are not honoring the release cadences of major projects like KDE or Gnome. Plasma 5.6 just came out and will not be in Ubuntu 16.04 alongside Qt 5.6, despite both fixing a tremendous number of bugs and issues with the desktop. That isn't cutting edge features, that is bug fixes, and I don't really believe in holding back major project releases like KDE or Gnome regardless of distro. Just have a switch to pin it if its corporate. But there is a tremendous lack of communication between upstream when major software projects like KDE cannot bugfix their major userbases at all for years (IE, Ubuntu LTS).

A great comparison would be to the Android world. Google devices see continuous releases for their support periods monthly now, like fixed release distros. Cyanogenmod has daily releases like a rolling distro. Any non-Google phone basically never gets updates and plays Debian Stable. But all of them, when using the Play Store, will upgrade every user facing APK on the system whenever updates are available, because those updates are not Google's responsibility, they are the developers, and users are used to knowing it is the app makers fault when something breaks, not the distributor (Google Play). General adoption of the Linux desktop requires this distinction be made, where developers can both easily offer their software to Linux users and be held responsible when they break it, rather than having everything filtered through distros that will basically throw the baby out with the bathwater by freezing all software because they trust nothing.

But on topic, it seems like we now have a half dozen different solutions to the same problem. Why can't I have a distro with SUSE's infrastructure, Ubuntu's brand and userbase, Debian's community, and Arch's software availability? It is like everyone has their own piece of the pie perfected but rather than us having a whole pie to solve any of these 2/3 use cases (I'd consider the server use case is extremely well provided for nowadays, the only domain Linux distros are doing a good job at, between RHEL / Stable / Ubuntu Server). It isn't even really about different distros for different desktops anymore, since pretty much every desktop is available on every distro - either officially like in Arch / Debian, or through the software universe of Ubuntu / SUSE / Fedora. The distinguishing factors are just the holes the other distros will not fill because they are too busy fixing another problem unaddressed at home.

It does not help that the work is then duplicated across all these projects. Packaging Qt and KDE are a pain in the ass, but there are four release teams between all these distros maintaining those releases independently. There is no actual way to fix this - the Debian, SUSE, Ubuntu, Fedora, and Arch devs have already dug in within their camps - but it is still sad that desktop Linux remains niche because rather than working together and combining the best of everything we have everyone is working on their own thing while the whole is lackluster against the competition.

Re: Why You Should Use Tumbleweed

#26
post #24

Things that prevented me from using OpenSuSE: 1. no single letter user name allowed in the installer 2. yast rewriting config files 3. I couldn't get the partitioning tool to do what I tried which is plain simple /boot plus encrypted swap and root.

1. kinda true, though the current version of the installer lets you skip the username creation so you can do whatever you want afterwards :)

2. formerly true - YaST lives happily with config files these days. When possible it co-exists, only a few specific YaST modules need that absolute control and only rewrites them by warning you well in advance. ie. Not true any more

3. I think we fixed that..it's a radio button now.. Encrypted LVM-based proposal https://lizards.opensuse.org/2016/03/15/highlights-of-develo...

Re: Why You Should Use Tumbleweed

#27
post #22

This does all sound quite compelling. Somehow OpenSUSE has fallen under my radar, I've been an Arch user for a few years, and Gentoo user before that, and I'd only ever be interested in rolling distros, but I wasn't aware that OpenSUSE had Tumbleweed for this. I did find dependency conflicts all too common on Gentoo, and keeping the system up to date was a frequent struggle. I've not had any major issues with Arch re…

nvidia drivers - we don't recommend them because we have a habit of adding kernels quicker than NVIDIA can keep up with their proprietary drivers If you really want to use them, I'd recommend the dkms drivers we have in OBS https://en.opensuse.org/SDB:NVIDIA_the_hard_way#Further_read... And yes, I believe if you want you can install with sysvinit, though we are primarily a systemd distribution first (with extensive s…

Ah, that's fine in theory then - I use a dkms package on Arch too since I use a non standard kernel with VFIO patches for PCI passthrough. Interestingly I see people have reported getting PCI passthrough working with the standard SUSE kernel too, so I'll have to give that a try.

As far as I can see the x11-video-nvidia package in the page you linked has quite an old nvidia driver version for Tumbleweed - https://software.opensuse.org/package/x11-video-nvidia

Again I might be missing something, and in practice it might be easy to install the latest drivers, but this is a bit off putting. I don't know the details of how your build system works or why it keeping up with Nvidia drivers complicated, but this seems like it'd be quite a fundamental thing for a lot of users. The vast majority of people who play games on Linux are going to want recent proprietary Nvidia drivers, so having that as a footnote at the bottom of an article that says it's not recommended/supported doesn't inspire confidence.

Still, I'm intrigued enough to give it a try.

Re: Why You Should Use Tumbleweed

#28
post #21

Earlier quoted context omitted.

and one question that doesn't get answered by that link - yes, we properly separate non-free software from our free packages

"Who Owns It" seems to be a company owned by a company floated on the stock markets. But with excellent community input. That company is apparently actually making money selling at-least-mostly-free software, while supporting the properly-free openSuse. Is that about right? That's probably better than being Shuttleworth's toy. Looks easily enough forked if needed. I think I'd feel weird about going back to a OS suppo…

I'd say that's a fair assessment :)

SUSE isn't your typical 'for-profit', and the nature of the relationship with openSUSE reflects that

Thanks for the consideration

Re: Why You Should Use Tumbleweed

#30
post #27

Earlier quoted context omitted.

nvidia drivers - we don't recommend them because we have a habit of adding kernels quicker than NVIDIA can keep up with their proprietary drivers If you really want to use them, I'd recommend the dkms drivers we have in OBS https://en.opensuse.org/SDB:NVIDIA_the_hard_way#Further_read... And yes, I believe if you want you can install with sysvinit, though we are primarily a systemd distribution first (with extensive s…

Ah, that's fine in theory then - I use a dkms package on Arch too since I use a non standard kernel with VFIO patches for PCI passthrough. Interestingly I see people have reported getting PCI passthrough working with the standard SUSE kernel too, so I'll have to give that a try. As far as I can see the x11-video-nvidia package in the page you linked has quite an old nvidia driver version for Tumbleweed - https://soft…

The search seems to be doing something weird at the moment..

There is a second "openSUSE Tumbleweed" under the "unsupported distributions" category, and that has the more up to date nvidia packages I'd expect

If someone would like to take a look at the lovely ruby behind software.opensuse.org and fix that bug, I'm sure we'd love the pull requests :) https://github.com/openSUSE/software-o-o

Post reply on HN