Hacker News Reader

Hacker News

Comment by cm3 | Hacker News Reader

Full thread

cm3

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.

View on HN

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

where can I find exact documentation about which config files are still manipulated / changed by yast and which are not?

the only one I can think of is the apache one. If you use the YaST apache configuration module it will warn you before taking over and changing any local changes. It actually does its best to do a merge of local changes and its own, but it's the one case I know of where that merge can be destructive.

Thank you very much for your attention - however I asked where I can find exact documentation about these things?

"Mr Brown from Suse wrote in a HN thread..." will not be enough as a reliable source of information. Yes, I could just read the source, however I am expecting such an extraordinary important thing that will change my config files to be documented. I need precise information here.

Also it would be important to know how this conflicts with configuration management systems like chef, ansible, puppet etc. - or is yast able to manage multiple workstations itself, so is is a replacement for these tools?

Thanks!

There is pretty extensive documentation on http://yast.github.io/documentation.html

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

Multiple 404 on that page:

http://www.rubydoc.info/github/yast/yast-yast2/

http://yast-core.readthedocs.org/en/latest/

I am not trying to make you angry, but I think I put the finger right on the place where it hurts very much.

There is no clear documentation about what yast does or what it will not do - basically a blackbox. Maybe it will change apache config. Maybe not. Who knows.

:) fair point..I'll let the YaST team know (or you could if you happen to be on freenode, they live in the #yast channel)

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

Reply on news.ycombinator.com