rbrownsuse

All you need if you're never going to update it or you're going to take steps to ensure the installed workload doesn't eat up excess space.

docker pull opensuse

;)

https://hub.docker.com/_/opensuse/

https://store.docker.com/images/99f9bd45-4c65-4e45-aa36-234e...

Both claims are demonstrably false.

Seriously? the author has no idea what they're talking about

http://software.opensuse.org

"For each ISO, we offer a checksum file with the corresponding SHA256 sum. For extra security, you can use GPG to verify who signed those .sha256 files. It should be 22C0 7BA5 3417 8CD0 2EFE 22AA B88B 2FD4 3DBD C284."

https://en.opensuse.org/openSUSE:Tumbleweed_installation

http://download.opensuse.org/tumbleweed/iso/openSUSE-Tumblew...

http://download.opensuse.org/tumbleweed/iso/openSUSE-Tumblew...

http://download.opensuse.org/distribution/leap/42.1/iso/open...

http://download.opensuse.org/distribution/leap/42.1/iso/open...

All signed, happy and healthy...and regularly checked.. people really should double check before making statements like this..

Users know - YaST doesn't change stuff without telling you, that was the point I was trying to make earlier. Users of YaST no longer have to worry about it silently taking over config files, it either co-exists or doesn't do anything without telling the user with great big pop-up boxes first

on the commandline, there is a plugin for osc (the OBS commandline tool) https://build.opensuse.org/package/show/openSUSE:Tools/osc-p...

This enables 'osc install $foo' which will search the build service for package $foo and install it, which I believe to be the closest approximation of what you expect from AUR

It doesn't conflict with other configuration management systems. I've used openSUSE extensively with puppet and saltstack.

Many of SUSE's products use other configuration management systems as part of their toolchain, and SUSE are shipping SUSE Manager 3.0 with SaltStack, so their customers are expected to be able to use YaST alongside such a system

These days YaST no longer overwrites config files, except from a very few corner cases where it really really wants to be in control of specific config files for very specific reasons. But if it notices local changes, it warns the admin and doesn't take over unless the admin consents

So, no more unexpected config file obliteration :)

(and even if it did, YaST is integrated with openSUSE's default btrfs snapshot tooling, so YaST takes a snapshot before and after it changes anything, so you could always revert)

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

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

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 :)

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

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

Thanks for the consideration

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...

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)

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/Writi...

The above doc covers the basics, we also have a whole bunch of tutorials on YouTube

https://www.youtube.com/watch?v=-fqvaSO6nKE https://www.youtube.com/watch?v=a8LmqhwpVvg https://www.youtube.com/watch?v=EM3XmaQXcLg