public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] problems with udev
Date: Thu, 14 Jul 2005 18:24:54 +0100	[thread overview]
Message-ID: <42D69FE6.4030009@gentoo.org> (raw)
In-Reply-To: <200507141251.41218.volker.armin.hemmann@tu-clausthal.de>

Volker Armin Hemmann wrote:
> I switched last night from devfs to udev and had the same kde problem.
> I solved it by running udevstart as root. Oh, and I checked the permissions 
> file in /etc/udev

If running 'udevstart' fixes your ownership/permissions problem, try logging
in again and see if the problem reappears. If it does, then it means something
is running on login and imposing its own permissions. This is probably pam,
which you'll want to turn off.

Daniel
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-07-14 17:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-14  9:07 [gentoo-user] problems with udev renna
2005-07-14 10:51 ` Volker Armin Hemmann
2005-07-14 17:24   ` Daniel Drake [this message]
2005-07-14 10:52 ` Sean Higgins
2005-07-14 12:41   ` Dirk Heinrichs
2005-07-19  0:23     ` Neil Bothwick
2005-07-14 13:12   ` renna

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42D69FE6.4030009@gentoo.org \
    --to=dsd@gentoo.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox