From: MALET JL <malet.jean-luc@laposte.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug
Date: Fri, 27 Feb 2004 16:43:46 +0000 [thread overview]
Message-ID: <403F73C2.1030406@laposte.net> (raw)
In-Reply-To: <marc-linux-hotplug-106906141231187@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
Philip MacIver a écrit :
>I've just read something that may be causing my
>problem with udev, and I would just like to confirm
>this before I actually go ahead and do any changes.
>
>Running "/proc/sys/kernel/hotplug" on my system prints
>out "/bin/true", I've read that to change this you do
>echo "/sbin/hotplug" > /proc/sys/kernel/hotplug.
>
>But what I want to know is, is this the reason that my
>linux system won't boot up when I try and use udev
>with /dev as the udev_root. The reason that I ask is
>because when I tested out udev using /udev as the
>udev_root and my system started up, the hotplug demon
>started up after the hard disks are mounted. And the
>problem was that the /dev/hda device nodes (and
>others) were not being created.
>
>Thanks in advanced for any help.
>
>=====
>Philip MacIver
>--
>e: pmaciver@arishi.com
>e: philipmaciver@yahoo.co.uk
>
>
what script do you use to start udev? is this the start_udev one?
when you use /udev : the entries are created? (do an ls don't assume
that they are created because no errors occurs)
are you mounting a /dev in fstab? (i know someone that did that...)
[-- Attachment #2: Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2004-02-27 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 9:28 hotplug raja sekhar kottapalli
2004-02-27 11:10 ` Hotplug Philip MacIver
2004-02-27 16:43 ` MALET JL [this message]
2004-02-27 16:53 ` Hotplug Philip MacIver
2004-02-27 17:14 ` Hotplug MALET JL
2004-02-27 17:20 ` Hotplug Philip MacIver
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=403F73C2.1030406@laposte.net \
--to=malet.jean-luc@laposte.net \
--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).