Jasper Capel wrote:
Michael DeHaan wrote:
> Right now the interface name could be arbitrary, so it seems it would
> only depend on the magic to set things up right in %post. Does anyone
> care to take a shot at cleaning up the "post-network-system-config"
> snippet on the Wiki now? We should make it account for mutliple
> interfaces first, add it to %post in the default templates, and then we
> can teach it about bonding once that is established.
>
I spent some time on this yesterday, but unfortunately I won't be able
to test it this week, so there's probably some typo in it.
If someone wants to look at it, then great, else I'll try to find the
time next week. :)
Tested, removed a few bugs and this works for EL5 now. I don't know if
we'd want to call this one by default, as there's still a default
interface intf0 for systems. This would result in the first interface
being called intf0 instead of eth0, which doesn't make much sense to me.
I think we should change that behaviour first. :)
And I'm not too happy with the name post_network_system_config, so I
renamed it to post_install_network_config, any objections?
Once this is done, we can look into bonding and vlan support. VLANs
would be fairly easy, so that's a nice next target.
http://bender.newnewyork.nl/git/gitweb.cgi?p=cobbler/.git;a=shortlog;h=re...
or:
git://bender.newnewyork.nl/cobbler (branch: post-network)
Jasper