Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #262472 > unrolled thread
| Started by | Pocket <pocket@columbus.rr.com> |
|---|---|
| First post | 2023-10-21 18:40 +0200 |
| Last post | 2023-10-22 02:30 +0200 |
| Articles | 20 on this page of 246 — 32 participants |
Back to article view | Back to linux.debian.user
Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 18:40 +0200
Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-21 18:50 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 19:10 +0200
Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-21 19:30 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 19:40 +0200
Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-21 20:00 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 20:10 +0200
Re: Bookworm: NetworkManager Max Nikulin <manikulin@gmail.com> - 2023-10-22 10:10 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 14:30 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 14:50 +0200
Re: Bookworm: NetworkManager Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-22 15:20 +0200
Re: Bookworm: NetworkManager Max Nikulin <manikulin@gmail.com> - 2023-10-22 18:50 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 19:50 +0200
Re: Bookworm: NetworkManager Andy Smith <andy@strugglers.net> - 2023-10-22 19:40 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 20:00 +0200
Re: Bookworm: NetworkManager Henning Follmann <hfollmann@itcfollmann.com> - 2023-10-22 17:10 +0200
Re: Bookworm: NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-22 18:30 +0200
Re: Bookworm: NetworkManager Dan Ritter <dsr@randomstring.org> - 2023-10-22 20:40 +0200
Re: Bookworm: NetworkManager Max Nikulin <manikulin@gmail.com> - 2023-10-24 18:50 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-24 19:30 +0200
Re: Bookworm: NetworkManager "Andrew M.A. Cater" <amacater@einval.com> - 2023-10-24 19:40 +0200
Re: Bookworm: NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-25 03:10 +0200
Re: Bookworm: NetworkManager David Wright <deblis@lionunicorn.co.uk> - 2023-10-25 03:50 +0200
link-local 169.254.x.y addresses Max Nikulin <manikulin@gmail.com> - 2023-10-25 18:50 +0200
Re: Bookworm: NetworkManager Andy Smith <andy@strugglers.net> - 2023-10-25 01:40 +0200
Alternative to NetworkManager on Debian 12 Alessandro Baggi <alessandro.baggi@gmail.com> - 2023-11-01 11:50 +0100
Re: Alternative to NetworkManager on Debian 12 Greg Wooledge <greg@wooledge.org> - 2023-11-01 12:20 +0100
Re: Alternative to NetworkManager on Debian 12 Nicolas George <george@nsup.org> - 2023-11-01 12:40 +0100
Re: Alternative to NetworkManager on Debian 12 Max Nikulin <manikulin@gmail.com> - 2023-11-01 17:10 +0100
Re: Alternative to NetworkManager on Debian 12 Nicolas George <george@nsup.org> - 2023-11-01 17:20 +0100
Re: Alternative to NetworkManager on Debian 12 yxcv@vienna.at - 2023-11-01 12:20 +0100
Re: Alternative to NetworkManager on Debian 12 <tomas@tuxteam.de> - 2023-11-01 12:20 +0100
Re: Alternative to NetworkManager on Debian 12 <tomas@tuxteam.de> - 2023-11-01 12:20 +0100
Re: Alternative to NetworkManager on Debian 12 Felix Miata <mrmazda@earthlink.net> - 2023-11-01 15:20 +0100
Re: Alternative to NetworkManager on Debian 12 <tomas@tuxteam.de> - 2023-11-01 15:40 +0100
Re: Alternative to NetworkManager on Debian 12 Alessandro Baggi <alessandro.baggi@gmail.com> - 2023-11-01 15:50 +0100
Re: Alternative to NetworkManager on Debian 12 Max Nikulin <manikulin@gmail.com> - 2023-11-01 16:10 +0100
Re: Alternative to NetworkManager on Debian 12 <tomas@tuxteam.de> - 2023-11-01 18:50 +0100
Re: Alternative to NetworkManager on Debian 12 Max Nikulin <manikulin@gmail.com> - 2023-11-02 16:50 +0100
Re: Alternative to NetworkManager on Debian 12 Jeffrey Walton <noloader@gmail.com> - 2023-11-02 18:00 +0100
Re: Alternative to NetworkManager on Debian 12 <tomas@tuxteam.de> - 2023-11-02 19:00 +0100
Re: Alternative to NetworkManager on Debian 12 Max Nikulin <manikulin@gmail.com> - 2023-11-03 16:50 +0100
Re: Alternative to NetworkManager on Debian 12 debian-user@howorth.org.uk - 2023-11-01 21:00 +0100
Re: Alternative to NetworkManager on Debian 12 "Marco M." <mm@dorfdsl.de> - 2023-11-01 12:30 +0100
Re: Alternative to NetworkManager on Debian 12 Joe <joe@jretrading.com> - 2023-11-01 13:20 +0100
Making resolv.conf immutable [was: Bookworm: NetworkManager] <tomas@tuxteam.de> - 2023-10-22 07:20 +0200
Re: Bookworm: NetworkManager Felix Miata <mrmazda@earthlink.net> - 2023-10-21 20:00 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 20:20 +0200
Re: Bookworm: NetworkManager Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-21 20:40 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 20:50 +0200
Re: Bookworm: NetworkManager Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-10-21 21:00 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 21:20 +0200
Re: Bookworm: NetworkManager Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-21 21:10 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 21:40 +0200
Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-21 21:50 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 22:00 +0200
Re: Bookworm: NetworkManager Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-21 23:40 +0200
Re: Bookworm: NetworkManager <tomas@tuxteam.de> - 2023-10-22 07:30 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 14:40 +0200
Re: Bookworm: NetworkManager Charles Curley <charlescurley@charlescurley.com> - 2023-10-21 22:50 +0200
Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-21 23:00 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 23:20 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 23:20 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-22 13:20 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 14:30 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager Jeffrey Walton <noloader@gmail.com> - 2023-10-22 17:20 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-22 19:00 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager John Hasler <john@sugarbit.com> - 2023-10-22 20:20 +0200
Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-22 20:40 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 00:10 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager John Hasler <john@sugarbit.com> - 2023-10-23 00:50 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 02:40 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-23 02:50 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager John Hasler <john@sugarbit.com> - 2023-10-23 04:40 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-23 05:10 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager Max Nikulin <manikulin@gmail.com> - 2023-10-23 09:20 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 17:20 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 18:00 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 04:40 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager Andy Smith <andy@strugglers.net> - 2023-10-23 22:40 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-24 02:00 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager Dan Ritter <dsr@randomstring.org> - 2023-10-22 20:40 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager Jeffrey Walton <noloader@gmail.com> - 2023-10-22 21:10 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-22 23:50 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager ghe2001 <ghe2001@protonmail.com> - 2023-10-23 02:00 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager Jeffrey Walton <noloader@gmail.com> - 2023-10-23 07:40 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager Christian Groessler <chris@groessler.org> - 2023-10-23 12:40 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager David Wright <deblis@lionunicorn.co.uk> - 2023-10-25 03:50 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager ghe2001 <ghe2001@protonmail.com> - 2023-10-25 05:50 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager "Marco M." <mm@dorfdsl.de> - 2023-10-25 07:40 +0200
Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-25 11:10 +0200
Re: Domain name to use on home networks Joe <joe@jretrading.com> - 2023-10-25 13:20 +0200
Re: Domain name to use on home networks "Marco M." <mm@dorfdsl.de> - 2023-10-25 14:20 +0200
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-25 16:50 +0200
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-25 13:30 +0200
Re: Domain name to use on home networks "Marco M." <mm@dorfdsl.de> - 2023-10-25 14:20 +0200
Re: Domain name to use on home networks Jeffrey Walton <noloader@gmail.com> - 2023-10-25 18:30 +0200
Re: Domain name to use on home networks Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-26 03:30 +0200
Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-26 03:50 +0200
Re: Domain name to use on home networks Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-26 04:50 +0200
Re: Domain name to use on home networks David Wright <deblis@lionunicorn.co.uk> - 2023-10-27 05:20 +0200
Re: Domain name to use on home networks Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-27 06:50 +0200
Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-27 12:10 +0200
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 13:20 +0200
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-27 13:30 +0200
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-27 14:00 +0200
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 15:10 +0200
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-27 15:40 +0200
Re: Domain name to use on home networks "Andrew M.A. Cater" <amacater@einval.com> - 2023-10-27 16:10 +0200
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-27 16:20 +0200
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 17:50 +0200
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 16:30 +0200
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:10 +0200
Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-29 17:30 +0100
Re: Domain name to use on home networks Jeffrey Walton <noloader@gmail.com> - 2023-10-29 19:30 +0100
Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-30 03:30 +0100
Re: Changing host name and domain name on Debian; was: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-27 16:20 +0200
Re: Changing host name and domain name on Debian; was: Domain nameto use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:10 +0200
Re: Changing host name and domain name on Debian; was: Domain nameto use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-29 17:10 +0100
Re: Changing host name and domain name on Debian; was: Domain nametouse on home networks gene heskett <gheskett@shentel.net> - 2023-10-29 18:10 +0100
Re: Changing host name and domain name on Debian; was: Domain nametouse on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-31 04:20 +0100
Re: Changing host name and domain name on Debian; was: Domain nametouse on home networks The Wanderer <wanderer@fastmail.fm> - 2023-10-31 10:20 +0100
Re: Changing host name and domain name on Debian; was: Domain nametouseon home networks gene heskett <gheskett@shentel.net> - 2023-10-31 15:30 +0100
Re: Changing host name and domain name on Debian; was: Domainnametouse on home networks gene heskett <gheskett@shentel.net> - 2023-10-31 15:30 +0100
Re: Changing host name and domain name on Debian; was: Domainnametouse on home networks John Hasler <john@sugarbit.com> - 2023-10-31 17:40 +0100
Re: Changing host name and domain name on Debian; was: Domainnametouse on home networks Felix Miata <mrmazda@earthlink.net> - 2023-11-01 22:10 +0100
Re: Changing host name and domain name on Debian; was:Domainnametouse on home networks gene heskett <gheskett@shentel.net> - 2023-11-02 00:30 +0100
Re: Changing host name and domain name on Debian; was:Domainnametouse on home networks Greg Wooledge <greg@wooledge.org> - 2023-11-02 00:40 +0100
Re: Changing host name and domain name on Debian;was:Domainnametouse on home networks gene heskett <gheskett@shentel.net> - 2023-11-02 01:20 +0100
Re: Changing host name and domain name on Debian;was:Domainnametouse on home networks Greg Wooledge <greg@wooledge.org> - 2023-11-02 01:40 +0100
Re: Changing host name and domain name on Debian;was:Domainnametouse on home networks Jeffrey Walton <noloader@gmail.com> - 2023-11-02 02:20 +0100
Re: Changing host name and domain name on Debian; was:Domainnametouse on home networks John Hasler <john@sugarbit.com> - 2023-11-02 00:40 +0100
Re: report a Debian bug (was: Changing host name and dom...) Felix Miata <mrmazda@earthlink.net> - 2023-11-02 01:00 +0100
Re: report a Debian bug gene heskett <gheskett@shentel.net> - 2023-11-02 02:40 +0100
Re: report a Debian bug David Christensen <dpchrist@holgerdanske.com> - 2023-11-02 06:50 +0100
Re: report a Debian bug gene heskett <gheskett@shentel.net> - 2023-11-02 09:10 +0100
Re: report a Debian bug David Christensen <dpchrist@holgerdanske.com> - 2023-11-02 22:20 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 17:30 +0200
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 17:50 +0200
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:40 +0200
Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-27 18:50 +0200
Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-27 19:10 +0200
Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-27 19:20 +0200
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 14:00 +0200
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 17:20 +0200
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 17:50 +0200
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:30 +0200
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:50 +0200
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 19:30 +0200
Re: Domain name to use on home networks David Wright <deblis@lionunicorn.co.uk> - 2023-10-29 15:30 +0100
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-29 16:30 +0100
Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-29 17:00 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-29 17:30 +0100
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-29 18:10 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-29 19:20 +0100
Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-29 19:40 +0100
Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-30 03:20 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 09:00 +0100
Re: Domain name to use on home networks Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-10-30 10:20 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 17:10 +0100
Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-30 17:20 +0100
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 17:50 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 18:30 +0100
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 18:40 +0100
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 17:50 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 18:10 +0100
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 18:30 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 18:40 +0100
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 18:30 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 18:40 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 17:50 +0100
Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-30 18:40 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 19:40 +0100
Re: Domain name to use on home networks "Andrew M.A. Cater" <amacater@einval.com> - 2023-10-30 19:40 +0100
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-30 19:50 +0100
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 22:10 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 22:40 +0100
Re: Domain name to use on home networks Charles Curley <charlescurley@charlescurley.com> - 2023-10-31 02:40 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-31 15:10 +0100
Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-31 04:10 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 19:50 +0100
Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-31 04:00 +0100
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 13:20 +0100
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 13:30 +0100
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-30 13:30 +0100
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 13:40 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 17:40 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 17:20 +0100
Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-30 16:00 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 17:40 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 16:40 +0200
Re: Domain name to use on home networks "Marco M." <mm@dorfdsl.de> - 2023-10-27 16:50 +0200
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:10 +0200
Re: Domain name to use on home networks "Marco M." <mm@dorfdsl.de> - 2023-10-27 21:30 +0200
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 16:50 +0200
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:20 +0200
Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-27 18:30 +0200
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 19:20 +0200
Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-27 20:00 +0200
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 20:10 +0200
Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-27 21:00 +0200
Re: Domain name to use on home networks The Wanderer <wanderer@fastmail.fm> - 2023-10-27 21:10 +0200
Re: Domain name to use on home networks Jeffrey Walton <noloader@gmail.com> - 2023-10-28 00:50 +0200
Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-28 07:40 +0200
Re: Domain name to use on home networks David Wright <deblis@lionunicorn.co.uk> - 2023-10-27 16:40 +0200
Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-26 10:20 +0200
Re: Domain name to use on home networks "Marco M." <mm@dorfdsl.de> - 2023-10-26 10:40 +0200
Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-26 11:20 +0200
Re: Domain name to use on home networks Jeffrey Walton <noloader@gmail.com> - 2023-10-26 11:10 +0200
Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-26 11:20 +0200
Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-27 17:30 +0200
Re: Domain name to use on home networks "Marco M." <mm@dorfdsl.de> - 2023-10-26 10:30 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager Jeffrey Walton <noloader@gmail.com> - 2023-10-25 22:10 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager David Wright <deblis@lionunicorn.co.uk> - 2023-10-26 01:30 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager jeremy ardley <jeremy.ardley@gmail.com> - 2023-10-26 02:00 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager Dan Purgert <dan@djph.net> - 2023-10-26 02:20 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager David Wright <deblis@lionunicorn.co.uk> - 2023-10-27 05:30 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager ghe2001 <ghe2001@protonmail.com> - 2023-10-23 18:00 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager Max Nikulin <manikulin@gmail.com> - 2023-10-23 04:50 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 18:20 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-23 20:10 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager "Andrew M.A. Cater" <amacater@einval.com> - 2023-10-23 20:30 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 23:40 +0200
Re: Bookworm: NetworkManager Dan Ritter <dsr@randomstring.org> - 2023-10-22 14:50 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 14:50 +0200
Re: example.org and other RFC 2606 domains; was: Bookworm: NetworkManager Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-22 15:20 +0200
Re: Bookworm: NetworkManager Dan Ritter <dsr@randomstring.org> - 2023-10-22 17:00 +0200
Re: Bookworm: NetworkManager Tixy <tixy@yxit.co.uk> - 2023-10-22 18:20 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 19:50 +0200
Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-21 20:40 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 20:50 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 22:30 +0200
Re: Bookworm: NetworkManager "Andrew M.A. Cater" <amacater@einval.com> - 2023-10-21 22:40 +0200
Re: Bookworm: NetworkManager Lee <ler762@gmail.com> - 2023-10-22 17:30 +0200
Re: Bookworm: NetworkManager <tomas@tuxteam.de> - 2023-10-22 17:30 +0200
Re: Bookworm: NetworkManager Lee <ler762@gmail.com> - 2023-10-22 17:50 +0200
Re: Bookworm: NetworkManager Max Nikulin <manikulin@gmail.com> - 2023-10-25 19:00 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 19:40 +0200
Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-22 19:20 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 19:50 +0200
Re: Bookworm: NetworkManager Lee <ler762@gmail.com> - 2023-10-23 00:40 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-23 01:20 +0200
Re: Bookworm: NetworkManager Lee <ler762@gmail.com> - 2023-10-23 19:10 +0200
Re: Bookworm: NetworkManager Andy Smith <andy@strugglers.net> - 2023-10-23 22:30 +0200
Re: Bookworm: NetworkManager Lee <ler762@gmail.com> - 2023-10-27 21:40 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 02:30 +0200
Page 7 of 13 — ← Prev page 1 … 5 6 [7] 8 9 … 13 Next page →
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-10-31 04:20 +0100 |
| Subject | Re: Changing host name and domain name on Debian; was: Domain nametouse on home networks |
| Message-ID | <HuNsl-21Um-3@gated-at.bofh.it> |
| In reply to | #262872 |
On 30/10/2023 00:00, gene heskett wrote: > Somebody who /can/ report it. I changed ISP's over a decade back, so I > am not me to bugzilla, and because I am known also by name, I can't > re-register. I can't even get a pw reset cuz it (I'm guessing here) is > sending it to my earlier ISP's Sorry, it is not clear what particular bugzilla instance you are writing about. You are sending e-mails and you should be able to register a new account. Do you mean that you have managed to upset developers to the degree when they decide to ban your active mail address?
[toc] | [prev] | [next] | [standalone]
| From | The Wanderer <wanderer@fastmail.fm> |
|---|---|
| Date | 2023-10-31 10:20 +0100 |
| Subject | Re: Changing host name and domain name on Debian; was: Domain nametouse on home networks |
| Message-ID | <HuT4J-25CI-9@gated-at.bofh.it> |
| In reply to | #262947 |
[Multipart message — attachments visible in raw view] — view raw
On 2023-10-30 at 23:11, Max Nikulin wrote: > On 30/10/2023 00:00, gene heskett wrote: > >> Somebody who /can/ report it. I changed ISP's over a decade back, >> so I am not me to bugzilla, and because I am known also by name, I >> can't re-register. I can't even get a pw reset cuz it (I'm guessing >> here) is sending it to my earlier ISP's > > Sorry, it is not clear what particular bugzilla instance you are > writing about. You are sending e-mails and you should be able to > register a new account. Do you mean that you have managed to upset > developers to the degree when they decide to ban your active mail > address? I parsed it as something like "I can't register an account that has the same name (in whatever sense matters to me) as the one I had before, because that account already exists, and I can't recover that account, because it's trying to recover via an E-mail address I no longer have access to.". The question of in what sense the account has the "same name" is undetermined, but the existence of such an additional constraint is the only way I can see to parse the given scenario so that it makes sense. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-31 15:30 +0100 |
| Subject | Re: Changing host name and domain name on Debian; was: Domain nametouseon home networks |
| Message-ID | <HuXUJ-28vP-1@gated-at.bofh.it> |
| In reply to | #262954 |
On 10/31/23 05:12, The Wanderer wrote: > On 2023-10-30 at 23:11, Max Nikulin wrote: > >> On 30/10/2023 00:00, gene heskett wrote: >> >>> Somebody who /can/ report it. I changed ISP's over a decade back, >>> so I am not me to bugzilla, and because I am known also by name, I >>> can't re-register. I can't even get a pw reset cuz it (I'm guessing >>> here) is sending it to my earlier ISP's >> >> Sorry, it is not clear what particular bugzilla instance you are >> writing about. You are sending e-mails and you should be able to >> register a new account. Do you mean that you have managed to upset >> developers to the degree when they decide to ban your active mail >> address? > > I parsed it as something like "I can't register an account that has the > same name (in whatever sense matters to me) as the one I had before, > because that account already exists, and I can't recover that account, > because it's trying to recover via an E-mail address I no longer have > access to.". > > The question of in what sense the account has the "same name" is > undetermined, but the existence of such an additional constraint is the > only way I can see to parse the given scenario so that it makes sense. > correct Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-31 15:30 +0100 |
| Subject | Re: Changing host name and domain name on Debian; was: Domainnametouse on home networks |
| Message-ID | <HuXUJ-28vP-3@gated-at.bofh.it> |
| In reply to | #262947 |
On 10/30/23 23:12, Max Nikulin wrote: > On 30/10/2023 00:00, gene heskett wrote: >> Somebody who /can/ report it. I changed ISP's over a decade back, so I >> am not me to bugzilla, and because I am known also by name, I can't >> re-register. I can't even get a pw reset cuz it (I'm guessing here) is >> sending it to my earlier ISP's > > Sorry, it is not clear what particular bugzilla instance you are writing > about. You are sending e-mails and you should be able to register a new > account. Do you mean that you have managed to upset developers to the > degree when they decide to ban your active mail address? > > . I thought I made it clear. I've changed ISP's, several times over the last 30 years. And I am registered, but the bugzilla software apparently sends all correspondence reply's to an old address so I am not able to confirm because I never get the confirmation message. But bugzilla knows me by name and I am not me when coming from a new ISP. The only way for me to register is to have the admins nuke me out of the system entirely. Until that is done and I can then register a new account, I'm screwed. I've requested pw resets, never got them, presumable because it sends the reset link to a 20 yo address. If you know someone who has admin rights and could fix it, put it to me. Mail sent to admin@bugzilla.com bounces. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | John Hasler <john@sugarbit.com> |
|---|---|
| Date | 2023-10-31 17:40 +0100 |
| Subject | Re: Changing host name and domain name on Debian; was: Domainnametouse on home networks |
| Message-ID | <HuZWx-29Im-7@gated-at.bofh.it> |
| In reply to | #262969 |
Gene writes: > But bugzilla knows me by name and I am not me when coming from a new > ISP. So use a different name. > Mail sent to admin@bugzilla.com bounces. bugzilla.com is a site about customized Volkswagen beetles. -- John Hasler john@sugarbit.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2023-11-01 22:10 +0100 |
| Subject | Re: Changing host name and domain name on Debian; was: Domainnametouse on home networks |
| Message-ID | <HvqDn-2rcC-11@gated-at.bofh.it> |
| In reply to | #262969 |
gene heskett composed on 2023-10-31 10:26 (UTC-0400): > I've requested pw resets, never got them, presumable because it sends > the reset link to a 20 yo address. If you know someone who has admin > rights and could fix it, put it to me. Mail sent to admin@bugzilla.com > bounces. Bugzilla.com has nothing to do with tracking any kind of software issues. It's about Volkswagen Bug automobiles. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-11-02 00:30 +0100 |
| Subject | Re: Changing host name and domain name on Debian; was:Domainnametouse on home networks |
| Message-ID | <HvsOR-2sxS-3@gated-at.bofh.it> |
| In reply to | #263010 |
On 11/1/23 17:08, Felix Miata wrote: > gene heskett composed on 2023-10-31 10:26 (UTC-0400): > >> I've requested pw resets, never got them, presumable because it sends >> the reset link to a 20 yo address. If you know someone who has admin >> rights and could fix it, put it to me. Mail sent to admin@bugzilla.com >> bounces. > > Bugzilla.com has nothing to do with tracking any kind of software issues. It's > about Volkswagen Bug automobiles. That is informative, thanks Felix, but what is wrong with publishing the correct address? Not being able to use it, I haven't reserved space for it in the wet ram... ;o)> Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-11-02 00:40 +0100 |
| Subject | Re: Changing host name and domain name on Debian; was:Domainnametouse on home networks |
| Message-ID | <HvsYx-2sB6-1@gated-at.bofh.it> |
| In reply to | #263013 |
On Wed, Nov 01, 2023 at 07:20:27PM -0400, gene heskett wrote: > On 11/1/23 17:08, Felix Miata wrote: > > gene heskett composed on 2023-10-31 10:26 (UTC-0400): > > > > > I've requested pw resets, never got them, presumable because it sends > > > the reset link to a 20 yo address. If you know someone who has admin > > > rights and could fix it, put it to me. Mail sent to admin@bugzilla.com > > > bounces. > > > > Bugzilla.com has nothing to do with tracking any kind of software issues. It's > > about Volkswagen Bug automobiles. > That is informative, thanks Felix, but what is wrong with publishing the > correct address? Not being able to use it, I haven't reserved space for it > in the wet ram... ;o)> The problem is, you haven't yet told us *whose* bugzilla-based bug tracking system you're talking about. That makes it hard for anyone to offer assistance.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-11-02 01:20 +0100 |
| Subject | Re: Changing host name and domain name on Debian;was:Domainnametouse on home networks |
| Message-ID | <HvtBf-2t4m-1@gated-at.bofh.it> |
| In reply to | #263014 |
On 11/1/23 19:30, Greg Wooledge wrote: > On Wed, Nov 01, 2023 at 07:20:27PM -0400, gene heskett wrote: >> On 11/1/23 17:08, Felix Miata wrote: >>> gene heskett composed on 2023-10-31 10:26 (UTC-0400): >>> >>>> I've requested pw resets, never got them, presumable because it sends >>>> the reset link to a 20 yo address. If you know someone who has admin >>>> rights and could fix it, put it to me. Mail sent to admin@bugzilla.com >>>> bounces. >>> >>> Bugzilla.com has nothing to do with tracking any kind of software issues. It's >>> about Volkswagen Bug automobiles. >> That is informative, thanks Felix, but what is wrong with publishing the >> correct address? Not being able to use it, I haven't reserved space for it >> in the wet ram... ;o)> > > The problem is, you haven't yet told us *whose* bugzilla-based bug > tracking system you're talking about. That makes it hard for anyone > to offer assistance. > > . I wasn't aware there was more than 1 Greg, debian of course Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-11-02 01:40 +0100 |
| Subject | Re: Changing host name and domain name on Debian;was:Domainnametouse on home networks |
| Message-ID | <HvtUB-2tba-7@gated-at.bofh.it> |
| In reply to | #263018 |
On Wed, Nov 01, 2023 at 08:18:45PM -0400, gene heskett wrote: > On 11/1/23 19:30, Greg Wooledge wrote: > > The problem is, you haven't yet told us *whose* bugzilla-based bug > > tracking system you're talking about. That makes it hard for anyone > > to offer assistance. > > > I wasn't aware there was more than 1 Greg, debian of course As far as I'm aware, Debian doesn't use bugzilla. The Debian bug tracking system is based on sending email. Users are encouraged to use the "reportbug" program to generate the email, because it gathers various pieces of useful information. But it's not required. You can simply send an email with the correct body content to the correct email address, and a bug will be filed. See <https://www.debian.org/Bugs/>.
[toc] | [prev] | [next] | [standalone]
| From | Jeffrey Walton <noloader@gmail.com> |
|---|---|
| Date | 2023-11-02 02:20 +0100 |
| Subject | Re: Changing host name and domain name on Debian;was:Domainnametouse on home networks |
| Message-ID | <Hvuxj-2tDa-1@gated-at.bofh.it> |
| In reply to | #263019 |
On Wed, Nov 1, 2023 at 8:35 PM Greg Wooledge <greg@wooledge.org> wrote:
>
> On Wed, Nov 01, 2023 at 08:18:45PM -0400, gene heskett wrote:
> > On 11/1/23 19:30, Greg Wooledge wrote:
> > > The problem is, you haven't yet told us *whose* bugzilla-based bug
> > > tracking system you're talking about. That makes it hard for anyone
> > > to offer assistance.
> > >
> > I wasn't aware there was more than 1 Greg, debian of course
>
> As far as I'm aware, Debian doesn't use bugzilla.
Debian uses the infamous BTS or Bug Tracking System. Sometimes it is
called Debbugs. Others (and you) already provided
<https://www.debian.org/Bugs/> and
<https://www.debian.org/Bugs/Reporting>. Add me as a "mee too" (but I
don't think it will help).
The short of it is, send an email to <submit@bugs.debian.org>. The
email must be formatted in a particular way. The important parts that
must be at the head of the email's body are the Package and Version
fields. Package and Version are part of the "pseudo-headers":
Package: b43-fwcutter
Version: 1:019-7
Tags: sid
dpkg will provide the package name and version.
I sometimes use the X-Debbugs-CC field to include a CC, if someone
other than the package maintainer should receive an email.
After the pseudo-headers, describe the problem. I.e., provide the text
of the bug.
Jeff
[toc] | [prev] | [next] | [standalone]
| From | John Hasler <john@sugarbit.com> |
|---|---|
| Date | 2023-11-02 00:40 +0100 |
| Subject | Re: Changing host name and domain name on Debian; was:Domainnametouse on home networks |
| Message-ID | <HvsYx-2sB6-7@gated-at.bofh.it> |
| In reply to | #263013 |
Gene writes: > That is informative, thanks Felix, but what is wrong with publishing > the correct address? Correct address for what? You don't want bugzilla.org: that's the home page for the Bugzilla bug tracking program which whoever you are trying to contact uses. -- John Hasler john@sugarbit.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2023-11-02 01:00 +0100 |
| Subject | Re: report a Debian bug (was: Changing host name and dom...) |
| Message-ID | <HvthT-2sIq-1@gated-at.bofh.it> |
| In reply to | #263013 |
gene heskett composed on 2023-11-01 19:20 (UTC-0400): > Felix Miata wrote: >> gene heskett composed on 2023-10-31 10:26 (UTC-0400): >>> Mail sent to admin@bugzilla.com bounces. >> Bugzilla.com has nothing to do with tracking any kind of software issues. It's >> about Volkswagen Bug automobiles. > That is informative, thanks Felix, but what is wrong with publishing > the correct address? Not being able to use it, I haven't reserved space > for it in the wet ram... ;o)> For one thing, I never use it directly, and another, it doesn't include the string bugzilla, so I don't remember what it is, and thus need to look it up, same as you, if and when I want it. I use the Debian software named reportbug. If you don't wish to use reportbug, start here: https://www.debian.org/Bugs/ If you do: https://www.debian.org/Bugs/Reporting or man reportbug -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-11-02 02:40 +0100 |
| Subject | Re: report a Debian bug |
| Message-ID | <HvuQF-2tJG-3@gated-at.bofh.it> |
| In reply to | #263016 |
On 11/1/23 19:57, Felix Miata wrote: > gene heskett composed on 2023-11-01 19:20 (UTC-0400): > >> Felix Miata wrote: > >>> gene heskett composed on 2023-10-31 10:26 (UTC-0400): > >>>> Mail sent to admin@bugzilla.com bounces. > >>> Bugzilla.com has nothing to do with tracking any kind of software issues. It's >>> about Volkswagen Bug automobiles. > >> That is informative, thanks Felix, but what is wrong with publishing >> the correct address? Not being able to use it, I haven't reserved space >> for it in the wet ram... ;o)> > > For one thing, I never use it directly, and another, it doesn't include the string > bugzilla, so I don't remember what it is, and thus need to look it up, same as > you, if and when I want it. I use the Debian software named reportbug. If you > don't wish to use reportbug, start here: > > https://www.debian.org/Bugs/ > > If you do: > > https://www.debian.org/Bugs/Reporting > > or > > man reportbug I started with that, was amazed at the complexity so I figured I'd just wing it, used the novice profile but when it asked me for package I gave it 12 for other, then got stuck in a forever loop and when it was obvious it wasn't going let me go by I gave it a ctl-c. I have no clue what to file it against as it doesn't give me a program list to choose from but a list of mostly web pages. I can however, describe the miss-behaviour I get and have 2 or 4 times on this list and been ignored. So what i'm going to do next is transfer my /home, the whole MaryAnn from a 4 drive raid10 to a single 2T SSD,, and then switch /home from the raid to a single drive, thereby removing the raid10 from the culprit list. If that doesn't fix it, then its something to do with the graficks. I have one real clue, some one the openscad list said the preview mode opened a bunch of gfx buffers it used the preview mode that it didn't do in final build mode, so I ran some tests on a fairly complex project, noting that the openscad logging window said a preview was done in a bit over a second but the final monocolored version took over 9 seconds to render, giving me an image I could move in 3d space in the preview window in real time. But that 1.2 second preview render took 30 to 45 seconds to show in\on screen and every update of that image took at least 45 seconds to register on screen, and during that 45 seconds or more, openscad was frozen from all other input. That is as close to a clue as I have, also manifested when any kind of a file requester needs to be drawn on screen it is subjectto to that same time killing lockup except it might be as long as 5 minutes before the requestor is drawn on screen. That raid was built by buster, worded fine for bullseye, but seems to be a disaster for bookworm, yet an fsck finds nothing wrong. Those are the clues I have. Nothing obvious and common to all this contaminates the logs. I own the whole nearly 1.8T raid10, every byte of it. Why can't I use it? Instead its holding me for an undefined ransom in time that I at 89 don't have a lot of left. Thanks Felix, take care & stay well. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2023-11-02 06:50 +0100 |
| Subject | Re: report a Debian bug |
| Message-ID | <HvyKB-2wbT-1@gated-at.bofh.it> |
| In reply to | #263021 |
On 11/1/23 18:34, gene heskett wrote: > So what i'm going to do next is transfer my /home, the whole MaryAnn > from a 4 drive raid10 to a single 2T SSD,, and then switch /home from > the raid to a single drive, thereby removing the raid10 from the culprit > list. > > If that doesn't fix it, then its something to do with the graficks. > I have one real clue, some one the openscad list said the preview mode > opened a bunch of gfx buffers it used the preview mode that it didn't do > in final build mode, so I ran some tests on a fairly complex project, > noting that the openscad logging window said a preview was done in a bit > over a second but the final monocolored version took over 9 seconds to > render, giving me an image I could move in 3d space in the preview > window in real time. But that 1.2 second preview render took 30 to 45 > seconds to show in\on screen and every update of that image took at > least 45 seconds to register on screen, and during that 45 seconds or > more, openscad was frozen from all other input. That is as close to a > clue as I have, also manifested when any kind of a file requester needs > to be drawn on screen it is subjectto to that same time killing lockup > except it might be as long as 5 minutes before the requestor is drawn on > screen. That raid was built by buster, worded fine for bullseye, but > seems to be a disaster for bookworm, yet an fsck finds nothing wrong. > > Those are the clues I have. Nothing obvious and common to all this > contaminates the logs. > > I own the whole nearly 1.8T raid10, every byte of it. Why can't I use > it? Instead its holding me for an undefined ransom in time that I at 89 > don't have a lot of left. I assume this is the computer with the Asus PRIME Z370-A II motherboard, Intel i5-9600K processor, 32 GB RAM, WD Black 2 TB NVMe PCIe 3.0 x4 SSD, a few PCIe x1 SATA III HBA's with many ports, many SATA III SSD's and/or HDD's, and a few md RAID (?). Did you connect the /home RAID10 4 @ 1 TB SSD's to one PCIe x1 HBA? Are your file systems full? # df /boot / /tmp /home Do your file systems need defragmenting? # e4defrag -c /boot / /home David
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-11-02 09:10 +0100 |
| Subject | Re: report a Debian bug |
| Message-ID | <HvAW5-2xFF-7@gated-at.bofh.it> |
| In reply to | #263023 |
On 11/2/23 01:46, David Christensen wrote:
> On 11/1/23 18:34, gene heskett wrote:
>
>> So what i'm going to do next is transfer my /home, the whole MaryAnn
>> from a 4 drive raid10 to a single 2T SSD,, and then switch /home from
>> the raid to a single drive, thereby removing the raid10 from the
>> culprit list.
>>
>> If that doesn't fix it, then its something to do with the graficks.
>> I have one real clue, some one the openscad list said the preview mode
>> opened a bunch of gfx buffers it used the preview mode that it didn't
>> do in final build mode, so I ran some tests on a fairly complex
>> project, noting that the openscad logging window said a preview was
>> done in a bit over a second but the final monocolored version took
>> over 9 seconds to render, giving me an image I could move in 3d space
>> in the preview window in real time. But that 1.2 second preview
>> render took 30 to 45 seconds to show in\on screen and every update of
>> that image took at least 45 seconds to register on screen, and during
>> that 45 seconds or more, openscad was frozen from all other input.
>> That is as close to a clue as I have, also manifested when any kind of
>> a file requester needs to be drawn on screen it is subjectto to that
>> same time killing lockup except it might be as long as 5 minutes
>> before the requestor is drawn on screen. That raid was built by
>> buster, worded fine for bullseye, but seems to be a disaster for
>> bookworm, yet an fsck finds nothing wrong.
>>
>> Those are the clues I have. Nothing obvious and common to all this
>> contaminates the logs.
>>
>> I own the whole nearly 1.8T raid10, every byte of it. Why can't I use
>> it? Instead its holding me for an undefined ransom in time that I at
>> 89 don't have a lot of left.
>
>
> I assume this is the computer with the Asus PRIME Z370-A II motherboard,
> Intel i5-9600K processor, 32 GB RAM, WD Black 2 TB NVMe PCIe 3.0 x4
> SSD, a few PCIe x1 SATA III HBA's with many ports, many SATA III SSD's
> and/or HDD's, and a few md RAID (?).
>
Yup, I just added another 3.6Tb of sdd's that are still unformatted.
Gigastone's from Taiwan.
>
> Did you connect the /home RAID10 4 @ 1 TB SSD's to one PCIe x1 HBA?
I assume its an X1 card, small footprint, cheap version with 10 bondouts
but only 6 have drive cable sockets installed. Only 4 for the raid10 are
actually used. I have another card I haven't tried, is a full 16 ports
but is also the narrow pci-e footprint. Neither is sold as a raid card,
so its all mdadm.
This worked perfectly for buster and bullseye, so it seems this problem
is bookworms problem.
>
>
> Are your file systems full?
/home is currently about 20% used, everything else is much lower yet.
>
> # df /boot / /tmp /home
The whole thing:
gene@coyote:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 16329748 0 16329748 0% /dev
tmpfs 3272676 1880 3270796 1% /run
/dev/sda1 863983352 15989096 804032608 2% /
tmpfs 16363376 1232 16362144 1% /dev/shm
tmpfs 5120 8 5112 1% /run/lock
/dev/sda3 47749868 260 45291600 1% /tmp
/dev/md0p1 1796382580 327360472 1377697132 20% /home
tmpfs 3272672 3768 3268904 1% /run/user/1000
>
>
> Do your file systems need defragmenting?
>
> # e4defrag -c /boot / /home
dnk, wasn't fam with how to do it, And worst case score for that cmd is 1.
/home was the last check:
<Fragmented files> now/best size/ext
1.
/home/gene/.mozilla/firefox/f8j7d2lj.default-esr/storage/default/https+++www.wsaz.com/ls/data.sqlite
7/1 4 KB
2.
/home/gene/.mozilla/firefox/f8j7d2lj.default-esr/storage/default/https+++apps.sascdn.com/ls/data.sqlite
7/1 4 KB
3.
/home/gene/.mozilla/firefox/f8j7d2lj.default-esr/storage/default/https+++www.euronews.com/ls/data.sqlite
6/1 4 KB
4.
/home/gene/.mozilla/firefox/f8j7d2lj.default-esr/storage/default/https+++www.britannica.com/ls/data.sqlite
6/1 4 KB
5.
/home/gene/.mozilla/firefox/f8j7d2lj.default-esr/storage/default/https+++travelermaster.com/ls/data.sqlite
6/1 4 KB
Total/best extents 1245442/1166289
Average size per extent 262 KB
Fragmentation score 1
[0-30 no problem: 31-55 a little bit fragmented: 56- needs defrag]
This directory (/home) does not need defragmentation.
Done.
> David
Thank you David.
>
> .
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2023-11-02 22:20 +0100 |
| Subject | Re: report a Debian bug |
| Message-ID | <HvNgB-2FFs-1@gated-at.bofh.it> |
| In reply to | #263033 |
On 11/2/23 01:05, gene heskett wrote:
> On 11/2/23 01:46, David Christensen wrote:
>> On 11/1/23 18:34, gene heskett wrote:
>>
>>> So what i'm going to do next is transfer my /home, the whole MaryAnn
>>> from a 4 drive raid10 to a single 2T SSD,, and then switch /home from
>>> the raid to a single drive, thereby removing the raid10 from the
>>> culprit list.
The df(1) output, below, indicates that /home is still on RAID10.
>>> If that doesn't fix it, then its something to do with the graficks.
>>> I have one real clue, some one the openscad list said the preview
>>> mode opened a bunch of gfx buffers it used the preview mode that it
>>> didn't do in final build mode, so I ran some tests on a fairly
>>> complex project, noting that the openscad logging window said a
>>> preview was done in a bit over a second but the final monocolored
>>> version took over 9 seconds to render, giving me an image I could
>>> move in 3d space in the preview window in real time. But that 1.2
>>> second preview render took 30 to 45 seconds to show in\on screen and
>>> every update of that image took at least 45 seconds to register on
>>> screen, and during that 45 seconds or more, openscad was frozen from
>>> all other input. That is as close to a clue as I have, also
>>> manifested when any kind of a file requester needs to be drawn on
>>> screen it is subjectto to that same time killing lockup except it
>>> might be as long as 5 minutes before the requestor is drawn on
>>> screen. That raid was built by buster, worded fine for bullseye, but
>>> seems to be a disaster for bookworm, yet an fsck finds nothing wrong.
>>>
>>> Those are the clues I have. Nothing obvious and common to all this
>>> contaminates the logs.
>>>
>>> I own the whole nearly 1.8T raid10, every byte of it. Why can't I
>>> use it? Instead its holding me for an undefined ransom in time that I
>>> at 89 don't have a lot of left.
>>
>> I assume this is the computer with the Asus PRIME Z370-A II
>> motherboard, Intel i5-9600K processor, 32 GB RAM, WD Black 2 TB NVMe
>> PCIe 3.0 x4 SSD, a few PCIe x1 SATA III HBA's with many ports, many
>> SATA III SSD's and/or HDD's, and a few md RAID (?).
>
> Yup, I just added another 3.6Tb of sdd's that are still unformatted.
> Gigastone's from Taiwan.
4 @ 1 TB or 2 @ 2 TB? If and when you configure them, please note that
in future posts.
>> Did you connect the /home RAID10 4 @ 1 TB SSD's to one PCIe x1 HBA?
>
> I assume its an X1 card, small footprint, cheap version with 10 bondouts
> but only 6 have drive cable sockets installed. Only 4 for the raid10 are
> actually used.
One PCIe 3.0 lane is rated for 985 MB/s, which is less than the sum of
the throughputs for 4 @ SATA III SSD's. But, it should not cause the
openscad issues.
> I have another card I haven't tried, is a full 16 ports
> but is also the narrow pci-e footprint. Neither is sold as a raid card,
> so its all mdadm.
I recall discussing that about two months ago. Similar to the 6 port
HBA, it will limit the aggregate throughput; but should not cause
openscad issues.
> This worked perfectly for buster and bullseye, so it seems this problem
> is bookworms problem.
If you have a Buster or Bullseye drives or system images, they could be
useful for testing.
>> Are your file systems full?
> /home is currently about 20% used, everything else is much lower yet.
>>
>> # df /boot / /tmp /home
> The whole thing:
> gene@coyote:~$ df
> Filesystem 1K-blocks Used Available Use% Mounted on
> udev 16329748 0 16329748 0% /dev
> tmpfs 3272676 1880 3270796 1% /run
> /dev/sda1 863983352 15989096 804032608 2% /
> tmpfs 16363376 1232 16362144 1% /dev/shm
> tmpfs 5120 8 5112 1% /run/lock
> /dev/sda3 47749868 260 45291600 1% /tmp
> /dev/md0p1 1796382580 327360472 1377697132 20% /home
> tmpfs 3272672 3768 3268904 1% /run/user/1000
Okay -- no free space issues.
What drive corresponds to /dev/sda? If not the WD Black 2 TB NVMe
drive, then is the WD Black installed and configured?
>> Do your file systems need defragmenting?
>>
>> # e4defrag -c /boot / /home
> dnk, wasn't fam with how to do it, And worst case score for that cmd is 1.
> /home was the last check:
>
> <Fragmented files> now/best size/ext
> 1.
> /home/gene/.mozilla/firefox/f8j7d2lj.default-esr/storage/default/https+++www.wsaz.com/ls/data.sqlite
> 7/1 4 KB
> 2.
> /home/gene/.mozilla/firefox/f8j7d2lj.default-esr/storage/default/https+++apps.sascdn.com/ls/data.sqlite
> 7/1 4 KB
> 3.
> /home/gene/.mozilla/firefox/f8j7d2lj.default-esr/storage/default/https+++www.euronews.com/ls/data.sqlite
> 6/1 4 KB
> 4.
> /home/gene/.mozilla/firefox/f8j7d2lj.default-esr/storage/default/https+++www.britannica.com/ls/data.sqlite
> 6/1 4 KB
> 5.
> /home/gene/.mozilla/firefox/f8j7d2lj.default-esr/storage/default/https+++travelermaster.com/ls/data.sqlite
> 6/1 4 KB
>
> Total/best extents 1245442/1166289
> Average size per extent 262 KB
> Fragmentation score 1
> [0-30 no problem: 31-55 a little bit fragmented: 56- needs defrag]
> This directory (/home) does not need defragmentation.
> Done.
Okay -- no fragmentation issues.
> Thank you David.
YW. :-)
The "PRIME Z370-A II Series" user's manual indicates various RAID and
non-RAID storage configurations using PCIe slots, PCIe Hyper M.2 cards,
M.2 sockets, M.2 drives, SATA 6.0 Gb/s ports, SATA drives, and Setup
NVRAM settings. The details are non-trivial -- perhaps your system is
mis-configured (?):
https://www.asus.com/us/supportonly/prime%20z370-a%20ii/helpdesk_manual/
Please examine the following NVRAM settings:
BIOS Setup
Advanced menu
PCH Storage Configuration
SATA Mode Selection AHCI
If the WD Black is installed in socket M.2_1:
BIOS Setup
Advanced menu
Onboard Devices Configuration
M.2_1 Configuration PCIE mode
If the WD Black is installed in socket M.2_2 (ports SATA6G_5 and
SATA6G_6 will be disabled in X4 mode):
BIOS Setup
Advanced menu
Onboard Devices Configuration
M.2_2 PCIe Bandwidth Configuration X4
To check the hardware and NVRAM configuration, tear down the system to
just the motherboard and one SATA drive with Bookworm, reset Setup NVRAM
to defaults, and test. If the openscad issue is present, try Bullseye
and/or Buster. If the issue is absent, continue adding hardware,
configuring NVRAM, and testing until either you find the problem or the
system is complete.
David
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-27 17:30 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtwWB-1fzz-7@gated-at.bofh.it> |
| In reply to | #262775 |
On 10/27/23 07:59, Pocket wrote: > > On 10/27/23 07:50, Greg Wooledge wrote: >> On Fri, Oct 27, 2023 at 07:29:20AM -0400, Pocket wrote: >>> On 10/27/23 07:12, gene heskett wrote: >>>> I tried to change just this machine to see how its done, and managed to >>>> get all the right answers, which did not affect my local network >>>> since I >>>> generally use the alias name for an ssh or sshfs login, but on a reboot >>>> its all gone. So how the heck do we do that so it survives a reboot? >> *What* is "all gone"? Show us commands and their output, and then >> explain >> why the output is not what you expected. >> >>> /etc/hosts >> If you're using short-form hostnames like this: >> >> unicorn:~$ hostname >> unicorn >> >> then yeah, that's all you need. If you're using long-form hostnames >> (with dots in them), then you also need to configure /etc/hostname. >> >> I use the short-form hostnames, so mine is simply: >> >> unicorn:~$ cat /etc/hostname >> unicorn >> >> Couldn't be simpler, really. > > Are you referring to the domain name or FQDN? Not a systemd luver nor expert. Someone suggested that if I was using dotted names, then I should edit (as sudo) /etc/hostname which I have now done t add the FQDN name of coyote.home.arpa. but: gene@coyote:/etc$ sudo nano hostname (and add .home.arpa to the alias name it had) [sudo] password for gene: gene@coyote:/etc$ domainname (none) gene@coyote:/etc$ hostname coyote gene@coyote:/etc$ So instead of giving me static cuz I'm not doing it right, show me the right way! Thank you. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-10-27 17:50 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtxfX-1fG6-1@gated-at.bofh.it> |
| In reply to | #262791 |
On Fri, Oct 27, 2023 at 11:25:00AM -0400, gene heskett wrote: > Not a systemd luver nor expert. Someone suggested that if I was using dotted > names, then I should edit (as sudo) /etc/hostname which I have now done t > add the FQDN name of coyote.home.arpa. You should undo that. There's no reason to switch your philosophy at this point. I did not say that you SHOULD use hostnames with dots in them. I said that SOME PEOPLE use hostnames with dots in them, and that IF you are one of those people, there's an extra step to perform. I don't have any idea how this was so misunderstood.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-27 18:40 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Hty2m-1gbJ-15@gated-at.bofh.it> |
| In reply to | #262792 |
On 10/27/23 11:45, Greg Wooledge wrote: > On Fri, Oct 27, 2023 at 11:25:00AM -0400, gene heskett wrote: >> Not a systemd luver nor expert. Someone suggested that if I was using dotted >> names, then I should edit (as sudo) /etc/hostname which I have now done t >> add the FQDN name of coyote.home.arpa. > > You should undo that. There's no reason to switch your philosophy at > this point. > > I did not say that you SHOULD use hostnames with dots in them. > > I said that SOME PEOPLE use hostnames with dots in them, and that IF you > are one of those people, there's an extra step to perform. > > I don't have any idea how this was so misunderstood. > > . Confusing, miss leading man pages are a lot of it. If the domainname command is only for NIS systems, whatever the hell that means, the first line of the man page should plainly state VALID FOR NIS SYSTEMS ONLY. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
Page 7 of 13 — ← Prev page 1 … 5 6 [7] 8 9 … 13 Next page →
Back to top | Article view | linux.debian.user
csiph-web