Date: Sun, 23 Nov 2003 18:27:01 -0500 From: Richard Coleman <richardcoleman@mindspring.com> To: current@freebsd.org Cc: Tim Kientzle <kientzle@acm.org> Subject: Re: Unfortunate dynamic linking for everything Message-ID: <3FC14245.6030509@mindspring.com> In-Reply-To: <20031123225117.GA24696@dragon.nuxi.com> References: <62981.24.0.61.35.1069202574.squirrel@mail.yazzy.org> <200311190103.hAJ13Nlg000923@dyson.jdyson.com> <20031119015433.GN30485@roark.gnf.org> <3FBC2053.6040208@mindspring.com> <20031120022009.GB29530@dan.emsphone.com> <3FBC29EF.3030009@mindspring.com> <3FBC50DB.3000002@acm.org> <20031123225117.GA24696@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David O'Brien wrote: > We should build /bin/sh static and be done with the argument. > Or rather, lets find a /bin/sh interactive user and have him argue that > /bin/sh needs NSS support. I dare say that will be a thread two orders > of magnitude shorter than this one. Statically linking /bin/sh wouldn't be that big a deal. It would be trivial to add a port to compile a dynamic version of sh for customers that *really* want sh. Personally, I can't remember a customer specifically requesting that. You would need to make sure that startup scripts never use tilde expansion. I'm not sure how common that is with RCNG. But it would be sorta odd to have statically linked versions of sh in both /bin and /rescue. Richard Coleman richardcoleman@mindspring.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FC14245.6030509>