Le 04/01/2017 à 16:31, Michael Biebl a écrit : > Am 04.01.2017 um 15:41 schrieb Michael Biebl: >> Am 04.01.2017 um 14:59 schrieb Aurélien COUDERC: >> >>> For fsck/others I think the support is to be done… everywhere else ! >>> Basically we've taken inspiration (read blindly copied) what Ubuntu >>> does, so Plymouth and the Debian theme support fsck display since wheezy. >>> The missing part is that init/fsck/whoever else actually sends >>> information to plymouthd to display. >> >> >> I actually think this is not the case. systemd, or rather fsckd *does* >> send progress information (see the patch we ship in Debian for systemd >> [1]) for plymouth. But it seems this information is not used on either >> the plymouth or the theme side. > > I just tried the following > > a/ copied /usr/share/plymouth/themes/ubuntu-logo/ from a Ubuntu yakkety > installation into my Debian sid system > b/ plymouth-set-default-theme ubuntu-logo > c/ update-initramfs -u > > Upon reboot, I get the Ubuntu plymouth splash screen and progress > information seems to work nicely (I get the msg that fsck is running for > 1 Disk and the percentage done). I can successfully cancel the fsck > process with CTRL+C > > So it looks like systemd and plymouth provide everything that's needed > and it's a theme issue.
Indeed, I ensure we do have all bits needed in plymouth, and then, only the themes can hook up as they need and treat the prepending "fsckd:" message in a special way (took a look at what we do in the text and ubuntu-logo theme, it should be straightforward) Didier
