On Thu, Sep 11, 2014 at 06:44:37PM +0200, Kurt Roeckx wrote: > > So I changed both FORK cases to be: $cmd "$@" > > That doesn't change anything, and I don't see why that should > change anything.
Strange things can happen early in the boot process and this is the only relevant change between the recent versions of console-setup and the previous versions (and the previous versions have been tested for more than an year, so I trust they don't have the bug you reported). There have been bug reports about console-setup hanging because (maybe?) of non-existent devices /dev/ttyN. Nobody knows the cause of this and the forks in the present version of console-setup are there to fight this. Now, imagine this is what happens in your system. The previous version of console-setup would hang but the present is going to fork hanging printf commands instead. These printf commands are what configures the console from UTF-8 to 8-bit mode. We can hope that eventualy /dev/ttyN will activate and the printf will do its job, but who knows... maybe something is killing these processes (init, systemd, whatever). Anton Zinoviev -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140912132341.ga11...@logic.fmi.uni-sofia.bg
