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: udev 16, two copies of udevd
Date: Thu, 05 Feb 2004 23:49:46 +0000	[thread overview]
Message-ID: <20040205234946.GA3607@vrfy.org> (raw)
In-Reply-To: <20040204011117.26382.qmail@web14912.mail.yahoo.com>

On Thu, Feb 05, 2004 at 09:25:05AM -0800, Greg KH wrote:
> On Tue, Feb 03, 2004 at 05:30:24PM -0800, Jon Smirl wrote:
> > Yes, I'm mounting a tmpfs. I'm using the tmpfs becuase I've been having trouble
> > with stale nodes in my udev dir when I crash the kernel.
> > 
> > How is this going to work in final form? Will I need an initial /dev with mknod
> > for the 4-5 minimal devices needed to boot, and then can I mount a tmpfs over
> > this to hold udev devices?
> 
> I don't know, what do you think it should look like?

Jon, please try the current bk tree. We switched away from the socket file,
that gets missing with the tmpfs mount.
It should work now, cause we can't listen twice on the same socket in
abstract namespace.

Greg, it seems we can remove the lock file code completely.
Anyone willing to try? Just comment out the one_and_only() and look if
you can produce any situation with two udevd's running. It works for me
nice without it, also on tmpfs.


thanks,
Kay


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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

  parent reply	other threads:[~2004-02-05 23:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-04  1:11 udev 16, two copies of udevd Jon Smirl
2004-02-04  1:19 ` Kay Sievers
2004-02-04  1:30 ` Jon Smirl
2004-02-05 17:25 ` Greg KH
2004-02-05 23:49 ` Kay Sievers [this message]
2004-02-05 23:56 ` Jon Smirl
2004-02-06  0:01 ` Jon Smirl
2004-02-06  0:01 ` Kay Sievers
2004-02-06  0:08 ` Kay Sievers
2004-02-06  0:32 ` Greg KH
2004-02-06  0:47 ` Kay Sievers
2004-02-06  1:09 ` 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=20040205234946.GA3607@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).