summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--README10
-rw-r--r--etc/udev/udev-devfs.rules2
-rw-r--r--extras/dvb.sh3
-rw-r--r--extras/inputdev.sh30
-rw-r--r--extras/name_cdrom.pl7
-rw-r--r--extras/start_udev102
6 files changed, 10 insertions, 144 deletions
diff --git a/README b/README
index fe56095686..9e1aae3452 100644
--- a/README
+++ b/README
@@ -36,11 +36,13 @@ Operation:
a tmpfs filesystem mounted, which is populated from scratch by udev.
Created nodes or changed permissions don't survive a reboot.
- - The content of /lib/udev/devices directory should be copied over to the
- tmpfs mounted /dev, to provide the required nodes to initialize udev.
+ - The content of /lib/udev/devices directory which contains the nodes,
+ symlinks and directories, which are always expected to be in/dev, should
+ be copied over to the tmpfs mounted /dev, to provide the required nodes
+ to initialize udev and continue booting.
- - The udevd daemon must be started to receive netlink events from the kernel
- driver core.
+ - The udevd daemon must be started by an init script to receive netlink
+ events from the kernel driver core.
- From kernel version 2.6.15 on, the hotplug helper /sbin/hotplug should
be disabled with an init script before the boot scripts are run and
diff --git a/etc/udev/udev-devfs.rules b/etc/udev/udev-devfs.rules
index 380bbee85b..ec44692d68 100644
--- a/etc/udev/udev-devfs.rules
+++ b/etc/udev/udev-devfs.rules
@@ -2,7 +2,7 @@
# is just kept around to proof that udev is able to emulate the devfs scheme.
#
# In a world where devices can come and go at any time, the devfs device
-# naming scheme of simple grouping and enumeration does not help _anything_.
+# naming scheme of simple grouping and enumeration DOES NOT HELP ANYTHING.
#
# Use custom rules to name your device or look at the persistent device
# naming scheme, which is implemented for disks and extend it in a
diff --git a/extras/dvb.sh b/extras/dvb.sh
deleted file mode 100644
index b14a6d0d7b..0000000000
--- a/extras/dvb.sh
+++ /dev/null
@@ -1,3 +0,0 @@
-#!/bin/sh -e
-echo $1 | sed -e 's#^dvb\([0-9]\)\.\([^0-9]*\)\([0-9]\)#dvb/adapter\1/\2\3#'
-exit 0
diff --git a/extras/inputdev.sh b/extras/inputdev.sh
deleted file mode 100644
index 82e4fdc374..0000000000
--- a/extras/inputdev.sh
+++ /dev/null
@@ -1,30 +0,0 @@
-#!/bin/sh -e
-#
-# Scans /proc/bus/input/devices for the given device.
-#
-# (c) 2004 Darren Salt <linux@youmustbejoking.demon.co.uk>
-# GPL v2 or later applies.
-
-[ "$1" ] || exit 0
-
-# input device name, less leading "input/"
-DEVICE=${1#input/}
-
-# "|"-separated list.
-# The first found in the given device's "N:" line will be output.
-DEFAULT_KEYWORDS='dvb|saa7134'
-KEYWORDS=${2:-$DEFAULT_KEYWORDS}
-
-exec sed -nre '
- /^I:/ {
- : gather
- N
- /\nH:/! b gather
- /'"$DEVICE"'/ {
- s/^.*\nN:[^\n]*("|\b)('"$KEYWORDS"')("|\b)[^\n]*\n.*$/inputdev/
- T
- p
- }
- }
-' < /proc/bus/input/devices
-
diff --git a/extras/name_cdrom.pl b/extras/name_cdrom.pl
index 5e696f33ae..28d2d29a3d 100644
--- a/extras/name_cdrom.pl
+++ b/extras/name_cdrom.pl
@@ -1,9 +1,8 @@
#!/usr/bin/perl
-# a horribly funny script that shows how flexible udev can really be
-# This is to be executed by udev with the following rules:
-#
-# KERNEL="hd*[!0-9]|sr*", PROGRAM="name_cdrom.pl $tempnode", SYMLINK+="%c"
+# Horrible but funny script that shows how flexible udev can really be
+# This is to be executed by udev with the following rule:
+# KERNEL="hd*[!0-9]|sr*", PROGRAM="name_cdrom.pl $tempnode", SYMLINK+="%c"
use strict;
use warnings;
diff --git a/extras/start_udev b/extras/start_udev
deleted file mode 100644
index c2518761e3..0000000000
--- a/extras/start_udev
+++ /dev/null
@@ -1,102 +0,0 @@
-#! /bin/sh
-#
-# start_udev
-#
-# script to initialize /dev by using udev.
-#
-# Copyright (C) 2004 Greg Kroah-Hartman <greg@kroah.com>
-#
-# Released under the GPL v2 only.
-#
-# This needs to be run at the earliest possible point in the boot
-# process.
-#
-# Based on the udev init.d script
-#
-# Thanks go out to the Gentoo developers for proving
-# that this is possible to do.
-#
-# Yes, it's very verbose, feel free to turn off all of the echo calls,
-# they were there to make me feel better that everything was working
-# properly during development...
-#
-
-. /etc/udev/udev.conf
-
-prog=udev
-sysfs_dir=/sys
-bin=/sbin/udev
-udevd=/sbin/udevd
-
-run_udev () {
- export ACTION=add
-
- # handle block devices and their partitions
- for i in ${sysfs_dir}/block/*; do
- # add each drive
- export DEVPATH=${i#${sysfs_dir}}
- echo "$DEVPATH"
- $bin block
-
- # add each partition, on each device
- for j in $i/*; do
- if [ -f $j/dev ]; then
- export DEVPATH=${j#${sysfs_dir}}
- echo "$DEVPATH"
- $bin block
- fi
- done
- done
- # all other device classes
- for i in ${sysfs_dir}/class/*; do
- for j in $i/*; do
- if [ -f $j/dev ]; then
- export DEVPATH=${j#${sysfs_dir}}
- CLASS=`echo ${i#${sysfs_dir}} | \
- cut --delimiter='/' --fields=3-`
- echo "$DEVPATH"
- $bin $CLASS
- fi
- done
- done
- return 0
-}
-
-make_extra_nodes () {
- # there are a few things that sysfs does not export for us.
- # these things go here (and remember to remove them in
- # remove_extra_nodes()
- #
- # Thanks to Gentoo for the initial list of these.
- ln -snf /proc/self/fd $udev_root/fd
- ln -snf /proc/self/fd/0 $udev_root/stdin
- ln -snf /proc/self/fd/1 $udev_root/stdout
- ln -snf /proc/self/fd/2 $udev_root/stderr
- ln -snf /proc/kcore $udev_root/core
-
- mkdir $udev_root/pts
- mkdir $udev_root/shm
-}
-
-# don't use udev if sysfs is not mounted.
-if [ ! -d $sysfs_dir/block ]; then
- exit 1
-fi
-
-echo "mounting... ramfs at $udev_root"
-mount -n -t ramfs none $udev_root
-
-# propogate /udev from /sys
-echo "Creating initial udev device nodes:"
-
-# You can use the shell scripts above by calling run_udev or execute udevstart
-# which does the same thing, but much faster by not using shell.
-# only comment out one of the following lines.
-#run_udev
-/sbin/udevstart
-
-echo "making extra nodes"
-make_extra_nodes
-
-echo "udev startup is finished!"
-exit 0