auto url=autoserver fetches wrong preseed file (squeeze, not maverick/natty/oneiric)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
preseed (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Maverick |
Won't Fix
|
Low
|
Unassigned | ||
Natty |
Won't Fix
|
Low
|
Unassigned |
Bug Description
While experimenting with d-i, I stumpled in the documentation https:/
<quote>
There are several features of Debian Installer that combine to allow fairly simple command lines at the boot prompt to result in arbitrarily complex customized automatic installs. To illustrate this, here are some examples that can be used at the boot prompt:
auto url=autoserver
This relies on there being a DHCP server that will get the machine to the point where autoserver can be resolved by DNS, perhaps after adding the local domain if that was provided by DHCP. If this was done at a site where the domain is example.com, and they have a reasonably sane DHCP setup, it would result in the preseed file being retrieved from http://
</quote>
This, however, is wrong, a tcpdump revealed that the installer tries to download http://
Related branches
- Colin Watson: Approve
-
Diff: 26 lines (+8/-1)2 files modifieddebian/changelog (+7/-0)
debian/network-preseed.templates (+1/-1)
- Ubuntu Core Development Team: Pending requested
-
Diff: 46 lines (+13/-3)3 files modifieddebian/changelog (+7/-0)
debian/control (+5/-2)
debian/network-preseed.templates (+1/-1)
- Ubuntu Core Development Team: Pending requested
-
Diff: 46 lines (+13/-3)3 files modifieddebian/changelog (+7/-0)
debian/control (+5/-2)
debian/network-preseed.templates (+1/-1)
I've now pushed a proposed fix for natty in the linked bzr branch, but I didn't actually test it.
From looking at the source code, I strongly believe that the same problem also exists in maverick and lucid. For maverick the fix is basically the same. However, I don't understand how the url is determined in lucid.