AutoYast uses proper variables for s390 instead of LanItems::chan_mode.
Merge pull request #31 from mchf/Code-11-SP2

AutoYast uses proper variables for s390 instead of LanItems::chan_mode.
Fixing the incomplete commit e34287a8d5160a31bf909490906cdd5d530702d3
InitSlave: Formatting, indentation. Fixed debug level.
Only devices with L2 support can be enslaved in bond. See bnc#719881

When creating bond device on s390 all devices used to be offered for
enslaving. This was incorrect because devices without MAC cannot be
used by Linux bond driver.
Added loading qeth config during NICs switching (SetItem).
Updated changelog
Merge pull request #35 from mchf/Code-11-SP2

s390: Only devices with Layer 2 support can be enslaved in bond (bnc#719881)
AutoYaST: write /etc/hosts even if keep_install_network=true (bnc#796580)

The regression was introduced in SP2 in yast2-network-2.17.166
(2012-01-13) in a fix for bnc#712864.
https://github.com/yast/yast-network/commit/4f67f62d9f16f774fac6870d932a53d1d29d10dc
There, a Lan::Read(`cache) call is added with the intent to merge in the
config provided by linuxrc; it also calls Host::Read, which should
always cache, but wrongly discards the Host::Import'ed data. So a later
Host::Write call thinks there is nothing new to write.
(y2log: "Host.ycp:153 Hosts not modified")

This is an incomplete fix for early testing. It should work
but leaves the code messy: `modified`, `initialized` and
`hosts_init` should all be merged.
version + .changes