On Fri, Apr 22, 2016 at 04:48:02PM +0200, Lennart Poettering wrote: > However, I think that shouldn't stop you from implementing > something like this, and I think you can do this relatively easily > without direct support in networkd. For example, you could place your > choice of .network files somewhere, and then write a short script that > symlinks them depending on the profile to use in > /run/systemd/network/, and restart networkd. That script could even > use /dev/null masking to mask out some default config in some > profiles, so that you can relatively easily build something that comes > up with some default config, but by running that script disables some > .network files and adds in others instead. > > I hope this makes sense?
Yes, thank you. Sounds like a good solution for my use case! Clemens _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
