Date: Fri, 25 Jan 2019 21:15:19 +0100 From: Robert Clausecker <fuz@fuz.su> To: freebsd-arch@freebsd.org Cc: freebsd-arch@freebsd.org Subject: Re: Importing mksh in base Message-ID: <20190125201519.GA77486@fuz.su> In-Reply-To: <201901251953.x0PJrCpQ004492@slippy.cwsent.com> References: <fuz@fuz.su> <20190125193525.GA74966@fuz.su> <201901251953.x0PJrCpQ004492@slippy.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 25, 2019 at 11:53:12AM -0800, Cy Schubert wrote: > In message <20190125193525.GA74966@fuz.su>, Robert Clausecker writes: > > On Fri, Jan 25, 2019 at 09:12:58AM -0800, Cy Schubert wrote: > > > Why not ksh93 instead? It is the original and authoritative Korn > > > shell. EPL is compatible with the BSD license. Personally, I've been > > > toying with the idea of importing ksh93 for a while now. > > > > Note that ksh93 comes with a builtin user land from AT&T which should > > behave quite a bit differently from the FreeBSD userland. So unless we > > want to maintain two slightly different userlands (one of which needs to > > be maintained in conflict with upstream), that has to be torn out, which > > kills one of the performance advantages of ksh93. > > Oh really? Explain please. Ksh93 is part of the AT&T ast distribution. This distribution contains a large amount of standard programs and ksh93 would use them over the system's own programs if $PATH was set up correctly (ksh93 recognised a dummy path for "my own user land"). It does seem like they tore these out in the latter releases, so this concern is probably no longer important. Yours, Robert CLausecker -- () ascii ribbon campaign - for an 8-bit clean world /\ - against html email - against proprietary attachments
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190125201519.GA77486>