Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #208030 > unrolled thread

forcedeth?

Started byGene Heskett <gheskett@shentel.net>
First post2019-05-02 13:30 +0200
Last post2019-05-25 19:10 +0200
Articles 20 on this page of 72 — 18 participants

Back to article view | Back to linux.debian.user


Contents

  forcedeth? Gene Heskett <gheskett@shentel.net> - 2019-05-02 13:30 +0200
    Re: forcedeth? songbird <songbird@anthive.com> - 2019-05-02 14:20 +0200
    Re: forcedeth? Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-05-02 20:20 +0200
      Re: forcedeth? Gene Heskett <gheskett@shentel.net> - 2019-05-02 22:30 +0200
        Re: forcedeth? Andrei POPESCU <andreimpopescu@gmail.com> - 2019-05-25 12:40 +0200
          Re: forcedeth? Gene Heskett <gheskett@shentel.net> - 2019-05-25 13:00 +0200
            Re: forcedeth? Andy Smith <andy@strugglers.net> - 2019-05-25 13:40 +0200
              Re: forcedeth? Gene Heskett <gheskett@shentel.net> - 2019-05-25 17:30 +0200
                That time IPv6 farted in Gene's church (Was Re: forcedeth?) Andy Smith <andy@strugglers.net> - 2019-05-27 04:20 +0200
                  Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Gene Heskett <gheskett@shentel.net> - 2019-05-27 06:50 +0200
                    Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Andy Smith <andy@strugglers.net> - 2019-05-27 08:10 +0200
                      Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Gene Heskett <gheskett@shentel.net> - 2019-05-27 18:20 +0200
                      Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Jimmy Johnson <field.engineer@gmail.com> - 2019-05-27 19:20 +0200
                        Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Andy Smith <andy@strugglers.net> - 2019-05-28 17:50 +0200
                          Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Jimmy Johnson <field.engineer@gmail.com> - 2019-05-28 19:20 +0200
                            Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Andy Smith <andy@strugglers.net> - 2019-05-28 20:40 +0200
                    Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) <tomas@tuxteam.de> - 2019-05-27 09:00 +0200
                      Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Curt <curty@free.fr> - 2019-05-27 09:50 +0200
                        Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) <tomas@tuxteam.de> - 2019-05-27 11:00 +0200
                        Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Jonas Smedegaard <jonas@jones.dk> - 2019-05-27 11:00 +0200
                          Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Jimmy Johnson <field.engineer@gmail.com> - 2019-05-27 19:30 +0200
                        Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Jimmy Johnson <field.engineer@gmail.com> - 2019-05-27 19:30 +0200
                          Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Brian <ad44@cityscape.co.uk> - 2019-05-27 22:00 +0200
                            Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Jimmy Johnson <field.engineer@gmail.com> - 2019-05-28 08:40 +0200
                              Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Erik Christiansen <dvalin@internode.on.net> - 2019-05-28 13:20 +0200
                        Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Gene Heskett <gheskett@shentel.net> - 2019-05-27 19:50 +0200
                          Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Brian <ad44@cityscape.co.uk> - 2019-05-27 21:30 +0200
                            Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Gene Heskett <gheskett@shentel.net> - 2019-05-27 23:30 +0200
                              Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Brian <ad44@cityscape.co.uk> - 2019-05-28 00:50 +0200
                                Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Gene Heskett <gheskett@shentel.net> - 2019-05-28 04:50 +0200
                              Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) mick crane <mick.crane@gmail.com> - 2019-05-28 05:10 +0200
                          Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Jonas Smedegaard <jonas@jones.dk> - 2019-05-27 21:50 +0200
                            Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Gene Heskett <gheskett@shentel.net> - 2019-05-28 00:20 +0200
                              Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2019-05-28 05:40 +0200
                                Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Curt <curty@free.fr> - 2019-05-28 09:50 +0200
                                  Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Reco <recoverym4n@enotuniq.net> - 2019-05-28 10:00 +0200
                                    Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) <tomas@tuxteam.de> - 2019-05-28 10:50 +0200
                                  Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Jonas Smedegaard <jonas@jones.dk> - 2019-05-28 10:00 +0200
                                  Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2019-05-28 18:00 +0200
                                    Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Curt <curty@free.fr> - 2019-05-28 18:50 +0200
                                Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Gene Heskett <gheskett@shentel.net> - 2019-05-28 14:10 +0200
                                  Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Erik Christiansen <dvalin@internode.on.net> - 2019-05-28 14:40 +0200
                                    Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Gene Heskett <gheskett@shentel.net> - 2019-05-28 15:10 +0200
                                      Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Erik Christiansen <dvalin@internode.on.net> - 2019-05-28 15:50 +0200
                                        Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Gene Heskett <gheskett@shentel.net> - 2019-05-28 17:00 +0200
                                  Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-05-28 14:50 +0200
                      Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Gene Heskett <gheskett@shentel.net> - 2019-05-27 19:20 +0200
                    IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)) rhkramer@gmail.com - 2019-05-27 15:00 +0200
                      Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) <tomas@tuxteam.de> - 2019-05-27 15:20 +0200
                      Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)) Gene Heskett <gheskett@shentel.net> - 2019-05-27 20:20 +0200
                        Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) Reco <recoverym4n@enotuniq.net> - 2019-05-27 21:30 +0200
                          Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)) Gene Heskett <gheskett@shentel.net> - 2019-05-27 23:10 +0200
                            Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) <tomas@tuxteam.de> - 2019-05-28 06:40 +0200
                            Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) Reco <recoverym4n@enotuniq.net> - 2019-05-28 07:50 +0200
                              Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)) Gene Heskett <gheskett@shentel.net> - 2019-05-28 14:40 +0200
                                Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's  church (Was Re: forcedeth?)) Dan Purgert <dan@djph.net> - 2019-05-28 15:00 +0200
                                  Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)) Gene Heskett <gheskett@shentel.net> - 2019-05-28 15:10 +0200
                                Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) Reco <recoverym4n@enotuniq.net> - 2019-05-28 15:10 +0200
                                Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) Greg Wooledge <wooledg@eeg.ccf.org> - 2019-05-28 15:40 +0200
                                  Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)) Gene Heskett <gheskett@shentel.net> - 2019-05-28 16:30 +0200
                            Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) Erik Christiansen <dvalin@internode.on.net> - 2019-05-28 13:10 +0200
                              Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) <tomas@tuxteam.de> - 2019-05-28 15:00 +0200
                                Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) <tomas@tuxteam.de> - 2019-05-28 15:30 +0200
                                  Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)) Gene Heskett <gheskett@shentel.net> - 2019-05-28 16:00 +0200
                                    Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) <tomas@tuxteam.de> - 2019-05-28 16:50 +0200
                                Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)) Gene Heskett <gheskett@shentel.net> - 2019-05-28 15:30 +0200
                                Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) Erik Christiansen <dvalin@internode.on.net> - 2019-05-28 15:40 +0200
                                  Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)) Gene Heskett <gheskett@shentel.net> - 2019-05-28 16:20 +0200
                              Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)) Gene Heskett <gheskett@shentel.net> - 2019-05-28 15:00 +0200
                      Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's  church (Was Re: forcedeth?)) Dan Purgert <dan@djph.net> - 2019-05-28 03:00 +0200
              Re: forcedeth? rhkramer@gmail.com - 2019-05-25 18:40 +0200
                Re: forcedeth? Gene Heskett <gheskett@shentel.net> - 2019-05-25 19:10 +0200

