Re: Bug#3146: 1.1 installation: ae doesn't work
bruce@pixar.com (Bruce Perens) wrote on 29.05.96 in <[🔎] m0uOxyy-0005z7C@mongo.pixar.com>:
> This is something we should probably take up with the FSSTD group,
> as I think our reasons for not using "ed" are valid. I agree that
> there should be _an_ editor available, and that there should perhaps
> be certain command names that are guaranteed to get you an editor.
> However, compelling users to learn "ed" these days makes about as much
> sense as compelling ham radio operators to learn Morse Code.
Actually, I seem to recall that the reason for ed is scripts, not humans.
However, the standard doesn't say, and the newest draft (5) for the next
version is nearly exactly identical in this respect:
Version 1.2:
[...]
Required files for /bin:
o General commands:
The following commands have been included because they are
essential. A few are present because of their traditional
placement in /bin.
{ arch, cat, chgrp, chmod, chown, cp, date, dd, df, dmesg, echo,
ed, false, kill, ln, login, ls, mkdir, mknod, more, mount, mv,
ps, pwd, rm, rmdir, sed, setserial, sh, stty, su, sync, true,
umount, uname }
If /bin/sh is Bash, then /bin/sh should be a symbolic or hard link
[...]
Draft:
[...]
.HU "Required files for /bin:"
.BL
.LI
General commands:
.sp
The following commands have been included because they are essential. A
few are present because of their traditional placement in \f(CW/bin\fP.
.VL 2
.LI "\f(CW{"
cat, chgrp, chmod, chown, cp, date, dd, df, dmesg, echo, ed,
false, kill, ln, login, ls, mkdir, mknod, more, mount, mv, ps, pwd, rm,
rmdir, sed, setserial, sh, stty, su, sync, true, umount, uname }\fP
.LE
.P
If \f(CW/bin/sh\fP is Bash, then \f(CW/bin/sh\fP should be a symbolic or
[...]
That is, arch is gone, everything else stays the same.
MfG Kai
Reply to: