From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [patch] udevd - cleanup and better timeout handling
Date: Mon, 02 Feb 2004 18:45:29 +0000 [thread overview]
Message-ID: <20040202184529.GA31071@kroah.com> (raw)
In-Reply-To: <20040125200314.GA8376@vrfy.org>
On Mon, Feb 02, 2004 at 12:50:24PM +0100, Kay Sievers wrote:
> On Mon, Feb 02, 2004 at 12:21:39AM -0800, Greg KH wrote:
> > On Mon, Feb 02, 2004 at 03:19:22AM +0100, Kay Sievers wrote:
> > >
> > > Same patch with a fix for the stack size setting.
> >
> > Nice, applied.
> >
> > I also cleaned up the way the logging code works, so that now we can see
> > what program is spitting out what messages in the syslog.
>
> Fine, I've missed it too sometimes.
> We may include unistd.h for get_pid()?
Is it needed for you to build? It seems to work for me :)
> > Also, udevsend can _almost_ be built with klibc. Any reason we have to
> > use a struct sockaddr_un instead of just a struct sockaddr? If that is
> > changed than only udevd would rely on glibc.
>
> The sockaddr doesn't contain the 108 char long pathname of the socket file.
Ah, ok, that makes more sense.
> > I don't mind udevd using glibc, I just want the programs that get run a
> > lot of different times (udev and udevsend) to be as small as possible to
> > get the best cache results. As udevd sticks around all the time, it's
> > not as important. Sound sane to you?
>
> Oh, nice. Good idea.
> I have two alternatives attached:
>
> 01-udevsend-klibc.patch
> not the nicest, but it works
>
> 01-klibc-unix-domain.patch
> clean, but touches klibc sources by inserting the missing header file
I applied this version, and then cleaned up udevsend a bit more so now
it builds a 2.5kb binary using klibc. That's very nice.
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
next prev parent reply other threads:[~2004-02-02 18:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 20:03 [patch] udevd - cleanup and better timeout handling Kay Sievers
2004-01-26 18:22 ` Greg KH
2004-01-26 19:11 ` Kay Sievers
2004-01-26 19:28 ` Greg KH
2004-01-26 19:42 ` Kay Sievers
2004-01-26 22:26 ` Greg KH
2004-01-26 22:56 ` Kay Sievers
2004-01-27 6:56 ` Kay Sievers
2004-01-27 18:55 ` Greg KH
2004-01-27 19:08 ` Kay Sievers
2004-01-27 19:13 ` Greg KH
2004-01-28 21:47 ` Kay Sievers
2004-01-29 1:52 ` Kay Sievers
2004-01-29 1:56 ` Kay Sievers
2004-01-29 15:55 ` Kay Sievers
2004-01-31 2:42 ` Kay Sievers
2004-02-01 9:08 ` Greg KH
2004-02-01 18:16 ` Kay Sievers
2004-02-02 2:19 ` Kay Sievers
2004-02-02 8:21 ` Greg KH
2004-02-02 11:50 ` Kay Sievers
2004-02-02 18:45 ` Greg KH [this message]
2004-02-02 21:36 ` Kay Sievers
2004-02-03 1:26 ` Greg KH
2004-02-03 6:43 ` Ling, Xiaofeng
2004-02-03 20:12 ` Kay Sievers
2004-02-04 0:56 ` Greg KH
2004-02-08 9:43 ` Olaf Hering
2004-02-08 15:22 ` Kay Sievers
2004-02-08 15:40 ` Olaf Hering
2004-02-08 15:57 ` Kay Sievers
2004-02-08 16:09 ` Olaf Hering
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=20040202184529.GA31071@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.