[Pkg-sysvinit-devel] Bug#764786: initscripts: forced fsck on root filesystem doesn't give progress after installing sysvinit-core

[Arthur Marsh]

Package: initscripts
Version: 2.88dsf-53.4
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

After installing sysvinit-core and associated systemd stuff, I had a situation
where the root filesystem had been mounted 34 times without checking and an
fsck was forced.

The fsck completed successfully but there was no progress indication unlike 
previously and I could not even tell if fsck was running or if the boot
process had hung until it completed.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

Progress reports on all fsck at boot-up.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.17.0+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages initscripts depends on:
ii  coreutils       8.23-2
ii  debianutils     4.4
ii  libc6           2.19-11
ii  lsb-base        4.1+Debian13
ii  mount           2.25.1-3
ii  sysv-rc         2.88dsf-53.4
ii  sysvinit-utils  2.88dsf-53.4

Versions of packages initscripts recommends:
ii  e2fsprogs  1.42.12-1
ii  psmisc     22.21-2

initscripts suggests no packages.

-- Configuration Files:
/etc/default/rcS changed:
VERBOSE=yes


-- no debconf information