-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Man Shankar wrote:
Mark Haney wrote:
This may be a n00b question, but how the heck do I get KDE 4.2 to start?
I've edited /etc/rc.conf to XESSSION=kde-4.2 and that didn't work. I
don't think I hhad to edit /etc/conf.d/xdm last time since it was
Здравствуйте, ABCD.
Вы писали 4 февраля 2009 г., 12:03:56:
A -BEGIN PGP SIGNED MESSAGE-
A Hash: SHA1
A Man Shankar wrote:
Mark Haney wrote:
This may be a n00b question, but how the heck do I get KDE 4.2 to start?
I've edited /etc/rc.conf to XESSSION=kde-4.2 and that didn't work. I
Tom wrote:
Aren't you contradicting yourself here?
I don't mean to be rude, but you've managed to confuse me ;)
Okay, hang on. Let's see if we can straighten this out.
But isn't there always, in any case a filesystem? Which completely or in
parts gets encrypted/decrypted by the encryption
Осипов Станислав wrote:
Здравствуйте, ABCD.
Вы писали 4 февраля 2009 г., 12:03:56:
A -BEGIN PGP SIGNED MESSAGE-
A Hash: SHA1
A Man Shankar wrote:
Mark Haney wrote:
This may be a n00b question, but how the heck do I get KDE 4.2 to start?
I've edited /etc/rc.conf to
Здравствуйте, Mark.
By the way these days XSESSION is set in
/etc/env.d/90xsession
and do env-update, but that only controls startx behaviour. I missed the
kdm
part as well. With xdm initscript failing I had to set
DISPLAYMANAGER=kdm-4.2
in /etc/conf.d/xdm
A For those of you
Mark Haney wrote:
I set DISPLAYMANAGER=kdm-4.2 in /etc/conf.d/xdm and while I got a
different background screen on the login, it still logged into 4.1.
AHA!! I think I have a suggestion that may just work. In the kdm login
screen, down near the bottom toward the right side is a
Stan Sander wrote:
AHA!! I think I have a suggestion that may just work. In the kdm login
screen, down near the bottom toward the right side is a Session menu.
click on this and select KDE 4.2 as your session. By default, this is
set to your previous session, which is obviously KDE 4.1
Recently my AMD64 machine has started displaying this message at boot
time. I don't know exactly when it started but I suspect it was when I
started testing a new kernel that didn't have the RTC enabled when I
was first testing it.
Anyway, what's the process of fixing this. It says it's 'fixed'
Mark Haney wrote:
Stan Sander wrote:
AHA!! I think I have a suggestion that may just work. In the kdm login
screen, down near the bottom toward the right side is a Session menu.
click on this and select KDE 4.2 as your session. By default, this is
set to your previous session, which is
Mark Knecht markkne...@gmail.com skribis:
Subject: [gentoo-amd64] Superblock last mount time is in the future. FIXED
but it isn't...
From: Mark Knecht markkne...@gmail.com
Reply-to: gentoo-amd64@lists.gentoo.org
Date: Wed, 4 Feb 2009 10:05:54 -0800
To: gentoo-amd64@lists.gentoo.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Knecht escreveu:
Recently my AMD64 machine has started displaying this message at
boot time. I don't know exactly when it started but I suspect it
was when I started testing a new kernel that didn't have the RTC
enabled when I was first
On Wed, Feb 4, 2009 at 10:47 AM, Barry Schwartz
chemoelect...@chemoelectric.org wrote:
Mark Knecht markkne...@gmail.com skribis:
Subject: [gentoo-amd64] Superblock last mount time is in the future. FIXED
but it isn't...
From: Mark Knecht markkne...@gmail.com
Reply-to:
On Wed, Feb 4, 2009 at 10:49 AM, Zhu Sha Zang zhushaz...@yahoo.com.br wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Knecht escreveu:
Recently my AMD64 machine has started displaying this message at
boot time. I don't know exactly when it started but I suspect it
was when I
Mark Knecht markkne...@gmail.com skribis:
On Wed, Feb 4, 2009 at 10:47 AM, Barry Schwartz
chemoelect...@chemoelectric.org wrote:
You can get that message if you have the HW clock set to local time.
In my case it must be local (AFAIK) as I'm dual boot with a Windows XP
installation.
I
Does that make sense?
Yes indeed! :)
I'm no longer confused. Those examples made it quite clear what you
meant.
Thanks for explaining
Tom
I only ever see that message when my system goes out to lunch an I have
to hit the big switch to reset it.
I get it once, then fschk does its magic, and all is good.
I also once built my kernel without rtc support by mistake, and I then
also got that message + a message complaining it couldn't
Stan Sander wrote:
Mark Haney wrote:
I set DISPLAYMANAGER=kdm-4.2 in /etc/conf.d/xdm and while I got a
different background screen on the login, it still logged into 4.1.
AHA!! I think I have a suggestion that may just work. In the kdm login
screen, down near the bottom toward the
On Wed, Feb 4, 2009 at 12:30 PM, Tom uebersh...@googlemail.com wrote:
I only ever see that message when my system goes out to lunch an I have
to hit the big switch to reset it.
I get it once, then fschk does its magic, and all is good.
I also once built my kernel without rtc support by
Mark Haney wrote:
Yep. That was it. Man, am I an idiot. Yet another case of me
overthinking a problem.
Don't be too hard on yourself. It never occurred to me either until you
stated you got a different background after setting DISPLAYMANAGER, but
still logged into kde 4.1 That's
On Sat, Jan 31, 2009 at 12:28 PM, Tom uebersh...@googlemail.com wrote:
Hi List,
Doesn't really belong here, but security seems dead, so...
I'm planning on encrypting a 1TB usb-disc that I have, for
preserved storage.
I've been reading a lot about fde and the other various
approaches
On Wed, Feb 4, 2009 at 12:05 PM, Mark Knecht markkne...@gmail.com wrote:
Recently my AMD64 machine has started displaying this message at boot
time. I don't know exactly when it started but I suspect it was when I
started testing a new kernel that didn't have the RTC enabled when I
was first
On Wed, Feb 4, 2009 at 2:09 PM, Paul Hartman
paul.hartman+gen...@gmail.com wrote:
On Wed, Feb 4, 2009 at 12:05 PM, Mark Knecht markkne...@gmail.com wrote:
Recently my AMD64 machine has started displaying this message at boot
time. I don't know exactly when it started but I suspect it was when I
On Wed, Feb 4, 2009 at 4:51 PM, Mark Knecht markkne...@gmail.com wrote:
On Wed, Feb 4, 2009 at 2:09 PM, Paul Hartman
paul.hartman+gen...@gmail.com wrote:
On Wed, Feb 4, 2009 at 12:05 PM, Mark Knecht markkne...@gmail.com wrote:
Recently my AMD64 machine has started displaying this message at
On Wed, Feb 4, 2009 at 3:00 PM, Paul Hartman
paul.hartman+gen...@gmail.com wrote:
On Wed, Feb 4, 2009 at 4:51 PM, Mark Knecht markkne...@gmail.com wrote:
On Wed, Feb 4, 2009 at 2:09 PM, Paul Hartman
paul.hartman+gen...@gmail.com wrote:
On Wed, Feb 4, 2009 at 12:05 PM, Mark Knecht
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Hartman wrote:
On Wed, Feb 4, 2009 at 5:46 PM, Mark Knecht wrote:
On Wed, Feb 4, 2009 at 3:00 PM, Paul Hartman wrote:
On Wed, Feb 4, 2009 at 4:51 PM, Mark Knecht wrote:
On Wed, Feb 4, 2009 at 2:09 PM, Paul Hartman wrote:
On Wed, Feb 4, 2009
25 matches
Mail list logo
