Date: Wed, 29 Sep 2021 02:38:50 -0400 From: grarpamp <grarpamp@gmail.com> To: freebsd-current@freebsd.org Cc: arch@freebsd.org Subject: Re: [HEADSUP] making /bin/sh the default shell for root Message-ID: <CAD2Ti28tkY=Fyz-OrTjxQVwrNaDxitO_bn29TxoM=9WoP1ON5Q@mail.gmail.com> In-Reply-To: <c9c908af-0151-2e77-2333-979ecc44d52a@FreeBSD.org> References: <20210922083645.4vnoajyvwq6wfhdf@aniel.nours.eu> <97ebc390-a19e-3203-7016-ce541796eb18@beastielabs.net> <c9c908af-0151-2e77-2333-979ecc44d52a@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
The system shell really only need to support the language of the shipped scripts of the base tooling such as rc subsystem. If those were someday written in Greek, then the shell serves alone, the most common expectation of any "unix" to have there seems to be an "sh", from which users can further customize the box in whatever ways. Base's simplicity, perhaps that is in part why 14 would go with sh, and no longer litter the password file with any other shells, else base must really add and carry them all... zoor zsh toor tcsh coor csh qoor sql poor python boor bash goor go plus the entire rest of world of shellish thingies just to satisfy. Which is obviously untenable and absurd and causes futher legacies, maintenance, dependencies. Where does it stop, what is the limiting definition. Moving to just one, some type of an "sh", seems best to resolve the question. > The little help you get on the command line to search and repeat commands is very useful compared to plain "sh". That is in part why the sh UI appears to be getting some nice improvements as noted in the HEADSUP / thread. BSD users could contribute more to that effort, or run on the systems whichever shells are preferred. > change "Charlie &" in the gecos field to something more > sensible, e.g. just "Superuser" Seconded. It seems somewhat against good idea to have expandos in and downstream with a passwd file. This update can also help users minimize parsing and gotcha bugs by removing some possible escaping/AND/backgrounding interpretation problems, and reducing complexity and surface. There's actually been a good bit of stepwise cleaning and organization of the passwd/group file, and UID/GID to filesystem/daemons, etc over the years. It's good to view this as part of that effort as well. Another problem and lost opportunity cost and burnt cycles this update finally fixes is the decades worth of N times a year debate on this issue. It's a cumulative friction and waste of time. By selecting just one and sh, that goes away, and can move forward there now too :) > More bashism and linuxism in BSD world, > you are waking the devil. It was meant to say 'sh-like', bash is GPL so it shouldn't be in BSD base, the two shells just have some common than with *csh. Let the beastie daemon... and its more free copyright and unique approach to the "unix", its ongoing "pros" "innovatives" and much more that make bsd good... boil the waterparks of linux into vaporware ;) > Like https://github.com/shellspec/shellbench ? Interesting tool and data :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAD2Ti28tkY=Fyz-OrTjxQVwrNaDxitO_bn29TxoM=9WoP1ON5Q>