From: Ilja Honkonen <ilja.honkonen@helsinki.fi>
To: linux-hotplug@vger.kernel.org
Subject: [N00B] Need a dvb device in udev
Date: Fri, 26 Mar 2004 10:33:00 +0000 [thread overview]
Message-ID: <406406DC.9070804@helsinki.fi> (raw)
Hi all
I've been thinking about making udev handle the device nodes in my
newest computer, but I'd like udev to create the following devices
before I switch to it:
dvb
`-- adapter0
|-- demux0
|-- dvr0
`-- net0
Should I complain about this on the linux-tv mailing list? When can I
expect to see udev create these nodes?
There are couple of more devices in /dev which are not created in /udev
but I don't know if I need these:
gpmctl
initctl
nvidia0
nvidiactl
pts
`-- 0
tts
|-- 0
|-- 1
|-- 2
|-- 3
|-- 4
|-- 5
|-- 6
`-- 7
vc
|-- 0
|-- 1
|-- 10
|-- 11
|-- 12
|-- 13
|-- 14
|-- 15
|-- 16
|-- 17
|-- 18
|-- 19
|-- 2
.
.
.
vcc
|-- 0
|-- 1
|-- 2
|-- 3
|-- 4
|-- 5
|-- 6
|-- 7
|-- a0
|-- a1
.
.
.
Do I need the nvidia* files? I'm using their IA32 driver version 1.0-5336.
Thanks.
Ilja
-------------------------------------------------------
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 reply other threads:[~2004-03-26 10:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 10:33 Ilja Honkonen [this message]
2004-03-26 23:02 ` [N00B] Need a dvb device in udev Greg KH
2004-03-26 23:22 ` Marco d'Itri
2004-03-26 23:34 ` Greg KH
2004-03-26 23:40 ` Marco d'Itri
2004-03-28 7:19 ` 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=406406DC.9070804@helsinki.fi \
--to=ilja.honkonen@helsinki.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.