From: Virgil Anderson <vda@earthlink.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: trying 068 with Gentoo
Date: Sat, 29 Jul 2006 02:49:56 +0000 [thread overview]
Message-ID: <loom.20060729T034719-54@post.gmane.org> (raw)
In-Reply-To: <200508312302.39102.bobb@absamail.co.za>
Greg KH <greg <at> kroah.com> writes:
>
> On Wed, Aug 31, 2005 at 11:02:39PM +0200, Bob Barry wrote:
> > I installed udev-068 on Gentoo, installed the new /etc/udev/udev.conf
> > and /etc/udev/rules.d/50-udev.rules, and restarted with kernel 2.6.13.
>
> You forgot to mention that you ignored the ewarn messages that the 068
> gentoo release stated that explained how to fix this problem.
>
> Also, this isn't a Gentoo specific mailing list, if you have Gentoo
> specific problems with udev (like this) please enter a bug into their
> bugzilla system (bugs.gentoo.org)
>
> thanks,
>
> greg k-h
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
>
Actually greg k-h,
This is NOT a gentoo specific problem ... it's a udev / agetty / openvt problem.
It appears to occur when you move completely away from devfs, such that udevd is
generating all /dev entries. The problem is /dev/vc/%d and /dev/tty are
hardcoded into programs in the kbd and util-linux packages. For whatever reason
udev does not properly populate these devices in /dev no mater what you put in
the control statements - probably because the console is pre-existing when udevd
comes up. There are a number of fixes floating around, none of which really
work to my satisfaction. One is to have a /lib/dev space for pre-existing
devices and then copy it to /dev. Personally, I would have the software tell
udevd that device entries are needed, and udevd respond by inserting the
requested virtual device or whatever into /dev. If such a mechanism is
available it certainly is not being used, or well documented.
Virgil Anderson.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2006-07-29 2:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 21:02 trying 068 with Gentoo Bob Barry
2005-09-01 1:55 ` Greg KH
2006-07-29 2:49 ` Virgil Anderson [this message]
2006-07-30 5:52 ` Greg KH
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=loom.20060729T034719-54@post.gmane.org \
--to=vda@earthlink.net \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).