I've been watching the development and looking forward to testing out the
systemd-networkd features that are coming out.
One of the things I haven't seen yet is the ability to configure a SIT device
via systemd.netdev for IPv6 in IPv4 tunneling, for example with
he.net/tunnelbroker.net.
Unfort
Hello
To do tests I made a new Arch Linux (x86_64) base installation running
in qemu/kvm with systemd-210-3 and polkit-0.112-1 to discard any weird
thing on my system.
I can reboot/poweroff/suspend/hibernate the system with a normal user
logged from a local VT or remote SSH does not care. I can n
konstantin...@yandex.ru
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On 09.03.2014 18:23, Tom Gundersen wrote:
> On Sun, Mar 9, 2014 at 5:20 PM, poma wrote:
>>
>> 'man/systemd.link.xml' recovery from:
>>
>> commit eac684ef1c29684b1bcd27a89c38c202e568e469
>> Author: Tom Gundersen
>> Date: Tue Feb 25 19:30:40 2014 +0100
>>
>> man: split out systemd.net{work,de
On 09/03/14 21:49, Michael Biebl wrote:
> 2014-03-08 8:52 GMT+01:00 Samuli Suominen :
>> If eg. setcap is in /sbin and user is building as a normal user without
>> $PATH having /sbin, the build system
>> will default to /usr/sbin/setcap as it's defined in AC_PATH_PROG and
>> fail during the build
2014-03-08 8:52 GMT+01:00 Samuli Suominen :
> If eg. setcap is in /sbin and user is building as a normal user without
> $PATH having /sbin, the build system
> will default to /usr/sbin/setcap as it's defined in AC_PATH_PROG and
> fail during the build with 'setcap: command not found'
>
> For exampl
On Sat, 08.03.14 08:16, Andrey Borzenkov (arvidj...@gmail.com) wrote:
> > Putting this altogether this should work fine for multi-boot cases. That
> > said, the benefit of not requiring an /etc/fstab is primarily one for
> > simpler "appliance" style disk images where only one OS is installed,
> >
On Sun, Mar 9, 2014 at 5:20 PM, poma wrote:
>
> 'man/systemd.link.xml' recovery from:
>
> commit eac684ef1c29684b1bcd27a89c38c202e568e469
> Author: Tom Gundersen
> Date: Tue Feb 25 19:30:40 2014 +0100
>
> man: split out systemd.net{work,dev}(5) from systemd-networkd(8)
>
>
> poma
Manually
'man/systemd.link.xml' recovery from:
commit eac684ef1c29684b1bcd27a89c38c202e568e469
Author: Tom Gundersen
Date: Tue Feb 25 19:30:40 2014 +0100
man: split out systemd.net{work,dev}(5) from systemd-networkd(8)
poma
I wanna feel sunlight on my face
I see the dust cloud disappear withou
On 09.03.2014 14:24, arnaud gaboury wrote:
> On Mar 9, 2014 1:21 PM, "poma" wrote:
>>
>> ...
>> systemd-networkd/systemd-udevd - bridges/netdev
>> https://bugzilla.redhat.com/show_bug.cgi?id=1074294
>>
> I am far from saying it is a bug.
> It sounds to me your configuration is a mess. Please have
On Mar 9, 2014 1:21 PM, "poma" wrote:
>
> ...
> systemd-networkd/systemd-udevd - bridges/netdev
> https://bugzilla.redhat.com/show_bug.cgi?id=1074294
>
I am far from saying it is a bug.
It sounds to me your configuration is a mess. Please have a look at the
previous posts from me about networkd. I
...
systemd-networkd/systemd-udevd - bridges/netdev
https://bugzilla.redhat.com/show_bug.cgi?id=1074294
poma
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On 09.03.2014 11:39, Kai Krakow wrote:
> poma schrieb:
>
>> BRIDGED !?
>>
>> $ ll /etc/systemd/network/
>> ... bridge0.netdev
>> ... enp3s0.network
>>
>> $ cat /etc/systemd/network/enp3s0.network
>> [Match]
>> Name=enp3s0
>>
>> [Network]
>> Address=192.168.2.2/24
>> Gateway=192.168.2.1
>> DNS=192
poma schrieb:
> BRIDGED !?
>
> $ ll /etc/systemd/network/
> ... bridge0.netdev
> ... enp3s0.network
>
> $ cat /etc/systemd/network/enp3s0.network
> [Match]
> Name=enp3s0
>
> [Network]
> Address=192.168.2.2/24
> Gateway=192.168.2.1
> DNS=192.168.2.1
> Bridge=bridge0
>
> $ cat /etc/systemd/netw
On 09.03.2014 05:58, poma wrote:
>
> %
>
> STATIC OK!
>
> $ ll /etc/systemd/network/
> ... enp3s0.network
>
> $ cat /etc/systemd/network/enp3s0.network
> [Match]
> Name=enp3s0
>
> [Network]
> Address=192.168.2.2/24
> Gatew
On 09.03.2014 10:55, arnaud gaboury wrote:
> ...
>>
>> $ brctl show
>> bridge name bridge id STP enabled interfaces
>> bridge0 8000. no
>>
>
> $ brctl show
> bridge name bridge id STP enabled interfaces
> bridge0
...
>
> $ brctl show
> bridge name bridge id STP enabled interfaces
> bridge0 8000. no
>
$ brctl show
bridge name bridge id STP enabled interfaces
bridge0 8000. noenps0
17 matches
Mail list logo