This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: Patch for shutdown
- From: Fedin Pavel <p dot fedin at samsung dot com>
- To: jaltman at openafs dot org
- Cc: cygwin at cygwin dot com
- Date: Mon, 20 May 2013 17:59:42 +0400
- Subject: RE: Patch for shutdown
- References: <CAKf2h5QYs69d8RL647Fysji=fFCrEsg2HOMNenkjjcfd0fTJ6g at mail dot gmail dot com> <519A2341 dot 5030708 at openafs dot org>
> I would be unhappy with this proposed change. The Windows
> "shutdown.exe" uses:
>
> 'h' for hibernate
> 'l' for logoff
> 's' for shutdown and halt
> 'r' for shutdown and restart
> 'g' for shutdown and restart including registered applications
>
> 'a' for abort shutdown
>
> with the following modifiers:
>
> 'f' for force
> 'p' for 'no warning
> 'e' document the reason
> 'i' display GUI
> 'm' specify target computer
> 't' specify timeout
> 'c' specify comment
> 'd' shutdown reason code
>
> I believe it is very important that the Cygwin shutdown not alter the
> meaning of command line parameters such that they are different from
> the
> Windows native version. The various options are already too confusing
> to remember. Typing the right option value into wrong shell should not
> result in the wrong behavior if we can help it.
At the other hand, IMHO, Windows .bat scripts are never run from wihin bash, and vice versa, UNIX .sh scripts are never run from within cmd.exe...
And following the same logic we would need to teach our find.exe (already mentioned on this list) to understand Windows options instead of UNIX options...
Even further, in terminal case, why have Cygwin at all ? It is different from Windows command line and this is confusing...
Kind regards.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple