Don't allow read to make use of the shell's internal '='
terminates var names feature (which exists so in things
like "external foo=bar" the shell can simply set the "variable"
"foo=bar" to "bar" and doesn't need to put \0 on top of the '=',
or copy the var name part elsewhere, and other similar internal
advantages) - in most cases either allowing the '=' is intended, (as
in the export example) or other checks make it impossible (${var} etc),
but nothing was checking the var names passed to the read command.
Fix that ... (side effect is that now if an invalid name is
given, it will be detected before anything is read, before a
prompt is written, rather than after the read, when the vars
are being set to the fields from the line read).
Don't bother doing this in SMALL shells, avoid the (small) extra
code bloat - SMALL shells can just treat being able to say
read a b=hello c (which means the same as read a b c)
as a harmless foible...
PR bin/59495
Make umount less noisy when a single -v is used (just say
what has been unmounted), and only include details of
running (or not running) external umount_fstype progs
when more than one -v is given.
While here, make it more clear in the messages produce
when the -F (fake it) option is used, that nothing was
actually unmounted (just what would have been).
Man page updated to match.
PR bin/59494
Cause "mount -v [spec] filesystem" to indicate only what was
mounted (and where), to obtain all the rest of the data that
used to be printed, -v must be given twice.
Implemented differently from the patch given in the PR from
greywolf, but the same idea.
While here, avoid the -d option, after indicating what mount
command would have been run, but wasn't, going on to attempt
to report statistics on the never mounted filesystem, and
instead getting those from the intended mount point.
Update the man page to match.
final (hopefully...) piece of PowerMac7,2 support - deal with multiple
/u3/i2c/i2c-hwclock instances, figure out which one controls CPU speed, and
call slew-high on it
tests/make: force expected lines to be listed in execution order
The diagnostics from the program to check the "expect" lines in the unit
test files were hard to follow since the "out-of-order" lines were
confusing. For out-of-order lines, state where they should be placed
instead.
tests/make: sort missing messages using a stable algorithm
Lua's table.sort does not provide a stable sort. No idea how this could
go unnoticed for two years and a few days.
Noticed in directive-for-escape.mk, which has several diagnostics in the
same location, in the body of .for loops.
make: fix parsing of modifier parts for :gmtime and :localtime
There's no practical use for escaping the ":" or "}" in these two
modifiers, but the same scheme may prove useful for the :M and :N
modifiers, which are currently parsed in a completely different manner,
thus adding needless complexity.
Parsing of the :M and :N modifiers is discussed in PR bin/46139.
