> fsck in particularly is slowly undergoing big changes that will mean
you can do it on the fly, with no need to reboot, etc.
6 years later ext4 still does not support online fsck.
> so why support -F ?
Because with systemd it is even more cumbersome to force a fsck of the
root FS.
--
You rece
** Changed in: upstart
Target: 0.5 => None
--
shutdown missing -F (force fsck) option
https://bugs.launchpad.net/bugs/74139
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Upstart upstream took a decision to abandon one of its goals of userland
tools compatible with other init systems. In practice, it never got any
further than implementing tools somewhat like the SysV tools that were
in Debian (which were even different from those in RedHat), and these
had plenty o
Sorry. I will not do that again.
--
shutdown missing -F (force fsck) option
https://bugs.launchpad.net/bugs/74139
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
Please don't unmark bugs as Invalid or Won't Fix
** Changed in: upstart (Ubuntu)
Status: Incomplete => Invalid
--
shutdown missing -F (force fsck) option
https://bugs.launchpad.net/bugs/74139
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
lets see if we can fix this thing.
** Changed in: upstart (Ubuntu)
Status: Invalid => Incomplete
--
shutdown missing -F (force fsck) option
https://bugs.launchpad.net/bugs/74139
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Surely its not too hard just to add the -f option that touches
/forcefsck before you issue your shutdown.
That isn't hard.
--
shutdown missing -F (force fsck) option
https://bugs.launchpad.net/bugs/74139
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
For various reasons, the compat branch of shutdown and reboot are being
dropped -- these will now be considered Upstart Native tools and may not
behave 100% like their sysvinit equivalents
** Changed in: upstart
Status: Triaged => Won't Fix
--
shutdown missing -F (force fsck) option
https
** Changed in: upstart
Status: Confirmed => Triaged
--
shutdown missing -F (force fsck) option
https://bugs.launchpad.net/bugs/74139
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
** Changed in: upstart (upstream)
Target: 0.3 => 0.5
--
shutdown missing -F (force fsck) option
https://bugs.launchpad.net/bugs/74139
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
Rejecting the Ubuntu portion of this bug since the missing -F feature is
in the upstream code
** Changed in: upstart (Ubuntu)
Status: Confirmed => Rejected
--
shutdown missing -F (force fsck) option
https://bugs.launchpad.net/bugs/74139
You received this bug notification because you are a
This is a missing feature from the "compat" shutdown utility, it should
be pretty trivial to add since it just seems to touch a file.
I wrote compat/sysv/shutdown by reading the documentation, so there are
several "hidden" features like this that are missing.
--
shutdown missing -F (force fsck)
** Summary changed:
- /sbin/shutdown on Ubuntu 6.10: where did -F go ?
+ shutdown missing -F (force fsck) option
--
shutdown missing -F (force fsck) option
https://launchpad.net/bugs/74139
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu
13 matches
Mail list logo
