Thus spake Terry Lambert <[EMAIL PROTECTED]>: > David Schultz wrote: > > > > We've been over this before. To make this work right, we need to make > > > > /bin and /sbin dynamically linked. NetBSD's /rescue/* approach would > > > > solve the "oops!" and other foot shooting problems. > > > > > > Yes please. Our root filesystem space requirements are too high, IMHO. > > > > Why is it absolutely necessary to dynamically link everything just > > to move the resolver out of libc? > > Because ELF supports linking a shared library to another shared > library, which will automatically get you the appearance of the > historical "libresolv is integrated into libc". But it does not > support the linking of a static library to a static library, or > a static library to a shared library, the same way.
At least in the case of the base system, it should be easy to link all programs that actually use the resolver with -lresolv. Is there some standard that says that the resolver is an integral part of the C library, such that separating the two would break compatibility beyond comprehension? If you wanted to be really evil, I suppose you could have a libc.a that included the resolver and a libc.so that didn't. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
