Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #239470 > unrolled thread
| Started by | Harald Dunkel <harri@afaics.de> |
|---|---|
| First post | 2021-08-30 21:40 +0200 |
| Last post | 2021-08-31 16:10 +0200 |
| Articles | 6 — 6 participants |
Back to article view | Back to linux.debian.user
ifupdown lost at upgrade time to bullseye Harald Dunkel <harri@afaics.de> - 2021-08-30 21:40 +0200
Re: ifupdown lost at upgrade time to bullseye Brian <ad44@cityscape.co.uk> - 2021-08-30 22:00 +0200
Re: ifupdown lost at upgrade time to bullseye Dan Ritter <dsr@randomstring.org> - 2021-08-30 22:00 +0200
Re: ifupdown lost at upgrade time to bullseye Jude DaShiell <jdashiel@panix.com> - 2021-08-31 04:50 +0200
Re: ifupdown lost at upgrade time to bullseye Michael Stone <mstone@debian.org> - 2021-08-31 16:30 +0200
Re: ifupdown lost at upgrade time to bullseye David Wright <deblis@lionunicorn.co.uk> - 2021-08-31 16:10 +0200
| From | Harald Dunkel <harri@afaics.de> |
|---|---|
| Date | 2021-08-30 21:40 +0200 |
| Subject | ifupdown lost at upgrade time to bullseye |
| Message-ID | <CRViq-1n4-25@gated-at.bofh.it> |
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
[toc] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2021-08-30 22:00 +0200 |
| Message-ID | <CRVBL-1tH-3@gated-at.bofh.it> |
| In reply to | #239470 |
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 question :). -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Dan Ritter <dsr@randomstring.org> |
|---|---|
| Date | 2021-08-30 22:00 +0200 |
| Message-ID | <CRVBM-1tH-11@gated-at.bofh.it> |
| In reply to | #239470 |
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; all but two of them depended on /etc/network/interfaces and nothing weird happened regarding ifupdown. -dsr-
[toc] | [prev] | [next] | [standalone]
| From | Jude DaShiell <jdashiel@panix.com> |
|---|---|
| Date | 2021-08-31 04:50 +0200 |
| Message-ID | <CS20x-5Ma-5@gated-at.bofh.it> |
| In reply to | #239476 |
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 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; all but two of them depended on > /etc/network/interfaces and nothing weird happened regarding > ifupdown. > > -dsr- > >
[toc] | [prev] | [next] | [standalone]
| From | Michael Stone <mstone@debian.org> |
|---|---|
| Date | 2021-08-31 16:30 +0200 |
| Message-ID | <CScVY-4Tm-13@gated-at.bofh.it> |
| In reply to | #239476 |
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 yet happened to me in nine or ten upgrades to >bullseye; all but two of them depended on >/etc/network/interfaces and nothing weird happened regarding >ifupdown. +1 We'd need more information to diagnose the problem.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2021-08-31 16:10 +0200 |
| Message-ID | <CScCC-4N1-11@gated-at.bofh.it> |
| In reply to | #239470 |
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 system qualifies for the treatment outlined in the Release Notes §4.1.3, and perhaps you could be just plain unlucky if hit by the scenario in footnote ². Cheers, David.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web