Allow for the HWADDR configuration line to optionally disabled #42
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Unfortunately in some really unsual environements, the MAC address may not be persistent. In some environments there may even be a valid reason for the MAC address not being persistent.
In our z/vm environment a guest may move from one LPAR to another and boot up with a different MAC address. Hence it's useful to make the HWADDR line in the network config file optional. This doesn't cause an issue, since the SUBCHANNELS line exists in this case.
Ideally our z/vm environment would be configured correctly, in that the MAC address would be persistent but that is another issue altogether.