[arch-projects] [netctl][PATCH] Support dynamically appearing interfaces

Jouke Witteveen j.witteveen at gmail.com
Sat Mar 2 11:03:57 EST 2013

On Fri, Feb 15, 2013 at 4:31 PM, Ivan Shapovalov <intelfx100 at gmail.com> wrote:
> On 15 February 2013 10:40:52 Thomas Bächler wrote:
>> Am 14.02.2013 21:45, schrieb Jouke Witteveen:
>> > On Tue, Feb 12, 2013 at 1:40 PM, Ivan Shapovalov <intelfx100 at gmail.com>
> wrote:
>> >> If a profile is WantedBy=multi-user.target, it breaks init sequence
>> >> if its interface is not immediately available at runtime
>> >> (e. g. a cell-phone or USB modem).
>> >
>> > Does this work? Is there a reason not to make the device the default
>> > trigger?
>> That's an interesting question. You can always add a profile as a
>> dependency to
>>  /etc/systemd/system/sys-subsystem-net-devices-FOO.device.wants/
>> and add
>>  BindsTo=sys-subsystem-net-devices-FOO.device
>> so it goes down when the devices vanishes. This is actually pretty nice
>> if you think about it.
>> But do we really want that? Some people may say that they only want
>> their devices going up when they launch multi-user.target, but not when
>> they launch rescue.target. It's a matter you should consider carefully.
> Yes, I also thought about that. Maybe adding RequisiteOverridable=multi-
> user.target will suffice?

Perhaps a really good solution would also take care of ifplugd, which
has to go some day. Until such a solution comes around, I think this
entire problem is best left for advanced users to tackle themselves.
It is not trivial to get this right in netctl and it is easy for a
knowledgeable user to fix things for this particular use-case. All
that is needed is to move the symlink from multi-user.target.wants/ to
some other directory, issue `systemctl daemon-reload` and everything
should work as wanted.

- Jouke

More information about the arch-projects mailing list