On Sunday 13 September 2015 13:57:04 Peter Humphrey wrote:
>On Sunday 13 September 2015 13:16:29 Marc Joliet wrote:
>> I couldn't get KMail -- which I am still getting used to -- to stop it's
>> automatic line wrapping just for those lines, if it even supports that
>
>You can switch it on or off, b
On Sun, 13 Sep 2015 13:16:29 +0200, Marc Joliet wrote:
> On Friday 11 September 2015 15:08:54 walt wrote:
> >My very old and slow ~amd64 machine took 3 hours and 45-minutes to
> >compile systemd-226 today.
>
> Just out of curiosity: exactly how old? My dual-core amd64 system is
> almost 9 year
On Sunday 13 September 2015 13:16:29 Marc Joliet wrote:
> I couldn't get KMail -- which I am still getting used to -- to stop it's
> automatic line wrapping just for those lines, if it even supports that
You can switch it on or off, but it applies to the whole message. What I do if
I want a line
On Friday 11 September 2015 15:08:54 walt wrote:
>My very old and slow ~amd64 machine took 3 hours and 45-minutes to
>compile systemd-226 today.
Just out of curiosity: exactly how old? My dual-core amd64 system is almost 9
years old now, and systemd compiles in about 6 minutes:
# genlop -t syste
On Fri, Sep 11, 2015 at 6:08 PM, walt wrote:
> My very old and slow ~amd64 machine took 3 hours and 45-minutes to
> compile systemd-226 today. I was curious to know why it was taking so
> long to finish, so I used 'top' to see what was happening.
>
> Turns out that two instances of 'sh' were each
My very old and slow ~amd64 machine took 3 hours and 45-minutes to
compile systemd-226 today. I was curious to know why it was taking so
long to finish, so I used 'top' to see what was happening.
Turns out that two instances of 'sh' were each using 15-30% of CPU for
a total of 30-60% (the machine
6 matches
Mail list logo