From: Arnd Bergmann <arnd@arndb.de>
To: linux-hotplug@vger.kernel.org
Subject: udev.permissions: symbolic group/owner broken
Date: Tue, 25 Nov 2003 14:22:59 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106977058220005@msgid-missing> (raw)
I noticed (after debugging for about an hour) that the calls
to getgrnam() and getpwnam() in udev-add.c always fail when
udev is statically linked to a recent glibc version (here:
Fedora glibc-2.3.2-57 on s390x).
Thinking about it a bit more, I found it to be fairly pointless
to have a statically linked /sbin/udev in the root fs when it
is not used on initramfs.
The obvious fix is not to link statically when building
udev for glibc.
Arnd <><
=== Makefile 1.38 vs edited ==--- 1.38/Makefile Mon Nov 24 05:38:01 2003
+++ edited/Makefile Tue Nov 25 15:18:36 2003
@@ -106,7 +106,7 @@
endif
# If we are using our version of klibc, then we need to build and link it.
-# Otherwise, use glibc and link statically.
+# Otherwise, use glibc and link dynamically.
ifeq ($(strip $(KLIBC)),true)
KLIBC_DIR = klibc/klibc
INCLUDE_DIR := $(KLIBC_DIR)/include
@@ -130,7 +130,6 @@
LIBC =
CFLAGS += -I$(GCCINCDIR)
LIB_OBJS = -lc
- LDFLAGS = --static
+ LDFLAGS endif
all: $(LIBC) $(ROOT)
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
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:[~2003-11-25 14:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-106977058220005@msgid-missing \
--to=arnd@arndb.de \
--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.