Configuring a valid system hostname during install and boot
We do not do a very good job of making sure that systems have a valid hostname. This session is to review the ways that hostname gets set during install and on boot for desktop and server and for DHCP and static assignment and have clear documentation on how this is supposed to work so we can identify all the current deficiencies and get them fixed.
See the following thread for more detail:
https:/
Blueprint information
- Status:
- Not started
- Approver:
- Robbie Williamson
- Priority:
- High
- Drafter:
- Colin Watson
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- Accepted for natty
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
| Bug #677496: do not add localhost.localdomain entries to loopback addresses | Fix Released |
Whiteboard
Work items:
[mathieu-tl] NM shouldn't write localhost.
[cjwatson] strip any trailing dot from domain: DONE
[lamont] make postfix cope with invalid hostname (270521): TODO
[clint-fewbar] Make postfix's apport hook include /var/log/
[cjwatson] check that ubiquity's netcfg clone is in sync: DONE
fix netcfg to make it possible for ubiquity to use it directly: TODO
line-by-line compare netcfg's hostname validation with postfix's: TODO
