but not the least, I see that /etc/resolv.conf is now part of
systemd-resolved files, which means that it would be deleted when the
systemd-resolved package is removed from the system. I think it would
also deserve its own bug with some high priority.
Regards,
--
Raphaël Halimi
a Linux system" that we finally embraced.
It's almost as if you want to discourage us to use the non-init-related
parts of systemd.
Regards,
--
Raphaël Halimi
.
Being obtuse and condescending won't help.
Regards,
--
Raphaël Halimi
/resolve/resolv.conf,
or just manage it manually ?
Plus, it would solve both problems I mentioned before.
Regards,
--
Raphaël Halimi
if you think there's no problem here, I don't agree and
I think those are bugs, and serious ones at that.
I'll file them just for the record, so feel free to immediately close
them as wontfix, I won't mind.
Regards,
--
Raphaël Halimi
ping comments and
empty lines) in maintainers scripts.
Regards,
--
Raphaël Halimi
bypassing the stub
resolver). This would keep DNS resolution working (until the next
reboot, that is), but the user will at least have the time to read the
NEWS entry, and act accordingly.
Regards,
--
Raphaël Halimi
), and split only
systemd-resolvconf.
Best regards,
--
Raphaël Halimi
in its own package.
Regards,
--
Raphaël Halimi
t shouldn't be evaluated since
it's enclosed between single quotes.
Downgrading systemd to version 253.5-1 fixes the problem.
Regards,
--
Raphaël Halimi
ts
"default-dbus-system-bus" as first alternative, which is provided by "dbus".
Regards,
--
Raphaël Halimi
to reassign it ?
Fwiw, you might use an alternative debootstrap tool like mmdebstrap
which works properly in that regard.
I didn't know about this tool. Thanks for the tip :)
Regards,
--
Raphaël Halimi
12 matches
Mail list logo
