Date: Tue, 30 Jun 2009 23:34:36 +0200 From: Marc Balmer <marc@msys.ch> To: Kostik Belousov <kostikbel@gmail.com> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, Sam Leffler <sam@freebsd.org>, Martin Blapp <mbr@freebsd.org>, src-committers@freebsd.org Subject: Re: svn commit: r195200 - in head/usr.sbin: . wake Message-ID: <C82689DB-5B5A-42C9-B486-A7259E9557AD@msys.ch> In-Reply-To: <20090630212936.GC2884@deviant.kiev.zoral.com.ua> References: <200906301851.n5UIpNJQ089171@svn.freebsd.org> <4A4A626A.4080801@freebsd.org> <5A796102-063B-4032-92C9-EC97AF2E5D5B@msys.ch> <4A4A7F0B.1010001@freebsd.org> <70EA13C9-997D-488D-83D6-06D603B76D11@msys.ch> <20090630212936.GC2884@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 30.06.2009 um 23:29 schrieb Kostik Belousov: [...] >> >> a compelling argument could be that wake(8) is BSD licensed while wol >> found in ports/net/wol is GPL licensed and brings in a whole lot of a >> whole lot of a whole lot of a whole lot of a stuff with it, when >> actually, to send out Wake on LAN package, a small BSD licensed >> command like wake(8) is sufficient. it is much smaller an cleaner >> code. > > Then, add the wake program to ports. > My opinion is that this better be kept in ports. I find it a rather basic operation to be able to wake up remote systems from a central place, so I think base is the right place for this. Wak-on-LAN as become part of our everydays IT infrastructure, as much as we support it in BIOSes and ifconfig's, we should also support waking up systems.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C82689DB-5B5A-42C9-B486-A7259E9557AD>