Page 2 of 4 — ← Prev page 1 [2] 3 4  Next page →


#209244 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromJimmy Johnson <field.engineer@gmail.com>
Date2019-05-27 19:30 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2rBD-8bH-1@gated-at.bofh.it>
In reply to#209213
On 05/27/2019 01:51 AM, Jonas Smedegaard wrote:
> Quoting Curt (2019-05-27 09:46:00)
>> On 2019-05-27, <tomas@tuxteam.de> <tomas@tuxteam.de> wrote:
>>> If Network Manager is giving you grief, please go bark up /that/
>>> tree (I can't say much about N-M, because I banned it from my boxes
>>> about ten years ago: I was at a customer's, in his LAN via an
>>> Ethernet, when N-M suddenly saw a WLAN out there, out the window and
>>> said "oh, let's go online over there" and obliterated my network
>>> setting in favor of some seedy captive portal. That was when I
>>> decided that N-M and me, we aren't made for each other).
>>>
>>
>> This is a grave bug. I suppose we can assume from your description
>> that the seedier the wifi portal, the more likely it is to
>> spontaneously occur, despite any and all user configuration or
>> intervention.
>>
>> Would it be possible to post the link to your bug report? To your
>> knowledge has the bug been fixed since you reported it a decade ago?
>> As many users here including myself rely on the N-M app, I'm sure we
>> would all be interested in knowing where we stand.
> 
> I fully agree, this is a quite scary and severe bug in network-manager
> that I want to inspect closer as Debian Developer.
> 
> Please do share information about where it was reported to I can follow
> up on it.  I sincerely hope that it has not gone unfixed through these
> many years!!!


Who needs it and what for?

Why is NetworkManager installed?
-- 
Jimmy Johnson

14.2 - KDE - AMD A8-7600 - EXT4 at sda9 - Registered Linux User #380263

[toc] | [prev] | [next] | [standalone]


#209245 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromJimmy Johnson <field.engineer@gmail.com>
Date2019-05-27 19:30 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2rBD-8bH-7@gated-at.bofh.it>
In reply to#209209
On 05/27/2019 12:46 AM, Curt wrote:
> On 2019-05-27, <tomas@tuxteam.de> <tomas@tuxteam.de> wrote:
>>
>>
>> If Network Manager is giving you grief, please go bark up /that/ tree
>> (I can't say much about N-M, because I banned it from my boxes about
>> ten years ago: I was at a customer's, in his LAN via an Ethernet, when
>> N-M suddenly saw a WLAN out there, out the window and said "oh, let's
>> go online over there" and obliterated my network setting in favor of
>> some seedy captive portal. That was when I decided that N-M and me,
>> we aren't made for each other).
>>
> 
> This is a grave bug. I suppose we can assume from your description that
> the seedier the wifi portal, the more likely it is to spontaneously
> occur, despite any and all user configuration or intervention.
> 
> Would it be possible to post the link to your bug report? To your
> knowledge has the bug been fixed since you reported it a decade ago?  As
> many users here including myself rely on the N-M app, I'm sure we would
> all be interested in knowing where we stand.


Who needs NetworkManager and why?

Thanks,
-- 
Jimmy Johnson

14.2 - KDE - AMD A8-7600 - EXT4 at sda9 - Registered Linux User #380263

[toc] | [prev] | [next] | [standalone]


#209260 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromBrian <ad44@cityscape.co.uk>
Date2019-05-27 22:00 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2tWO-15y-9@gated-at.bofh.it>
In reply to#209245
On Mon 27 May 2019 at 10:19:45 -0700, Jimmy Johnson wrote:

> On 05/27/2019 12:46 AM, Curt wrote:
> > On 2019-05-27, <tomas@tuxteam.de> <tomas@tuxteam.de> wrote:
> > > 
> > > 
> > > If Network Manager is giving you grief, please go bark up /that/ tree
> > > (I can't say much about N-M, because I banned it from my boxes about
> > > ten years ago: I was at a customer's, in his LAN via an Ethernet, when
> > > N-M suddenly saw a WLAN out there, out the window and said "oh, let's
> > > go online over there" and obliterated my network setting in favor of
> > > some seedy captive portal. That was when I decided that N-M and me,
> > > we aren't made for each other).
> > > 
> > 
> > This is a grave bug. I suppose we can assume from your description that
> > the seedier the wifi portal, the more likely it is to spontaneously
> > occur, despite any and all user configuration or intervention.
> > 
> > Would it be possible to post the link to your bug report? To your
> > knowledge has the bug been fixed since you reported it a decade ago?  As
> > many users here including myself rely on the N-M app, I'm sure we would
> > all be interested in knowing where we stand.
> 
> Who needs NetworkManager and why?

Curt's query was concise and to the point. You are obviously unable
to respond to it in a manner which advances the discusion. Hence your
pathetic attempt at topic divergence.

Please try to read and respond sympathetically to the posts in -user.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]


#209283 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromJimmy Johnson <field.engineer@gmail.com>
Date2019-05-28 08:40 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2DW9-7xW-1@gated-at.bofh.it>
In reply to#209260
On 05/27/2019 12:54 PM, Brian wrote:
> On Mon 27 May 2019 at 10:19:45 -0700, Jimmy Johnson wrote:
> 
>> On 05/27/2019 12:46 AM, Curt wrote:
>>> On 2019-05-27, <tomas@tuxteam.de> <tomas@tuxteam.de> wrote:
>>>>
>>>>
>>>> If Network Manager is giving you grief, please go bark up /that/ tree
>>>> (I can't say much about N-M, because I banned it from my boxes about
>>>> ten years ago: I was at a customer's, in his LAN via an Ethernet, when
>>>> N-M suddenly saw a WLAN out there, out the window and said "oh, let's
>>>> go online over there" and obliterated my network setting in favor of
>>>> some seedy captive portal. That was when I decided that N-M and me,
>>>> we aren't made for each other).
>>>>
>>>
>>> This is a grave bug. I suppose we can assume from your description that
>>> the seedier the wifi portal, the more likely it is to spontaneously
>>> occur, despite any and all user configuration or intervention.
>>>
>>> Would it be possible to post the link to your bug report? To your
>>> knowledge has the bug been fixed since you reported it a decade ago?  As
>>> many users here including myself rely on the N-M app, I'm sure we would
>>> all be interested in knowing where we stand.
>>
>> Who needs NetworkManager and why?
> 
> Curt's query was concise and to the point. You are obviously unable
> to respond to it in a manner which advances the discusion. Hence your
> pathetic attempt at topic divergence.
> 
> Please try to read and respond sympathetically to the posts in -user.


No, seriously I would like to get some user feedback to the question.
And also why is net-tools being deprecated?
-- 
Jimmy Johnson

14.2 - KDE - AMD A8-7600 - EXT4 at sda9 - Registered Linux User #380263

[toc] | [prev] | [next] | [standalone]


#209295 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromErik Christiansen <dvalin@internode.on.net>
Date2019-05-28 13:20 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2Ij7-1U6-7@gated-at.bofh.it>
In reply to#209283
On 27.05.19 23:32, Jimmy Johnson wrote:
> No, seriously I would like to get some user feedback to the question.
> And also why is net-tools being deprecated?

It's not. You and I fully approve of it, so it's fine for the use cases
in which it gives the desired results. (See ifconfig use on this thread.)

It's Network-Munger which I have had to deprecate right off my machines
in the past, in order to get static networking running. 

If I were Gene, I'd blow it away first, ask questions afterwards. But
that's just my experience. His WV mountain gremlins might have placed
other obstacles, but one less can only help in this case.

Erik

[toc] | [prev] | [next] | [standalone]


#209248 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromGene Heskett <gheskett@shentel.net>
Date2019-05-27 19:50 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2rV0-8iI-3@gated-at.bofh.it>
In reply to#209209
On Monday 27 May 2019 03:46:00 am Curt wrote:

> On 2019-05-27, <tomas@tuxteam.de> <tomas@tuxteam.de> wrote:
> > If Network Manager is giving you grief, please go bark up /that/
> > tree (I can't say much about N-M, because I banned it from my boxes
> > about ten years ago: I was at a customer's, in his LAN via an
> > Ethernet, when N-M suddenly saw a WLAN out there, out the window and
> > said "oh, let's go online over there" and obliterated my network
> > setting in favor of some seedy captive portal. That was when I
> > decided that N-M and me, we aren't made for each other).
>
> This is a grave bug. I suppose we can assume from your description
> that the seedier the wifi portal, the more likely it is to
> spontaneously occur, despite any and all user configuration or
> intervention.

This would appear to be more common, but as far as filing a bug report, I 
logged in to do something in 2015, creating a new account at the time, 
so now it refuses to let me in because the username content rules have 
been changed and my username is now invalid.  And because it knows my 
email address, it won't let me create a new account. So its the classic 
chicken v egg. I am locked out, so I rant on this list.

So if your are scanning the bugs looking for my submissions, taint gonna 
happen. I have emailed admin and postmaster to ask that my account be 
expunged so I can create a new one, but like most such emails its been 
dumped to /dev/null, or at least ignored. I never got a bounce msg.  

Those bounces I do get are because my ISP's spam filtering is a hell of a 
lot better than bendels. I have looked at the message bendel claimed was 
bounced, and with an exception in the last since wheezy time scale, 
every one of those bounced messages were spam/phishing. So my isp 
bounces it, and then I get a msg threatening to unsub me from bendel.

We've also had this discussion several times since 2015. Fix it so I can 
file a bug report, and you will get bug reports.  Till then.......
>
> Would it be possible to post the link to your bug report? To your
> knowledge has the bug been fixed since you reported it a decade ago? 
> As many users here including myself rely on the N-M app, I'm sure we
> would all be interested in knowing where we stand.


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)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]


#209257 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromBrian <ad44@cityscape.co.uk>
Date2019-05-27 21:30 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2ttM-Uq-7@gated-at.bofh.it>
In reply to#209248
On Mon 27 May 2019 at 13:42:46 -0400, Gene Heskett wrote:

> On Monday 27 May 2019 03:46:00 am Curt wrote:
> 
> > On 2019-05-27, <tomas@tuxteam.de> <tomas@tuxteam.de> wrote:
> > > If Network Manager is giving you grief, please go bark up /that/
> > > tree (I can't say much about N-M, because I banned it from my boxes
> > > about ten years ago: I was at a customer's, in his LAN via an
> > > Ethernet, when N-M suddenly saw a WLAN out there, out the window and
> > > said "oh, let's go online over there" and obliterated my network
> > > setting in favor of some seedy captive portal. That was when I
> > > decided that N-M and me, we aren't made for each other).
> >
> > This is a grave bug. I suppose we can assume from your description
> > that the seedier the wifi portal, the more likely it is to
> > spontaneously occur, despite any and all user configuration or
> > intervention.
> 
> This would appear to be more common, but as far as filing a bug report, I 
> logged in to do something in 2015, creating a new account at the time, 
> so now it refuses to let me in because the username content rules have 
> been changed and my username is now invalid.  And because it knows my 
> email address, it won't let me create a new account. So its the classic 
> chicken v egg. I am locked out, so I rant on this list.

Let's get this totally straight. Whatever you logged into was not the
BTS. No account needs to be set up to report a bug. You can rant as much
as you want, but whatever you did is now unknown and it is extremely
doubtful you can supply details.

And, to make it clear - the BTS is open to anyone without setting up an
account. Please do not downplay the importance of this when it comes to
user involvement. Chicken and eggs have nothing to do with it; your
vague, FUDDY stuff does a disservice to yourself and Debian.

> So if your are scanning the bugs looking for my submissions, taint gonna 
> happen. I have emailed admin and postmaster to ask that my account be 
> expunged so I can create a new one, but like most such emails its been 
> dumped to /dev/null, or at least ignored. I never got a bounce msg.

What account?
> 
> Those bounces I do get are because my ISP's spam filtering is a hell of a 
> lot better than bendels. I have looked at the message bendel claimed was 
> bounced, and with an exception in the last since wheezy time scale, 
> every one of those bounced messages were spam/phishing. So my isp 
> bounces it, and then I get a msg threatening to unsub me from bendel.

Totally irrelevant.

> We've also had this discussion several times since 2015. Fix it so I can 
> file a bug report, and you will get bug reports.  Till then.......

Nothing on the Debian side needs to be fixed. We have tried to fix users
but some are unfixable. :)

-- 
Brian

[toc] | [prev] | [next] | [standalone]


#209262 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromGene Heskett <gheskett@shentel.net>
Date2019-05-27 23:30 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2vlT-26a-1@gated-at.bofh.it>
In reply to#209257
On Monday 27 May 2019 03:25:21 pm Brian wrote:

> On Mon 27 May 2019 at 13:42:46 -0400, Gene Heskett wrote:
> > On Monday 27 May 2019 03:46:00 am Curt wrote:
> > > On 2019-05-27, <tomas@tuxteam.de> <tomas@tuxteam.de> wrote:
> > > > If Network Manager is giving you grief, please go bark up /that/
> > > > tree (I can't say much about N-M, because I banned it from my
> > > > boxes about ten years ago: I was at a customer's, in his LAN via
> > > > an Ethernet, when N-M suddenly saw a WLAN out there, out the
> > > > window and said "oh, let's go online over there" and obliterated
> > > > my network setting in favor of some seedy captive portal. That
> > > > was when I decided that N-M and me, we aren't made for each
> > > > other).
> > >
> > > This is a grave bug. I suppose we can assume from your description
> > > that the seedier the wifi portal, the more likely it is to
> > > spontaneously occur, despite any and all user configuration or
> > > intervention.
> >
> > This would appear to be more common, but as far as filing a bug
> > report, I logged in to do something in 2015, creating a new account
> > at the time, so now it refuses to let me in because the username
> > content rules have been changed and my username is now invalid.  And
> > because it knows my email address, it won't let me create a new
> > account. So its the classic chicken v egg. I am locked out, so I
> > rant on this list.
>
> Let's get this totally straight. Whatever you logged into was not the
> BTS. No account needs to be set up to report a bug. You can rant as
> much as you want, but whatever you did is now unknown and it is
> extremely doubtful you can supply details.

Then what was I looking at 3 hours ago, looked like a login form to me, 
wanted my username, my real name and my email address. That popped up 
and denied me access when I clicked on add bug in the upper right corner 
of the screen? It flat refused to let me proceed without a valid login.  
Yet you're telling me it should sail right on by just by clicking on the 
add button?

One of us is full of it.

I'd much rather believe your ethernet chips MAC is your passwd because 
you've told it to keep you logged in.

But I am all for hammering on this till it does work...

> And, to make it clear - the BTS is open to anyone without setting up
> an account. Please do not downplay the importance of this when it
> comes to user involvement. Chicken and eggs have nothing to do with
> it; your vague, FUDDY stuff does a disservice to yourself and Debian.

It denied me access. So what the heck am I supposed to do next?  I'm all 
ears.

> > So if your are scanning the bugs looking for my submissions, taint
> > gonna happen. I have emailed admin and postmaster to ask that my
> > account be expunged so I can create a new one, but like most such
> > emails its been dumped to /dev/null, or at least ignored. I never
> > got a bounce msg.
>
> What account?
>
> > Those bounces I do get are because my ISP's spam filtering is a hell
> > of a lot better than bendels. I have looked at the message bendel
> > claimed was bounced, and with an exception in the last since wheezy
> > time scale, every one of those bounced messages were spam/phishing.
> > So my isp bounces it, and then I get a msg threatening to unsub me
> > from bendel.
>
> Totally irrelevant.
>
> > We've also had this discussion several times since 2015. Fix it so I
> > can file a bug report, and you will get bug reports.  Till
> > then.......
>
> Nothing on the Debian side needs to be fixed. We have tried to fix
> users but some are unfixable. :)


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)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]


