This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Markus Schoder <markus@gammarayburst.de> writes: > I think the possibility to deploy statically linked binaries that do not > depend on the libc of the target system is very valuable. > > The fact that this is currently not possible due to the NSS > implementation makes me wonder why this design was chosen. I could Note that on Solaris you cannot use static binaries at all due to NSS. Under Linux you can use them but just have to keep the restrictions in mind. > instead imagine say a name service daemon that would be queried for name > lookup. This would nicely decouple the libc versions of the binary and > the target system. But this would enforce a daemon running everytime and you might not have this one in a chroot environment or at system bootup. > Of course the protocol would need to be designed in such a way that it > is very stable -- but this seems achievable if some extension mechanism > is built into it. > > I hope I am making some sense but I am getting tired of static binaries > crashing left and right. Don't use them ;-) Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Attachment:
pgp00000.pgp
Description: PGP signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |