Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Content-ID: <alpine.LNX.2.00.1304201931300.27588@Telcontar.valinor>
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