netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: David Miller <davem@davemloft.net>
Cc: shemminger@osdl.org, netdev@vger.kernel.org
Subject: Re: Wake On Lan device semantics
Date: Fri, 03 Nov 2006 19:42:49 -0500	[thread overview]
Message-ID: <454BE209.4020407@pobox.com> (raw)
In-Reply-To: <20061103.160230.71088561.davem@davemloft.net>

David Miller wrote:
> From: Jeff Garzik <jgarzik@pobox.com>
> Date: Fri, 03 Nov 2006 18:51:25 -0500
> 
>> The purpose of WOL is being able to turn on a system remotely, if it is 
>> in a power-off or sleep state.
>>
>> So, if the system is -on- and the interface is down and/or driver is 
>> unloaded, are you saying WOL is a problem somehow?
> 
> Stephen is saying that if you down an interface, it should disable
> that WoL functionality.

Many distros down the interface on poweroff, a state from which WOL is 
often used, so we don't want this.


> I guess you can argue that, like IP addresses, this WoL thing is an
> attribute of the "system".

Yeah, it's definitely a system state.  When the magic packet arrives, 
the WOL wire on the motherboard is tickled, turning the machine on.

	Jeff



  parent reply	other threads:[~2006-11-04  0:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-03 23:20 Wake On Lan device semantics Stephen Hemminger
2006-11-03 23:44 ` Auke Kok
2006-11-03 23:48   ` Stephen Hemminger
2006-11-04  1:35     ` Auke Kok
2006-11-03 23:50   ` Stephen Hemminger
2006-11-04  1:36     ` Auke Kok
2006-11-04  1:37       ` Stephen Hemminger
2006-11-04  1:44         ` Auke Kok
2006-11-03 23:51 ` Jeff Garzik
2006-11-04  0:02   ` David Miller
2006-11-04  0:11     ` Stephen Hemminger
2006-11-04  1:53       ` Auke Kok
2006-11-04  0:42     ` Jeff Garzik [this message]
2006-11-04  1:02       ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=454BE209.4020407@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).