Generate /etc/casper.conf when building a livefs instead of having casper guess the product name at boot time
Bug #904482 reported by
Stéphane Graber
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| casper (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
| livecd-rootfs (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Today's casper (1.295) now uses the product name as the username and hostname, instead of the hardcoded "ubuntu" we used to have everywhere.
It's doing that by parsing .disk/info at boot time and changing its environment to what it finds in there.
This works fine except that it's then non-trivial for something running in the live environment to know what hostname and username ended up using (well, hostname is pretty easy :)).
Instead, it'd be better to have /etc/casper.conf in the livefs contain the right HOST and USERNAME, these will then be used by casper (deprecating the code I added today) and by software running in the live environment like ubiquity (through its ubiquity.casper module).
Related branches
Revision history for this message
| Mario Limonciello (superm1) wrote | #1 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in casper (Ubuntu): | |
| status: | New → Fix Released |
| Changed in casper (Ubuntu): | |
| status: | Fix Released → New |
| Changed in livecd-rootfs (Ubuntu): | |
| status: | New → Triaged |
| Changed in casper (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in livecd-rootfs (Ubuntu): | |
| importance: | Undecided → Low |
Revision history for this message
| Sergey "Shnatsel" Davidoff (shnatsel) wrote | #3 |
To post a comment you must log in.
I've added a temporary workaround for casper that makes the changes in the casper.conf in the initrd (as well as livefs) until this can be fixed directly in livecd-rootfs.
This will unbreak any applications that were parsing casper.conf to find the proper values to be using for now.