On 6/14/16, Jörg-Volker Peetz wrote:
> Richard Barmann wrote on 06/14/16 05:36:
>> About once a week when I boot up I find the clock is exactly 4 hours slow.
>> I am
>> using Kubuntu 16.04. If I am asking the question in the wrong place please
>> send
>> me to the correct forum.
>> Thank you.
>>
>
Richard Barmann wrote on 06/14/16 05:36:
> About once a week when I boot up I find the clock is exactly 4 hours slow. I
> am
> using Kubuntu 16.04. If I am asking the question in the wrong place please
> send
> me to the correct forum.
> Thank you.
>
The four hours seem to be related to your ti
Richard Barmann composed on 2016-06-13 23:36 (UTC-0400):
About once a week when I boot up I find the clock is exactly 4 hours
slow. I am using Kubuntu 16.04. If I am asking the question in the wrong
place please send me to the correct forum.
Kubuntu is not Debian, but is heavily Debian based,
On Mon, Jun 13, 2016 at 11:36:59PM -0400, Richard Barmann wrote:
> About once a week when I boot up I find the clock is exactly 4 hours slow. I
> am using Kubuntu 16.04. If I am asking the question in the wrong place
> please send me to the correct forum.
> Thank you.
Kubuntu has its own community
On Monday 13 June 2016 18:31:11 Ric Moore wrote:
> On 06/13/2016 04:09 PM, Erwan David wrote:
> > Le 13/06/2016 à 23:08, Doug a écrit :
> >> On 06/13/2016 02:36 PM, Nicolas George wrote:
> >>> Le sextidi 26 prairial, an CCXXIV, Bob Holtzman a écrit :
> >>
> >> /snip/
> >>
> >> Just what planet are
About once a week when I boot up I find the clock is exactly 4 hours
slow. I am using Kubuntu 16.04. If I am asking the question in the wrong
place please send me to the correct forum.
Thank you.
On Tue, Jun 14, 2016 at 2:17 AM Morten Bo Johansen wrote:
> On 2016-06-13 Nicolas George wrote:
>
> > As I already explained twice, a solution that requires a
> > different action when it is a mailing-list and when it is not
> > is not an acceptable solution.
>
> Why not? Don't you know when you
On Monday 13 June 2016 23:31:11 Ric Moore wrote:
> On 06/13/2016 04:09 PM, Erwan David wrote:
> > Le 13/06/2016 à 23:08, Doug a écrit :
> >> On 06/13/2016 02:36 PM, Nicolas George wrote:
> >>> Le sextidi 26 prairial, an CCXXIV, Bob Holtzman a écrit :
> >>
> >> /snip/
> >>
> >> Just what planet are
On Monday 13 June 2016 22:08:36 Doug wrote:
> On 06/13/2016 02:36 PM, Nicolas George wrote:
> > Le sextidi 26 prairial, an CCXXIV, Bob Holtzman a écrit :
>
> /snip/
>
> Just what planet are you writing from, Bob? I don't recognize the date
> at all.
It isn't Bob that put that date in - it's Nicol
On 06/13/2016 04:09 PM, Erwan David wrote:
Le 13/06/2016 à 23:08, Doug a écrit :
On 06/13/2016 02:36 PM, Nicolas George wrote:
Le sextidi 26 prairial, an CCXXIV, Bob Holtzman a écrit :
/snip/
Just what planet are you writing from, Bob? I don't recognize the
date at all.
Bob is across the
On Mon, 13 Jun 2016 19:57:08 +0200
Michael Lange wrote:
> Hi,
>
> I just encountered an odd problem with a repo hosted on sourceforge,
> when calling apt-get update with this repo enabled in the sources.list
> I ended with a 301 error. Apparently this happens because sourceforge
> dropped its ht
On Monday 13 June 2016 14:46:42 Lisi Reisz wrote:
> On Monday 13 June 2016 19:35:54 Gene Heskett wrote:
> > And I am not sure that this tempest in a teapot is all about, the
> > older kmail that I use and the older TBird that I have unwillingly
> > used way back up the logbook now, both have a rep
On Monday 13 June 2016 13:53:14 Thomas Schmitt wrote:
> Hi,
>
> > ++ /usr/bin/inotifywait -q -e close --format %f /var/spool/mail/
>
> From the man page i learn that you let it watch the whole directory.
> This way you get notifications about any file in there.
>
> The empty variable content possi
On 06/13/2016 12:43 PM, Lisi Reisz wrote:
But you manage it. You take the trouble.
I do because I've seen such whinage from people who get email to them.
All that goes into the archives. I don't like iMail's stupidity but
there's not a lot I can do if I want a light laptop on the bedside
t
Le 13/06/2016 à 23:08, Doug a écrit :
>
> On 06/13/2016 02:36 PM, Nicolas George wrote:
>> Le sextidi 26 prairial, an CCXXIV, Bob Holtzman a écrit :
>>
> /snip/
>
> Just what planet are you writing from, Bob? I don't recognize the
> date at all.
>
> --doug
>
>
That's french revolutionary calendar
On 06/13/2016 02:36 PM, Nicolas George wrote:
Le sextidi 26 prairial, an CCXXIV, Bob Holtzman a écrit :
/snip/
Just what planet are you writing from, Bob? I don't recognize the date
at all.
--doug
Le sextidi 26 prairial, an CCXXIV, Bob Holtzman a écrit :
> I have always found that when using mutt, as we both seem to do, "L"
> replys to a message and sends that reply to the list only.
For the last time: this command works only for mailing-lists, not for
private discussions, and therefore is
On 6/13/2016 12:36 PM, Nicolas George wrote:
> Let me try to re-state it one more time another way:
>
> A is annoyed by unwanted CCs and wants to make it stop.
>
> Solution 1: ask every people who reply to A, i.e. people who do not care
> about the unwanted CCs, to make a (moderate) effort witho
On Monday 13 June 2016 13:51:46 Lisi Reisz wrote:
> On Monday 13 June 2016 18:09:23 Nicolas George wrote:
> > Le sextidi 26 prairial, an CCXXIV, Lisi Reisz a écrit :
> > > So tell us how. You have not done so. You have said:
> > > -
> > > Conforming to that attitude,
On Monday 13 June 2016 19:35:50 Dutch Ingraham wrote:
> On Mon, Jun 13, 2016 at 06:51:46PM +0100, Lisi Reisz wrote:
> > On Monday 13 June 2016 18:09:23 Nicolas George wrote:
> > > Le sextidi 26 prairial, an CCXXIV, Lisi Reisz a écrit :
> >
> > meant to go to the mailing list. Any half way decent m
On Monday 13 June 2016 12:39:31 Lisi Reisz wrote:
> On Monday 13 June 2016 17:36:53 Nicolas George wrote:
> > Solution 2: A makes the moderate punctual effort to configure the
> > MUA to set the header correctly and directly reaps the benefits.
> >
> > Stated like that, it is pretty much a no-brai
On Monday 13 June 2016 19:35:54 Gene Heskett wrote:
> And I am not sure that this tempest in a teapot is all about, the older
> kmail that I use and the older TBird that I have unwillingly used way
> back up the logbook now, both have a reply-to-list button. This is a
> list and I use that button
On Monday 13 June 2016 19:24:43 ghe wrote:
> On 06/13/2016 10:48 AM, Martin Read wrote:
> > Solution 3: A makes the probably-smaller-per-incident effort to set up
> > filters dropping on the floor any mail sent by the people whose MUAs
> > have bad default behaviour on Debian mailing lists.
> >
> >
On Monday 13 June 2016 11:28:00 Cindy-Sue Causey wrote:
> On 6/13/16, Nicolas George wrote:
> > Le sextidi 26 prairial, an CCXXIV, Tanstaafl a écrit :
> >> This is why Reply-To-List is the way to reply when engaged in a
> >> mailing list.
> >>
> >> If your client doesn't have this, then maybe it
On Mon, Jun 13, 2016 at 06:51:46PM +0100, Lisi Reisz wrote:
> On Monday 13 June 2016 18:09:23 Nicolas George wrote:
> > Le sextidi 26 prairial, an CCXXIV, Lisi Reisz a écrit :
> meant to go to the mailing list. Any half way decent mail client can be
> configured to reply to a mailing list when re
On Monday 13 June 2016 10:08:33 David Wright wrote:
> On Mon 13 Jun 2016 at 10:19:46 (+0200), Thomas Schmitt wrote:
> > Gene Heskett wrote:
> > > if test ${InMail} = "gene"
> > > bin/mailwatcher: line 66: test: =: unary operator expected
> >
> > The syntax problem is most probably about missing "-
On 06/13/2016 10:48 AM, Martin Read wrote:
Solution 3: A makes the probably-smaller-per-incident effort to set up
filters dropping on the floor any mail sent by the people whose MUAs
have bad default behaviour on Debian mailing lists.
E-mail sent to the Debian mailing list contains sufficient i
Lisi writes:
> He is too important.
That's what killfiles are for.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
On Monday 13 June 2016 08:50:58 Jörg-Volker Peetz wrote:
> watch -d -n 1.5 ls -la /var/spool/mail/
Interesting tool, 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)
Ge
On Mon, Jun 13, 2016 at 05:42:40PM +0200, Nicolas George wrote:
snip...
>
>
> Mine do (and I have explained the procedure to achieve it), therefore I
> never receive unwanted CCs and I am perfectly happy about it. I guess some
> people like whining.
If yours do, you will ha
Hi,
I just encountered an odd problem with a repo hosted on sourceforge, when
calling apt-get update with this repo enabled in the sources.list I ended
with a 301 error. Apparently this happens because sourceforge dropped its
http service and now uses https exclusively. It took me a while to find
On Monday 13 June 2016 18:51:46 Bob Holtzman wrote:
> I suspect (maybe wrong) that you
> may be one of those individuals that wants to do it his/her way and the
> hell with the CoC. Like I said, maybe I'm wrong.
He has actually said that in so many words. He can't be bothered to follow
CoCs. He
Hi,
> ++ /usr/bin/inotifywait -q -e close --format %f /var/spool/mail/
>From the man page i learn that you let it watch the whole directory.
This way you get notifications about any file in there.
The empty variable content possibly stems from this feature:
"-format
...
%f
When an ev
On Monday 13 June 2016 18:09:23 Nicolas George wrote:
> Le sextidi 26 prairial, an CCXXIV, Lisi Reisz a écrit :
> > So tell us how. You have not done so. You have said:
> > -
> > Conforming to that attitude, I have documented my personal preferences in
> > the headers
On Monday 13 June 2016 06:34:00 Gene Heskett wrote:
> On Monday 13 June 2016 05:21:23 to...@tuxteam.de wrote:
> > On Mon, Jun 13, 2016 at 10:19:46AM +0200, Thomas Schmitt wrote:
> > > Hi,
> > >
> > > Gene Heskett wrote:
> > > > if test ${InMail} = "gene"
> > > > bin/mailwatcher: line 66: test: =:
On Monday 13 June 2016 06:30:39 Thomas Schmitt wrote:
> Hi,
>
> i wrote:
> > > Is ${InMail} supposed to be empty ?
It is not supposed to be. Empty only if I kill it with a killall in practice.
>
> Gene Heskett wrote:
> > That is set by inotifywait's return of the name of the file that
> > procma
On 2016-06-13 Nicolas George wrote:
> As I already explained twice, a solution that requires a
> different action when it is a mailing-list and when it is not
> is not an acceptable solution.
Why not? Don't you know when you are corresponding on a mailing
list or not? You only need to switch betw
Martin Read writes:
> Solution 3: A makes the probably-smaller-per-incident effort to set up
> filters dropping on the floor any mail sent by the people whose MUAs
> have bad default behaviour on Debian mailing lists.
Or to detect and drop duplicates whatever the cause.
--
John Hasler
jhas...@ne
Le sextidi 26 prairial, an CCXXIV, Lisi Reisz a écrit :
> So tell us how. You have not done so. You have said:
> -
> Conforming to that attitude, I have documented my personal preferences in
> the headers of the mails I send with the following Mutt rules:
>
> send-hoo
On 13/06/16 17:36, Nicolas George wrote:
Solution 1: ask every people who reply to A, i.e. people who do not care
about the unwanted CCs, to make a (moderate) effort without getting any
benefit for themselves.
Solution 2: A makes the moderate punctual effort to configure the MUA to set
the heade
Hi,
David Wright wrote:
> Thomas, your patience appears unbounded.
That's a character strength which a programmer must have
at least in part.
> https://lists.debian.org/debian-user/2016/04/msg00652.html
Yeah. I advised Gene to put "-quotes around variable evaluations.
Now we have the education
On Monday 13 June 2016 17:36:53 Nicolas George wrote:
> Solution 2: A makes the moderate punctual effort to configure the MUA to
> set the header correctly and directly reaps the benefits.
>
> Stated like that, it is pretty much a no-brainer.
Except that you are continuing to refuse to explain sol
Le sextidi 26 prairial, an CCXXIV, Morten Bo Johansen a écrit :
> Since you are using Mutt, all you need to do to be well behaved
> (i.e. not send personal CCs) is to hit 'L' when you reply
As I already explained twice, a solution that requires a different action
when it is a mailing-list and when
On Monday 13 June 2016 05:21:23 to...@tuxteam.de wrote:
> On Mon, Jun 13, 2016 at 10:19:46AM +0200, Thomas Schmitt wrote:
> > Hi,
> >
> > Gene Heskett wrote:
> > > if test ${InMail} = "gene"
> > > bin/mailwatcher: line 66: test: =: unary operator expected
> >
> > The syntax problem is most probabl
On Monday 13 June 2016 16:42:40 Nicolas George wrote:
> Mark Fletcher:
> > You know we are not talking about running a nuclear reactor here, right?
>
> What is your point?
>
> > But this only works if all participants agree to use such headers,
> > surely?
>
> No. The header I am referring to has b
On Monday 13 June 2016 16:12:57 Nicolas George wrote:
> I gave the technical solution and headers I use.
I asked what *I* needed to do, and how to do it, to avoid your replies. Not
what you do to insist on replying to me. As you say, you have told me. I
consider that one ought to "reply to li
On 6/13/2016 11:42 AM, John Hasler wrote:
> "Reply to List" needs to be enabled in the mailing list software.
Not precisely right - mailing list software only needs to add the
appropriate list headers defined by the relevant RFCs.
This list does (and so Reply-To-List works as it should).
> Thus
On 2016-06-13 Nicolas George wrote:
> Le quintidi 25 prairial, an CCXXIV, Lisi Reisz a écrit :
>> I expect you to conform to the CoC and not continue to reply to me
>> personally.
>
> Nobody can be expected to remember the personal preferences of each
> mailing-list member, nor the subscription s
Mark Fletcher:
> You know we are not talking about running a nuclear reactor here, right?
What is your point?
> But this only works if all participants agree to use such headers, surely?
No. The header I am referring to has been supported by all half-decent MUAs
for years, possibly decades, and
Mark Fletcher writes:
> Or does it need to be a feature of the machines hosting the list?
"Reply to List" needs to be enabled in the mailing list software. Thus
those who want it need to take the issue up with the list masters. In
the meantime, it's a feature this list does not have. Pretending
On 6/13/16, Nicolas George wrote:
> Le sextidi 26 prairial, an CCXXIV, Tanstaafl a écrit :
>> This is why Reply-To-List is the way to reply when engaged in a mailing
>> list.
>>
>> If your client doesn't have this, then maybe it is time to consider
>> changing.
>
> I am not sure what you are aimin
On 6/13/2016 11:12 AM, Nicolas George wrote:
> Le sextidi 26 prairial, an CCXXIV, Tanstaafl a écrit :
>> This is why Reply-To-List is the way to reply when engaged in a mailing
>> list.
>>
>> If your client doesn't have this, then maybe it is time to consider
>> changing.
> I am not sure what you
On Tue, Jun 14, 2016 at 12:13 AM Nicolas George wrote:
> Le sextidi 26 prairial, an CCXXIV, Tanstaafl a écrit :
>
> If you are referring to a MUA command, then first let me remind you that
> MUA
> commands are not standardized, and therefore using the name of the command
> on your particular MUA
Le sextidi 26 prairial, an CCXXIV, Tanstaafl a écrit :
> This is why Reply-To-List is the way to reply when engaged in a mailing
> list.
>
> If your client doesn't have this, then maybe it is time to consider
> changing.
I am not sure what you are aiming at. If "Reply-To-List" is supposed to be a
On 6/13/2016 5:57 AM, Nicolas George wrote:
> Nobody can be expected to remember the personal preferences of each
> mailing-list member,
This is why Reply-To-List is the way to reply when engaged in a mailing
list.
If your client doesn't have this, then maybe it is time to consider
changing.
On Monday 13 June 2016 15:17:19 Nicolas George wrote:
> Le sextidi 26 prairial, an CCXXIV, Lisi Reisz a écrit :
> > I appreciate that. Thank you. But it isn't just my personal
> > preferences, it is part of the CoC:
>
> And the mail headers state differently. Given contradictory directives, I
> e
On Mon 13 Jun 2016 at 05:17:42 (-0400), Gene Heskett wrote:
> On Monday 13 June 2016 04:19:46 Thomas Schmitt wrote:
>
> > Hi,
> >
> > Gene Heskett wrote:
> > > if test ${InMail} = "gene"
> > > bin/mailwatcher: line 66: test: =: unary operator expected
> >
> > The syntax problem is most probably ab
Le sextidi 26 prairial, an CCXXIV, Lisi Reisz a écrit :
> I appreciate that. Thank you. But it isn't just my personal preferences, it
> is part of the CoC:
And the mail headers state differently. Given contradictory directives, I
explained in my previous mail why the only sane solution is to ad
On Mon 13 Jun 2016 at 10:19:46 (+0200), Thomas Schmitt wrote:
> Gene Heskett wrote:
> > if test ${InMail} = "gene"
> > bin/mailwatcher: line 66: test: =: unary operator expected
>
> The syntax problem is most probably about missing "-quotes around
> the variable ecaluation ${InMail} which would ha
Gene Heskett wrote on 06/13/16 12:34:
> In any event a pair of "" around the left argument silenced the warning,
> and it still works. However it may be that inotifywait is premature, as
> I see that InMail occasionall contains a hash name of the order of:
> + test _KQG,TdoXXB.coyote = gene
> +
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Jun 13, 2016 at 09:34:06PM +0900, Byung-Hee HWANG (황병희) wrote:
> On 2016년 6월 13일 오후 8시 52분 49초 GMT+09:00, Lisi Reisz
> wrote:
> >On Monday 13 June 2016 10:57:05 Nicolas George wrote:
> >> [...]
> >"When replying to messages on the mailing lis
On Monday 13 June 2016 10:57:05 Nicolas George wrote:
> This time only, as a particular courtesy, I have edited manually the list
> of recipients to adhere to your personal preferences.
I appreciate that. Thank you. But it isn't just my personal preferences, it
is part of the CoC:
"When replyi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Jun 13, 2016 at 12:30:39PM +0200, Thomas Schmitt wrote:
> Hi,
[...]
> to...@tuxteam.de wrote:
> > One could argue "unary operator expected" is a strange way to
> > restate this.
>
> It's the way how the gild of land surveyors and bean counte
On Monday 13 June 2016 05:21:23 to...@tuxteam.de wrote:
> On Mon, Jun 13, 2016 at 10:19:46AM +0200, Thomas Schmitt wrote:
> > Hi,
> >
> > Gene Heskett wrote:
> > > if test ${InMail} = "gene"
> > > bin/mailwatcher: line 66: test: =: unary operator expected
> >
> > The syntax problem is most probabl
Hi,
i wrote:
> > Is ${InMail} supposed to be empty ?
Gene Heskett wrote:
> That is set by inotifywait's return of the name of the file that procmail
> just closed.
Hmm. I don't have inotifywait installed.
According to http://linux.die.net/man/1/inotifywait it should put out
lines like
CLOSE_
On 9 June 2016 at 19:27, Morten Bo Johansen wrote:
> On 2016-06-08 Johann Spies wrote:
>
>
> I use the following in ~/.mailcap:
>
> text/html; chromium %s;
> text/html; /usr/bin/elinks -force-html -dump %s; copiousoutput
>
> and in ~/.muttrc:
>
> bind attachview-mailcap
> alternative
Le quintidi 25 prairial, an CCXXIV, Lisi Reisz a écrit :
> I expect you to conform to the CoC and not continue to reply to me personally.
Nobody can be expected to remember the personal preferences of each
mailing-list member, nor the subscription status of all contributors, and
more importantly n
To avoid booting delay while DHCP tries to get an IP address, I decided
to use a static address for the wlan0 interface.
I tried this:
auto wlan0
iface wlan0 inet static
address 192.168.1.124
gateway 192.168.1.1
netmask 255.255.255.0
wireless-mode managed
wpa-ssid XXX
wap-psk XXX
Thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Jun 13, 2016 at 10:19:46AM +0200, Thomas Schmitt wrote:
> Hi,
>
> Gene Heskett wrote:
> > if test ${InMail} = "gene"
> > bin/mailwatcher: line 66: test: =: unary operator expected
>
> The syntax problem is most probably about missing "-quotes
On Monday 13 June 2016 04:19:46 Thomas Schmitt wrote:
> Hi,
>
> Gene Heskett wrote:
> > if test ${InMail} = "gene"
> > bin/mailwatcher: line 66: test: =: unary operator expected
>
> The syntax problem is most probably about missing "-quotes around
> the variable ecaluation ${InMail} which would ha
Hi,
Gene Heskett wrote:
> if test ${InMail} = "gene"
> bin/mailwatcher: line 66: test: =: unary operator expected
The syntax problem is most probably about missing "-quotes around
the variable ecaluation ${InMail} which would have to be empty to
cause the message:
$ test $notdefined = "hello w
Greetings bashers;
I have a set -x at the top of this script, and this line, while working
as expected:
if test ${InMail} = "gene"
also spits out this warning:
bin/mailwatcher: line 66: test: =: unary operator expected
What syntax correction does this need?
Thanks.
Cheers, Gene Heskett
--
"
Gene Heskett wrote:
> On Sunday 12 June 2016 17:21:10 Sven Hartge wrote:
>> egrep is in /bin/egrep and in the package grep. grep itself is
>> "Priority: required" so you can't not have this package. If you don't
>> have /bin/egrep, then your system is way more broken than you may
>> hope. Or "/bi
73 matches
Mail list logo
