** Description changed: During instance boot, cloud-init installs packages (if instructed by the user). During instance boot, there is no state of the system that the user cares about. I'd like to use eatmydata for apt-get install at that point, as it is dramatically faster than apt-get even with --force-unsafe-io. From an ubuntu perspective, this change would mean: a.) depending on (or recommending) eatmydata b.) MIR for eatmydata - c.) fixing eatmydata's relationship with sysvinit scripts. The thing to fix there is that if you 'eatmydata apt-get install some-service' and some-service starts a daemon, the daemon will inherit the LD_PRELOAD which is most likely not desired. + c.) fixing eatmydata's relationship with sysvinit scripts. The thing to fix there is that if you 'eatmydata apt-get install some-service' and some-service starts a daemon, the daemon will inherit the LD_PRELOAD which is most likely not desired. (bug 1257036) + + Related bugs: + * bug 1257036: services started with eatmydata should remove eatmydata by default
** No longer affects: libeatmydata (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1236531 Title: support running apt with eatmydata To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1236531/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