#209266 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromBrian <ad44@cityscape.co.uk>
Date2019-05-28 00:50 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2wBj-2NI-1@gated-at.bofh.it>
In reply to#209262
On Mon 27 May 2019 at 17:22:30 -0400, Gene Heskett wrote:

> On Monday 27 May 2019 03:25:21 pm Brian wrote:
> 
> > On Mon 27 May 2019 at 13:42:46 -0400, Gene Heskett wrote:
> > > On Monday 27 May 2019 03:46:00 am Curt wrote:
> > > > On 2019-05-27, <tomas@tuxteam.de> <tomas@tuxteam.de> wrote:
> > > > > If Network Manager is giving you grief, please go bark up /that/
> > > > > tree (I can't say much about N-M, because I banned it from my
> > > > > boxes about ten years ago: I was at a customer's, in his LAN via
> > > > > an Ethernet, when N-M suddenly saw a WLAN out there, out the
> > > > > window and said "oh, let's go online over there" and obliterated
> > > > > my network setting in favor of some seedy captive portal. That
> > > > > was when I decided that N-M and me, we aren't made for each
> > > > > other).
> > > >
> > > > This is a grave bug. I suppose we can assume from your description
> > > > that the seedier the wifi portal, the more likely it is to
> > > > spontaneously occur, despite any and all user configuration or
> > > > intervention.
> > >
> > > This would appear to be more common, but as far as filing a bug
> > > report, I logged in to do something in 2015, creating a new account
> > > at the time, so now it refuses to let me in because the username
> > > content rules have been changed and my username is now invalid.  And
> > > because it knows my email address, it won't let me create a new
> > > account. So its the classic chicken v egg. I am locked out, so I
> > > rant on this list.
> >
> > Let's get this totally straight. Whatever you logged into was not the
> > BTS. No account needs to be set up to report a bug. You can rant as
> > much as you want, but whatever you did is now unknown and it is
> > extremely doubtful you can supply details.
> 
> Then what was I looking at 3 hours ago, looked like a login form to me, 
> wanted my username, my real name and my email address. That popped up 
> and denied me access when I clicked on add bug in the upper right corner 
> of the screen? It flat refused to let me proceed without a valid login.  
> Yet you're telling me it should sail right on by just by clicking on the 
> add button?

