From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev hang
Date: Wed, 19 May 2004 16:22:07 +0000 [thread overview]
Message-ID: <20040519162207.GA28503@kroah.com> (raw)
In-Reply-To: <Pine.BSO.4.58.0405162023230.20177@metawire.org>
On Wed, May 19, 2004 at 11:02:24AM -0500, jnf wrote:
> No I hadn't read that, but I just did (assuming rh_udev_for_dev.txt) is
> it; I didn't see anything that applied, I already figured out those little
> quirks when I had the paths set wrong in the config file- none of those
> seem to be the problem-
> the system hands when it tries to start udevstart on boot, if i do it
> manually it seems to work ok. Anyways, to answer you question- I am
> running slackware 9.0 w/ a 2.6.6 kernel and glibc 2.3.2.
Hm, I don't know of anyone who has got this to work on Slackware, you
might try on one of their mailing lists...
But as to why udevstart doesn't work, did you build it with klibc or
glibc? If glibc, can you actually get to the libraries needed that
early in the boot process? Try using the klibc version and see if that
helps or not.
If not, can you enable full debug logging and let us know what the
syslog says?
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
next prev parent reply other threads:[~2004-05-19 16:22 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
2004-05-19 16:02 ` jnf
2004-05-19 16:22 ` Greg KH [this message]
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=20040519162207.GA28503@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).