From: "Marco d'Itri" <md@Linux.IT>
To: linux-hotplug@vger.kernel.org
Subject: starting with an empty /dev
Date: Fri, 13 Feb 2004 10:24:34 +0000 [thread overview]
Message-ID: <20040213102434.GA3991@wonderland.linux.it> (raw)
IIRC initramfs already contains these devices, but anyway it's important
to remember that if they are removed everything will break.
Should we start thinking about how udev could be used in the real world?
----- Forwarded message from mat@nask.pl -----
From: mat@nask.pl
To: Marco d'Itri <md@Linux.IT>
Subject: Re: [udev] howto
On Wed, 4 Feb 2004, Marco d'Itri wrote:
> On Feb 04, mat@nask.pl wrote:
>
> >Can You please explain me how to do it? Or point me to some link where it is
> You don't. Currently udev is experimental and uses /udev to not mess
> with your system. If you feel brave then make a symlink from /dev.
Maybe you dont care but I have installed udev and it is working for me great.
But there were some problems.
I have found that devices:
/dev/null,
/dev/console
are needed befode /etc/init.d/udev starts (/etc/rcS.d/S37udev) so I twisted
the init script not to remove those file during shutdown, and to create it
during booting only if needed.
I didnt know where should I send this thing (maybe this is only my problem) but
I use your debs so I am sending it to you.
Bye
-mat
This is the patch:
--- ./orig/udev 2004-02-03 22:23:02.000000000 +0100
+++ /etc/init.d/udev 2004-02-12 08:45:26.000000000 +0100
@@ -28,7 +28,19 @@
export DEVPATH=${j#/sys}
class=${DEVPATH#/class/}
class=${class%/*}
-# echo -n " $DEVPATH($class)"
+
+ special=${DEVPATH#/class/}
+ special=${special#$class/}
+ case "$special" in
+ null | console)
+ [ -c "/dev/$special" ] && continue
+ echo "/dev/$special included."
+ ;;
+ *)
+ #echo "$special -> udev."
+ ;;
+ esac
+ #echo -n " $DEVPATH($class)"
{ $UDEV $class || echo -n " failed: $DEVPATH"; } &
done
done
@@ -62,7 +74,7 @@
[ -d /udev ] || mkdir /udev
mount_sysfs
export ACTIONd
- echo -n "Creating initial udev device nodes..."
+ echo "Creating initial udev device nodes..."
synthesize_events
make_extra_nodes
echo "done."
>
> --
> ciao, |
> Marco | [4460 diQvhSSO5SlHk]
>
-mat
----- End forwarded message -----
--
ciao, |
Marco | [4582 ig78KWqxlsXk.]
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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:[~2004-02-13 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 10:24 Marco d'Itri [this message]
2004-02-13 17:58 ` starting with an empty /dev Mike Frysinger
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=20040213102434.GA3991@wonderland.linux.it \
--to=md@linux.it \
--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).