-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cauldron on Acer Aspire One 533
I tested a Cauldron install (beta 2 download) on VirtualBox and found
no serious problems, so started yesterday to prepare my netbook for my
holiday.
It took 5 hours to install - using a USB DVD drive. Once Coling
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/04/12 16:25, Manuel Hiebel wrote:
Le 15/04/2012 15:16, Anne Wilson a écrit :
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
Cauldron on Acer Aspire One 533
I tested a Cauldron install (beta 2 download) on VirtualBox and
found no serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/04/12 17:47, Anne Wilson wrote:
Attempting to install sound-scripts separately asks whether I want
to use systemd-sysvinit or sysvinit-legacy. I've tried both, but
both fail due to missing sound-scripts.
Found the package listed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/04/12 09:21, Colin Guthrie wrote:
'Twas brillig, and Anne Wilson at 15/04/12 18:39 did gyre and
gimble:
On 15/04/12 17:47, Anne Wilson wrote:
Attempting to install sound-scripts separately asks whether I
want to use systemd-sysvinit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/04/12 13:15, Anne Wilson wrote:
On 16/04/12 09:21, Colin Guthrie wrote:
'Twas brillig, and Anne Wilson at 15/04/12 18:39 did gyre and
gimble:
On 15/04/12 17:47, Anne Wilson wrote:
Attempting to install sound-scripts separately asks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/04/12 14:27, Colin Guthrie wrote:
'Twas brillig, and Anne Wilson at 16/04/12 13:28 did gyre and
gimble:
On 16/04/12 13:15, Anne Wilson wrote:
On 16/04/12 09:21, Colin Guthrie wrote:
'Twas brillig, and Anne Wilson at 15/04/12 18:39 did gyre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/04/12 14:41, Colin Guthrie wrote:
'Twas brillig, and Thierry Vignaud at 16/04/12 14:34 did gyre and
gimble:
BTW why not displaying a message switch to tty2 for a login?
In the normal case of X or prefdm.service failing, this is exactly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/04/12 10:00, Colin Guthrie wrote:
'Twas brillig, and Anne Wilson at 17/04/12 07:24 did gyre and
gimble:
On 16/04/12 16:58, Colin Guthrie wrote:
OK, so this is incorrect, (prefdm *is* started, but perhaps
some other jobs had to be cancelled
On 17/04/12 21:22, Colin Guthrie wrote:
'Twas brillig, and Colin Guthrie at 17/04/12 16:49 did gyre and
gimble:
'Twas brillig, and Anne Wilson at 17/04/12 15:13 did gyre and
gimble:
On 17/04/12 10:00, Colin Guthrie wrote:
All of this should be fixed when we update all the legacy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/04/12 12:57, Colin Guthrie wrote:
'Twas brillig, and Anne Wilson at 18/04/12 12:32 did gyre and
gimble:
On 17/04/12 21:22, Colin Guthrie wrote:
As you do not have any legacy initscripts messing things up, I
think the problem you now face
On 18/04/12 13:09, Colin Guthrie wrote:
'Twas brillig, and Colin Guthrie at 18/04/12 12:57 did gyre and
gimble:
'Twas brillig, and Anne Wilson at 18/04/12 12:32 did gyre and
gimble:
On 17/04/12 21:22, Colin Guthrie wrote:
As you do not have any legacy initscripts messing things up, I
think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/04/12 14:52, Colin Guthrie wrote:
'Twas brillig, and Anne Wilson at 18/04/12 13:46 did gyre and
gimble:
On 18/04/12 13:09, Colin Guthrie wrote:
I'm pretty sure it's KDM that failing and subsequently
bringing X down with it. I'll see if I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/04/12 17:41, Thomas Backlund wrote:
15.04.2012 16:16, Anne Wilson skrev:
In desperation I tried rm -fR /var/lib/rpm/* - I hope I
haven't broken anything too drastic, but nothing seems to have
changed. The database will still not rebuild
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/04/12 17:58, Thomas Backlund wrote:
18.04.2012 19:49, Anne Wilson skrev:
On 18/04/12 17:41, Thomas Backlund wrote:
15.04.2012 16:16, Anne Wilson skrev:
In desperation I tried rm -fR /var/lib/rpm/* - I hope I
haven't broken anything too
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/04/12 18:32, Thomas Backlund wrote:
18.04.2012 20:25, Anne Wilson skrev:
On 18/04/12 17:58, Thomas Backlund wrote:
If you want to restore the database at this point you need to
reinstall all packages as listed in /var/log/rpmpkgs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You may remember that I said that the beta 2 install took 5 hours -
beta 3 took just over one hour. Maybe there always was a problem with
my beta 2 install, although the sha1sum verified.
Beta 3 then - install went absolutely fine until the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mageia Beta3, KDE 4.8.2. KMail has successfully connected to all my
GMail folders and to my Google Calendar. No contacts so far, though.
I'll try connecting to my local IMAP server next. So far it looks as
though there is an impressive
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have been using lines such as this to mount nfs shares:
192.168.0.40:/Data1 /mnt/borg2_Data1 nfs4
rsize=8192,wsize=8192,timeo=14,intr
mount -a
Mount is denied because the NTFS volume is already exclusively opened.
The volume may be already
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/04/12 19:35, Anssi Hannula wrote:
19.04.2012 21:16, Anne Wilson kirjoitti:
I have been using lines such as this to mount nfs shares:
192.168.0.40:/Data1 /mnt/borg2_Data1 nfs4
rsize=8192,wsize=8192,timeo=14,intr
mount -a Mount
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It looks as though locks are not released after any urpmi activity.
Is anyone else experiencing this?
Anne
- --
Need KDE help? Try
http://userbase.kde.org or
http://forum.kde.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/04/12 20:04, Thierry Vignaud wrote:
On 20 April 2012 21:50, Anne Wilson an...@kde.org wrote:
It looks as though locks are not released after any urpmi
activity. Is anyone else experiencing this?
They are unless you kill it while installing
I have been using lines such as this to mount nfs shares:
192.168.0.40:/Data1 /mnt/borg2_Data1 nfs4
rsize=8192,wsize=8192,timeo=14,intr
mount -a
Mount is denied because the NTFS volume is already exclusively opened.
The volume may be already mounted, or another software may use it
which
could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/06/12 15:43, Colin Guthrie wrote:
'Twas brillig, and Jerome Quelin at 01/06/12 14:44 did gyre and
gimble:
considering perl upgrade to be finished. please report any
problem other than the ones above.
Just for reference, I did my upgrade
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/06/12 19:02, Thomas Backlund wrote:
01.06.2012 20:55, Anne Wilson skrev:
On 01/06/12 15:43, Colin Guthrie wrote:
'Twas brillig, and Jerome Quelin at 01/06/12 14:44 did gyre and
gimble:
considering perl upgrade to be finished. please report
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/06/12 14:33, Angelo Naselli wrote:
One thing that has always been annoying to me, in Mandrake,
Mandriva and now Mageia, is the proliferation of entries in the
Grub menu by the time you've done a few updates. Fedora get
around this by having
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Whilst following anaselli's advice to browse around, I discovered that
on https://wiki.mageia.org/en/Documentation_team the link to the
Calenco user's guide meets a redirect, which goes to a 404.
Anne
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/06/12 21:24, Angelo Naselli wrote:
Il 07/06/2012 18:11, Anne Wilson ha scritto:
I feel guilty in requesting work when I have no coding skills
myself, however, I am sure that there will be some tasks
somewhere that you can give me.
If you
I have been using lines such as this to mount nfs shares:
192.168.0.40:/Data1 /mnt/borg2_Data1 nfs4
rsize=8192,wsize=8192,timeo=14,intr
mount -a
Mount is denied because the NTFS volume is already exclusively opened.
The volume may be already mounted, or another software may use it
which
could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/06/12 23:36, andre999 wrote:
But using a DVD to upgrade an already installed system is a good
way to get around the fact that many packages, including nonfree
firmware, are missing from the DVD. If one does a clean install,
one has to try to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/07/12 19:34, AL13N wrote:
i think that everyone would appreciate if the system proposes
to install: - all the proprietary drivers your system needs -
all the multimedia codecs necessary to play your films and
music (if possible) - some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Could someone please tell me what to look for, and where, to solve
this puzzle?
- - iptables firewall Begin
Listed by source hosts:
Dropped 9 packets on interface eth0
From 192.168.0.40 - 9 packets
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/07/12 15:42, Pascal Terjan wrote:
On Wed, Jul 4, 2012 at 4:07 AM, Anne Wilson an...@kde.org wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
Could someone please tell me what to look for, and where, to
solve this puzzle?
Where do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/07/12 16:58, Johnny A. Solbu wrote:
Am I not running any firmware at all? Or am I just running an
older buggier and equally untrustworthy version of the same
code that was burned into the ROM at the factory?
You are running an old, most
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/07/12 11:42, Colin Guthrie wrote:
I've clarified these instructions on the wiki:
https://wiki.mageia.org/en/Feature:UsrMove#Release_Notes
Feel free to augment them with better info as needed.
I now have a functioning system, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/07/12 15:24, Anne Wilson wrote:
On 22/07/12 11:42, Colin Guthrie wrote:
I've clarified these instructions on the wiki:
https://wiki.mageia.org/en/Feature:UsrMove#Release_Notes
Feel free to augment them with better info as needed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
46 packages are reported as being orphans after the move, but many of
those are libraries and video drivers, of which the intel one is, I
think, the one I use. OTOH, /usr/sbin/remove-unused-packages finds
only a wacom driver to be removed.
Advice?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/07/12 10:20, Colin Guthrie wrote:
'Twas brillig, and Anne Wilson at 24/07/12 09:42 did gyre and
gimble:
46 packages are reported as being orphans after the move, but
many of those are libraries and video drivers, of which the intel
one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/07/12 15:09, Colin Guthrie wrote:
'Twas brillig, and Anne Wilson at 24/07/12 14:42 did gyre and
gimble:
On 24/07/12 10:20, Colin Guthrie wrote:
'Twas brillig, and Anne Wilson at 24/07/12 09:42 did gyre and
gimble:
46 packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/08/12 09:58, Pascal Terjan wrote:
On Mon, Aug 13, 2012 at 9:39 AM, Anne Wilson an...@kde.org
wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
On 13/08/12 08:34, Guillaume Rousse wrote:
Le 12/08/2012 21:57, David Walser a écrit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/08/12 10:01, Colin Guthrie wrote:
'Twas brillig, and Anne Wilson at 13/08/12 18:06 did gyre and
gimble:
On 13/08/12 11:04, Olav Vitters wrote:
On Mon, Aug 13, 2012 at 09:39:07AM +0100, Anne Wilson wrote:
Why would anyone need root login
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
First, there is a situation that could have influenced this. I have
had little time for the last few weeks. I stayed with regular updates
to Cauldron until just after the /usr move thing, and all was well
when I left it.
This weekend I went back to
On 05/09/2012 07:57, Angelo Naselli wrote:
i had to boot again with the vga monitor pluuged and set the
output to my notebook display again. After that it booted ok.
And i didn't use mcc, but just krandrtray settings
Hmm - I'm on vacationnow, and I can't remember how many things I tried,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My laptop uses fstab lines to mount directories on the old server and
also on a QNAS box. I've no idea what version of Linux is running on
the QNAS, but the mounts are working there. The old server is running
Mageia 2, and mount to that don't work.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/09/12 15:53, Wolfgang Bornath wrote:
Are paper magazines still relevant here? (true question)
Yes, they are an important distribution method. Additionally there
will be reviews/articles accompanying the cover DVDs. Don't
forget, this is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/09/12 21:47, Guillaume Rousse wrote:
Le 19/09/2012 19:46, Anne Wilson a écrit :
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
My laptop uses fstab lines to mount directories on the old server
and also on a QNAS box. I've no idea what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/09/12 11:19, Wolfgang Bornath wrote:
2012/9/19 Anne Wilson an...@kde.org:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
On 19/09/12 15:53, Wolfgang Bornath wrote:
Are paper magazines still relevant here? (true question)
Yes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/09/12 11:59, Guillaume Rousse wrote:
Le 20/09/2012 11:54, Anne Wilson a écrit :
and -v option to mount.nfs on client side to get more verbose
error reporting.
How do I do that? mount.nfs is an executable, not a shell
script, so I can't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/09/12 16:27, Guillaume Rousse wrote:
Le 20/09/2012 15:00, Anne Wilson a écrit :
Also, you can check available NFS version on your servers:
rpcinfo -s 192.168.0.40
rpcinfo -s 192.168.0.40 program version(s) netid(s)
service owner 10
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/09/12 12:13, Wolfgang Bornath wrote:
2012/9/20 Anne Wilson an...@kde.org:
On 20/09/12 11:19, Wolfgang Bornath wrote:
This is the reason why over here nobody thinks of abandoning
the cover media. Quite to the opposite as I learned from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/09/12 12:42, Donald Stewart wrote:
On 20 September 2012 12:13, Wolfgang Bornath
molc...@googlemail.com wrote:
Says a resident in the UK with superfast internet for everybody.
:)
While I don't buy magazines as *I* can download any of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/09/12 21:37, Guillaume Rousse wrote:
Le 20/09/2012 20:17, Anne Wilson a écrit :
Looks as though the problem relates to rpc on the server. I
don't mind doing the digging, but can you point me to the
right place to start the hole?
I'd try
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/09/12 21:37, Guillaume Rousse wrote:
If everything else fails, you may also inhibit IPv6 completly: just
add 'install ipv6 /bin/true' in any file under /etc/modprobe.d, and
reboot.
Using MCC, I disabled IPv6 and rebooted. Now 'mount -a'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/09/12 11:01, Guillaume Rousse wrote:
Le 21/09/2012 20:54, Anne Wilson a écrit :
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
On 20/09/12 21:37, Guillaume Rousse wrote:
If everything else fails, you may also inhibit IPv6 completly:
just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just wondered whether these msec lines tell you anything useful -
tcp0 0 *:imaps *:*
LISTEN dovecot
tcp0 0 *:4001 *:*
LISTEN rpc.statd
tcp0 0 *:nfs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/09/12 07:04, Guillaume Rousse wrote:
Le 22/09/2012 20:53, Anne Wilson a écrit :
and if
rpc.idmapd is running on both side (service nfs-utils status
on both side).
This is driving me mad. 'service nfs-utils status' on the
server tells me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/09/12 08:26, Thierry Vignaud wrote:
On 23 September 2012 11:18, Anne Wilson
cannewil...@googlemail.com wrote:
Package nfs-utils blahblah is already installed
nfs-common service, sorry.
That may well point to the problem, though I've
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I finally got around to connecting my netbook, which has been running
Cauldron for some time. This was fully up to date before my holidays,
and apart from the recent display problem (which as Angelo Naselli
suspected, is a KDE problem) it has behaved
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sent yesterday, but not seen on-list, so apologies if this is a duplicate.
I finally got around to connecting my netbook, which has been running
Cauldron for some time. This was fully up to date before my holidays,
and apart from the recent display
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/09/12 15:41, Colin Guthrie wrote:
'Twas brillig, and Anne Wilson at 25/09/12 15:02 did gyre and
gimble:
Sent yesterday, but not seen on-list, so apologies if this is a
duplicate.
I finally got around to connecting my netbook, which has
: [Mageia-dev] M3 won't complete boot after update
Date: Tue, 25 Sep 2012 16:37:20 +0100
From: Anne Wilson an...@kde.org
To: Mageia development mailing-list mageia-dev@mageia.org
On 25/09/12 15:41, Colin Guthrie wrote:
'Twas brillig, and Anne Wilson at 25/09/12 15:02 did gyre and
gimble:
Sent
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/09/2012 16:44, Jani Välimaa wrote:
On 24.09.2012 22:21, Anne Wilson wrote:
I finally got around to connecting my netbook, which has been
running Cauldron for some time. This was fully up to date before
my holidays, and apart from the recent
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/09/2012 16:24, Jani Välimaa wrote:
On 26.09.2012 18:00, Anne Wilson wrote:
Colin, I sent this last evening, but I haven't seen it on-list.
For some reason a fair number of my messages don't get through.
Could it be that the digital signing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/09/2012 17:05, Jani Välimaa wrote:
On 26.09.2012 18:29, Wolfgang Bornath wrote:
2012/9/26 Jani Välimaa jani.vali...@gmail.com:
On 26.09.2012 18:00, Anne Wilson wrote:
Colin, I sent this last evening, but I haven't seen it
on-list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/09/12 16:12, Marja van Waes wrote:
Can you try doing systemctl show prefdm.service | grep
ActiveEnter.*Mono after a fresh boot.
I don't need to know the results, just whether it's non-zero or
still at 0.
Assuming it's still at zero,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/09/12 23:20, AL13N wrote:
Op woensdag 26 september 2012 20:57:43 schreef Anne Wilson:
On 26/09/2012 16:24, Jani Välimaa wrote:
On 26.09.2012 18:00, Anne Wilson wrote:
Colin, I sent this last evening, but I haven't seen it
on-list. For some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/09/12 09:40, Colin Guthrie wrote:
I pointed you at this mail in the archives when you were having
troubles, but I don't think you're replied to it to give the
necessary debug info.
Hi Colin. No, I had next to no time to spend on it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/09/12 10:15, Colin Guthrie wrote:
Does it work when forcing a runlevel 3 boot instead. This is
closer to a proper boot and likely a better testing environment. I
presume the getty's are showing for you in level 3?
To my surprise, the same,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/09/12 09:59, Anne Wilson wrote:
On 26/09/12 23:20, AL13N wrote:
this is normal behavior for gmail, it's why i stopped using it:
it works like this, if you are on a mailing list, and it ends up
at google, and you're using the gmail imap
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/09/12 13:31, Colin Guthrie wrote:
Oh I would disagree. I think intel is more common (but I base this
on very little evidence!) Certainly I *always* ensure I have an
intel card in anything I purchase. Their Open Source commitment is
just much
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/09/12 13:40, Anne Wilson wrote:
On 27/09/12 13:31, Colin Guthrie wrote:
Oh I would disagree. I think intel is more common (but I base
this on very little evidence!) Certainly I *always* ensure I have
an intel card in anything I purchase
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I often work with my netbook connected to a VGA monitor. The
Configure Display page shows
LVDS size 1280 x 720 (Auto)
VGA1 size 1024 x 768
Those settings look correct. The problem comes with the Primary
Output setting.
If I set LVDS as Primary
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/09/12 14:37, Colin Guthrie wrote:
Ahh a nice simple answer in the end!
I probably should have been more persistant in asking this question
initially (I think I did mention it in an earlier mail, but also
asked a whole bunch of other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/09/12 16:09, Thomas Backlund wrote:
Colin Guthrie skrev 27.9.2012 15:31:
'Twas brillig, and Anne Wilson at 27/09/12 11:02 did gyre and
gimble:
While the new reboot is completing, and while I remember -
irqbalance daemon always fails
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 01 Oct 2012 13:18:36 Guillaume Rousse wrote:
Le 22/09/2012 21:16, Anne Wilson a écrit :
udp0 0 *:nfs *:*
unfsd
Ouch... You're running an obsolete alternative nfs server. You
should uninstall
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/10/12 12:18, Guillaume Rousse wrote:
Le 22/09/2012 21:16, Anne Wilson a écrit :
udp0 0 *:nfs *:* unfsd
Ouch... You're running an obsolete alternative nfs server. You
should uninstall the unfs3 package
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/10/12 19:02, Guillaume Rousse wrote:
Le 01/10/2012 17:46, Anne Wilson a écrit :
The good news (after rebooting server and client) that the server
now is running nfs and nfs_acl
Over IPv4, or over IPv6 only as previously ?
The less good
Argh!! re-reading those lines, it's giving the IP address instead of the
mount point.
Garbage. Ignore.
I've obviously stared at this too long and I'm not making any sense at all
now.
Anne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/10/12 20:16, Anne Wilson wrote:
Argh!! re-reading those lines, it's giving the IP address
instead of the mount point.
Garbage. Ignore.
I've obviously stared at this too long and I'm not making any
sense at all now.
For a moment I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
GOT IT!!!
Remembered that you said it would mount as /, to which I don't have
access of course. I removed 'fsid=0', restarted, and all is well. I
can see all my data!
Thanks for your patience.
Anne
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/10/12 02:31, Colin Guthrie wrote:
'Twas brillig, and Guillaume Rousse at 01/10/12 21:41 did gyre and
gimble:
With NFSv4, the server remaps its actual filesystem (/home, for
instance) in a pseudo-filesystem, which is seen by clients as a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been away from Cauldron for a while, but trying to update today I get
The following packages have to be removed for others to be upgraded:
digikam-2.9.0-1.mga3.i586
(due to missing marble-common)
marble-4.9.1-1.mga3.i586
(due to missing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/10/12 13:21, Nicolas Lécureuil wrote:
Le lundi 8 octobre 2012 14:19:54 Nicolas Lécureuil a écrit :
Le lundi 8 octobre 2012 13:14:14 Anne Wilson a écrit :
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
I've been away from Cauldron
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/10/12 12:32, Thierry Vignaud wrote:
This is Mageia Linux, we don't care about other OSes, especially in
description
If one has to work in a Windows environment (or other, for that
matter) at times, then knowing that an application is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Earlier today I did a big update on Cauldron. Since then my wireless
connection has not been working. I started to gather information to
report this, but when I asked MCC for hardware detection I was
immediately told that broadcom-wl-kernel and two
Earlier today I did a big update on Cauldron. Since then my wireless
connection has not been working. I started to gather information to
report this, but when I asked MCC for hardware detection I was
immediately told that broadcom-wl-kernel and two other packages (one
was
On 29/10/2012 20:01, AL13N wrote:
Op maandag 29 oktober 2012 19:52:47 schreef Anne Wilson:
Earlier today I did a big update on Cauldron. Since then my wireless
connection has not been working. I started to gather information to
report this, but when I asked MCC for hardware detection I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/11/2012 09:15, Donald Stewart wrote:
On 8 November 2012 00:45, Johnny A. Solbu coo...@solbu.net
mailto:coo...@solbu.net wrote:
On Tuesday 06 November 2012 23:39, Shlomi Fish wrote:
Dear sirs or madams,
To me, this sounds a little to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/11/2012 10:03, Wolfgang Bornath wrote:
2012/11/8 Anne Wilson cannewil...@googlemail.com:
This is an official letter, and therefore should have the
official address to the recipient.
Consider using a more generinc term, like «Greetings
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/11/2012 10:52, Wolfgang Bornath wrote:
2012/11/8 Trish Fraser tr...@thefrasers.org:
Hi Donald and Johnny,
On Thu, 8 Nov 2012 09:15:09 + Donald Stewart
watersnowr...@gmail.com wrote:
On 8 November 2012 00:45, Johnny A. Solbu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been seeing this message every few minutes for the past week or
so (Cauldron on my netbook, BCM4313). It request a password, but no
indication of what password. I've tried the network password, the
root password and the user password. All I
I've been seeing this message every few minutes for the past week or
so (Cauldron on my netbook, BCM4313). It request a password, but no
indication of what password. I've tried the network password, the
root password and the user password. All I ever get is a minute's
delay, then the same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/11/12 17:42, Bo Lan wrote:
On Wed, 2012-11-14 at 17:14 +, Anne Wilson wrote:
I've been seeing this message every few minutes for the past
week or so (Cauldron on my netbook, BCM4313). It request a
password, but no indication of what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've added updates-testing to my sources, hoping to test HPLIP (which
hasn't offered me an update of that package yet). Most of the
proposed update installed, but it ended with
Installation failed:file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/11/12 17:42, Bo Lan wrote:
On Wed, 2012-11-14 at 17:14 +, Anne Wilson wrote:
I've been seeing this message every few minutes for the past
week or so (Cauldron on my netbook, BCM4313). It request a
password, but no indication of what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/11/2012 10:29, André Salaün wrote:
Hello !
Is it possible to reintroduce gnubiff in Mageia 3. All mail
checkers (in mga 2) depend on a wm. In kde they don't check the
mail spooler, only kmail, gmail, thunderbird etc. Gnubiff is more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/11/2012 13:39, Olav Vitters wrote:
You really like VLC :)
So do I :-) It plays whatever you throw at it. Not as pretty as
some, perhaps, but by heck, it works, and works everywhere :-)
Anne
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/11/2012 01:31, David W. Hodgins wrote:
On Wed, 21 Nov 2012 19:39:15 -0500, Richard Couture
r...@linuxcabal.org wrote:
I was looking at the Bose Companion 5 speaker system and noticed
that it intefaces with the computer via USB.
Am I
On 22/11/2012 01:31, David W. Hodgins wrote:
On Wed, 21 Nov 2012 19:39:15 -0500, Richard Couture r...@linuxcabal.org
wrote:
I was looking at the Bose Companion 5 speaker system and noticed that it
intefaces with the computer via USB.
Am I going to run into problems with Mageia if I buy it?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/11/2012 15:27, EatDirt wrote:
On 22/11/12 15:45, Michael Wood wrote:
Or if you happy to run rm as it was written and risk deleting
something you didn't want too, then comment out the alias (and
any others that get on your nerves:) ) from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After today's Cauldron update I find that my screen is locked
frequently, requiring my password to unlock it. Since I normally work
with two laptops at the same time - Cauldron and M2 - this is a huge
nuisance to me. Where can I change that setting?
1 - 100 of 148 matches
Mail list logo