You know the pack drill. Give a link to what you were looking at.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]


#209270 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromGene Heskett <gheskett@shentel.net>
Date2019-05-28 04:50 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2Alz-5cE-1@gated-at.bofh.it>
In reply to#209266
On Monday 27 May 2019 06:45:42 pm Brian wrote:

> On Mon 27 May 2019 at 17:22:30 -0400, Gene Heskett wrote:
> > On Monday 27 May 2019 03:25:21 pm Brian wrote:
> > > On Mon 27 May 2019 at 13:42:46 -0400, Gene Heskett wrote:
> > > > On Monday 27 May 2019 03:46:00 am Curt wrote:
> > > > > On 2019-05-27, <tomas@tuxteam.de> <tomas@tuxteam.de> wrote:
> > > > > > If Network Manager is giving you grief, please go bark up
> > > > > > /that/ tree (I can't say much about N-M, because I banned it
> > > > > > from my boxes about ten years ago: I was at a customer's, in
> > > > > > his LAN via an Ethernet, when N-M suddenly saw a WLAN out
> > > > > > there, out the window and said "oh, let's go online over
> > > > > > there" and obliterated my network setting in favor of some
> > > > > > seedy captive portal. That was when I decided that N-M and
> > > > > > me, we aren't made for each other).
> > > > >
> > > > > This is a grave bug. I suppose we can assume from your
> > > > > description that the seedier the wifi portal, the more likely
> > > > > it is to spontaneously occur, despite any and all user
> > > > > configuration or intervention.
> > > >
> > > > This would appear to be more common, but as far as filing a bug
> > > > report, I logged in to do something in 2015, creating a new
> > > > account at the time, so now it refuses to let me in because the
> > > > username content rules have been changed and my username is now
> > > > invalid.  And because it knows my email address, it won't let me
> > > > create a new account. So its the classic chicken v egg. I am
> > > > locked out, so I rant on this list.
> > >
> > > Let's get this totally straight. Whatever you logged into was not
> > > the BTS. No account needs to be set up to report a bug. You can
> > > rant as much as you want, but whatever you did is now unknown and
> > > it is extremely doubtful you can supply details.
> >
> > Then what was I looking at 3 hours ago, looked like a login form to
> > me, wanted my username, my real name and my email address. That
> > popped up and denied me access when I clicked on add bug in the
> > upper right corner of the screen? It flat refused to let me proceed
> > without a valid login. Yet you're telling me it should sail right on
> > by just by clicking on the add button?
>
> You know the pack drill. Give a link to what you were looking at.

The link came from a post to this list, 2 or so days back.  And my 
plastic eyes are fogging up from lack of sleep, so I am not going to try 
to find it yet tonight.

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)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]


