From: MALET JL <malet.jean-luc@laposte.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug
Date: Fri, 27 Feb 2004 17:14:28 +0000 [thread overview]
Message-ID: <403F7AF4.60509@laposte.net> (raw)
In-Reply-To: <marc-linux-hotplug-106906141231187@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 2891 bytes --]
Philip MacIver a écrit :
> --- MALET JL <malet.jean-luc@laposte.net> wrote: >
>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?
>>
>>
>
>Yes.
>
>
>
>>when you use /udev : the entries are created? (do an
>>ls don't assume
>>that they are created because no errors occurs)
>>
>>
>
>Yes all the enteries are created, I've learnt never to
>assume
>
>
>>are you mounting a /dev in fstab? (i know someone
>>that did that...)
>>
>>
>>
>
>Nope I've checked my fstab many times and I don't
>mount a dev.
>
>When I do set the udev_root to /dev some devices get
>created, like fd0 and a few others that I can't
>remember.
>
>But i'm wondering if where i'm starting udev in my
>rc.sysinit is the problem. Just for your reference I
>start it (and also mount sysfs) right after /proc gets
>mounted (and yes I do mmount sysfs before I run
>start_udev :) )
>
>
>
>
>=====
>Philip MacIver
>--
>e: pmaciver@arishi.com
>e: philipmaciver@yahoo.co.uk
>
>
>
>
>
>___________________________________________________________
>Yahoo! Messenger - Communicate instantly..."Ping"
>your friends today! Download Messenger Now
>http://uk.messenger.yahoo.com/download/index.html
>
>
I remember having such trouble but this was because the udev script was
run twice...... but I can't remember exactly what was the causes and how
they disapeard.....
what I remember is that : I loged into the box, noticed that /dev wasn't
the right one (a fixed dev tree) so tried to rerun the script and only
get a partial /dev structure.... looking what was mounted told me that
/dev was mounted twice with ramfs..... maybe it can help :/
[-- Attachment #2: Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2004-02-27 17:14 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 ` Hotplug MALET JL
2004-02-27 16:53 ` Hotplug Philip MacIver
2004-02-27 17:14 ` MALET JL [this message]
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=403F7AF4.60509@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).