[Bug 764479] New: shutdown lacks -F and -f options
https://bugzilla.novell.com/show_bug.cgi?id=764479 https://bugzilla.novell.com/show_bug.cgi?id=764479#c0 Summary: shutdown lacks -F and -f options Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jdelvare@suse.com QAContact: qa-bugs@suse.de CC: fcrozat@suse.com Found By: Community User Blocker: --- The new shutdown command that comes with systemd lacks options -F and -f to force, resp. inhibit filesystem check. The previous version of the shutdown command had these options. This is a functional regression. Option -F in particular is widely referenced in system administration manuals, blog posts and forum discussions, dropping it seems quite wrong. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=764479 https://bugzilla.novell.com/show_bug.cgi?id=764479#c1 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |http://unixhelp.ed.ac.uk/CG | |I/man-cgi?shutdown+8 --- Comment #1 from Frederic Crozat <fcrozat@suse.com> 2012-05-29 09:34:27 UTC --- added "non" systemd shutdown manpage as url but upstream doesn't seem willing to implement this behaviour (it was also removed in upstart), see https://bugzilla.redhat.com/show_bug.cgi?id=733874 and https://bugzilla.redhat.com/show_bug.cgi?id=784960 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=764479 https://bugzilla.novell.com/show_bug.cgi?id=764479#c2 --- Comment #2 from Jean Delvare <jdelvare@suse.com> 2012-05-29 10:51:19 UTC --- Doh. I can understand that we don't always preserve compatibility as it comes to a cost, but here the cost is very small as far as I can see, and the compatibility breakage seems to make a lot of people unhappy. At the very least I'd expect the manual page to explain the alternative way of doing the same. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=764479 https://bugzilla.novell.com/show_bug.cgi?id=764479#c kk zhang <kkzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |nld10-bugs-qa@forge.provo.n |ovo.novell.com |ovell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=764479 https://bugzilla.novell.com/show_bug.cgi?id=764479#c Andreas Jaeger <aj@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|nld10-bugs-qa@forge.provo.n |fcrozat@suse.com |ovell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=764479 https://bugzilla.novell.com/show_bug.cgi?id=764479#c Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|fcrozat@suse.com |systemd-maintainers@suse.de -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com