linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev.rules.devfs + symlinks & a question
Date: Wed, 17 Dec 2003 22:27:21 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-107170109912686@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107105799027697@msgid-missing>

On Wed, Dec 17, 2003 at 09:39:08PM +0100, Svetoslav Slavtchev wrote:
> 
> could you change the sed rule for generating udev.conf
> to use ":" instead "-" for separater, as  it's getting confused
> if you install to RPM_BUILD_ROOT/udev-$(version)/

What do you mean?  The sed rule:
	sed -e "s-@udevdir@-$(udevdir)-" < udev.conf.in > $@

doesn't work for you?  If not, patches to fix it are appreciated.

> and the question
> how should i compile udev to use shared libraries,
> not to link it staticaly? static udev using libc is arround 500k,
> so it's a way too big for initrd, 
> why not have a klibc udev static binary for initrd,
> and a not static one against libc to manage the devices,
> after root is mounted and the libraries are available

Ok, changes to the Makefile to make the glibc build dynamic are welcome.

thanks,

greg k-h


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
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:[~2003-12-17 22:27 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-10 12:01 udev.rules.devfs + symlinks & a question Svetoslav Slavtchev
2003-12-10 12:31 ` Arnd Bergmann
2003-12-10 13:17 ` Svetoslav Slavtchev
2003-12-10 17:00 ` Marco d'Itri
2003-12-10 22:07 ` Greg KH
2003-12-10 22:45 ` Svetoslav Slavtchev
2003-12-10 23:14 ` Greg KH
2003-12-10 23:19 ` Svetoslav Slavtchev
2003-12-11  0:17 ` Greg KH
2003-12-11  1:14 ` Svetoslav Slavtchev
2003-12-11  1:31 ` Svetoslav Slavtchev
2003-12-12 22:17 ` Svetoslav Slavtchev
2003-12-12 23:42 ` Greg KH
2003-12-12 23:43 ` Greg KH
2003-12-12 23:45 ` Greg KH
2003-12-13  0:02 ` Svetoslav Slavtchev
2003-12-13  0:06 ` Greg KH
2003-12-13  0:39 ` Svetoslav Slavtchev
2003-12-13  0:57 ` Greg KH
2003-12-13  0:58 ` Svetoslav Slavtchev
2003-12-13  1:17 ` Svetoslav Slavtchev
2003-12-13 15:47 ` Kay Sievers
2003-12-13 21:33 ` Svetoslav Slavtchev
2003-12-14  3:34 ` Kay Sievers
2003-12-15 22:55 ` Greg KH
2003-12-15 22:56 ` Greg KH
2003-12-15 22:57 ` Greg KH
2003-12-17 20:16 ` Svetoslav Slavtchev
2003-12-17 20:39 ` Svetoslav Slavtchev
2003-12-17 21:13 ` Svetoslav Slavtchev
2003-12-17 22:24 ` Greg KH
2003-12-17 22:25 ` Greg KH
2003-12-17 22:27 ` Greg KH [this message]
2003-12-17 22:28 ` Greg KH
2003-12-17 22:29 ` Greg KH
2003-12-17 22:30 ` Greg KH
2003-12-17 22:51 ` Marco d'Itri
2003-12-17 22:55 ` Svetoslav Slavtchev
2003-12-17 22:59 ` Svetoslav Slavtchev
2003-12-17 23:04 ` Svetoslav Slavtchev
2003-12-17 23:06 ` Svetoslav Slavtchev
2003-12-17 23:08 ` 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=marc-linux-hotplug-107170109912686@msgid-missing \
    --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 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).