RE: bash /usr/bin/ls invalid argument

> From: Nicolas BUONOMO > Sent: Wednesday, October 29, 2003 9:52 AM > Hello, > > Hannu E K Nevalainen a écrit : > > >>From: Jared Ingersoll > >>Sent: Monday, October 27, 2003 8:55 PM > > > > > > > > There is a 32KB length limit on the command line. This is > imposed on us by > > the underlyin

Re: bash /usr/bin/ls invalid argument

Hello, Hannu E K Nevalainen a écrit : From: Jared Ingersoll Sent: Monday, October 27, 2003 8:55 PM There is a 32KB length limit on the command line. This is imposed on us by the underlying "OS" - i.e. not likely to change. To check how long your command line would be, try something like thi

Re: bash /usr/bin/ls invalid argument

On Tue, Oct 28, 2003 at 07:02:15AM -0500, Jared Ingersoll wrote: >Thanks, I thought it may be something inherent. I can work around this >limitation. Let me again point out that there is a way around this limitation: http://sources.redhat.com/ml/cygwin/2003-09/msg01607.html -- Please use the reso

RE: bash /usr/bin/ls invalid argument

Thanks, I thought it may be something inherent. I can work around this limitation. Jared -Original Message- From: Hannu E K Nevalainen [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 28, 2003 5:20 AM To: [EMAIL PROTECTED] Subject: RE: bash /usr/bin/ls invalid argument > From: Ja

RE: bash /usr/bin/ls invalid argument

> From: Jared Ingersoll > Sent: Monday, October 27, 2003 8:55 PM > I'm using bash 2.05b-16 on Win2K pro and I'm running into problems listing > directory contents with a wildcard. This particular directory has > over 8000 > files in it, most of which (99%) are files that start with > send.log.*. W

Re: bash /usr/bin/ls invalid argument

Jared Ingersoll wrote: Hi, I'm using bash 2.05b-16 on Win2K pro and I'm running into problems listing directory contents with a wildcard. This particular directory has over 8000 files in it, most of which (99%) are files that start with send.log.*. When I issue the following commands, I get the s