From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: how to use udev
Date: Sat, 03 Jan 2004 05:56:21 +0000 [thread overview]
Message-ID: <20040103055621.GB5306@kroah.com> (raw)
In-Reply-To: <3FF61CFA.2080501@mail.ru>
On Sat, Jan 03, 2004 at 05:54:24AM +0000, Roman Duka wrote:
>
> No Greg I don't get anything in /udev the script calls udev and there
> are no error messages or anything, however /udev is still empty I need
> to ask you a few questions:
Ick. You ran that as root, right?
Hm, try running the udev-test.pl script in that directory. Let us know
if the tests there pass or not. They should.
> - I compiled udev on Linux running kenel 2.4.20, however I am trying to
> get udev working on kernel 2.6.0 which has support for hot-pluggable
> devices and module loading/unloading enabled. I don't think I need to be
> running kernel 2.6.0 in order to just compile udev, am I correct here??
You are correct. You can build udev on any kernel. _but_ the test.all
script will _not_ show anything in /udev if you are not on a 2.6.0
kernel. That's probably the problem.
The udev-test.pl script will work on any kernel, it uses its own fake
sysfs tree.
> - I didn't switch my system to kernel 2.6.0 and udev, I am trying to
> test it within initrd (Initial Ram Disk), so what I have is a
> subdirectory in my home directory, where I installed busybox, bash,
> insmod, modprobe, hotplug scripts and udev, plus the needed shared
> libraries in /lib. Note I installed udev with the following command
> "make DESTDIR=mydir install" i.e. I didn't use "prefix" so all the
> config files etc should be relative to the root directory, and I've
> checked them, they're fine. I created a initrd and put it on a CD-RW
> disk and that's what I am booting from and testing udev. My question is,
> does running udev withing initrd make any impact on its operations?
It shouldn't. You built the klibc version, right?
> May be the reason why it doesn't work for me is because it has some
> issues in initrd environment???
Is sysfs mounted when udev is called? That's a requirement.
thanks,
greg k-h
-------------------------------------------------------
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 prev parent reply other threads:[~2004-01-03 5:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-03 1:38 how to use udev Roman Duka
2004-01-03 4:53 ` Greg KH
2004-01-03 5:54 ` Roman Duka
2004-01-03 5:56 ` Greg KH [this message]
2004-01-03 6:01 ` Jon Smirl
2004-01-03 6:10 ` Roman Duka
2004-01-03 6:18 ` Roman Duka
2004-01-03 6:26 ` Roman Duka
2004-01-03 6:31 ` Jon Smirl
2004-01-03 6:39 ` Roman Duka
2004-01-03 6:55 ` Roman Duka
2004-01-03 6:58 ` Greg KH
2004-01-03 7:00 ` 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=20040103055621.GB5306@kroah.com \
--to=greg@kroah.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).