In fact I don't think we even deliberately enabled parallelized background fsck'ing. For this bug and bug 255563 I just plan to make the init scripts wait properly for fsck termination again. For now I have no idea why fsck suddenly runs in the background, the usplash scripts didn't change since Hardy. We probably inherited it from Debian with a new sysvinit merge, I'll track it down.
In fact I don't think we even deliberately enabled parallelized background fsck'ing. For this bug and bug 255563 I just plan to make the init scripts wait properly for fsck termination again. For now I have no idea why fsck suddenly runs in the background, the usplash scripts didn't change since Hardy. We probably inherited it from Debian with a new sysvinit merge, I'll track it down.