Subject: Re: bin/4167: WIBNI sh supported file/command/etc completion?
To: None <current-users@NetBSD.ORG>
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
Date: 09/28/1997 10:41:31
> I'm a very fast typist, and I still get a great deal of benefit out
> of shell history recall, command line editing and filename
> I don't particularly care if it's in sh, since I don't use sh, but if
> other people do use sh and do care, I think it's perfectly reasonable
> to add it.
Ditto here - but not in the root filesystem.
If we had /bin/sh, a full-featured shell with respect to programming
features but minimalist with respsect to interactive use, and
/usr/bin/sh, bells-whistles-and-gongs, I'd have no problem. Or even if
/bin/sh were minimalist but tried to dlopen /usr/libexec/fatsh.so or
some such, carrying on minimally if it weren't present but using it to
give all the features if it were, that would be fine too.
> I don't understand this macho desire to prevent all ease-of-use
I am not trying to make life harder for people who want to use sh
interactively, except insofar as that is required for what I consider
to be a more important concern, namely, that the stuff in /bin be
minimal and as small as possible. Line editing isn't minimal.
For that matter, what are mountd, nfsd, nfsiod doing in /sbin?
7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B