On Wednesday 31 August 2005 2:16 pm, Carlos E. R. wrote:
In any case, as I mentioned, my solutions are not very good.
Note that a 64-bit system might handle this better.
I don't think so, it is a bash limit, not an architecture limit.
Yes and no.
The ls problem that Albert had was not a bash problem, but was most likely
an ls buffer issue.
The 32-bit architecture limits has been improved in the 2.6 kernel, but
significantly improved on 64-bit systems, but may not apply to ls or bash.
The bash limit comes into play when expanding wild cards on the command
line, so cp * <some directory> will fail, which is why I suggested using
find which deals with files and wild cards much differently than does bash.
--
Jerry Feldman