From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevstart problem
Date: Mon, 08 Nov 2004 19:36:53 +0000 [thread overview]
Message-ID: <1099942613.8789.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20041107140753.GB1722@schottelius.org>
On Sun, 2004-11-07 at 15:07 +0100, Nico Schottelius wrote:
> Hello!
>
> I am trying to use udev with an empty /dev.
>
> It works more or less good, when mounting /sys and then
> runnig udevstart. But udevstart does not produce
> /dev/null nor /dev/urandom.
>
> Is that a bug or is it wanted that I create/mknod them myself?
It should be created by udevstart. What does:
[kay@pim ~]$ udevtest /class/mem/null
version 043
looking at '/class/mem/null'
parse error /etc/udev/rules.d/50-udev.rules, line 76:31, rule skipped
configured rule in '/etc/udev/rules.d/50-udev.rules' at line 49 applied, added symlink 'XOR'
creating device node '/dev/null', major = '1', minor = '3', mode = '020666', uid = '0', gid = '0'
print for you?
Kay
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&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-11-08 19:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 14:07 udevstart problem Nico Schottelius
2004-11-07 14:37 ` Marco d'Itri
2004-11-08 12:41 ` Nico Schottelius
2004-11-08 17:20 ` Marco d'Itri
2004-11-08 19:36 ` Kay Sievers [this message]
2004-11-08 21:26 ` Nico Schottelius
2004-11-09 21:39 ` Nico Schottelius
2004-11-10 0:06 ` Kay Sievers
2004-11-10 6:41 ` Nico Schottelius
2004-11-10 9:37 ` Marco d'Itri
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=1099942613.8789.10.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--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).