Hello,
On Sun, 20 May 2012 22:15:58 +0100
Justin B Rye <jbr@edlug.org.uk> wrote:
> > If ifup or ifquery is called with the --all option, if doesn't
> > just bring up all interfaces marked as "auto", but all interfaces
> > of a specified class, 'auto' by default. For the most uses, this
> > doesn't change anything, but lets all the interfaces of a specific
> > class to be brought up or queried.
> There are a couple of tiny grammar glitches there, and a fiendishly
> subtle distinction between "auto" and 'auto'. More importantly, when
> it says "ifup or ifquery", it seems in fact to mean "ifup, ifdown, or
> (the new addition) ifquery".
No, it doesn't mean that. Ifdown works with all interfaces currently
up, that's why it's not mentioned here.
> Thanks for sneaking in /sbin/ifquery, by the way!
> > If ifupdown is called with the --all option, before or after
> > doing
> I spent a while trying to work out why it should be drawing this
> contrast between "If ifup or ifquery is called with the --all option"
> and "If ifupdown is called with the --all option". But I don't think
> that's intended - when it says "ifupdown" here it doesn't mean (say)
> /etc/init.d/ifupdown, it's using the name as a shorthand for "the
> single binary hardlinked as ifup and ifdown". That seems like an
> unnecessarily obscure implementation detail, especially when in fact
> ifquery now provides a third name for the same file!
Actually, it's intended ;) ifupdown == 'ifup or ifdown or ifquery', or,
in some cases, 'ifup or ifdown'.
> Or here's an ultra-squeezed version of the whole thing:
> The --all option to if{up,down,query} can now be combined with the
> --allow option to act on all interfaces of a specific class (still
> defaulting to the class "auto"). See interfaces(5) for details of
> how hook scripts are called.
Sounds good. Probably will use this 'squeezed' version.
--
WBR, Andrew
Attachment:
signature.asc
Description: PGP signature