linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@yahoo.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev for /dev
Date: Fri, 20 Feb 2004 17:38:32 +0000	[thread overview]
Message-ID: <20040220173832.2346.qmail@web14914.mail.yahoo.com> (raw)
In-Reply-To: <20040220062015.85721.qmail@web14907.mail.yahoo.com>

--- Marco d'Itri <md@Linux.IT> wrote:
> On Feb 20, Jon Smirl <jonsmirl@yahoo.com> wrote:
> 
>  >More missing devices, /dev/aumix, /dev/dsp. These are from the OSS
> compatibility
>  >layer in ALSA.
> 
> You need to configure module-init-tools to automatically load
> snd_{pcm,mixer}_oss after snd_{pcm,mixer} are loaded.

I have these modules loaded. OSS compatibily was working before I switched to
udev for /dev. The problem is that these modules don't export their devices
under /sys so udev doesn't make device nodes for them.

I'm missing three classes of devices so far:
1) ALSA OSS compatibilty
2) floppies
3) sitX, network tunnel

The script for recreating /dev is in /dev called MAKEDEV. I couldn't find it
because udev was masking /dev.

I used the gentoo permission file. It has enough permissions in it that Fedora
will work. There probably needs to be a specific one built for Fedora.

I've also checked that you can boot with a single console device in /dev.
mknod /dev/console c 5 1


==Jon Smirl
jonsmirl@yahoo.com

__________________________________
Do you Yahoo!?
Yahoo! Mail SpamGuard - Read only the mail you want.
http://antispam.yahoo.com/tools


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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

  parent reply	other threads:[~2004-02-20 17:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-20  6:20 udev for /dev Jon Smirl
2004-02-20  6:26 ` Jon Smirl
2004-02-20 16:19 ` Jon Smirl
2004-02-20 16:36 ` John L Fjellstad
2004-02-20 16:50 ` Frédéric L. W. Meunier
2004-02-20 16:58 ` Frédéric L. W. Meunier
2004-02-20 17:13 ` Marco d'Itri
2004-02-20 17:38 ` Jon Smirl [this message]
2004-02-20 17:39 ` Marco d'Itri
2004-02-20 17:49 ` Jon Smirl
2004-02-20 19:25 ` Mike Frysinger
2004-02-20 21:41 ` Jon Smirl
2004-02-20 22:06 ` Jon Smirl
2004-02-23  7:37 ` mjl
2004-02-26  6:10 ` Jon Smirl
2004-02-28  0:32 ` 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=20040220173832.2346.qmail@web14914.mail.yahoo.com \
    --to=jonsmirl@yahoo.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).