hotplug

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: [email protected]
e: [email protected]

Quoted 7 lines

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

Quoted 1 line

out "/bin/true", I've read that to change this you

do

Quoted 3 lines

echo "/sbin/hotplug" > /proc/sys/kernel/hotplug.

But what I want to know is, is this the reason that

my

Quoted 2 lines

linux system won't boot up when I try and use udev with /dev as the udev_root. The reason that I ask

is

Quoted 2 lines

because when I tested out udev using /udev as the udev_root and my system started up, the hotplug

demon

Quoted 1 line

started up after the hard disks are mounted. And

the

Quoted 5 lines

problem was that the /dev/hda device nodes (and others) were not being created.

Thanks in advanced for any help.

Quoted 6 lines

==> >Philip MacIver
--
e: [email protected]
e: [email protected]

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...)

--- MALET JL <[email protected]> wrote: >

Quoted 59 lines · Philip MacIver

Quoted 8 lines

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

Quoted 3 lines

out "/bin/true", I've read that to change this you

do

Quoted 5 lines

echo "/sbin/hotplug" > /proc/sys/kernel/hotplug.

But what I want to know is, is this the reason that

my

Quoted 4 lines

linux system won't boot up when I try and use udev with /dev as the udev_root. The reason that I ask

is

Quoted 4 lines

because when I tested out udev using /udev as the udev_root and my system started up, the hotplug

demon

Quoted 3 lines

started up after the hard disks are mounted. And

the

Quoted 14 lines

problem was that the /dev/hda device nodes (and others) were not being created.

Thanks in advanced for any help.

=====
Philip MacIver
--
e: [email protected]
e: [email protected]

Quoted 4 lines

what script do you use to start udev? is this the start_udev one?

Yes.

Quoted 4 lines

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

Quoted 5 lines

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: [email protected]
e: [email protected]

___________________________________________________________
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 :/