Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!olivea!apple!agate!ziploc!eps
From: eps@toaster.SFSU.EDU (Eric P. Scott)
Newsgroups: comp.sys.next
Subject: Re: libc.a replaced with libsys.a in 2.0
Message-ID: <1087@toaster.SFSU.EDU>
Date: 3 Jan 91 07:07:14 GMT
References: <1991Jan2.125711.6400@cs.umn.edu>
Reply-To: eps@cs.SFSU.EDU (Eric P. Scott)
Organization: San Francisco State University
Lines: 17

I don't mind having the shared library pulled in by default--99+%
of the time it's what you want.  HOWEVER, there has to be some
way of making staticly linked executables for "anything that
would belong in /bin" or it's impossible to build small bootable
media or chroot()ed environments.  The kernel traps aren't going
to change (i.e. all of man 2 is "safe"), and nearly everything
else from BSD isn't likely to change (or at least not in a way
that breaks anything).  If NeXT changes the interfaces to
netinfo, the format of Mach-O files, or adds new signals or
error codes, there might be problems.  The only part of libc.a in
1.0a that "needs replacement" is the BIND resolver routines.

I can live with relinking for each major software revision.

(Did none of the beta sites catch this???)

					-=EPS=-