(how) are if-up.d/* scripts managed under opensuse 13.2+ wicked? I'm not yet clear if this "TODO" (https://github.com/openSUSE/wicked/issues/56) implies that they are not.
currently, in my
/etc/sysconfig/network
i've an if-up.d script
if-up.d/99-ethX-setup
which, on 13.1, prior to an upgrade to 13.2 -- with its 'wicked' package -- would always exec as expected, no matter the script's content.
now, after the 13.2 upgrade, the script no longer execs on boot.
after boot, once @ shell, if I exec manually
sh -x /etc/sysconfig/network/if-up.d/99-ethX-setup
it works without issue. in journalctl -xb, I don't see any evidence of the scripts' exec on boot.
Is there a config change needed, or is support for preexisting if-up.d/* scripts lacking in wicked?
This message from 'mge@suse' in a prior @factory thread
http://lists.opensuse.org/opensuse-factory/2013-12/msg00084.html
suggests
"... wicked will read and use the existing configuration files from /etc/sysconfig/network and configure your network accordingly. ..."
which I read as you CAN still use old if-up.d/* scripts, and they'll be handled accordingly
Is that the case in 13.2's wicked? or must my config be changed?
<grantksupport <at> operamail.com> writes:
(how) are if-up.d/* scripts managed under opensuse 13.2+ wicked? I'm not
yet clear if this "TODO"
(https://github.com/openSUSE/wicked/issues/56) implies that they are not.
currently, in my
/etc/sysconfig/network
i've an if-up.d script
if-up.d/99-ethX-setup
which, on 13.1, prior to an upgrade to 13.2 -- with its 'wicked' package
-- would always exec as expected, no
matter the script's content.
now, after the 13.2 upgrade, the script no longer execs on boot.
after boot, once <at> shell, if I exec manually
sh -x /etc/sysconfig/network/if-up.d/99-ethX-setup
it works without issue. in journalctl -xb, I don't see any evidence of
the scripts' exec on boot.
Is there a config change needed, or is support for preexisting if-up.d/*
scripts lacking in wicked?
This message from 'mge <at> suse' in a prior <at> factory thread
http://lists.opensuse.org/opensuse-factory/2013-12/msg00084.html
suggests
"... wicked will read and use the existing configuration files from /etc/sysconfig/network and configure your network accordingly. ..."
which I read as you CAN still use old if-up.d/* scripts, and they'll be
handled accordingly
Is that the case in 13.2's wicked? or must my config be changed?
If updating with wired network settings there is no problem that 13.2 picks up correctly. When updating my other PC (mobile broadband only) I got into major problems. After 3 days trying upgrading, new install with KDE, Gnome wiping all other linux partiton, I only got the broadband working for a short time. After restarting next day the connection was gone again. Now I am back to 13.1 with ifup and networkmanager and broadband is working fine. In between I tried Ubuntu,Mint & Knoppix on live CD and installed and broadband connections worked fine every time. As a old Opensuse user since version 5.2 this has been an absolute nightmare to say the least. And to answer your question: No there is no use of the if-up in wicked.
My advice is, stay with 13.1 or as I do with my wifes laptop on 12.2, which to me has been the smoothed and best version of Opensuse. It's running now for 3 years with the exception of a few restarts after major updates.
Maybe Opensuse is losing it's mojo.
On Thu, Nov 13, 2014 at 6:55 AM, Dieter Hoppe hopped@iinet.net.au wrote:
My advice is, stay with 13.1
Are you sure you selected the correct mailing list?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-11-13 06:57, Andrei Borzenkov wrote:
On Thu, Nov 13, 2014 at 6:55 AM, Dieter Hoppe <> wrote:
My advice is, stay with 13.1
Are you sure you selected the correct mailing list?
Well, he said he attempted 13.2 and, as it does not work, he was forced back. So, IMNSHO, yes.
- -- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)