public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bob <recbo@nishanet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: udev for dummies
Date: Thu, 11 Dec 2003 23:43:36 -0500	[thread overview]
Message-ID: <3FD94778.2020606@nishanet.com> (raw)
In-Reply-To: <1071183521.5900.36.camel@dhollis-lnx.kpmg.com>

David T Hollis wrote:

>On Thu, 2003-12-11 at 17:16, J.A. Magallon wrote:
>  
>
>>Hi all...
>>
>>I am starting to use 2.6, and I really would like to use udev.
>>But I can't find a doc about how to move from taditional heavily
>>populated /dev to new method.
>>
>>Any pointer ?
>>
Do you may mean heavily **over-populated**
/dev? Learning more about devfs would make it
easier to transition to udev. I'm going through this
now for myself.

You could learn how to strip out non-existent
devices from /dev by using
 /etc/devfs/compat_symlinks
by using regular expressions there to make symlinks
for standard device names like udev uses but only
permit devfsd to make device entries for devices
you have on your system.

Here is my /etc/devfs/compat_symlinks. At the
top I don't use anything but devfs naming, then
at the bottom I add a few symlinks both to limit
naming to real devices(see md*) and to make
conventional sd* hd* to make transition to
udev simpler.

-Bob

# Enable full compatibility mode for old device names. You may comment these
# out if you don't use the old device names. Make sure you know what you're
# doing!
#########REGISTER	.*		MKOLDCOMPAT
UNREGISTER	.*		RMOLDCOMPAT

# You may comment out the above and uncomment the following if you've
# configured your system to use the original "new" devfs names or the really
# new names
#####REGISTER	^vc/.*		MKOLDCOMPAT
UNREGISTER	^vc/.*		RMOLDCOMPAT
#####REGISTER	^pty/m0  	MKOLDCOMPAT
######REGISTER	^pty/s0  	MKOLDCOMPAT
UNREGISTER	^pty/.*		RMOLDCOMPAT
######REGISTER	^misc		MKOLDCOMPAT
UNREGISTER	^misc		RMOLDCOMPAT

# You may comment these out if you don't use the original "new" names
######REGISTER	.*		MKNEWCOMPAT
UNREGISTER	.*		RMNEWCOMPAT

# Create compatibility links for broken USB serial driver
REGISTER	^usb/tts/([0-9]+) CFUNCTION GLOBAL symlink $devname ttyUSB\1
#######UNREGISTER	^usb/tts/([0-9]+) CFUNCTION GLOBAL unlink ttyUSB\1

# Create compatibility link for broken misc/net/tun driver (must uncomment the
# MKOLDCOMPAT for misc above if you want to use this)
######REGISTER	^misc/net/tun$	CFUNCTION GLOBAL unlink   net/tun
######REGISTER	^misc/net/tun$	CFUNCTION GLOBAL symlink  /dev/$devname net/tun

# Bob removes non-existent /dev/md's, adds old conventional devices
# to aid transition to udev as this percolates through /etc/init.d
# scripts for fsck and mount--
REGISTER	^md/[0-4]		             MKOLDCOMPAT
UNREGISTER	^md/[5-9][0-9]*	                     RMOLDCOMPAT
REGISTER        ^ide/host[0-2]/.*                    MKOLDCOMPAT
REGISTER        ^scsi/host[0-2]/bus0/target[0-3]/.*  MKOLDCOMPAT
REGISTER        ^snd/.*                              MKOLDCOMPAT
REGISTER        ^sound/.*                            MKOLDCOMPAT
REGISTER        ^misc/rtc                            MKOLDCOMPAT






  parent reply	other threads:[~2003-12-12  4:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-11 22:16 udev for dummies J.A. Magallon
2003-12-11 22:59 ` David T Hollis
2003-12-12  2:49   ` Chris Friesen
2003-12-12 21:32     ` Greg KH
2003-12-12  4:43   ` Bob [this message]
2003-12-12 21:31 ` Greg KH
2003-12-14 18:36   ` Martin Schlemmer

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=3FD94778.2020606@nishanet.com \
    --to=recbo@nishanet.com \
    --cc=linux-kernel@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