I had a look at this, and believe your analysis of the problem is
wrong. First of all, the only ifdown related comment I find in the
changelog is this:
sysvinit (2.86.ds1-4) unstable; urgency=low
[...]
* Get ifdown working on kFreeBSD. (Closes: #327031)
[...]
-- Petter Reinholdtsen <[EMAIL PROTECTED]> Sun, 2 Oct 2005 11:44:07 +0200
[...]
sysvinit (2.75-2) frozen unstable; urgency=medium
[...]
* In ifdown.c first down all shaper devices then the real devices
[...]
-- Miquel van Smoorenburg <[EMAIL PROTECTED]> Tue, 2 Jun 1998 22:43:01
+0200
Nothing in the changelog about non-linux archs disabling ifdown for
their arch. Looking at the freebsd patch prove that there is no such
change being done either. In short, it is a dead end looking at
changes related to freebsd, and I am unable to find any code present
disabling the ifdown() function used by halt. To further check it,
run 'strings /sbin/halt |grep ifdown' and see how the text message
"ifdown: shutdown" is present in the binary. This text is only
present in the ifdown() function, proving that the function is present
in the halt binary. This make me believe that the size observation is
irrelevant to this problem to.
So, that leave me with only your observation that the Wake-On-LAN
feature do not work with the current sysvinit package, and no idea how
to debug it. Could this be related to bug #361935, a problem with
interfaces without a IP address?
Can you try to use 'strace halt' instead of just 'halt' to see if some
system call fail? I'm not sure how to debug this, as I do not have a
WOL-enabled machine to test on.
Friendly,
--
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
