From: Greg KH <greg@kroah.com>
To: "Frédéric L. W. Meunier" <1@pervalidus.net>
Cc: linux-kernel@vger.kernel.org, linux-hotplug-devel@lists.sourceforge.net
Subject: Re: HOWTO use udev to manage /dev
Date: Fri, 20 Feb 2004 01:54:34 +0000 [thread overview]
Message-ID: <20040220015433.GC3134@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0402192057590.694@pervalidus.dyndns.org>
On Thu, Feb 19, 2004 at 09:51:52PM -0300, Frédéric L. W. Meunier wrote:
> On Thu, 19 Feb 2004, Greg KH wrote:
>
> > So if you take out the line about starting udevd, does it
> > work for you?
>
> No.
>
> > How about changing the #!/bin/bash to #!/bin/sash in the
> > first line for the start_udev script?
>
> I didn't have it, but compiled and changed. Yes, it works.
>
> > What distro is this?
>
> Slackware, with a cute rc.S. /bin/bash was also recompiled, shared:
>
> $ ldd /bin/bash
> libreadline.so.4 => /usr/lib/libreadline.so.4 (0x4001c000)
> libhistory.so.4 => /usr/lib/libhistory.so.4 (0x40049000)
> libncurses.so.5 => /lib/libncurses.so.5 (0x40050000)
> libdl.so.2 => /lib/libdl.so.2 (0x4008f000)
> libc.so.6 => /lib/libc.so.6 (0x40092000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
>
> Maybe the problem ? Does yours differ ?
Mine does differ, but it is dynamic:
$ ldd /bin/bash
linux-gate.so.1 => (0xffffe000)
libtermcap.so.2 => /lib/libtermcap.so.2 (0x4d5b5000)
libdl.so.2 => /lib/libdl.so.2 (0x4d3b4000)
libc.so.6 => /lib/tls/libc.so.6 (0x4d254000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4d238000)
> bash from Slackware:
>
> libtermcap.so.2 => /lib/libtermcap.so.2 (0x4001c000)
> libdl.so.2 => /lib/libdl.so.2 (0x4005c000)
> libc.so.6 => /lib/libc.so.6 (0x4005f000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
>
> OK, I'll later boot with it and see if it works. If it does,
> I'll run strace with the other.
How about using sash? That is statically linked.
> > Can you run strace on the start_udev script after boot to see who is
> > needing access to /dev/null?
>
> I forgot to run it, but noticed there was a /dev/null, but a
> text file (0644). And I didn't create it anywhere.
That sounds like some program is trying to write to it.
Hm, there is a patch in the Red Hat version of udev that basically makes
udev do the start_udev logic, in the .c file because they do not have a
shell in their initrd. If you can dig it out of there, that might be a
solution for you to use.
Other than that, how about running strace on start_udev when your rc.S
script calls it? That might help out.
thanks,
greg k-h
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&opÌk
_______________________________________________
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
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: "Frédéric L. W. Meunier" <1@pervalidus.net>
Cc: linux-kernel@vger.kernel.org, linux-hotplug-devel@lists.sourceforge.net
Subject: Re: HOWTO use udev to manage /dev
Date: Thu, 19 Feb 2004 17:54:34 -0800 [thread overview]
Message-ID: <20040220015433.GC3134@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0402192057590.694@pervalidus.dyndns.org>
On Thu, Feb 19, 2004 at 09:51:52PM -0300, Frédéric L. W. Meunier wrote:
> On Thu, 19 Feb 2004, Greg KH wrote:
>
> > So if you take out the line about starting udevd, does it
> > work for you?
>
> No.
>
> > How about changing the #!/bin/bash to #!/bin/sash in the
> > first line for the start_udev script?
>
> I didn't have it, but compiled and changed. Yes, it works.
>
> > What distro is this?
>
> Slackware, with a cute rc.S. /bin/bash was also recompiled, shared:
>
> $ ldd /bin/bash
> libreadline.so.4 => /usr/lib/libreadline.so.4 (0x4001c000)
> libhistory.so.4 => /usr/lib/libhistory.so.4 (0x40049000)
> libncurses.so.5 => /lib/libncurses.so.5 (0x40050000)
> libdl.so.2 => /lib/libdl.so.2 (0x4008f000)
> libc.so.6 => /lib/libc.so.6 (0x40092000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
>
> Maybe the problem ? Does yours differ ?
Mine does differ, but it is dynamic:
$ ldd /bin/bash
linux-gate.so.1 => (0xffffe000)
libtermcap.so.2 => /lib/libtermcap.so.2 (0x4d5b5000)
libdl.so.2 => /lib/libdl.so.2 (0x4d3b4000)
libc.so.6 => /lib/tls/libc.so.6 (0x4d254000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4d238000)
> bash from Slackware:
>
> libtermcap.so.2 => /lib/libtermcap.so.2 (0x4001c000)
> libdl.so.2 => /lib/libdl.so.2 (0x4005c000)
> libc.so.6 => /lib/libc.so.6 (0x4005f000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
>
> OK, I'll later boot with it and see if it works. If it does,
> I'll run strace with the other.
How about using sash? That is statically linked.
> > Can you run strace on the start_udev script after boot to see who is
> > needing access to /dev/null?
>
> I forgot to run it, but noticed there was a /dev/null, but a
> text file (0644). And I didn't create it anywhere.
That sounds like some program is trying to write to it.
Hm, there is a patch in the Red Hat version of udev that basically makes
udev do the start_udev logic, in the .c file because they do not have a
shell in their initrd. If you can dig it out of there, that might be a
solution for you to use.
Other than that, how about running strace on start_udev when your rc.S
script calls it? That might help out.
thanks,
greg k-h
next prev parent reply other threads:[~2004-02-20 1:54 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 18:59 [ANNOUNCE] udev 018 release Greg KH
2004-02-19 18:59 ` Greg KH
2004-02-19 19:13 ` Greg KH
2004-02-19 19:13 ` Greg KH
2004-02-20 12:48 ` Michael Buesch
2004-02-20 12:48 ` Michael Buesch
2004-02-20 23:56 ` Greg KH
2004-02-20 23:56 ` Greg KH
2004-02-19 19:16 ` HOWTO use udev to manage /dev Greg KH
2004-02-19 19:16 ` Greg KH
2004-02-19 19:36 ` James Simmons
2004-02-19 19:36 ` James Simmons
2004-02-19 19:46 ` Greg KH
2004-02-19 19:46 ` Greg KH
2004-02-19 20:21 ` James Simmons
2004-02-19 20:21 ` James Simmons
2004-02-19 20:28 ` Greg KH
2004-02-19 20:28 ` Greg KH
2004-02-20 0:52 ` Andries Brouwer
2004-02-20 0:52 ` Andries Brouwer
2004-02-20 19:14 ` Johannes Stezenbach
2004-02-20 23:57 ` Greg KH
2004-02-20 23:57 ` Greg KH
2004-02-19 21:35 ` James Simmons
2004-02-19 21:35 ` James Simmons
2004-02-19 22:22 ` Frédéric L. W. Meunier
2004-02-19 22:22 ` Frédéric L. W. Meunier
2004-02-19 22:25 ` Frédéric L. W. Meunier
2004-02-19 22:25 ` Frédéric L. W. Meunier
2004-02-19 23:07 ` Greg KH
2004-02-19 23:07 ` Greg KH
2004-02-19 23:46 ` Frédéric L. W. Meunier
2004-02-19 23:46 ` Frédéric L. W. Meunier
2004-02-19 23:56 ` Greg KH
2004-02-19 23:56 ` Greg KH
2004-02-20 0:51 ` Frédéric L. W. Meunier
2004-02-20 0:51 ` Frédéric L. W. Meunier
2004-02-20 1:09 ` Frédéric L. W. Meunier
2004-02-20 1:09 ` Frédéric L. W. Meunier
2004-02-20 1:54 ` Greg KH [this message]
2004-02-20 1:54 ` Greg KH
2004-02-20 2:28 ` Frédéric L. W. Meunier
2004-02-20 2:28 ` Frédéric L. W. Meunier
2004-02-20 7:44 ` Frédéric L. W. Meunier
2004-02-20 7:44 ` Frédéric L. W. Meunier
2004-02-20 1:20 ` Tomasz Torcz
2004-02-21 17:42 ` Marco d'Itri
2004-02-22 0:30 ` Frédéric L. W. Meunier
2004-02-21 17:20 ` [ANNOUNCE] udev 018 release Prakash K. Cheemplavam
2004-02-21 17:20 ` Prakash K. Cheemplavam
2004-02-24 1:49 ` Greg KH
2004-02-24 1:49 ` Greg KH
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=20040220015433.GC3134@kroah.com \
--to=greg@kroah.com \
--cc=1@pervalidus.net \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.