public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Greg KH <greg@kroah.com>
Cc: linux-hotplug-devel@lists.sourceforge.net,
	Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>,
	Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [ANNOUNCE] udev 016 release
Date: Sun, 08 Feb 2004 15:01:42 +0200	[thread overview]
Message-ID: <1076245301.6996.63.camel@nosferatu.lan> (raw)
In-Reply-To: <1076239649.6996.58.camel@nosferatu.lan>

[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]

On Sun, 2004-02-08 at 13:27, Martin Schlemmer wrote:
> On Wed, 2004-02-04 at 06:25, Martin Schlemmer wrote:
> 
> > > > 2) events gets missing.  If you for example use udevsend in the
> > > > initscript that populate /dev (/udev), the amount of nodes/links
> > > > created is off with about 10-50 (once about 250) entries.
> > > 
> > > Hm, that's not good.  I'll go test that and see what's happening.
> > > 
> > 
> > Script is attached.  If I was being silly here, let me know.  Some
> > quick testing again, it seems like the missing events is more with
> > the echo not commented, but could be just some fluke (there was
> > still however more than 5 usually missing).
> > 
> 
> Btw, I also get this now and then for /dev/snd/* stuff.  I had a few
> times already where controlC0 was not created (and this is after the
> script runs to generate /dev ...).
> 

I should clarify here - /dev is generated, and only _after_ that the
sound modules is loaded which should then get /dev/snd/* created.  It
is thus not as many nodes as /dev creation that also causes missing
events ...


-- 
Martin Schlemmer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-02-08 13:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-03 20:13 [ANNOUNCE] udev 016 release Greg KH
2004-02-03 20:49 ` Martin Schlemmer
2004-02-03 23:14   ` Greg KH
2004-02-03 21:28 ` Martin Schlemmer
2004-02-03 23:03   ` Martin Schlemmer
2004-02-03 23:13     ` Greg KH
2004-02-04  0:01       ` Kay Sievers
2004-02-04  4:25       ` Martin Schlemmer
2004-02-08 11:27         ` Martin Schlemmer
2004-02-08 13:01           ` Martin Schlemmer [this message]
2004-02-03 21:43 ` Martin Schlemmer
2004-02-11 22:13   ` Greg KH
2004-02-11 22:27     ` Martin Schlemmer
2004-02-12  1:19       ` 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=1076245301.6996.63.camel@nosferatu.lan \
    --to=azarah@nosferatu.za.org \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --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