mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Frédéric L. W. Meunier" <1@pervalidus.net>
To: Greg KH <greg@kroah.com>
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 21:51:52 -0300 (BRT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0402192057590.694@pervalidus.dyndns.org> (raw)
In-Reply-To: <20040219235602.GI15848@kroah.com>

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 ?

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.

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

> Oh, and if you create the /dev/null node as the first thing in the
> start_udev script does that work?

No.

-- 
http://www.pervalidus.net/contact.html

  reply	other threads:[~2004-02-20  0:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-19 18:59 [ANNOUNCE] udev 018 release Greg KH
2004-02-19 19:13 ` Greg KH
2004-02-20 12:48   ` Michael Buesch
2004-02-20 23:56     ` Greg KH
2004-02-19 19:16 ` HOWTO use udev to manage /dev Greg KH
2004-02-19 19:36   ` James Simmons
2004-02-19 19:46     ` Greg KH
2004-02-19 20:21       ` James Simmons
2004-02-19 20:28         ` Greg KH
2004-02-19 21:35           ` James Simmons
2004-02-20  0:52         ` Andries Brouwer
2004-02-20 19:14           ` Johannes Stezenbach
2004-02-20 23:57           ` Greg KH
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 23:07     ` Greg KH
2004-02-19 23:46       ` Frédéric L. W. Meunier
2004-02-19 23:56         ` Greg KH
2004-02-20  0:51           ` Frédéric L. W. Meunier [this message]
2004-02-20  1:09             ` Frédéric L. W. Meunier
2004-02-20  1:54             ` Greg KH
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  1:20       ` Tomasz Torcz
2004-02-21 17:20 ` [ANNOUNCE] udev 018 release Prakash K. Cheemplavam
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=Pine.LNX.4.58.0402192057590.694@pervalidus.dyndns.org \
    --to=1@pervalidus.net \
    --cc=greg@kroah.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®