The problem sits in the postinst script, which calls siloconfig. siloconfig is interactive and asks questions in the background:
- Install a boot block using your current SILO configuration? - Wipe out your old SILO configuration and make a new one? - Install a partition boot record to boot Linux from $device? The right way to fix it would be to add command line options to siloconfig and wire them up to debconf. The attached patch simply pipes in `yes' to siloconfig in the postinst to make it work. As I understand it, it is safe to say yes to all three questions above, even in multi-boot environments. ** Patch added: "silo-fix-siloconfig-hanging-in-background.patch" http://launchpadlibrarian.net/39955371/silo-fix-siloconfig-hanging-in-background.patch -- Install hangs on SILO using a LDom on a T5220 https://bugs.launchpad.net/bugs/194032 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
