linux-kernel - Re: The vi editor causes brain damage

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070819133302.GA13719@1wt.eu>
Date:	Sun, 19 Aug 2007 15:33:02 +0200
From:	Willy Tarreau <w@....eu>
To:	Marc Perkel <mperkel@...oo.com>
Cc:	Jiri Slaby <jirislaby@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: The vi editor causes brain damage

On Sun, Aug 19, 2007 at 06:22:37AM -0700, Marc Perkel wrote:
> The important point that you are missing here is that
> the Linux world is willing to live with an rm command
> that is broken and the Windows and DOS world isn't.

The important point you are missing is that it is not the rm command
which is broken. Either it's *all* commands or it's *your* way of
thinking how they should work.

I could play your game and say the "type" command is broken under
DOS. Why can't I do "type *" under DOS while I can do "cat *" under
linux ? For the exact same reason : the "*" is not processed at
the same place. Unix initially chose to process it in the caller,
and DOS later chose to process it in the callee. Neither is right,
neither is wrong, those are just two different approaches which may
be justified in their context. Having discovered DOS at 1.25 which
did not even support directories, I certainly can say that missing
globbing was not a problem at this time!

> This isn't about the rm command it's about programming
> standards. It's about that the Linux community isn't
> committed to getting it right.

It has nothing to do with programming standards, the rm command works
exactly like all others. Touch does the same, mv does the same, etc...
Educate yourself before stating idiocies like this !

> Just like my thinking outside the box thread when I
> try to say "this is broken" people don't go fix it.
> Instead I get an explanation why Linux isn't capable
> of having an rm command that will delete an unlimited
> number of files.

$ rm -rf $DIR will remove an unlimited number of files in this directory.

If you want to make a special case of "rm", then implement the special
case in the command and make it possible to pass it a globbing expression
just like you can do with find. But this will be useless.

> I bet there are Microsoft people out there laughing at
> this.

Oh yes, they are surely laughing at you, but at the same time they may
feel sad to be defended by people puting such stupid statements in public.

> THINK ABOUT IT PEOPLE !!!
> 
> 20 years, a million programmers, tens of millions of
> users and RM is BROKEN. Am I the only one who has a
> problem with this? If so - I'm normal - and Linux is a
> cult.

Yes, I really think you're the only one who has this problem. Don't you
think that among those tens of millions of users, none of them has ever
had to remove a directory full of files in 20 years ? Please stop taking
yourself for the center of the world and buy a "unix for newbies" book
instead of complaining the world is not like you would like it to be.

Willy

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/