"cpu" command, other related stuff

[Nigel Roles ngr@symbionics.co.uk]

> if you really wanted to do this, i wouldn't break cpu.  i'd write findcpu:
>
>    cpu -h `{findcpu}
>
> or you could use it to set $cpu at login.
>
> i think cpu was intended to be used with a particular cpu server, not
> just one with a low 'load average' [a totally foreign concept to plan
> 9].  the choice being based on a particular function that cpu fulfills.
>
Also, making the decision once at the start is about as much use as a
chocolate teapot, since you might well stay connected to a CPU server
for days. In a 'real' system you might wish to choose the cpu
with the fast link to the fileserver where your files live.


Nigel Roles