m...@msys.ch wrote: > >>> I think this utility should be renamed wakeonlan because wake is > >>> too generic. > >> > >> FWIW I agree ... > > > > I disagree. Totally. > > > > and I forgot to mention why: the command name reflects what the > command does, > not how it does it. wakeonlan would be misleading, because a LAN > could also > be a token ring, where this would nor work... (ok, exaggerating a bit, > but you get > the idea) > > should we rename ssh to sshovertcpip ;) tcpdump to tcpdumponlan?
It looks you missed the point. - christos said "wake is ambiguous," not "all command should be verbose" - ssh and tcpdump are third party commands, so you can't refer them for examples Now you see an example that discussion after commit is annoying ;-p --- Izumi Tsustui
