Carlos E. R. wrote:
If there is broken functionality I want to know about it.
sashd no longer loads via it's own libc.
This is a distribution. Linda, if you want to demonstrate tool breakage, please do so on a system built using openSUSE standard code.
--- sudo -p broke because someone added a line to the config in pam. It's added in 12.3 and factory but wasn't in 12.2 or before. These are not uniq problems to my system.
Heck, I hate systemd. But I can not create my own sysinit scripts (I might), and then complain if they don't work. I may ask for help, of course, but not complain.
---- How does one start third party or their own services? I have at least 2 services I can think of off the top of my head that I run that suse doesn't provide run scripts for. transmission-daemon and an ipmi-hw daemon. Also my 3rd party HW monitory tools from Dell and LSI are currently broken due to the recent upgrades. The LSI tools worked in 12.2. The Dell... probably 11.4... It's NOT just my personal scripts, other companies can't jump and move as fast as suse twitches. They'll just drop support for suse and tell me I'm on my own. The VM system from oracle stopped functioning in 12.3 and is still out of commission in factory. It had about 3-4 startup scripts. Now they are a complete mess. Good thing I never got a chance to rely on them before I experienced this -- how will other users of VM like their stuff failing all over the place.. They just won't use suse. You want to agree to letting suse commit suicide, that's your business... I'll keep opening my mouth when I discover more *surprises*. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org