A curio I found working my way through the ifup execution traces is
that while ifup-local is called with the device name (eth0),
ifup-pre-local is called with the config file name (ifcfg-eth0).

Not the end of the world, but as these hooks aren't documented (that I
could find at least) and google has few hits for them,I thought it was
worth a mention.

cheers,



m
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Martin Langhoff (martin.langhoff@gmail.com) said:
> A curio I found working my way through the ifup execution traces is
> that while ifup-local is called with the device name (eth0),
> ifup-pre-local is called with the config file name (ifcfg-eth0).
>
> Not the end of the world, but as these hooks aren't documented (that I
> could find at least) and google has few hits for them,I thought it was
> worth a mention.

It's actually consistent with the main scripts, if confusing - ifup-pre-local
is called with the config (as ifup is), while ifup-local is called with the
device (as ifup-post is).

Bill

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list