mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Weinehall <tao@acc.umu.se>
To: Pavel Machek <pavel@suse.cz>
Cc: Alexander Viro <viro@math.psu.edu>,
	"H. Peter Anvin" <hpa@transmeta.com>,
	Bill Crawford <billc@netcomuk.co.uk>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Daniel Phillips <phillips@innominate.de>
Subject: Re: Hashing and directories
Date: Fri, 2 Mar 2001 13:58:53 +0100	[thread overview]
Message-ID: <20010302135853.F22985@khan.acc.umu.se> (raw)
In-Reply-To: <3A9EB984.C1F7E499@transmeta.com> <Pine.GSO.4.21.0103011608360.11577-100000@weyl.math.psu.edu> <20010302100410.I15061@atrey.karlin.mff.cuni.cz>
In-Reply-To: <20010302100410.I15061@atrey.karlin.mff.cuni.cz>; from pavel@suse.cz on Fri, Mar 02, 2001 at 10:04:10AM +0100

On Fri, Mar 02, 2001 at 10:04:10AM +0100, Pavel Machek wrote:
> Hi!
> 
> > > >         * userland issues (what, you thought that limits on the
> > > > command size will go away?)
> > > 
> > > Last I checked, the command line size limit wasn't a userland issue, but
> > > rather a limit of the kernel exec().  This might have changed.
> > 
> > I _really_ don't want to trust the ability of shell to deal with long
> > command lines. I also don't like the failure modes with history expansion
> > causing OOM, etc.
> > 
> > AFAICS right now we hit the kernel limit first, but I really doubt that
> > raising said limit is a good idea.
> 
> I am running with 2MB limit right now. I doubt 2MB will lead to OOM.

You know, with a box with 4MB of RAM (or indeed 2MB, which should still
be possible on a Linux-system), a 2MB command-line is a very effective
DoS :^)

> > xargs is there for purpose...
> 
> xargs is very ugly. I want to rm 12*. Just plain "rm 12*". *Not* "find
> . -name "12*" | xargs rm, which has terrible issues with files names
> 
> "xyzzy"
> "bla"
> "xyzzy bla"
> "12 xyzzy bla"
> 
> !
> 
> I do not want to deal with xargs. Xargs was made to workaround
> limitation at command line size (and is broken in itself). Now we have
> hardware that can handle bigger commandlines just fine, xargs should
> be killed.

/David Weinehall
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Project MCA Linux hacker        //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </

  parent reply	other threads:[~2001-03-02 12:59 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-22 23:08 Bill Crawford
2000-01-01  2:02 ` Pavel Machek
2001-03-01 20:54   ` Alexander Viro
2001-03-01 21:05     ` H. Peter Anvin
2001-03-01 21:13       ` Alexander Viro
2001-03-01 21:24         ` H. Peter Anvin
2001-03-02  9:04         ` Pavel Machek
2001-03-02 12:01           ` Oystein Viggen
2001-03-02 12:26             ` Tobias Ringstrom
2001-03-02 12:58           ` David Weinehall [this message]
2001-03-02 19:33           ` Tim Wright
2001-03-12 10:05           ` Herbert Xu
2001-03-12 10:43             ` Xavier Bestel
2001-03-01 21:23       ` Andreas Dilger
2001-03-01 21:26       ` Bill Crawford
2001-03-01 21:05     ` Tigran Aivazian
2001-03-02  8:56       ` Pavel Machek
2001-03-07  0:37         ` Jamie Lokier
2001-03-07  4:03           ` Linus Torvalds
2001-03-07 13:41             ` Jamie Lokier
2001-03-02  9:00     ` Pavel Machek
2001-03-03  0:03   ` Bill Crawford
2001-03-08 12:42   ` Goswin Brederlow
2001-04-27 16:20     ` Daniel Phillips
2001-02-22 23:22 ` H. Peter Anvin
2001-02-22 23:54   ` Bill Crawford
2001-03-10 11:22 ` Kai Henningsen
2001-03-07 15:56 Manfred Spraul
2001-03-07 16:10 ` Jamie Lokier
2001-03-07 16:23   ` Manfred Spraul
2001-03-07 18:21     ` Linus Torvalds

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=20010302135853.F22985@khan.acc.umu.se \
    --to=tao@acc.umu.se \
    --cc=billc@netcomuk.co.uk \
    --cc=hpa@transmeta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=phillips@innominate.de \
    --cc=viro@math.psu.edu \
    /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®