On Tue, 04.11.14 14:48, Dan Williams (d...@redhat.com) wrote:
> > > > Can you be more specific what precisely you intend to hook in there?
> > > > I'd really prefer if we could find different solutions for the common
> > > > usecases.
> > >
> > > Example: I'd like to add interface to proper fir
On Tue, 2014-11-04 at 19:40 +0100, Lennart Poettering wrote:
> BOn Tue, 04.11.14 19:07, Tomasz Torcz (to...@pipebreaker.pl) wrote:
>
> > On Thu, Oct 02, 2014 at 08:36:10AM +0200, Lennart Poettering wrote:
> > > On Wed, 01.10.14 21:36, Cameron Norman (camerontnor...@gmail.com) wrote:
> > >
> > > >
On 11/04/2014 06:07 PM, Tomasz Torcz wrote:
Example: I'd like to add interface to proper firewalld "zone".
Ideally it could be done by networkd itself (it just one dbus call:
addInterface(in s zone, in s interface, …) based on new Zone=string
setting in .netdev file.
Hook can determine w
BOn Tue, 04.11.14 19:07, Tomasz Torcz (to...@pipebreaker.pl) wrote:
> On Thu, Oct 02, 2014 at 08:36:10AM +0200, Lennart Poettering wrote:
> > On Wed, 01.10.14 21:36, Cameron Norman (camerontnor...@gmail.com) wrote:
> >
> > > Hello,
> > >
> > > ifupdown [1], NetworkManager, and WICD all support h
On Thu, Oct 02, 2014 at 08:36:10AM +0200, Lennart Poettering wrote:
> On Wed, 01.10.14 21:36, Cameron Norman (camerontnor...@gmail.com) wrote:
>
> > Hello,
> >
> > ifupdown [1], NetworkManager, and WICD all support hooks for when a
> > network interface is configured or deconfigured (before and a
On Thu, 09.10.14 18:38, Cameron Norman (camerontnor...@gmail.com) wrote:
> >actually not using avahi-autoipd is the way you really want to go.
> >Especially since networkd will do IPv4LL setup for you anyway. Same
> >applies to ethtool hooks since they should be done by link files and
> >configure
On Fri, 10.10.14 17:40, Dale R. Worley (wor...@alum.mit.edu) wrote:
> > From: Tom Gundersen
>
> > What we do, however, is to expose the configuration state using the
> > sd-network C API, which external programs can watch and react on (see
> > how timesyncd and resolved currently works).
>
> In
On Fri, Oct 10, 2014 at 11:40 PM, Dale R. Worley wrote:
>> From: Tom Gundersen
>
>> What we do, however, is to expose the configuration state using the
>> sd-network C API, which external programs can watch and react on (see
>> how timesyncd and resolved currently works).
>
> In a situation where
> From: Tom Gundersen
> What we do, however, is to expose the configuration state using the
> sd-network C API, which external programs can watch and react on (see
> how timesyncd and resolved currently works).
In a situation where one wants to do what a "hook" does, having a
separate daemon pro
On Thu, Oct 09, 2014 at 07:24:07AM +0200, Marcel Holtmann wrote:
> For the wpa_supplicant, we are going to fix that one with a proper daemon
> soon.
Interesting. Can you shed some light on this?
Zbyszek
___
systemd-devel mailing list
systemd-devel@lists
On Fri, Oct 10, 2014 at 3:38 AM, Cameron Norman
wrote:
> udev was indeed my first thought for ethtool, however how would the ethtool
> commands be hooked in on containers? Or is ethtool not relevant there?
In a container you'll either have devices that you have moved in from
the outside (these sh
El mié, 8 de oct 2014 a las 10:24 , Marcel Holtmann
escribió:
Hi Cameron,
ifupdown [1], NetworkManager, and WICD all support hooks for
when a
network interface is configured or deconfigured (before and
after
these actions).
Are there any plans to support something along these lines? If
Hi Cameron,
> ifupdown [1], NetworkManager, and WICD all support hooks for when a
> network interface is configured or deconfigured (before and after
> these actions).
>
> Are there any plans to support something along these lines? If so,
> what will that look like?
>
On Wed, Oct 8, 2014 at 2:26 PM, Lennart Poettering
wrote:
> On Thu, 02.10.14 19:48, Cameron Norman (camerontnor...@gmail.com) wrote:
>
>> On Wed, Oct 1, 2014 at 10:36 PM, Tom Gundersen wrote:
>> > Hi Cameron,
>> >
>> > On Thu, Oct 2, 2014 at 6:36 AM, Cameron Norman
>> > wrote:
>> >> ifupdown [1
On Thu, 02.10.14 19:48, Cameron Norman (camerontnor...@gmail.com) wrote:
> On Wed, Oct 1, 2014 at 10:36 PM, Tom Gundersen wrote:
> > Hi Cameron,
> >
> > On Thu, Oct 2, 2014 at 6:36 AM, Cameron Norman
> > wrote:
> >> ifupdown [1], NetworkManager, and WICD all support hooks for when a
> >> networ
Op 2 okt. 2014, om 15:29 heeft Tom Gundersen het volgende
geschreven:
> On Thu, Oct 2, 2014 at 2:20 PM, Lennart Poettering
> wrote:
>> On Thu, 02.10.14 13:00, Koen Kooi (k...@dominion.thruhere.net) wrote:
>>
>>>
>>> Op 2 okt. 2014, om 07:36 heeft Tom Gundersen het volgende
>>> geschreven:
On Wed, Oct 1, 2014 at 10:36 PM, Tom Gundersen wrote:
> Hi Cameron,
>
> On Thu, Oct 2, 2014 at 6:36 AM, Cameron Norman
> wrote:
>> ifupdown [1], NetworkManager, and WICD all support hooks for when a
>> network interface is configured or deconfigured (before and after
>> these actions).
>>
>> Are
On Thu, Oct 2, 2014 at 2:20 PM, Lennart Poettering
wrote:
> On Thu, 02.10.14 13:00, Koen Kooi (k...@dominion.thruhere.net) wrote:
>
>>
>> Op 2 okt. 2014, om 07:36 heeft Tom Gundersen het volgende
>> geschreven:
>>
>> > Hi Cameron,
>> >
>> > On Thu, Oct 2, 2014 at 6:36 AM, Cameron Norman
>> > w
On Thu, 02.10.14 13:00, Koen Kooi (k...@dominion.thruhere.net) wrote:
>
> Op 2 okt. 2014, om 07:36 heeft Tom Gundersen het volgende
> geschreven:
>
> > Hi Cameron,
> >
> > On Thu, Oct 2, 2014 at 6:36 AM, Cameron Norman
> > wrote:
> >> ifupdown [1], NetworkManager, and WICD all support hooks
Op 2 okt. 2014, om 07:36 heeft Tom Gundersen het volgende
geschreven:
> Hi Cameron,
>
> On Thu, Oct 2, 2014 at 6:36 AM, Cameron Norman
> wrote:
>> ifupdown [1], NetworkManager, and WICD all support hooks for when a
>> network interface is configured or deconfigured (before and after
>> these
On Wed, 01.10.14 21:36, Cameron Norman (camerontnor...@gmail.com) wrote:
> Hello,
>
> ifupdown [1], NetworkManager, and WICD all support hooks for when a
> network interface is configured or deconfigured (before and after
> these actions).
>
> Are there any plans to support something along these
Hi Cameron,
On Thu, Oct 2, 2014 at 6:36 AM, Cameron Norman wrote:
> ifupdown [1], NetworkManager, and WICD all support hooks for when a
> network interface is configured or deconfigured (before and after
> these actions).
>
> Are there any plans to support something along these lines? If so,
> wh
Hello,
ifupdown [1], NetworkManager, and WICD all support hooks for when a
network interface is configured or deconfigured (before and after
these actions).
Are there any plans to support something along these lines? If so,
what will that look like?
If there are no plans, how do networkd's devel
23 matches
Mail list logo
