Hi Scott, thanks for you comment. While I agree with you that simply returning 0 in one function won't solve *all* problems, it'll solve this one, in a cheap and fast way.
I tend to think initramfs-tool is a quite important package, it's part of the boot process. And yet, we have plenty of 5yr+ bugs complaining about this, while we couldn't find a perfect/generic solution. So I proposed we fix this one, for the sake of the giant user base in Ubuntu and Debian, and at small steps pursue a generic solution for the write() problem, that may involve a discussion with kernel and a change in long-term behavior. I'd rather not let users waiting while we do that... Oh, and I read the other LP you mentioned, it seems a different place of failure, in a different project. I say we go and fix there too, while we work a more generic/elegant solution. But that bug (cloud-init growpart related) it's not so common than this one (here we just need to remove 'quiet' and set the wrong console to break boot completely), so that one is a bit less priority than this one. Initramfs-tools is full of quirks to prevent issues, given its relevant role in the boot process. Thanks, Guilherme -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
