On Thu, Oct 25, 2012 at 1:14 AM, Thomas Bächler email@example.com wrote:
However, this may cause problems with legacy configurations where people used rc.d/net-profiles before and then switched to netcfg@.service. The networks will still be listed in NETWORKS=(), but netcfg.service is not enabled, so this was ignored. Using this in combination with netcfg@.service will enable the profiles twice.
Hm, so what we'd ideally have is that netcfg@.service goes away and that netcfg@$PROFILE.service is a symlink to netcfg-profile-$PROFILE.service?
Don't know what's the most elegant way to achieve that...