mythbuntu-bugs team mailing list archive

[Mario Limonciello <superm1@xxxxxxxxxx>]

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.

-- 
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/904482

Title:
  Generate /etc/casper.conf when building a livefs instead of having
  casper guess the product name at boot time

Status in “casper” package in Ubuntu:
  Fix Released
Status in “livecd-rootfs” package in Ubuntu:
  New

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).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/904482/+subscriptions