Marc Balmer wrote: > Am 27.06.2009 um 00:08 schrieb Marc Balmer: > > > > > Am 26.06.2009 um 20:22 schrieb David Laight: > > > >> On Fri, Jun 26, 2009 at 01:38:32PM -0400, Christos Zoulas 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?
"wake" is a lot more generic term than "ssh" or "tcpdump". When I first saw the subject "CVS commit: src/usr.sbin/wake" it wasn't in any way obvious that this sent wake-on-lan packets to remote hosts. My first guess was something that "woke up" processes blocked in the kernel that are otherwise unkillable - try "man -k wake" for example. Cheers, Simon.
