From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: temporarily disabling udev
Date: Sun, 19 Dec 2004 16:09:05 +0000 [thread overview]
Message-ID: <1103472545.5746.163.camel@localhost.localdomain> (raw)
In-Reply-To: <20041219145616.GA8975@wonderland.linux.it>
On Sun, 2004-12-19 at 16:43 +0100, Marco d'Itri wrote:
> On Dec 19, Kay Sievers <kay.sievers@vrfy.org> wrote:
>
> > > I need to patch udev to be sure that it will not modify /dev if
> > > udevstart has been not been run (e.g. because root disabled the
> > > init script, or it failed for some reason).
> > > Would this work?
> > Removing the database, should not prevent the next udev run to create
> > one.
> Do you have other suggestions?
No, not really. I just see problems with the patch in the upstream
version, cause of the numerous setups udev is used.
> > udev is used in initrd with /proc/sys/kernel/hotplug set
> > to /sbin/udev in some setups, which will not work with this patch.
> Why they do not run udevstart?
They want to use the device nodes after module load. At the time
udevstart would run, there may not all modules be loaded.
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
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-12-19 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 14:56 temporarily disabling udev Marco d'Itri
2004-12-19 15:32 ` Kay Sievers
2004-12-19 15:43 ` Marco d'Itri
2004-12-19 16:09 ` Kay Sievers [this message]
2004-12-19 16:58 ` 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=1103472545.5746.163.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.