#209272 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

Frommick crane <mick.crane@gmail.com>
Date2019-05-28 05:10 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2AEV-5yK-1@gated-at.bofh.it>
In reply to#209262
On 2019-05-27 22:22, Gene Heskett wrote:

> Then what was I looking at 3 hours ago, looked like a login form to me,
> wanted my username, my real name and my email address. That popped up
> and denied me access when I clicked on add bug in the upper right 
> corner
> of the screen? It flat refused to let me proceed without a valid login.
> Yet you're telling me it should sail right on by just by clicking on 
> the
> add button?
> 

This might be an issue with your browser.

mick

-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]


#209259 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromJonas Smedegaard <jonas@jones.dk>
Date2019-05-27 21:50 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2tN7-11M-1@gated-at.bofh.it>
In reply to#209248

[Multipart message — attachments visible in raw view] — view raw

Quoting Gene Heskett (2019-05-27 19:42:46)
> On Monday 27 May 2019 03:46:00 am Curt wrote:
> 
> > On 2019-05-27, <tomas@tuxteam.de> <tomas@tuxteam.de> wrote:
> > > If Network Manager is giving you grief, please go bark up /that/ 
> > > tree (I can't say much about N-M, because I banned it from my 
> > > boxes about ten years ago: I was at a customer's, in his LAN via 
> > > an Ethernet, when N-M suddenly saw a WLAN out there, out the 
> > > window and said "oh, let's go online over there" and obliterated 
> > > my network setting in favor of some seedy captive portal. That was 
> > > when I decided that N-M and me, we aren't made for each other).
> >
> > This is a grave bug. I suppose we can assume from your description 
> > that the seedier the wifi portal, the more likely it is to 
> > spontaneously occur, despite any and all user configuration or 
> > intervention.
> 
> This would appear to be more common, but as far as filing a bug 
> report, I logged in to do something in 2015, creating a new account at 
> the time, so now it refuses to let me in because the username content 
> rules have been changed and my username is now invalid.  And because 
> it knows my email address, it won't let me create a new account. So 
> its the classic chicken v egg. I am locked out, so I rant on this 
> list.

Account? You need no account to report bugs in Debian: 
https://www.debian.org/Bugs/Reporting


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

[toc] | [prev] | [next] | [standalone]


#209265 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromGene Heskett <gheskett@shentel.net>
Date2019-05-28 00:20 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2w8h-2Dm-1@gated-at.bofh.it>
In reply to#209259
On Monday 27 May 2019 03:42:52 pm Jonas Smedegaard wrote:

> Quoting Gene Heskett (2019-05-27 19:42:46)
>
> > On Monday 27 May 2019 03:46:00 am Curt wrote:
> > > On 2019-05-27, <tomas@tuxteam.de> <tomas@tuxteam.de> wrote:
> > > > If Network Manager is giving you grief, please go bark up /that/
> > > > tree (I can't say much about N-M, because I banned it from my
> > > > boxes about ten years ago: I was at a customer's, in his LAN via
> > > > an Ethernet, when N-M suddenly saw a WLAN out there, out the
> > > > window and said "oh, let's go online over there" and obliterated
> > > > my network setting in favor of some seedy captive portal. That
> > > > was when I decided that N-M and me, we aren't made for each
> > > > other).
> > >
> > > This is a grave bug. I suppose we can assume from your description
> > > that the seedier the wifi portal, the more likely it is to
> > > spontaneously occur, despite any and all user configuration or
> > > intervention.
> >
> > This would appear to be more common, but as far as filing a bug
> > report, I logged in to do something in 2015, creating a new account
> > at the time, so now it refuses to let me in because the username
> > content rules have been changed and my username is now invalid.  And
> > because it knows my email address, it won't let me create a new
> > account. So its the classic chicken v egg. I am locked out, so I
> > rant on this list.
>
> Account? You need no account to report bugs in Debian:
> https://www.debian.org/Bugs/Reporting
>
So that indicates I should have apt install reportbug, so I did. 
Configured it on 1st run. then became me and ran it again.  It never 
heard of NetworkManager or Network-Manager.  WTH?
>
>  - Jonas


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)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]


