linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: test script don't work anymore and some other issue
Date: Thu, 12 Feb 2004 22:44:10 +0000	[thread overview]
Message-ID: <20040212224410.GA21117@vrfy.org> (raw)
In-Reply-To: <402BFE6C.8090902@laposte.net>

On Thu, Feb 12, 2004 at 11:30:04PM +0100, mjl wrote:
> hello
> today I tried to see why some udev entries aren't created such as tty one
> so I gone into test subdir after rebuilding (wiht klibc, no issue) and 
> what a surprise the test script don't work anymore (but hotplug/udev 
> does since I got entries when pluging a usb device....)
> 
> so here are my questions :
> 1)howto force generation of "coldplug events" such as tty

Try the init script '/etc/init.d/udev start'.
It creates all devies available in sysfs.

> 2)the entries created aren't removed when unpluging, is it normal? what 
> to do to make them removed?

Try 'rm /udev/.udevdb'.
Yesterday we fixed the big in the current tree where the db is not compatible
with switching libcs, cause of the size of mode_t.

Kay


-------------------------------------------------------
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=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-02-12 22:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-12 22:30 test script don't work anymore and some other issue mjl
2004-02-12 22:44 ` Kay Sievers [this message]

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=20040212224410.GA21117@vrfy.org \
    --to=kay.sievers@vrfy.org \
    --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).