Lukas Märdian <sl...@debian.org> writes: > On 23.09.24 12:27, Ansgar 🙀 wrote: >> On Mon, 2024-09-23 at 12:22 +0200, Lukas Märdian wrote: >>> On 22.09.24 15:58, Ansgar 🙀 wrote: >>>> On Fri, 2024-09-20 at 13:12 +0200, Lukas Märdian wrote:
>>> The benefit that Netplan would provide in such cases is that >>> debian-installer >>> installs a /etc/netplan/01-network-manager-all.yaml config file, reading: >>> >>> network: >>> version: 2 >>> renderer: NetworkManager >> So on desktop installations including NetworkManager, netplan will >> be >> configured to do nothing? Why install netplan at all on desktop systems >> then? > > Because it allows to add configuration in a way that is common with > server, cloud > and other instances of Debian Could you give an example of why this is useful to unify? For example: is there a scenario in which someone is using systemd-networkd but then finds they need to do X, which they cant essily do using systend but which nm support is better--- therefore if they are using netplan they can simply install network-manager, change a netplan setting and gain X with no need to understand the differences between the network-manager and systemd configuration languages? (or swapping the roles of NM and systemd-neyworkd, or using ifupdown99 instead)
