Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #239502
| From | Jude DaShiell <jdashiel@panix.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: ifupdown lost at upgrade time to bullseye |
| Date | 2021-08-31 04:50 +0200 |
| Message-ID | <CS20x-5Ma-5@gated-at.bofh.it> (permalink) |
| References | <CRViq-1n4-25@gated-at.bofh.it> <CRVBM-1tH-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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- > >
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
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
csiph-web