#209274 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromJoe Pfeiffer <pfeiffer@cs.nmsu.edu>
Date2019-05-28 05:40 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2B7X-5Jg-5@gated-at.bofh.it>
In reply to#209265
Gene Heskett <gheskett@shentel.net> writes:

> On Monday 27 May 2019 03:42:52 pm Jonas Smedegaard wrote:
>
>> Quoting Gene Heskett (2019-05-27 19:42:46)
>>
>> > On Monday 27 May 2019 03:46:00 am Curt wrote:
>> > > On 2019-05-27, <tomas@tuxteam.de> <tomas@tuxteam.de> wrote:
>> > > > If Network Manager is giving you grief, please go bark up /that/
>> > > > tree (I can't say much about N-M, because I banned it from my
>> > > > boxes about ten years ago: I was at a customer's, in his LAN via
>> > > > an Ethernet, when N-M suddenly saw a WLAN out there, out the
>> > > > window and said "oh, let's go online over there" and obliterated
>> > > > my network setting in favor of some seedy captive portal. That
>> > > > was when I decided that N-M and me, we aren't made for each
>> > > > other).
>> > >
>> > > This is a grave bug. I suppose we can assume from your description
>> > > that the seedier the wifi portal, the more likely it is to
>> > > spontaneously occur, despite any and all user configuration or
>> > > intervention.
>> >
>> > This would appear to be more common, but as far as filing a bug
>> > report, I logged in to do something in 2015, creating a new account
>> > at the time, so now it refuses to let me in because the username
>> > content rules have been changed and my username is now invalid.  And
>> > because it knows my email address, it won't let me create a new
>> > account. So its the classic chicken v egg. I am locked out, so I
>> > rant on this list.
>>
>> Account? You need no account to report bugs in Debian:
>> https://www.debian.org/Bugs/Reporting
>>
> So that indicates I should have apt install reportbug, so I did. 
> Configured it on 1st run. then became me and ran it again.  It never 
> heard of NetworkManager or Network-Manager.  WTH?

