From: Andrew Haninger <ahaning@gmail.com>
To: Nick Warne <nick@linicks.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12 udev hangs at boot
Date: Sun, 19 Jun 2005 17:23:40 -0400 [thread overview]
Message-ID: <105c793f050619142339c2e762@mail.gmail.com> (raw)
In-Reply-To: <200506191639.27970.nick@linicks.net>
On 6/19/05, Nick Warne <nick@linicks.net> wrote:
> As to the missing /dev/ entries - remember you are using udev now - they
> appear 'on the fly' as and when you plug something in - ensure you have set
> 'hotplug' to start.
I have set hotplug to start on Slackware 10 (chmod a+x
/etc/rc.d/rc.hotplug) and it seems to start fine. When running the
default udev (v0.26) it loads all that I need for my external hard
disk except for sd_mod. If I manually modprobed sd_mod, /dev/sda and
/dev/sda1 would be automatically created, which was nice. With the
latest version of udev (v0.58) it loads sd_mod when I plug in the
drive, but /dev/sd** are not created dynamically (they are there all
the time). Having them created dynamically is nifty, but not necessary
for me. It would be nice if it was a little more brainless (e.g. /dev
entries are created on the fly by default) since I don't know how to
turn on/off dynamic creation of /dev entries.
Also, starting hotplug on boot gives a (slight) delay on my system.
This might be normal, but I'm not sure.
I'm probably not understanding something correctly, but this is what I'm seeing.
Thanks.
next prev parent reply other threads:[~2005-06-19 21:23 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-19 15:39 2.6.12 udev hangs at boot Nick Warne
2005-06-19 21:23 ` Andrew Haninger [this message]
2005-06-21 6:45 ` Greg KH
2005-06-21 17:06 ` Nick Warne
-- strict thread matches above, loose matches on Subject: below --
2005-06-18 15:32 Nick Warne
2005-06-21 6:40 ` Greg KH
2005-06-18 12:32 Nick Warne
2005-06-18 13:03 ` Alistair John Strachan
2005-06-18 13:44 ` Nick Warne
2005-06-18 14:58 ` Andrew Walrond
2005-06-18 16:53 ` Jeff Garzik
2005-06-18 17:06 ` Nick Warne
2005-06-19 15:04 ` Andrew Haninger
2005-06-20 10:04 ` Denis Vlasenko
2005-06-20 10:17 ` Stefan Smietanowski
2005-06-20 11:13 ` Denis Vlasenko
2005-06-20 16:25 ` Stefan Smietanowski
2005-06-20 16:39 ` Bill Davidsen
2005-06-20 16:48 ` Greg KH
2005-06-20 17:24 ` Jeff Garzik
2005-06-20 17:34 ` Greg KH
2005-06-20 19:00 ` Nick Warne
2005-06-20 19:21 ` Greg KH
2005-06-20 19:32 ` Nick Warne
2005-06-20 19:42 ` David Lang
2005-06-21 6:28 ` Greg KH
2005-06-21 6:31 ` David Lang
2005-06-21 6:47 ` Greg KH
2005-06-20 19:46 ` Jesper Juhl
2005-06-20 19:34 ` Andrew Haninger
2005-06-20 19:49 ` Josh Boyer
2005-06-21 6:42 ` Greg KH
2005-06-20 19:24 ` Olaf Hering
2005-06-20 21:26 ` Daniel Barkalow
2005-06-20 22:14 ` Jesper Juhl
2005-06-20 22:26 ` Tomasz Torcz
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=105c793f050619142339c2e762@mail.gmail.com \
--to=ahaning@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
/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