Date: Wed, 19 Nov 2003 21:27:55 -0800 From: Tim Kientzle <kientzle@acm.org> To: richardcoleman@mindspring.com Cc: imp@bsdimp.com Subject: Re: Unfortunate dynamic linking for everything Message-ID: <3FBC50DB.3000002@acm.org> In-Reply-To: <3FBC29EF.3030009@mindspring.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>
next in thread | previous in thread | raw e-mail | index | archive | help
Richard Coleman wrote: > It seems /bin/sh is the real sticking point. There is a problem here: Unix systems have historically used /bin/sh for two somewhat contradictory purposes: * the system script interpreter * as a user shell The user shell must be dynamically linked in order to support centralized administration. I personally see no way around that. Given that many users do rely on /bin/sh, it seems that /bin/sh must be dynamically linked. There are good reasons to want the system script interpreter statically linked. Maybe it's time to separate these two functions? I would be content to have a static /sbin/sh that is used as the system script interpreter for rc scripts, etc. Tim Kientzle
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FBC50DB.3000002>