On Thursday 31 Dec 2015 16:28:36 J. Roeleveld wrote:
> On Thursday, December 31, 2015 01:50:43 PM Mick wrote:
> > On Thursday 31 Dec 2015 11:14:48 J. Roeleveld wrote:
> > So, I'm reading the fine manual again, but I find myself asking questions
> > like ... how do I do this MySQL command on postgr
On Friday 01 January 2016 10:26:05 Mick wrote:
> ... my kmail2 still seems to be functioning properly and without any major
> problems so far. :-)
What, not even duplicates? I'm still getting a dozen a day.
--
Rgds
Peter
Peter Humphrey writes:
> I won't list all my objections here, but I have attached two screen shots of
> KMail: one in the standard qt4 KDE environment and the other in qt5. You can
> see how much less compact the qt5 version is, even after I've fiddled at some
> length with fonts and qt tweaks
"J. Roeleveld" writes:
> On Wednesday, December 30, 2015 09:32:55 PM lee wrote:
>> "J. Roeleveld" writes:
>> > On Tuesday, December 29, 2015 08:03:25 PM Mick wrote:
>> >> On Tuesday 29 Dec 2015 17:37:25 lee wrote:
>> >> > Are we at the point where users are accepting to have to install and
>> >>
"Stefan G. Weichinger" writes:
> On 12/30/2015 10:14 PM, lee wrote:
>> Hi,
>>
>> soon I'll be replacing the system disks and will copy over the existing
>> system to the new disks. I'm wondering how much merit there would be in
>> being able to make snapshots to be able to revert back to a prev
Paul Colquhoun writes:
> On Wed, 30 Dec 2015 17:32:44 lee wrote:
>> Neil Bothwick writes:
>> > On Tue, 29 Dec 2015 19:21:01 +0100, lee wrote:
> [...]
>> >> So if I'd never explicitly update everything but run emerge --sync
>> >> frequently, things would be updated over time, occasionally?
>> >
On Friday 01 January 2016 11:33:32 lee wrote:
> Peter Humphrey writes:
> > I won't list all my objections here, but I have attached two screen
> > shots of KMail: one in the standard qt4 KDE environment and the other
> > in qt5. You can see how much less compact the qt5 version is, even
> > after
On Friday 01 Jan 2016 10:41:40 Peter Humphrey wrote:
> On Friday 01 January 2016 10:26:05 Mick wrote:
> > ... my kmail2 still seems to be functioning properly and without any major
> > problems so far. :-)
>
> What, not even duplicates? I'm still getting a dozen a day.
Hi Peter,
I think your pr
On Friday 01 January 2016 11:47:16 Mick wrote:
> On Friday 01 Jan 2016 10:41:40 Peter Humphrey wrote:
> > On Friday 01 January 2016 10:26:05 Mick wrote:
> > > ... my kmail2 still seems to be functioning properly and without any
> > > major problems so far. :-)
> >
> > What, not even duplicates? I
On Fri, Jan 1, 2016 at 5:42 AM, lee wrote:
> "Stefan G. Weichinger" writes:
>
>> btrfs offers RAID-like redundancy as well, no mdadm involved here.
>>
>> The general recommendation now is to stay at level-1 for now. That fits
>> your 2-disk-situation.
>
> Well, what shows better performance? No
Hi lee
On 2015-12-30, lee wrote:
> Elias Diem writes:
>
> >> Whether this is a bug or not depends on what you're supposed to expect,
> >> which I don't know. If someone would run the test suite on a
> >> non-hardened profile and got the same warning from gcc, but vim wouldn't
> >> be terminate
On Friday 01 Jan 2016 13:06:55 Peter Humphrey wrote:
> Thanks for your thoughts Mick. I think most of my problems have persisted
> through many iterations from the early days of KMail-2. At any rate, I've
> just deleted the whole KMail structure once more and reimported from
> archive and so far
I am updating an old machine which does not see much usage these days. I came
across this blockage, which seems is caused by retaining the pre-Kmail2 KDEPIM
version on this PC:
===
# emerge @preserved-rebuild -a
These are the packages that would be merged
On 12/26/2015 06:44 AM, Paul Colquhoun wrote:
> Yes, using gcc-5.3.0 to recompile 5.3.0 with +jit worked.
Doing the same right now.
Does JIT make any difference yet when I recompile something with a
JIT-enabled gcc? Does any code in current gentoo actually use that already?
On Friday 01 January 2016 14:25:17 Mick wrote:
> On Friday 01 Jan 2016 13:06:55 Peter Humphrey wrote:
> > Thanks for your thoughts Mick. I think most of my problems have
> > persisted
> > through many iterations from the early days of KMail-2. At any rate,
> > I've
> > just deleted the whole KMail
On Friday, January 01, 2016 03:58:18 PM Peter Humphrey wrote:
> On Friday 01 January 2016 14:25:17 Mick wrote:
> > On Friday 01 Jan 2016 13:06:55 Peter Humphrey wrote:
> > > Thanks for your thoughts Mick. I think most of my problems have
> > > persisted
> > > through many iterations from the early
Mick gmail.com> writes:
> I am updating an old machine which does not see much usage these days.
> I came across this blockage, which seems is caused by retaining the
> pre-Kmail2 KDEPIM version on this PC:
When upgrading old systems, always there are packages that cause problems
or the
About a week ago, I have installed
gtypist and tried to run it with ru.typ
that comes with it:
$ gtypist ru.typ
gtypist: line 34: iconv() failed on 'B: Добро пожаловать!':
Invalid or incomplete multibyte or wide character
You should probably use a UTF-8 locale for the selected lesson!
:
?
What can
On Friday 01 Jan 2016 16:49:41 James wrote:
> Mick gmail.com> writes:
> > I am updating an old machine which does not see much usage these days.
> > I came across this blockage, which seems is caused by retaining the
>
> > pre-Kmail2 KDEPIM version on this PC:
> When upgrading old systems, alwa
Hello,
Am Freitag, 1. Januar 2016, 23:22:54 schrieb Mick:
> On Friday 01 Jan 2016 16:49:41 James wrote:
> > Mick gmail.com> writes:
> > > I am updating an old machine which does not see much usage
these days.
> > > I came across this blockage, which seems is caused by retaining
the
> >
> > >
First, basic definitions.
distcc ==> compile on machine A for machine B. No mention of whether
the processors are different architectures.
cross-compile ==> compile under architecture A for architecture B
I'm trying to run a distccserver in a 32-bit VM on a 64-bit host, for
Hi,
HAPPY NEW YEAR !!! :)
I am not using a physical printer.
Is it possible to get completly rid of cups and
other "physical printing"-related stuff somehow?
Any global USE-flag I can set/delete to accomplish
this?
Thank you very much for any help in advance!
Best regards,
mcc
On Fri, Jan 1, 2016 at 10:50 PM, wrote:
> Any global USE-flag I can set/delete to accomplish
> this?
I would think -cups should do the job.
Brandon Vincent
Den 19. des. 2015 01:01, skrev Dale:
...
> It sounds like the heads are doing random
> reads/writes and the heads are moving but doing so noisily. Thing is,
> there is no drive activity according to gkrellm or iotop. All the
> drives should be basically idle.
...
> Model=ST3000DM001
What kind o
Den 01. jan. 2016 00:49, skrev Linux:
> On 12/30/2015 10:32 AM, Roman Dobosz wrote:
>
> snip
>
>> Just redirect the standard end error output to the void, like:
>>
>> --- 8< ~/.config/mc/mc.ext ---
>> include/video2
>> Open=(mpv -vf-clr %f >/dev/null 2>&1 &)
>> View=%view{ascii} midentify
25 matches
Mail list logo
