public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jeffrey Altman <jaltman@openafs.org>
To: cygwin@cygwin.com
Subject: Re: Patch for shutdown
Date: Mon, 20 May 2013 14:23:00 -0000	[thread overview]
Message-ID: <519A31F3.4040200@openafs.org> (raw)
In-Reply-To: <002401ce5562$47768a30$d6639e90$%fedin@samsung.com>

On 5/20/2013 9:59 AM, Fedin Pavel wrote:
> 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. 

Unlike the 'find' command, the shutdown command can leave the machine in
a state which cannot be recovered without physical access.   That is the
difference as I see it and it is a significant difference.

Sincerely

Jeffrey Altman



--
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

  parent reply	other threads:[~2013-05-20 14:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 11:41 Frank Fesevur
2013-05-20 13:21 ` Jeffrey Altman
2013-05-20 13:59   ` Fedin Pavel
2013-05-20 14:07     ` Earnie Boyd
2013-05-20 14:23     ` Jeffrey Altman [this message]
2013-05-20 17:50     ` Andrey Repin
2013-05-21 13:01     ` Buchbinder, Barry (NIH/NIAID) [E]
2013-05-20 20:32   ` Frank Fesevur
2013-05-21  9:42 ` Corinna Vinschen
2013-05-21 15:20   ` Frank Fesevur
2013-05-21 16:05     ` Corinna Vinschen
2013-05-21 20:00       ` Frank Fesevur
2013-05-22  8:18         ` Corinna Vinschen
2013-06-06 12:22           ` Frank Fesevur
2013-06-06 14:29             ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=519A31F3.4040200@openafs.org \
    --to=jaltman@openafs.org \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).