On 03/26/2013 02:23 AM, Christofer C. Bell wrote:

On Mon, Mar 25, 2013 at 10:49 PM, lynn wrote:

...

12.3 zypper up'd today Hi I have disabled firewall using Yast however, each time I reboot, the firewall is always started. I have to go back into Yast and Disable/stop it each boot.

What can I do to make the Yast settings 'stick'?

At the command line, you can try this as root:

# systemctl disable SuSEfirewall2_init.service SuSEfirewall2.service # systemctl stop SuSEfirewall2_init.service SuSEfirewall2.service

This should disable and stop the firewall. No reboot necessary other than to test it if you'd like.

Yes, looks like the yast needs massive love as it is starting to bit-rot quickly :-| -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Tue, 2013-03-26 at 07:40 +0100, Per Jessen wrote:

lynn wrote:

...

12.3 zypper up'd today Hi I have disabled firewall using Yast however, each time I reboot, the firewall is always started. I have to go back into Yast and Disable/stop it each boot.

Please open a bugreport.

I have done so already. It is https://bugzilla.novell.com/show_bug.cgi?id=804894 Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 03/26/2013 10:41 AM, Carlos E. R. pecked at the keyboard and wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Tuesday, 2013-03-26 at 02:28 -0300, Cristian Rodríguez wrote:

...

On 03/26/2013 02:23 AM, Christofer C. Bell wrote:

...

...

This should disable and stop the firewall. No reboot necessary other than to test it if you'd like.

Yes, looks like the yast needs massive love as it is starting to bit-rot quickly :-|

Indeed.

There have been reports in the forums that the YaST module that starts/stop services does not work. People are been redirected to use "systemadm" instead.

This is a shame :-/

This is what happens when changes are forced upon the distro without regard to the tools to configure those changes. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

El 26/03/13 12:22, Ken Schneider - openSUSE escribió:

This is what happens when changes are forced upon the distro without regard to the tools to configure those changes.

No, this is what happends when Yast lacks of developers. that's all. Unfortunately, it is not just a matter of go and hack (heck, I have commit access !) but existent yast modules are written in YCP, a custom language. at the time and environment it was designed, probably was a good idea.. now it is a curse. There are two ways for Yast to gain developers. - SUSE hiring more people to work on it (do not hold your breath) - Interested volunteers have to learn YCP. - Existent Yast modules getting ported to a language that normal human beigns are familar with. this is probably the only way for it to survive in the long term. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: On Tuesday, 2013-03-26 at 02:28 -0300, Cristian Rodríguez wrote:

On 03/26/2013 02:23 AM, Christofer C. Bell wrote:

...

On Mon, Mar 25, 2013 at 10:49 PM, lynn <> wrote:

...

12.3 zypper up'd today Hi I have disabled firewall using Yast however, each time I reboot, the firewall is always started. I have to go back into Yast and Disable/stop it each boot.

What can I do to make the Yast settings 'stick'?

At the command line, you can try this as root:

# systemctl disable SuSEfirewall2_init.service SuSEfirewall2.service # systemctl stop SuSEfirewall2_init.service SuSEfirewall2.service

This should disable and stop the firewall. No reboot necessary other than to test it if you'd like.

Yes, looks like the yast needs massive love as it is starting to bit-rot quickly :-|

I came across a very strange thing. Some people claim that copying these files into 12.3 from 12.2 makes yast services and runleves module work again: /etc/inittab /etc/init.d/boot.localfs /etc/init.d/boot.rootfsck I think this is madness, but there you go... - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlFy0foACgkQtTMYHG2NR9VBwwCePef5yoL4ArFnE7Wgsy+Q0NnT 2C0An0cftfsgKbpN3be0tyjCkqkuYfdB =FBbt -----END PGP SIGNATURE-----

Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Content-ID:

On Tuesday, 2013-03-26 at 02:28 -0300, Cristian Rodríguez wrote:

...

On 03/26/2013 02:23 AM, Christofer C. Bell wrote:

...

On Mon, Mar 25, 2013 at 10:49 PM, lynn <> wrote:

...

12.3 zypper up'd today Hi I have disabled firewall using Yast however, each time I reboot, the firewall is always started. I have to go back into Yast and Disable/stop it each boot.

What can I do to make the Yast settings 'stick'?

At the command line, you can try this as root:

# systemctl disable SuSEfirewall2_init.service SuSEfirewall2.service # systemctl stop SuSEfirewall2_init.service SuSEfirewall2.service

This should disable and stop the firewall. No reboot necessary other than to test it if you'd like.

Yes, looks like the yast needs massive love as it is starting to bit-rot quickly :-|

I came across a very strange thing.

Some people claim that copying these files into 12.3 from 12.2 makes yast services and runleves module work again:

/etc/inittab /etc/init.d/boot.localfs /etc/init.d/boot.rootfsck

I think this is madness, but there you go...

Carlos, the true madness is that NOBODY tested this whilst 12.3 was being prepared/developed. -- Per Jessen, Zürich (4.8°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2013-04-20 at 21:35 +0200, Per Jessen wrote:

Carlos E. R. wrote:

...

I think this is madness, but there you go...

Carlos, the true madness is that NOBODY tested this whilst 12.3 was being prepared/developed.

Well, testers failed to test this, true, but YaST developers should have known very well what they had to do to adapt YaST to systemd. If they could not do the job, the module should have been removed entirely. - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlFzAwQACgkQtTMYHG2NR9XLYgCaAhsHOUGTe9+9dEdKbllK/Dmh wkYAni2kNoEw4UPo0dAU3AxRAx9vvGze =96q1 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2013-04-21 at 08:24 +0400, Andrey Borzenkov wrote:

В Sat, 20 Apr 2013 23:02:24 +0200 (CEST) "Carlos E. R." <> пишет:

...

It makes yast aparently work, because it can modify the file it wants. But that will not work, since inittab is not used now.

YaST2 run-level editor does not modify /etc/inittab (at least, not when enabling/disabling services).

I can not check for myself. I'm merely posting what others said they did on their computers, that the module works when you copy those files from 12.2. It is obvious that the module doesn't really work, because those files are ignored, at best. - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlF0LBAACgkQtTMYHG2NR9UogwCfdNdeNbjYm8N2dHWIZpgZar33 /8AAmgLZB28zbhBAuVgK0QZzO7u8adRD =PO5M -----END PGP SIGNATURE-----