linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev hang
Date: Wed, 19 May 2004 07:18:08 +0000	[thread overview]
Message-ID: <20040519071807.GC20079@kroah.com> (raw)
In-Reply-To: <Pine.BSO.4.58.0405162023230.20177@metawire.org>

On Sun, May 16, 2004 at 08:35:59PM -0500, jnf wrote:
> Hi,
> 
> I was told to post my query here just so it would be public/get archived 
> by the search engines. I recently installed udev under 2.6.6, I originally 
> had some problems with it, but as it turned out that part of it was an ID 
> 10 T error in that the default config used rules located in 
> '/etc/udev/rules.d' and '/etc/udev/permissions.d' [im on slackware, i 
> think the config/install mightve detected me as gentoo?], anyways my fault 
> i shouldve noticied that when i edited the config file. Noticing that 
> helped me figure out why udev refused to follow what I said to use for 
> permissions. Now I have a new and seperate problem, when I enable udev to 
> from boot, that is have it start on boot, I hang at:
> 
> echo 'udev: Creating initial udev devices nodes:'
> ... (comments removed here)
> /sbin/udevstart
> 
> Interesting to note is that if I boot with it enabled, then run the rc 
> script, everything works fine- and if my rules/permission files are misset 
> in the udev.config file, then it boots fine [just doesnt set the correct 
> perms to my devices]. Any idea's what would be causing this? I'm not sure 
> what information you all would like me to include,
> 
> $ udevinfo -V
> udevinfo, version 025
> 
> (I cant seem to figure out how to get the version from hotplug itself)
> $ ls hot*
> hotplug-2004_04_01.tar.bz2
> 
> hotplug-2004_04_01:
> (...)
> $
> 
> A thought off the top of my head is, I should be enabling this before 
> hotplug correct? rc.udev (start_udev) is called from my rc.S [system init] 
> scripts, just before I mount the other drives, just after sysfs is 
> mounted, and then hotplug isnt started until all the way into my rc.local 
> scripts; is that the correct order?

Did you take a look at the README that details how to add this to a Red
Hat distro?

What distro are you using?

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id%62&alloc_ida84&op=click
_______________________________________________
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

  reply	other threads:[~2004-05-19  7:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17  1:35 udev hang jnf
2004-05-19  7:18 ` Greg KH [this message]
2004-05-19 16:02 ` jnf
2004-05-19 16:22 ` Greg KH
2004-05-19 18:15 ` jnf
2004-05-20 21:58 ` Greg KH
2004-05-21  1:31 ` jnf

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=20040519071807.GC20079@kroah.com \
    --to=greg@kroah.com \
    --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).