linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Tomasz K?oczko <kloczek@rudy.mif.pg.gda.pl>
Cc: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 048 release
Date: Wed, 08 Dec 2004 22:05:00 +0000	[thread overview]
Message-ID: <20041208220500.GA19187@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.61L.0412082238420.18542@rudy.mif.pg.gda.pl>

On Wed, Dec 08, 2004 at 10:56:27PM +0100, Tomasz K?oczko wrote:
> 
> First: is it any real reason for use by udev private copy libsysfs which
> is statically linked with udev ?

Yes, the "system" version of libsysfs is not always the same one that
udev wants.  Over the past year or so, sometimes it has varied a lot.
Hopefully now we are properly synced up, but I still trust our own
version, not any other version (this really matters on boxes that have
older versions of libsysfs, like SLES 9 and friends.)

> I'm using udev with shared libsysfs for a months and all works correcly.

Great.  Notice any code size savings?  Yeah, it's not really all that
much.  You also need static linking when using klibc to get a very tiny
udev for your boot initramfs image.

> If no reasons patches for using system avalaible libsysfs for udev 048 
> can be downloaded from:
> 
> http://cvs.pld.org.pl/SOURCES/udev-uses_system_libsysfs.patch?rev=1.7
> http://cvs.pld.org.pl/SOURCES/udev-extras_scsi_id_sysfs.patch?rev=1.1
> 
> Also after aplying this patches libsysfs/ subdirectory can be removed from 
> udev source tree.

Will it still properly build with klibc?

Also, please realize that libsysfs is really not on many machines, due
to it only being used by 1 other program at this time.  So any memory
size savings is very limited.

> Second: in current udev Makefile is used direct stripping linked binaries.
> Why ?

Smaller size :)

> It makes harder packaging udev if someone will try generate udev in 
> for example rpm form with debug info in separated udev-debug package.

I'm sure those who package up rpms of udev have dealt with this properly
somehow.  For the rest of the world, I'd prefer to keep the current way.

thanks,

greg k-h


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
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-12-08 22:05 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08 18:58 [ANNOUNCE] udev 047 release Greg KH
2004-12-08 19:28 ` Greg KH
2004-12-08 19:46   ` [ANNOUNCE] udev 048 release Greg KH
2004-12-08 21:56     ` Tomasz Kłoczko
2004-12-08 22:05       ` Greg KH [this message]
2004-12-08 22:15         ` Kay Sievers
2004-12-08 23:25         ` Tomasz Kłoczko
2004-12-08 22:22     ` Marco d'Itri
2004-12-08 23:56     ` Marco d'Itri
2004-12-09  0:08     ` Mike Frysinger
2004-12-09 21:47     ` Andrew Walrond
2004-12-09 23:25       ` Greg KH
2004-12-10  8:46         ` Andrew Walrond
2004-12-09 21:56     ` Kay Sievers
2004-12-09 22:07     ` Andrew Walrond
2004-12-09 22:18     ` Kay Sievers
2004-12-09 22:24     ` Andrew Walrond
2004-12-09 22:27     ` Kay Sievers
2004-12-09 22:33     ` Andrew Walrond
2004-12-11 16:44 ` [ANNOUNCE] udev 047 release [u] Martin Schlemmer [c]
2004-12-11 17:46   ` Kay Sievers
2004-12-11 17:59   ` Martin Schlemmer [c]
2004-12-13 16:44   ` Martin Schlemmer [c]
2004-12-13 17:08   ` Kay Sievers
2004-12-13 19:18   ` Martin Schlemmer [c]
2004-12-14  0:46   ` Kay Sievers
2004-12-17  0:08   ` Greg KH
2004-12-17 17:11   ` Martin Schlemmer [c]
2004-12-17 23:32   ` 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=20041208220500.GA19187@kroah.com \
    --to=greg@kroah.com \
    --cc=kloczek@rudy.mif.pg.gda.pl \
    --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;
as well as URLs for NNTP newsgroup(s).