[Bug 765735] Re: mountall should cause fsck to show progress on text console

Mark - Syminet 765735 at bugs.launchpad.net
Fri Oct 12 12:58:45 UTC 2012


I read some other thread regarding Ubuntu making plymouth a too-strong dependency.  et. al., so I guesss this is our bug.   Most importantly, this: 

https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/556372

...to which you ignored your users?  And this:

https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553285

...to which

It's increasingly possible that you have bug reporters who are capable
of what they are doing, yet thwarted by "best approach" methods
determined by people who are looking out for their own best interests.
Although I might not question your take, if you would like this to go
away then your users would greatly appreciate an explicitly sound
explanation as to why you've decided to ram plymouth, which apparently
ignores the console,  our throats.

I've browsed at least a half-dozen other bug reports, some of them very long, which do not exist in debian systems.  
Although debian is a pain too, at least they are open about everything and those of us wiling and capable of modifying C code,  are not unilaterally thrown into the dustbin.   

If someone at Canonical is willing to get onto a con-call regarding your
userbase, I am happy to do so.

This is an Ubuntu-specific bug.  Politically saying, that freedom should
extend to new users.  Hiding the boot process behind a compiled C
program is a BAD THING.  Our users should always have the option to
understand and learn from the boot process from any terminal.  And this
should be an easy thing for them to do.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/765735

Title:
  mountall should cause fsck to show progress on text console

Status in “mountall” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: mountall

  mountall should cause fsck to show progress information (-C 0).

  Especially on large FS that take very long to fsck (sometimes many hours) it is very important 
  to know that the fsck isn't actually hanging and still working.
  It is not possible to log in via console or ssh to check the status even for filesystems that are not boot- essential.

  Plymouth splash screen is disabled as this machine is a server.

  This behaviour has caused trouble several times already as the system
  was believed to be hanging and unresponsive and got rebooted while the
  fsck was still running.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: mountall 2.25ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Tue Apr 19 11:51:06 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   LANGUAGE=en_US:en
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/765735/+subscriptions




More information about the foundations-bugs mailing list