At 7:04 AM +0200 7/1/09, Blapp, Martin wrote:
Hi folks,
I really was not my or Marcs intention to skip any discussions. Rwatson
told us that if we like to see it in 8.0, we need to approve it by RE
and commit it before the 1. of july, and that's what I've done. Sorry
if I've upset anyone.
Perso
On Wed, 1 Jul 2009, Blapp, Martin wrote:
I really was not my or Marcs intention to skip any discussions. Rwatson told
us that if we like to see it in 8.0, we need to approve it by RE and commit
it before the 1. of july, and that's what I've done. Sorry if I've upset
anyone.
Personally I thi
On Wed, 1 Jul 2009 01:45:53 +0400 Stanislav Sedov wrote:
> > + p = (u_char *)&pkt;
> > + len = sizeof(pkt);
> > + bw = 0;
> > + while (len) {
> > + if ((bw = write(bpf, &pkt, sizeof(pkt))) == -1)
> > + return -1;
> > + len -= bw;
> > + p += b
Am 01.07.2009 um 07:04 schrieb Blapp, Martin:
If the concensus is to back it out, I'll back it out.
That would be sad. After all there were very positive reactions from
folks that actually looked at the tool, the negative replies came from
folks that saw some process violated, iirc
Am 01.07.2009 um 07:04 schrieb Blapp, Martin:
Hi folks,
I really was not my or Marcs intention to skip any discussions.
Rwatson told us that
if we like to see it in 8.0, we need to approve it by RE and commit
it before the 1. of july,
and that's what I've done. Sorry if I've upset anyone.
> Nice! I guess I can now remove installed net/wol ports which does
> not work as expected when system have multiple interfaces. And I
> didn't understand why it requires perl to build such a simple
> utility.
Have a look at the build process and you see exactly why it needs
perl. The question sho
Hi folks,
I really was not my or Marcs intention to skip any discussions. Rwatson told us
that
if we like to see it in 8.0, we need to approve it by RE and commit it before
the 1. of july,
and that's what I've done. Sorry if I've upset anyone.
Personally I think the tool is quite handy, better
Martin Blapp skrev:
Author: mbr
Date: Tue Jun 30 18:51:22 2009
New Revision: 195200
URL: http://svn.freebsd.org/changeset/base/195200
Log:
Add wake, a tool to send Wake on LAN frames to hosts on a local Ethernet
network
Nice. Now I can finally nuke net/wol from my systems.
--
Joel
___
On Tue, 2009-06-30 at 21:56 -0400, Ken Smith wrote:
> On Tue, 2009-06-30 at 16:40 -0600, M. Warner Losh wrote:
> > I hate to be blunt, but this leaves a bad taste in everybody's mouth,
> > even if at the end of the day you get your way.
>
> Translation: I did it again. I hate it when that happens
On Tue, Jun 30, 2009 at 09:56:42PM -0400, Ken Smith wrote:
> On Tue, 2009-06-30 at 16:40 -0600, M. Warner Losh wrote:
> > I hate to be blunt, but this leaves a bad taste in everybody's mouth,
> > even if at the end of the day you get your way.
>
> The second thing that left a bad taste in some peo
At 2:09 PM -0700 6/30/09, Sam Leffler wrote:
I have yet to hear a compelling argument for why wake was chosen
over an existing tool that's been successfully used for a while.
OTOH this isn't something that'll keep me up at night; it just seems
like an ill-advised rush job that completely viol
On Tue, 2009-06-30 at 16:40 -0600, M. Warner Losh wrote:
> I hate to be blunt, but this leaves a bad taste in everybody's mouth,
> even if at the end of the day you get your way.
Translation: I did it again. I hate it when that happens... :-(
Two things happened here that were a bit unfortunate
On Tue, Jun 30, 2009 at 06:51:23PM +, Martin Blapp wrote:
> Author: mbr
> Date: Tue Jun 30 18:51:22 2009
> New Revision: 195200
> URL: http://svn.freebsd.org/changeset/base/195200
>
> Log:
> Add wake, a tool to send Wake on LAN frames to hosts on a local Ethernet
> network
>
> Submitte
In message: <7b9c309f-63e3-4cb8-9871-de2dee010...@msys.ch>
Marc Balmer writes:
:
: Am 30.06.2009 um 22:13 schrieb M. Warner Losh:
:
: > In message: <0e6d4fb2-a485-40ed-a856-acc311a90...@msys.ch>
: >Marc Balmer writes:
: > :
: > : Am 30.06.2009 um 21:36 schrieb M. Warner
Am 30.06.2009 um 23:43 schrieb Kostik Belousov:
On Tue, Jun 30, 2009 at 11:34:36PM +0200, Marc Balmer wrote:
Am 30.06.2009 um 23:29 schrieb Kostik Belousov:
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 t
On Tue, 30 Jun 2009 18:51:23 + (UTC)
Martin Blapp mentioned:
> Author: mbr
> Date: Tue Jun 30 18:51:22 2009
> New Revision: 195200
> URL: http://svn.freebsd.org/changeset/base/195200
>
> Log:
> Add wake, a tool to send Wake on LAN frames to hosts on a local Ethernet
> network
>
Cool!
On Tue, Jun 30, 2009 at 11:34:36PM +0200, Marc Balmer wrote:
>
> Am 30.06.2009 um 23:29 schrieb Kostik Belousov:
> >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 centr
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
On Tue, Jun 30, 2009 at 11:25:56PM +0200, Marc Balmer wrote:
>
> Am 30.06.2009 um 23:09 schrieb Sam Leffler:
>
> >Marc Balmer wrote:
> >>
> >>Am 30.06.2009 um 21:07 schrieb Sam Leffler:
> >>
> >>>Martin Blapp wrote:
> Author: mbr
> Date: Tue Jun 30 18:51:22 2009
> New Revision: 195200
2009/6/30 Marc Balmer :
>
> Am 30.06.2009 um 21:36 schrieb M. Warner Losh:
>
>> wake really is too generic a name for this. Why didn't the wol port
>> get committed anyway, it seems to be better than this...
>
> wake is a short, mnemonic and imperative name that describes what the
> command does.
Am 30.06.2009 um 23:09 schrieb Sam Leffler:
Marc Balmer wrote:
Am 30.06.2009 um 21:07 schrieb Sam Leffler:
Martin Blapp wrote:
Author: mbr
Date: Tue Jun 30 18:51:22 2009
New Revision: 195200
URL: http://svn.freebsd.org/changeset/base/195200
Log:
Add wake, a tool to send Wake on LAN frames
Marc Balmer wrote:
Am 30.06.2009 um 21:36 schrieb M. Warner Losh:
wake really is too generic a name for this. Why didn't the wol port
get committed anyway, it seems to be better than this...
wake is a short, mnemonic and imperative name that describes what the
command does. It is exactly t
Marc Balmer wrote:
Am 30.06.2009 um 21:07 schrieb Sam Leffler:
Martin Blapp wrote:
Author: mbr
Date: Tue Jun 30 18:51:22 2009
New Revision: 195200
URL: http://svn.freebsd.org/changeset/base/195200
Log:
Add wake, a tool to send Wake on LAN frames to hosts on a local
Ethernet network
Sub
In message: <7b9c309f-63e3-4cb8-9871-de2dee010...@msys.ch>
Marc Balmer writes:
:
: Am 30.06.2009 um 22:13 schrieb M. Warner Losh:
:
: > In message: <0e6d4fb2-a485-40ed-a856-acc311a90...@msys.ch>
: >Marc Balmer writes:
: > :
: > : Am 30.06.2009 um 21:36 schrieb M. Warner
Am 30.06.2009 um 22:02 schrieb Thomas Backman:
On Jun 30, 2009, at 08:51 PM, Martin Blapp wrote:
+void
+usage(void)
+{
+ (void)fprintf(stderr, "usage: wake interface lladdr\n");
+ exit(0);
+}
[...]
+ for (n = 2; n < argc; n++)
+ if (wake(argv[1], argv[n]))
+
Am 30.06.2009 um 22:13 schrieb M. Warner Losh:
In message: <0e6d4fb2-a485-40ed-a856-acc311a90...@msys.ch>
Marc Balmer writes:
:
: Am 30.06.2009 um 21:36 schrieb M. Warner Losh:
:
: > wake really is too generic a name for this. Why didn't the wol
port
: > get committed anyway, it
On Jun 30, 2009, at 08:51 PM, Martin Blapp wrote:
+void
+usage(void)
+{
+ (void)fprintf(stderr, "usage: wake interface lladdr\n");
+ exit(0);
+}
[...]
+ for (n = 2; n < argc; n++)
+ if (wake(argv[1], argv[n]))
+ warnx("error sending Wake on
In message: <0e6d4fb2-a485-40ed-a856-acc311a90...@msys.ch>
Marc Balmer writes:
:
: Am 30.06.2009 um 21:36 schrieb M. Warner Losh:
:
: > wake really is too generic a name for this. Why didn't the wol port
: > get committed anyway, it seems to be better than this...
:
: wake is a sho
Am 30.06.2009 um 21:07 schrieb Sam Leffler:
Martin Blapp wrote:
Author: mbr
Date: Tue Jun 30 18:51:22 2009
New Revision: 195200
URL: http://svn.freebsd.org/changeset/base/195200
Log:
Add wake, a tool to send Wake on LAN frames to hosts on a local
Ethernet network
Submitted by: Marc B
Am 30.06.2009 um 21:36 schrieb M. Warner Losh:
wake really is too generic a name for this. Why didn't the wol port
get committed anyway, it seems to be better than this...
wake is a short, mnemonic and imperative name that describes what the
command does. It is exactly the same command as
wake really is too generic a name for this. Why didn't the wol port
get committed anyway, it seems to be better than this...
Warner
In message: <200906301851.n5uipnjq089...@svn.freebsd.org>
Martin Blapp writes:
: Author: mbr
: Date: Tue Jun 30 18:51:22 2009
: New Revision: 195200
:
Martin Blapp wrote:
Author: mbr
Date: Tue Jun 30 18:51:22 2009
New Revision: 195200
URL: http://svn.freebsd.org/changeset/base/195200
Log:
Add wake, a tool to send Wake on LAN frames to hosts on a local Ethernet
network
Submitted by: Marc Balmer
Reviewed by:rwatson
Approved b
Author: mbr
Date: Tue Jun 30 18:51:22 2009
New Revision: 195200
URL: http://svn.freebsd.org/changeset/base/195200
Log:
Add wake, a tool to send Wake on LAN frames to hosts on a local Ethernet
network
Submitted by: Marc Balmer
Reviewed by:rwatson
Approved by: re
Musr.sb
33 matches
Mail list logo
