From owner-freebsd-arch@freebsd.org Sun Jan 27 00:19:55 2019 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D6F2014B453D; Sun, 27 Jan 2019 00:19:55 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5ED7174BBD; Sun, 27 Jan 2019 00:19:55 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x0R0JpAe096104; Sat, 26 Jan 2019 16:19:51 -0800 (PST) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id x0R0JpF4096103; Sat, 26 Jan 2019 16:19:51 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201901270019.x0R0JpF4096103@pdx.rh.CN85.dnsmgr.net> Subject: Re: Importing mksh in base In-Reply-To: <32153.1548546852@kaos.jnpr.net> To: "Simon J. Gerraty" Date: Sat, 26 Jan 2019 16:19:51 -0800 (PST) CC: Cy Schubert , arch@freebsd.org, Baptiste Daroussin , freebsd-arch@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 5ED7174BBD X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.97 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.97)[-0.969,0] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2019 00:19:56 -0000 > Cy Schubert wrote: > > Interactively ksh93's command completion listing looks unconventional > > but it functions the same. > > > > However programmatically it's the standard. Large commercial vendors, > > like Oracle, still require ksh for its array handling among other > > things. > > pdksh (hence I assume mksh) has had array support for ages. > The only thing I ever found it useful for was cd history, > and I actually have an implementation of that for sh that does not need > arrays. > > > It has that advantage. For embedded this is an advantage. However if > > embedded is using ksh as a scripting language mksh and pdksh aren't > > As noted earlier I've used [pd]ksh as shell for 30 years. > I do *not* write ksh scripts (except for .kshrc etc ;-) > > The beauty of ksh as interactive shell is it's (mostly) compatability > with /bin/sh - which scripts should be written in. > > Now on some systems (HPUX springs to mind ;-) /bin/sh is so bad that > one has to use ksh to run scripts - but they are still sh scripts. Doesnt pdksh have a "sh" compatible mode iirc when you invoke it via a path of sh it behaves as a traditional bourne shell, also if IIRC Openbsd is doing just that, /bin/sh -> /bin/pdksh (hard link) -- Rod Grimes rgrimes@freebsd.org