can anyone lookinto i was using ubuntu before and fedora also but never find this
i dont know much about systemd can anyone help here
in fedora i know it was systemd-resolved but here i cant find this package.
i want to have a dns over tls woth systemd-resolved.
Repository 'openSUSE:Tumbleweed' is out-of-date. You can run 'zypper refresh' as root to update it.
Repository 'packman' is out-of-date. You can run 'zypper refresh' as root to update it.
Repository 'snappy' is out-of-date. You can run 'zypper refresh' as root to update it.
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
--+-----------------+------------------------------------------------------+--------
| systemd-network | systemd network and Network Name Resolution managers | package
yes now how can i setup it i cant find that file etc/systemd/resolved.conf
S | Name | Summary | Type
–±----------------±-----------------------------------------------------±-------
| systemd-network | systemd network and Network Name Resolution managers | package
in fedora or ubuntu it have that by default
sudo zypper install systemd-network
[sudo] password for root:
Loading repository data…
Reading installed packages…
Resolving package dependencies…
Problem: nothing provides ‘this-is-only-for-build-envs’ needed by the to be installed systemd-mini-252.1-6.1.x
86_64
Solution 1: Following actions will be done:
install systemd-252.1-6.1.x86_64 from vendor obs://build.opensuse.org/Base:System
replacing systemd-252.1-1.1.x86_64 from vendor openSUSE
install udev-252.1-6.1.x86_64 from vendor obs://build.opensuse.org/Base:System
replacing udev-252.1-1.1.x86_64 from vendor openSUSE
Solution 2: do not install systemd-network-252.1-6.1.x86_64
Solution 3: break systemd-mini-252.1-6.1.x86_64 by ignoring some of its dependencies
**Choose from above solutions by number or cancel [1/2/3/c/d/?] (c):
Are you sure? Every openSUSE installation I have that is current, which is several tens, not only has systemd-network installed, but has systemd-networkd enabled, systemd-resolved disabled, and wicked masked. I have no recollection (not a good indicator of something happening or not) of ever having to specifically select to add systemd-network during- or post-installation. I mostly only do NET installs, with recommends disabled, using static IP and with NetworkMangler explicitly tabooed, so possibly those could make a difference.
thanks it solved my issues but i think systemd-network should be installed by default like ubuntu fedora and centos
can you loookinto and make sure that this package stay installed in in all installations. thanks
It took a lot of work trying to find out when this happened, with TW’s filtering against the package’s rpm changelog bewildering. According to changelogs, the split occurred in TW 2019-09-18, and in Leap, 2020-05-29. The version the date represents for TW I didn’t find, but for Leap it appears to have been done in 15.1 updates 234-lp151.26.19.1 just a few weeks before release of 15.2, for which it appeared in 234-lp152.31.4.1 in August 2020. It’s not on release DVD for 15.2 or 15.1. As a split from a bigger package I guess is why it was so extensively installed here when I began switching to it from Wicked. With most of my Leaps existing as upgrades from prior releases, most would have had it installed as consequence of the split-off, creating the impression of its being part of a default installation.
obviously
and all major distros i have used have this like rhel alma rocky ubuntu arch garuda fedora kubuntu elementary os zorin os kde neon and debian kali popos! manjaro also
as you can see most distros major ones that i have tested and have been runnung in a droplate or a desktop i find it is always present now it is totally onto suse team if they want to go with all distros or make or not
i think having it help to setup own dns over tls as all linux distros does not offer a GUI like android to set that up and as per my thinking having a good encrypted dns is more useful as dns is the most insecure part in internet in modern times.