From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev 024 and missing virtual consoles
Date: Wed, 14 Apr 2004 19:13:09 +0000 [thread overview]
Message-ID: <20040414191309.GA7387@kroah.com> (raw)
In-Reply-To: <1081711157.7840.12.camel@parents>
On Mon, Apr 12, 2004 at 11:26:15PM -0400, Todd Musall wrote:
> Greg,
>
> Instead I used this rule to create /dev/vc/[0-9] symlinks:
>
> KERNEL="tty[0-9]", NAME="%k", SYMLINK="vc/%m"
>
> Works like a charm.
>
> I've almost got udev completely working. My last issue is with LIRC.
> The device node /dev/lirc0 isn't being created. I'm using a patched
> LIRC version for 2.6 kernels and on devfs everything works fine. I
> haven't had time to debug it further but wondered if anyone else has got
> LIRC working with udev?
Odds are lirc code needs to be patched to work with sysfs. Does anyone
know why the lirc code is not in the mainline kernel? I can't seem to
be able to connect to the site that holds their 2.6 kernel patch...
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
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:[~2004-04-14 19:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-11 19:19 udev 024 and missing virtual consoles Todd Musall
2004-04-12 3:03 ` Todd Musall
2004-04-12 19:18 ` Greg KH
2004-04-13 3:26 ` Todd Musall
2004-04-14 19:13 ` Greg KH [this message]
2004-04-14 19:58 ` Olivier Mehani
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=20040414191309.GA7387@kroah.com \
--to=greg@kroah.com \
--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).