[arch-projects] [netcfg] Call for testers: netctl

Thomas Bächler thomas at archlinux.org
Thu Jan 31 18:46:42 EST 2013

Am 01.02.2013 00:32, schrieb Jouke Witteveen:
> On Fri, Feb 1, 2013 at 12:29 AM, Thomas Bächler <thomas at archlinux.org> wrote:
>> Am 01.02.2013 00:25, schrieb Thomas Bächler:
>>> I took a quick glance at the code a minute ago and I am confused. I was
>>> wondering how you solved the problem of systemd starting the network
>>> services before the devices appear.
>>> And as it turned out, it doesn't! When you activate
>>> netctl at PROFILE.service, the netctl profile will often activate before
>>> the needed network devices appear. That is precisely the problem I
>>> addressed by my generator-based solution in my latest netcfg patches.
> It does. Use `netctl enable PROFILE` and you're all set.

I didn't see this before. Now that's clever.

>>> Apart from reduced code size (which is good), this is no improvement
>>> over netcfg.

I think I need to take that back.

>> Furthermore, every profile requires an interface name. For generic ppp
>> or 3g profiles, for example, there is no interface name prior to
>> establishing a connection - how do you plan to implement such profiles?
> When such names are really unknown a priori, you might need something
> different than netctl.

Why? This is true for all ppp-based connections, and they make lots of
sense in network profiles.

> Compared to netcfg, netctl tries to be simple
> and reasonably good at what it does. It no longer makes coffee, but
> when you want to connect to a network via a network interface, it is
> there for you.

Where is the interface name requirement even needed?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/arch-projects/attachments/20130201/5488a51b/attachment-0001.asc>

More information about the arch-projects mailing list