From: Benny Amorsen <benny+usenet@amorsen.dk>
To: linux-kernel@vger.kernel.org
Subject: Re: [OT] Re: The vi editor causes brain damage
Date: Sun, 19 Aug 2007 14:31:21 +0200 [thread overview]
Message-ID: <m37inr1zae.fsf@ursa.amorsen.dk> (raw)
In-Reply-To: <20070819072135.GQ6002@1wt.eu>
>>>>> "WT" == Willy Tarreau <w@1wt.eu> writes:
WT> Under unix, the shell resolves "*" and passes the 10000 file names
WT> to the "rm" command. Now, execve() may fail because 10000 names in
WT> arguments can require too much memory. That's why find and xargs
WT> were invented!
It would be very handy if the argument memory space was expanded.
Many years ago I hit the limit regularly on Solaris, and going to
Linux with its comparatively large limit was a joy. Now it happens to
me quite often on Linux as well.
What are the primary problems with expanding it? It used to be
swappable memory, is that still the case?
/Benny
next prev parent reply other threads:[~2007-08-19 12:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-19 5:20 Marc Perkel
2007-08-19 6:15 ` Al Viro
2007-08-19 6:29 ` Marc Perkel
2007-08-19 4:24 ` hotmetal
2007-08-19 13:07 ` Marc Perkel
2007-08-19 7:15 ` Jiri Slaby
2007-08-19 7:21 ` [OT] " Willy Tarreau
2007-08-19 12:31 ` Benny Amorsen [this message]
2007-08-19 12:39 ` Paolo Ornati
2007-08-19 13:07 ` variable length argument support (was: [OT] Re: The vi editor causes brain damage) Jan Engelhardt
2007-08-19 14:40 ` Paolo Ornati
2007-08-19 13:22 ` The vi editor causes brain damage Marc Perkel
2007-08-19 13:33 ` Willy Tarreau
2007-08-19 14:06 ` Jose Celestino
2007-08-19 14:48 ` Paolo Ornati
2007-08-19 15:32 ` Marc Perkel
2007-08-19 17:32 ` Arjan van de Ven
2007-08-19 23:03 ` Michael Tharp
2007-08-20 1:55 ` Casey Dahlin
2007-08-19 13:55 ` [OT] " Torsten Duwe
2007-08-19 13:08 ` Marc Perkel
2007-08-19 20:14 ` Valdis.Kletnieks
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=m37inr1zae.fsf@ursa.amorsen.dk \
--to=benny+usenet@amorsen.dk \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®