Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #263021
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: report a Debian bug |
| Date | 2023-11-02 02:40 +0100 |
| Message-ID | <HvuQF-2tJG-3@gated-at.bofh.it> (permalink) |
| References | (6 earlier) <HuNsl-21Um-3@gated-at.bofh.it> <HuXUJ-28vP-3@gated-at.bofh.it> <HvqDn-2rcC-11@gated-at.bofh.it> <HvsOR-2sxS-3@gated-at.bofh.it> <HvthT-2sIq-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
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
csiph-web