On Friday 29 May 2015 17:02:18 Mick wrote:
On Friday 29 May 2015 16:36:59 Peter Humphrey wrote:
On Friday 29 May 2015 16:19:38 Mick wrote:
On Friday 29 May 2015 10:36:37 Peter Humphrey wrote:
I had two sets of problems: one in KDE which I might have nailed
finally [1], and one at
On Sunday 31 May 2015 01:39:34 Peter Humphrey wrote:
On Saturday 30 May 2015 16:43:13 Peter Humphrey wrote:
On Saturday 30 May 2015 12:49:51 Mick wrote:
On my laptop which has stayed on Kmail-1 I have this:
---8
Have a look here for more details and warnings:
On Sunday 31 May 2015 13:18:06 Mick wrote:
You could look into ~/Mail/ or wherever you keep your mails and find the
Inbox directory. Then copy any messages you want shown there manually.
The index will be recreated when you restart Kmail, or if you click on
'Recreate Index' under the
On Sunday 31 May 2015 15:01:10 Peter Humphrey wrote:
On Sunday 31 May 2015 13:18:06 Mick wrote:
You could look into ~/Mail/ or wherever you keep your mails and find the
Inbox directory. Then copy any messages you want shown there manually.
The index will be recreated when you restart
On Saturday 30 May 2015 16:43:13 Peter Humphrey wrote:
On Saturday 30 May 2015 12:49:51 Mick wrote:
On my laptop which has stayed on Kmail-1 I have this:
---8
Have a look here for more details and warnings:
https://wiki.gentoo.org/wiki/KDE/KDEPIM-4.7_upgrade
Many thanks Mick -
On 29/05/2015 17:54, Mick wrote:
On Friday 29 May 2015 16:28:57 Alan Grimes wrote:
Mick wrote:
On Friday 29 May 2015 10:36:37 Peter Humphrey wrote:
I had two sets of problems: one in KDE which I might have nailed finally
[1], and one at boot time in which /dev/md7 (RAID-1 with metadata 1.0)
On Sat, 30 May 2015 00:20:51 +0100, Peter Humphrey wrote:
He was talking about tying the e-mail client to a database, not about
the KDE4 desktop, and I've protested at the same thing more than
once, sometimes in vigorous terms. Made no difference of course, but
then I'm just an insufficiently
On Saturday 30 May 2015 00:20:51 Peter Humphrey wrote:
Other than the odd bug here and there I was perfectly happy with KDE3 and
Kmail1 (still using with kde-base/kdepim-meta-4.4.11.1-r1).
I wonder if there's a way to go back to KMail-1 and import all my e-mails
from KMail-2 archive files
On Saturday 30 May 2015 09:53:23 Alan McKinnon wrote:
Akonadi was supposed to be a once-size-fits-all central store of all pim
info (contacts, addresses, mails and all metadata about that) which any
and all apps could use.
The vision was that an enormous awesome ecosystem all buying into
On Saturday 30 May 2015 12:49:51 Mick wrote:
On my laptop which has stayed on Kmail-1 I have this:
---8
Have a look here for more details and warnings:
https://wiki.gentoo.org/wiki/KDE/KDEPIM-4.7_upgrade
Many thanks Mick - that's very helpful.
I expect that sooner or later bitrot will
On Fri, 29 May 2015 01:10:52 +0100, Peter Humphrey wrote:
Just keep in mind that the UUID that goes into mdadm.conf might not be
the same UUID returned by blkid. I'm honestly not certain either way.
You can get the mdadm ID from mdadm --detail --scan.
Good grief! When is a UUID not a
On Friday 29 May 2015 11:13:22 Stephan Müller wrote:
Am 28.05.2015 um 19:03 schrieb Peter Humphrey:
(It would have been nice to sort on the final field but I can't see how to
do that.)
For example like this:
$ ls -l /dev/disk/by-uuid/ | awk '{print $11, $9}' | sort
That's something
Am 28.05.2015 um 19:03 schrieb Peter Humphrey:
1bb4ba53-677a-4a0e-b737-f3e274f0e71e - ../../sda2
1e20e3e6-e218-485b-b5ff-be85a287e364 - ../../sda3
3a2a6e94-a6f0-4479-ae87-44887946148c - ../../sda6
3befff76-2a0e-49fa-9e6f-2bd0ed73cf31 - ../../md5
43e655ca-a6ef-4931-99b6-3aa2ad6c30cb -
Mick wrote:
On Friday 29 May 2015 10:36:37 Peter Humphrey wrote:
I had two sets of problems: one in KDE which I might have nailed finally
[1], and one at boot time in which /dev/md7 (RAID-1 with metadata 1.0)
was not being started.
[1] Whenever I've had KMail screw up I've created a new
On Friday 29 May 2015 16:19:38 Mick wrote:
On Friday 29 May 2015 10:36:37 Peter Humphrey wrote:
I had two sets of problems: one in KDE which I might have nailed finally
[1], and one at boot time in which /dev/md7 (RAID-1 with metadata 1.0)
was not being started.
[1] Whenever I've had
On Friday 29 May 2015 16:28:57 Alan Grimes wrote:
Mick wrote:
On Friday 29 May 2015 10:36:37 Peter Humphrey wrote:
I had two sets of problems: one in KDE which I might have nailed finally
[1], and one at boot time in which /dev/md7 (RAID-1 with metadata 1.0)
was not being started.
On Friday 29 May 2015 10:36:37 Peter Humphrey wrote:
I had two sets of problems: one in KDE which I might have nailed finally
[1], and one at boot time in which /dev/md7 (RAID-1 with metadata 1.0)
was not being started.
[1] Whenever I've had KMail screw up I've created a new user and
On Friday 29 May 2015 16:36:59 Peter Humphrey wrote:
On Friday 29 May 2015 16:19:38 Mick wrote:
On Friday 29 May 2015 10:36:37 Peter Humphrey wrote:
I had two sets of problems: one in KDE which I might have nailed
finally [1], and one at boot time in which /dev/md7 (RAID-1 with
On Friday 29 May 2015 16:54:33 Mick wrote:
On Friday 29 May 2015 16:28:57 Alan Grimes wrote:
What in god's name is that stupid database for anyway? Does it perform
any useful function? Is there any tool that gives the user any
measurable benefit that even justifies one one hundredth of the
On Thu, May 28, 2015 at 1:03 PM, Peter Humphrey pe...@prh.myzen.co.uk wrote:
On Thursday 28 May 2015 15:36:04 I wrote:
On Thursday 28 May 2015 08:44:27 Rich Freeman wrote:
With an approach like yours, mdadm will attempt to create md1 by
looking ONLY at sda1 and sdb1, and if that pair forms a
On Thursday 28 May 2015 19:51:24 Rich Freeman wrote:
On Thu, May 28, 2015 at 1:03 PM, Peter Humphrey pe...@prh.myzen.co.uk
wrote:
I've found blkid, which tells me the UUIDs of my various devices, thus:
# blkid /dev/md7
/dev/md7: UUID=ycGMf9-hEP2-tjT4-AtkJ-n8RI-pZ44-RqvlEY
On Wed, May 27, 2015 at 8:01 PM, Peter Humphrey pe...@prh.myzen.co.uk wrote:
My mdadm.conf is now this:
DEVICE /dev/sd[ab]1
DEVICE /dev/sd[ab]5
DEVICE /dev/sd[ab]7
ARRAY /dev/md1 devices=/dev/sda1,/dev/sdb1
ARRAY /dev/md5 devices=/dev/sda5,/dev/sdb5
ARRAY /dev/md7
* Rich Freeman ri...@gentoo.org [150528 08:45]:
On Wed, May 27, 2015 at 8:01 PM, Peter Humphrey pe...@prh.myzen.co.uk wrote:
[..SNIP..]
UUIDs are often preferable in these kinds of configurations, because
you're less likely to run into duplicate identifiers, they don't
change, and so on. If I
On Thursday 28 May 2015 08:44:27 Rich Freeman wrote:
On Wed, May 27, 2015 at 8:01 PM, Peter Humphrey
pe...@prh.myzen.co.uk wrote:
My mdadm.conf is now this:
DEVICE /dev/sd[ab]1
DEVICE /dev/sd[ab]5
DEVICE /dev/sd[ab]7
ARRAY /dev/md1 devices=/dev/sda1,/dev/sdb1
ARRAY /dev/md5
On Thursday 28 May 2015 15:36:04 I wrote:
On Thursday 28 May 2015 08:44:27 Rich Freeman wrote:
With an approach like yours, mdadm will attempt to create md1 by
looking ONLY at sda1 and sdb1, and if that pair forms a valid array it
is started, and if not it is not. If you add a new drive to
On 27/05/2015 14:31, Canek Peláez Valdés wrote:
On Wed, May 27, 2015 at 6:59 AM, Peter Humphrey pe...@prh.myzen.co.uk
mailto:pe...@prh.myzen.co.uk wrote:
Hello list,
Hi.
Over the last few weeks I've been having odd things go bump in the
night. This
is a KDE amd64 system with /usr under
On Wed, May 27, 2015 at 8:02 AM, Alan McKinnon alan.mckin...@gmail.com
wrote:
On 27/05/2015 14:31, Canek Peláez Valdés wrote:
On Wed, May 27, 2015 at 6:59 AM, Peter Humphrey pe...@prh.myzen.co.uk
mailto:pe...@prh.myzen.co.uk wrote:
Hello list,
Hi.
Over the last few weeks I've
Hello list,
Over the last few weeks I've been having odd things go bump in the night. This
is a KDE amd64 system with /usr under / and no initrd.
The first thing was that my screen saver was being overlaid with a plain
default desktop. That was fixed by creating a new user for myself and
On Wed, May 27, 2015 at 6:59 AM, Peter Humphrey pe...@prh.myzen.co.uk
wrote:
Hello list,
Hi.
Over the last few weeks I've been having odd things go bump in the night.
This
is a KDE amd64 system with /usr under / and no initrd.
I have no idea what your problem can be. But as a friendly
On Wed, May 27, 2015 at 7:59 AM, Peter Humphrey pe...@prh.myzen.co.uk wrote:
This is a KDE amd64 system with /usr under / and no initrd.
Just to clarify, is /usr on a separate filesystem, or the same as /?
I don't think that is your problem in any case, but it might be
relevant.
... bunch of
On Wednesday 27 May 2015 09:21:37 Rich Freeman wrote:
On Wed, May 27, 2015 at 7:59 AM, Peter Humphrey pe...@prh.myzen.co.uk
wrote:
This is a KDE amd64 system with /usr under / and no initrd.
Just to clarify, is /usr on a separate filesystem, or the same as /?
I don't think that is your
On Wednesday 27 May 2015 15:16:35 Peter Humphrey wrote:
On Wednesday 27 May 2015 09:21:37 Rich Freeman wrote:
On Wed, May 27, 2015 at 7:59 AM, Peter Humphrey pe...@prh.myzen.co.uk
wrote:
This is a KDE amd64 system with /usr under / and no initrd.
Just to clarify, is /usr on a
On Wednesday 27 May 2015 21:40:37 Mick wrote:
On Wednesday 27 May 2015 15:16:35 Peter Humphrey wrote:
On Wednesday 27 May 2015 09:21:37 Rich Freeman wrote:
I suspect that an initramfs might help
you out, assuming the filesystems on that RAID are useful in early
boot. However, openrc
On Wednesday 27 May 2015 15:16:35 I wrote:
Since writing, I've found that my fonts have all changed as well.
Yet more clarity: fonts have not been affected in applications that control
their own fonts - KMail, Firefox... - but system functions and boinc-mgr
(which uses whatever fonts are
34 matches
Mail list logo