Debian package names are all lower case, and for better or worse the
package management software is case-sensitive.

snowball:532$ reportbug
Please enter the name of the package in which you have found a problem, or type 'other' to report a more general problem. If you don't know what package the bug is in, please contact debian-user@lists.debian.org for
assistance.
> network-manager
*** Welcome to reportbug.  Use ? for help at prompts. ***
Note: bug reports are publicly archived (including the email address of the submitter).
Detected character set: UTF-8
Please change your locale if this is incorrect.

Using 'Joe Pfeiffer <joseph@pfeifferfamily.net>' as your from address.
Getting status for network-manager...
Checking for newer versions at madison...

Your version (1.14.6-2) of network-manager appears to be out of date.
The following newer release(s) are available in the Debian archive:
  experimental: 1.18.0-1
Please try to verify if the bug you are about to report is already addressed by these releases.  Do you still want to file a report [y|N|q|?]? 

(at which point I entered a ^C since I didn't actually want to report a
bug)

[toc] | [prev] | [next] | [standalone]


#209286 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromCurt <curty@free.fr>
Date2019-05-28 09:50 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2F1T-8bE-3@gated-at.bofh.it>
In reply to#209274
On 2019-05-28, Joe Pfeiffer <pfeiffer@cs.nmsu.edu> wrote:

>   experimental: 1.18.0-1
> Please try to verify if the bug you are about to report is already addressed by these releases.  Do you still want to file a report [y|N|q|?]? 

Think I might've entered 'q' here on the off chance it represented the word
quit. Maybe it means "'q'ueue the report for further reflection," though.

;-)

> (at which point I entered a ^C since I didn't actually want to report a
> bug)
>

'N' also seems a reasonable alternative. 'y' is first in line, but 'N'
is upper case, and there must be a reason for that, so I'm thinking if
you just hit enter the default would be to do nothing (no).

On a more serious note, as exim is set up to deliver only local mail on
many machines (default installation), what happens when you cannot hand
your bug report over to a sendmail-like MTA?

-- 
“Decisions are never really made – at best they manage to emerge, from a chaos
of peeves, whims, hallucinations and all around assholery.” – Thomas Pynchon

[toc] | [prev] | [next] | [standalone]


#209287 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromReco <recoverym4n@enotuniq.net>
Date2019-05-28 10:00 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2FbA-8fe-3@gated-at.bofh.it>
In reply to#209286
	Hi.

On Tue, May 28, 2019 at 07:47:36AM -0000, Curt wrote:
> On a more serious note, as exim is set up to deliver only local mail on
> many machines (default installation), what happens when you cannot hand
> your bug report over to a sendmail-like MTA?

