Date: Fri, 25 Jan 2019 16:39:06 -0800 (PST) From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> To: "Edward Tomasz Napiera?a" <trasz@freebsd.org> Cc: Gleb Popov <arrowd@freebsd.org>, arch@freebsd.org, Baptiste Daroussin <bapt@freebsd.org> Subject: Re: Importing mksh in base Message-ID: <201901260039.x0Q0d6mE090975@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <20190125093042.GB26635@v2>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 0125T2110, Gleb Popov wrote: > > On Fri, Jan 25, 2019 at 8:58 PM Baptiste Daroussin <bapt@freebsd.org> wrote: > > > > > Hi everyone, > > > > > > I would like to import mksh in base, https://www.mirbsd.org/mksh.htm > > > And make it the default root shell (not necessary in one step) > > > > > > Why: > > > 1/ it is tiny 400k (in the packaged version) all other shells fitting the > > > expectation are bigger > > > 2/ it's default frontend in interactive mode is very close to what most > > > people > > > are used to with bash > > > > > > Are there FreeBSD users that are used to bash? If not, this proposal looks > > like another "let's do like Linux" thing. > > To be honest I'd expect most FreeBSD users to be used to bash. I know > I was, until few years ago I've moved to zsh. You can expect it, and you might be able to collect some data to confirm that, but without that data this is a wag. > Most people nowadays come from Linux background, sometimes also OSX. I suspect, without data though, we get more people coming from Windows to FreeBSD than we do from Linux to FreeBSD. > aND THat means their primary shell, the one they are used to, is bash, > since it's the default on both of those platforms. It's fine to > provide something different if it is actually better - but being different > just for the sake of it, like defaulting to a shell that can't handle > a basic "2>&1", is not. This is none sense. csh syntax for 2>&1 is simple >&. -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201901260039.x0Q0d6mE090975>