On 2016-11-14 20:47, Lennart Poettering wrote:
On Mon, 14.11.16 20:35, Sylvain Pasche (spas...@spasche.net) wrote:
On 2016-11-14 15:14, Lennart Poettering wrote:
>
> Hmm, I figure this would be much better, no:
>
> ln -s /dev/null /etc/systemd/network/99-default.link
On 2016-11-14 04:48, Andrei Borzenkov wrote:
14.11.2016 00:51, Sylvain Pasche пишет:
Hi,
On the Predictable Network Interface Names wiki page [1], one of the
option for disabling predictable network interface names is to mask
the 80-net-setup-link.rules udev rule.
This has a side effect
On 2016-11-14 15:14, Lennart Poettering wrote:
Hmm, I figure this would be much better, no:
ln -s /dev/null /etc/systemd/network/99-default.link
Wouldn't that work to for you?
Hi,
Yes, that works for me and looks better indeed.
Do you want to update the wiki, or should this need more
Hi,
On the Predictable Network Interface Names wiki page [1], one of the option for
disabling predictable network interface names is to mask the
80-net-setup-link.rules udev rule.
This has a side effect of somewhat breaking systemd-network: net_setup_link
builtin is not run and the
Hi,
I was looking for the instructions on how to enable a systemd-nspawn
container on boot in the systemd-nspawn documentation.
I saw that the example containing the systemctl enable
systemd-nspawn@CONTAINER.service command was removed in:
commit e0ea94c1e2ab3930c85c6057189a2a829a13a800
On 04/26/2015 07:40 PM, Kai Krakow wrote:
Sylvain Pasche sylvain.pas...@gmail.com schrieb:
I was looking for the instructions on how to enable a systemd-nspawn
container on boot in the systemd-nspawn documentation.
I saw that the example containing the systemctl enable
systemd-nspawn
