On 23/07/2015 22:41, Peter Maloney wrote:
What's wrong with these, which Thunderbird handles just fine?
Ah, indeed it does, when the list address is in the To:
It does not when the list address is in the Cc:
So the solution is to make sure to always send To: the list. :)
Thanks for the noti
On 07/22/2015 10:41 PM, Laurent Bercot wrote:
> OT: I would like it if the list host could set the "Mailing-List:"
> header on list messages. Most MUAs understand it and implement a
> "reply to list" feature; without it, we're stuck with manual
> configuration
> or hitting "reply to all", which ca
On Wed, 22 Jul 2015 10:00:48 +0200, Oz Tiram wrote:
Please explain it to me with out flames. [1]:
http://sysadmin.tme520.net/systemd-our-songs-of-innocence/
Cannot explain but I like this article very much. Especially this :
"Now, for at least a couple of years, two versions of Linux wi
On 22/07/2015 22:20, T.J. Duchene wrote:
That said, the reality of the situation is quite different than it is
in theory. As the old saying goes in the American Midwest: "The
proof is in the pudding." Until someone provides a systemd
alternative that works better than systemd, yet provides conv
> In general, I'd agree with you, but there are some situations where it's
> possible to argue for hotplugger/service manager integration:
> if you hotplug a scanner or printer, there's reason to think that the
> corresponding daemon (sane/cups/lprng/lpr) should start.
> Note that I did not say th
Am Mittwoch, 22. Juli 2015 schrieb Steve Litt:
> Pre-cisely! I don't have Lennart Poettering's coding skills or system
> wisdom, nor do I have the budget by which his team operates, but even I
> was able to put together the most challenging part of hotplugging,
> using inotifywait:
>
> http://www
On Wed, 22 Jul 2015 16:57:55 +0200
Laurent Bercot wrote:
> On 22/07/2015 16:24, Isaac Dunham wrote:
> > In general, I'd agree with you, but there are some situations where
> > it's possible to argue for hotplugger/service manager integration:
> > if you hotplug a scanner or printer, there's rea
Hi,
Oz Tiram wrote on 22/07/2015 at 10:00 CEST:
One argument I hear often about systemd is that it more adapted to
current hardware needs, [e.g. here][1]
Computers changed so much that they often doesn’t even look
>> like computers. And their operating systems are very busy :
>> GPS, wireless
On 22/07/2015 16:24, Isaac Dunham wrote:
In general, I'd agree with you, but there are some situations where it's
possible to argue for hotplugger/service manager integration:
if you hotplug a scanner or printer, there's reason to think that the
corresponding daemon (sane/cups/lprng/lpr) shou
On Wed, Jul 22, 2015 at 12:59:56PM +0200, Laurent Bercot wrote:
> On 22/07/2015 10:00, Oz Tiram wrote:
> >One argument I hear often about systemd is that it more adapted to current
> >hardware needs, [e.g. here][1]
> >
> > > Computers changed so much that they often doesn’t even look like
> > > c
On 22/07/2015 10:00, Oz Tiram wrote:
One argument I hear often about systemd is that it more adapted to current
hardware needs, [e.g. here][1]
> Computers changed so much that they often doesn’t even look like
> computers. And their operating systems are very busy : GPS, wireless
> networks
On Wed, Jul 22, 2015 at 10:00:48AM +0200, Oz Tiram wrote:
> One argument I hear often about systemd is that it more adapted to current
> hardware needs, [e.g. here][1]
>
> > Computers changed so much that they often doesn’t even look like
> > computers. And their operating systems are very busy :
12 matches
Mail list logo
