[Bug 1041018] [NEW] "halt" command should not have a default action

[James E. LaBarre]

Public bug reported:

If (as per bug #880240) you are intent on changing a *long-standing* function to do something other than what it used to do, you should either 1: remove the command *entirely* and replace it with some other command alias (so that there is no confusion between releases of which version of a command will behave which way), or 2: have "halt" *require* a switch so that there is *NO* default action.  The user will then have to *explicitly* instruct the system which behavior they want the command to do.  That way if you are working on systems at a variety of release levels, there can be no conusion on which way any particular system will behave.
 
Changing a commnd's behavior on a whim (whether that change is correct or not) is never good when it makes a major change in the outcome of the command, considering someone may have to manage a wide range of systems, each with their own interpretation of how the command works.

** Affects: upstart (Ubuntu)
     Importance: Undecided
         Status: New

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

Title:
  "halt" command should not have a default action

Status in “upstart” package in Ubuntu:
  New

Bug description:
  If (as per bug #880240) you are intent on changing a *long-standing* function to do something other than what it used to do, you should either 1: remove the command *entirely* and replace it with some other command alias (so that there is no confusion between releases of which version of a command will behave which way), or 2: have "halt" *require* a switch so that there is *NO* default action.  The user will then have to *explicitly* instruct the system which behavior they want the command to do.  That way if you are working on systems at a variety of release levels, there can be no conusion on which way any particular system will behave.
   
  Changing a commnd's behavior on a whim (whether that change is correct or not) is never good when it makes a major change in the outcome of the command, considering someone may have to manage a wide range of systems, each with their own interpretation of how the command works.

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