All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev 16, two copies of udevd
Date: Fri, 06 Feb 2004 00:32:16 +0000	[thread overview]
Message-ID: <20040206003216.GA18470@kroah.com> (raw)
In-Reply-To: <20040204011117.26382.qmail@web14912.mail.yahoo.com>

On Fri, Feb 06, 2004 at 12:49:46AM +0100, Kay Sievers wrote:
> 
> 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.

I agree, it should be safe to remove that now, which is a very good
thing.

Care to send a patch?  Or I can do it.

thanks,

greg k-h


-------------------------------------------------------
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-06  0:32 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
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 [this message]
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=20040206003216.GA18470@kroah.com \
    --to=greg@kroah.com \
    --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 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.