From: Tupshin Harper <tupshin@tupshin.com>
To: linux-hotplug@vger.kernel.org
Subject: initial udev foray...successes and failures...
Date: Thu, 18 Dec 2003 09:13:27 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107173885409205@msgid-missing> (raw)
As a long time devfs user and MAKEDEV hater(mostly for aesthetic
reason), I decided to bite the bullet and see how close to usable udev is.
The platform:
Debian Sid
kernel 2.6.0-test11+
hotplug that comes with sid
udev 0.009 built for debian downloaded from: http://www.bofh.it/~md/debian/
The scenario:
the Debian udev package creates everything in /udev. I moved /dev out of
the way, symlinked /udev to /dev and rebooted (ahhh...glorious optimism).
What worked:
Most things, including (to my surprise) lvm2 which had been running on
the devfs setup.
What didn't:
1) anything that needed /dev/null
2) anything that needed /dev/random (and probably urandom...didn't check)
3) anything other that single user mode, since /dev/tty[0-9] were not
present ..just /dev/tty
What was odd:
I have a number of ide hard drives in this machine(9). The first two
(hda, and hdb) and their partitions showed up as symlinks to
/dev/ide/host0/etc... The rest of them were not symlinks and were placed
directly in /dev (e.g. /dev/hde and /dev/hde3).
Despite these oddities, I was able to manually create /dev/null,
/dev/random, and /dev/tty[0-9] and everything on my machine worked.
So...given the limited information that seems to be available for udev,
I have a few questions:
1) should the missing devices be created by udev? Is this a [known] problem?
2) Why are some drives symlinked and others not?
3) Does it make sense that the debian package operates on /udev and I'm
testing it by creating a symlink to /dev? If not, how should things be done?
-Tupshin
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&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:[~2003-12-18 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 9:13 Tupshin Harper [this message]
2003-12-22 20:39 ` initial udev foray...successes and failures Greg KH
2003-12-22 22:41 ` Tupshin Harper
2003-12-23 0:16 ` Greg KH
2003-12-23 1:05 ` Tupshin Harper
2003-12-23 1:09 ` Greg KH
2003-12-23 1:36 ` Tupshin Harper
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=marc-linux-hotplug-107173885409205@msgid-missing \
--to=tupshin@tupshin.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).