The expected thing happens.
Your exim tries to send an e-mail to submit@bugs.debian.org, discovers
that it's disallowed to do so, and sends that 'Unable to deliver' e-mail
back to the user who has run reportbug.
Reportbug also sends the same e-mail to the user who run it, so at least
you have your bugreport verbatim.

Reco

[toc] | [prev] | [next] | [standalone]


#209291 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

From<tomas@tuxteam.de>
Date2019-05-28 10:50 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2FXX-jW-5@gated-at.bofh.it>
In reply to#209287

[Multipart message — attachments visible in raw view] — view raw

On Tue, May 28, 2019 at 10:59:41AM +0300, Reco wrote:
> 	Hi.
> 
> On Tue, May 28, 2019 at 07:47:36AM -0000, Curt wrote:
> > On a more serious note, as exim is set up to deliver only local mail on
> > many machines (default installation), what happens when you cannot hand
> > your bug report over to a sendmail-like MTA?
> 
> The expected thing happens.
> Your exim tries to send an e-mail to submit@bugs.debian.org [...]

See also the -o <file> option, which guides reportbug to dump its
output to <file> so you can mail it later with whatever method
you send out mails. Alternatively, the -M <mta> options, which lets
you choose the MTA via which you want to send mail. And others.

It's all in the man page...

cheers

"If everything else fails, check the instructions"

-- tomás

[toc] | [prev] | [next] | [standalone]


#209288 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromJonas Smedegaard <jonas@jones.dk>
Date2019-05-28 10:00 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2FbA-8fe-1@gated-at.bofh.it>
In reply to#209286

[Multipart message — attachments visible in raw view] — view raw

Quoting Curt (2019-05-28 09:47:36)
> On 2019-05-28, Joe Pfeiffer <pfeiffer@cs.nmsu.edu> wrote:
> 
> >   experimental: 1.18.0-1
> > Please try to verify if the bug you are about to report is already addressed by these releases.  Do you still want to file a report [y|N|q|?]? 
> 
> Think I might've entered 'q' here on the off chance it represented the word
> quit. Maybe it means "'q'ueue the report for further reflection," though.
> 
> ;-)
> 
> > (at which point I entered a ^C since I didn't actually want to report a
> > bug)
> >
> 
> 'N' also seems a reasonable alternative. 'y' is first in line, but 'N'
> is upper case, and there must be a reason for that, so I'm thinking if
> you just hit enter the default would be to do nothing (no).
> 
> On a more serious note, as exim is set up to deliver only local mail on
> many machines (default installation), what happens when you cannot hand
> your bug report over to a sendmail-like MTA?

First you actually _read_ https://www.debian.org/Bugs/Reporting and then 
if you are still lost you come back here and ask for help - skipping all 
the "funny" jokes that might discourage some from wanting to spend time 
on having a dialogue with you.



 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

[toc] | [prev] | [next] | [standalone]


#209321 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromJoe Pfeiffer <pfeiffer@cs.nmsu.edu>
Date2019-05-28 18:00 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2MG5-4um-1@gated-at.bofh.it>
In reply to#209286
Curt <curty@free.fr> writes:

> On 2019-05-28, Joe Pfeiffer <pfeiffer@cs.nmsu.edu> wrote:
>
>>   experimental: 1.18.0-1
>> Please try to verify if the bug you are about to report is already
>> addressed by these releases.  Do you still want to file a report
>> [y|N|q|?]?
>
> Think I might've entered 'q' here on the off chance it represented the word
> quit. Maybe it means "'q'ueue the report for further reflection," though.
>
> ;-)

No, it does mean 'quit'

>> (at which point I entered a ^C since I didn't actually want to report a
>> bug)
>>
>
> 'N' also seems a reasonable alternative. 'y' is first in line, but 'N'
> is upper case, and there must be a reason for that, so I'm thinking if
> you just hit enter the default would be to do nothing (no).

I don't remember...  I don't think I've ever taken the default option!

> On a more serious note, as exim is set up to deliver only local mail on
> many machines (default installation), what happens when you cannot hand
> your bug report over to a sendmail-like MTA?

The exim4 installation provides a symbolic link

snowball:558$ ls -l /usr/sbin/sendmail
lrwxrwxrwx 1 root root 5 May  7 11:44 /usr/sbin/sendmail -> exim4*

[toc] | [prev] | [next] | [standalone]


#209327 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromCurt <curty@free.fr>
Date2019-05-28 18:50 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2Nsu-51T-5@gated-at.bofh.it>
In reply to#209321
On 2019-05-28, Joe Pfeiffer <pfeiffer@cs.nmsu.edu> wrote:
>
> The exim4 installation provides a symbolic link
>
> snowball:558$ ls -l /usr/sbin/sendmail
> lrwxrwxrwx 1 root root 5 May  7 11:44 /usr/sbin/sendmail -> exim4*
>

Actually, the right way to configure reportbug on a local-mail-only system is
to "run the command reportbug --configure and answer “no” to the question
if an MTA is available. You will then be asked for the SMTP server to
be used for submitting bug reports."

https://www.debian.org/releases/stable/i386/ch08s05.html.en

[toc] | [prev] | [next] | [standalone]


Page 2 of 4 — ← Prev page 1 [2] 3 4  Next page →

Back to top | Article view | linux.debian.user


csiph-web