From: Stephen Hemminger <shemminger@osdl.org>
To: Auke Kok <auke-jan.h.kok@intel.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: Wake On Lan device semantics
Date: Fri, 3 Nov 2006 17:37:51 -0800 [thread overview]
Message-ID: <20061103173751.581ca5ab@localhost.localdomain> (raw)
In-Reply-To: <454BEEAD.70108@intel.com>
On Fri, 03 Nov 2006 17:36:45 -0800
Auke Kok <auke-jan.h.kok@intel.com> wrote:
> Stephen Hemminger wrote:
> > On Fri, 03 Nov 2006 15:44:13 -0800
> > Auke Kok <auke-jan.h.kok@intel.com> wrote:
> >
> >> Stephen Hemminger wrote:
> >>> It doesn't seem like a good idea for a network device to wake the system
> >>> if it is down.
> >> before suspend existed this was the only useful case for WoL. Why does it not seem a
> >> good idea to wake up a machine that was shutdown (and thus the interface `downed`) ?
> >>
> >> Auke
> >
> > Interestingly it looks like e100 is one of the ones that only wakes from suspend (not when down).
>
> that would be a bug, I'll have to get that checked especially after the latest changes
> to it.
>
Sorry, my bad my test machine was not setup properly.
next prev parent reply other threads:[~2006-11-04 1:38 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 [this message]
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
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=20061103173751.581ca5ab@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=auke-jan.h.kok@intel.com \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.