Hi Ubuntu expert,
May I ask how can one differentiate whether an OS is a desktop or a server
within the OS itself?
Can the presence of "/etc/netplan/01-network-manager-all.yaml" be used to
differentiate a desktop environment?
Best Regards,
Cheng
** Changed in: netplan.io (Ubuntu)
Status
Hi Danilo,
Thanks for your reply.
In the Desktop version vm, as the systemd-networkd is disactive, when no
renderer is set anywhere in the YAMLs, will it change to use Network Manager
for the network configuration during "netplan apply"?
I tested on the ubuntu 23.10 Desktop vm, no render is
Hi Nick,
Got it. Thanks a lot for your reply.
Best Regards,
Cheng
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066700
Title:
systemd-networkd is inactive by default since ubuntu 23.10?
To mana
Public bug reported:
In the Ubuntu-23.10-64-Desktop and Ubuntu-24.04-64-Desktop, I run the
commands as below. Found the systemd-networkd is inactive by default. In
the ubuntu 22.10 and ubuntu 22.04 the systemd-networkd is active by
default. I want to ask if there were any changes made since 23.10?
The commit 3c6b594 has been merged into canonical:main
https://github.com/canonical/cloud-init/commit/3c6b594b90b0647f398f41962def45fd0953ce5b
https://github.com/canonical/cloud-init/pull/1112/
** Changed in: cloud-init (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug no
Public bug reported:
For debian, the network configure file was named
/etc/network/interfaces.d/50-cloud-init, details in
https://github.com/canonical/cloud-init/blob/main/cloudinit/distros/debian.py#L48
but in the /etc/network/interfaces.d, it will "source
/etc/network/interfaces.d/*.cfg", det
