On Mon, Aug 30, 2021 at 03:56:09PM -0400, Dan Ritter wrote:
Harald Dunkel wrote:
how comes ifupdown is dropped at upgrade time to bullseye, leaving the
(headless) system without network connection while the upgrade is not completed
yet, and breaking network on the next reboot?
This has not y
On Mon 30 Aug 2021 at 21:37:50 (+0200), Harald Dunkel wrote:
> how comes ifupdown is dropped at upgrade time to bullseye, leaving the
> (headless) system without network connection while the upgrade is not
> completed yet, and breaking network on the next reboot?
I would presume that a headless
Is iwctl part of default bullseye installations? Maybe networkd.service
can be used with systemd this I haven't tried since I'm using ethernet but
do have wi-fi capability. I could try these avenues and see if they're
open.
On Mon, 30 Aug 2021, Dan Ritter wrote:
> Harald Dunkel wrote:
> > how
Harald Dunkel wrote:
> how comes ifupdown is dropped at upgrade time to bullseye, leaving the
> (headless) system without network connection while the upgrade is not
> completed yet, and breaking network on the next reboot?
This has not yet happened to me in nine or ten upgrades to
bullseye; al
On Mon 30 Aug 2021 at 21:37:50 +0200, Harald Dunkel wrote:
> Hi folks,
> how comes ifupdown is dropped at upgrade time to bullseye, leaving the
> (headless) system without network connection while the upgrade is not
That's a good question. Completely devoid of infirmation. But still a
good quest
Hi folks,
how comes ifupdown is dropped at upgrade time to bullseye, leaving the
(headless) system without network connection while the upgrade is not completed
yet, and breaking network on the next reboot?
Regards
Harri
6 matches
Mail list logo
