From: Dr Rainer Woitok <rainer.woitok@gmail.com>
To: cygwin@cygwin.com
Subject: Command line length in Ash or Dash Shells
Date: Mon, 26 Oct 2015 13:54:00 -0000 [thread overview]
Message-ID: <22062.2952.946000.358554@woitok.gmail.com> (raw)
Fellow Cygwinners,
recently I needed to remove quite a few Cygwin packages from my install-
ation, and due to all these interdependencies I wanted to do this in a
single call:
setup-x86*.exe -x ...,...,...
Calling this command as a Windows "*.bat" file failed with an error
message suggesting that the command line simply was too long. Searching
the web I found disagreeing figures for the maximum command line length
for "*bat" files under Windows Vista of 2000+ and 8000+, but since my
command line had a length of 12000+ anyway, I tried issuing this comm-
and from an Ash Shell script instead, which succeeded.
No I'm playing with the idea of using such an Ash Shell script (with
"setup-x86*.exe -P", of course) to carry my current Cygwin implementat-
ion over to my not yet decided upon next hardware. But nevertheless I
feel a bit uneasy about any potential command line length restriction
which could ultimately raise its ugly head and interfere with my glori-
ous plans.
Does anybody definitely know about a maximum command line length in the
Ash or Dash Shells?
Or alternatively: is there a way to cause "setup-x86*.exe" to read the
package list from a file or from standard input, even though "setup-x86*
--help" does not seem to indicate there is?
Any pointers appreciated.
Sincerely,
Rainer
--
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
next reply other threads:[~2015-10-26 11:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 13:54 Dr Rainer Woitok [this message]
2015-10-26 17:45 ` Eric Blake
2015-10-27 18:12 ` Dr Rainer Woitok
2015-10-27 19:06 ` Corinna Vinschen
2015-10-27 23:30 ` Dr Rainer Woitok
2015-10-28 0:30 ` Eric Blake
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=22062.2952.946000.358554@woitok.gmail.com \
--to=rainer.woitok@gmail.com \
--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).