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…
Why You Should Use Tumbleweed
31–40 of 68 posts
Re: Why You Should Use Tumbleweed
#32OpenQA seems really brilliant, but I guess someone could eventually just port it to Arch, Gentoo, Debian, or Fedora Rawhide? I hope they do.
But you really need to be using OBS too in order to produce those builds in the fast, easily contributed way that we then (ab)use with Tumbleweed
Of course, other projects could use OBS also..either hosting their own or by using our servers even..after all it builds Arch, Debian, Ubuntu, Fedora and other packages
But that's what being open is all about right? Doing cool things because you need them and then benefiting even more when everyone else finally catches up and starts working with you on it :)
Re: Why You Should Use Tumbleweed
#33This 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…
For years I only used distributions based on Debian, Slackware was my first distro but it's such a burden to get Wi-Fi going. I gave SUSE a shot and have not looked back, anything I need to install is available. I think my only issue with openSUSE was getting DMD (D language compiler) to cooperate for some reason. I'll likely just use Vagrant with Ubuntu as a work around. My only issue is the fact I can't have it on…
https://digitalocean.uservoice.com/forums/136585-digital-oce...
There are plenty of hosting providers who do offer Leap and sometimes even Tumbleweed images.
My blog is hosted on Hetzner (they're local ;))
We have a solid presence on all the major Public Clouds https://en.opensuse.org/Portal:Cloud
Would love to be everywhere, so if any hosting companies want to get in touch about using openSUSE on their platform, my contact details are on the bottom of that article
Re: Why You Should Use Tumbleweed
#34"It uses openCV and a library of reference screenshots (with areas of interest selected to allow openQA to ignore things we don’t care about) which we call ‘needles’ ..." OpenQA is a fascinating project. The tests are written in perl and I think the OpenCV magical stuff is around the "check_screen()" function. For example, a test for Firefox: x11_start_program("firefox https://html5test.com/index.html", 6, {valid =>…
check_screen is a non-fatal check, really useful for stuff like you cite in that example "tell openQA to see if something is on the screen, then react to it" assert_screen is it's fatal cousin "make sure the screen has this needle on it, or die" assert_and_click is it's mouse-controlling companion, "make sure the screen has this needle on it, then click on it" https://github.com/os-autoinst/openQA/blob/master/docs/Wr…
I found the piece of code I was looking for inside "tinycv" (about OpenCV): https://github.com/os-autoinst/os-autoinst/blob/3c2f5edda09b...
I switched to Debian from Fedora a year ago during the "freeze" in the release cycle. I wonder what is the stability level of Tumbleweed compared to a standard (non-beta) Fedora or a Debian testing.
Is it the good repo for Tumbleweed OpenQA test? https://github.com/os-autoinst/os-autoinst-distri-opensuse
Re: Why You Should Use Tumbleweed
#35Earlier quoted context omitted.
check_screen is a non-fatal check, really useful for stuff like you cite in that example "tell openQA to see if something is on the screen, then react to it" assert_screen is it's fatal cousin "make sure the screen has this needle on it, or die" assert_and_click is it's mouse-controlling companion, "make sure the screen has this needle on it, then click on it" https://github.com/os-autoinst/openQA/blob/master/docs/Wr…
That's great! I found the piece of code I was looking for inside "tinycv" (about OpenCV): https://github.com/os-autoinst/os-autoinst/blob/3c2f5edda09b... I switched to Debian from Fedora a year ago during the "freeze" in the release cycle. I wonder what is the stability level of Tumbleweed compared to a standard (non-beta) Fedora or a Debian testing. Is it the good repo for Tumbleweed OpenQA test? https://github.com/…
SUSE use openQA for testing their enterprise distributions too, and keeping all our tests together and reused as heavily as possible really helps in all directions (and proves the argument that maintaining openQA tests isnt hard even when dealing with multiple codebases-under-test all moving at different paces)
I use Tumbleweed as my daily driver on all my machines besides my server (Leap).
In 2 years I've had no problems that I didnt cause myself (eg. rm -rf /) and even then snapper saved the day and let me rollback to a working snapshot (Tumbleweed, like all openSUSE/SUSE distributions have btrfs snapshots and rollback by default)
So I'd say its comparible to Fedora or Debian testing
And we'd like to see more contributors, not only adding more packages and maintaining them, but to openQA also so that Tumbleweeds quality doesn't just stay at that level but gets even higher
Re: Why You Should Use Tumbleweed
#36"It uses openCV and a library of reference screenshots (with areas of interest selected to allow openQA to ignore things we don’t care about) which we call ‘needles’ ..." OpenQA is a fascinating project. The tests are written in perl and I think the OpenCV magical stuff is around the "check_screen()" function. For example, a test for Firefox: x11_start_program("firefox https://html5test.com/index.html", 6, {valid =>…
I also tend to think most package managers lack a sound foundation, unlike nix. It builds everything upon a basic but powerful idea, don't force to keep the whole package tree in sync.
[1] https://www.gnu.org/software/guix/manual/html_node/Invoking-...
Re: Why You Should Use Tumbleweed
#37Re: Why You Should Use Tumbleweed
#381. Active Directory: I'm not a Unix shop and everywhere I've had a need for it, AD has been the predominant identity service in the environment. Getting openSuSE setup, via yast, to work with my AD account is really simple. It can be done everywhere else, too, but being able to set it up during installation without touching a config file is nice.
2. Bleeding edge: I like to play and Tumbleweed was always on a later kernel (and other core bits) than other distributions, giving me access to the new toys early on with the "feeling" that I'm not running "beta" (and feelings aside, I've not run into anything on the stability, yet). Never having to think about doing a "distribution upgrade" (because you're basically doing it in pieces every time you update) is nice, too.
3. YaST: Much like the easy AD integration, there's a whole mess of administrative things that can be done without editing configuration files or using console tools that I'm not in nearly enough to memorize their usage. Simple things like opening a port in the firewall are as easy as they are on a consumer router and the ncurses interface is perfect over an SSH connection (I haven't used GUI YaST but it looks nice, too). People always say Ubuntu is the most "n00b" friendly Linux distribution, and it probably is when the large community behind it is factored in, but I find SuSE to be superior, personally.
On the downside, though:
There's less available in Zypper. I get jealous when every answer in StackExchange includes an apt-get and about 15% of the time no package even exists for whatever it is that I'm being told to apt-get. But it's little more pleasant to watch on the console.
The smaller community makes StackExchange less useful and they use different tools. Much of it is due to the bleeding edge nature of Tumbleweed and I've read plenty of "it's better, that old stuff will be deprecated everywhere else, too" and I can't speak to the merits of any of that, but when my network connection goes south, I instinctively reach for "ifconfig" and it's not there. And all of the help out there points me at things that don't work, either[1]. And because it's a rolling distribution, these kinds of changes don't pop up when you expect them (like when you're doing a distribution upgrade...)
Tumbleweed's rolling update model has thoroughly broken on me, once, but not in a "hey, it just decided not to boot this time" kind of way. I believe this happened when they switched to "Leap" and "Tumbleweed" as the only options. I thought I was up-to-date, but I was pointing to repos that were invalid and had to modify my configs and download an .rpm to fix it. Other than not seeing software updates (which is pretty odd since there's usually something every time I update), there was no indication that anything was wrong.
Out of the box, sudo isn't setup (maybe it is, now, I haven't done a fresh install in a long time). It's not hard to get working, though.
[1] It's one of the new "ip something" commands I can never remember when I need it: http://www.linuxfoundation.org/collaborate/workgroups/networ...
Re: Why You Should Use Tumbleweed
#39This 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…
Tumbleweed struck the right balance for me. Bleeding edge, rolling distribution with a mix of easy maintenance and configuration (and at the time all of Gentoo's emerge operations involved compiling from source, so you could add "faster maintenance" to the list).
I have a side-project I'm going to start this weekend that'll have me checking out Gentoo again, is it still this ugly or has that part improved?
Re: Why You Should Use Tumbleweed
#40Is this guy leaving out periods as some kind of intentional stylistic thing, or did he just fail at proofreading? Lots of other typos too. A little ironic when you're writing about doing things correctly and testing comprehensively!
The author mentions at the bottom that it was inspired by a Reddit article, so I think this was just thrown together in rapid-fire response style with little proofreading.
I think it's the nice color scheme and well-picked fonts that clash - we've all come to expect perfect typography when presented with good site design, and it's a bit of a shock.
Definitely hope the article gets cleaned up, because the content is really compelling.