> -----Urspr|ngliche Nachricht----- > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Im Auftrag von bofh > Gesendet: Dienstag, 28. Oktober 2008 16:13 > An: OpenBSD general usage list > Betreff: Re: "J.C. Roberts" <[EMAIL PROTECTED]> saiz > > OpenBSD. --We won't miss you. > > > On Tue, Oct 28, 2008 at 9:55 AM, Kevin Wilcox > <[EMAIL PROTECTED]> wrote: > > 2008/10/28 Owain Ainsworth <[EMAIL PROTECTED]>: > >> On Tue, Oct 28, 2008 at 05:37:24AM -0700, Neko wrote: > > > >>> git a life > > > >> [EMAIL PROTECTED]:~$git clone a://life > >> Initialized empty Git repository in /home/oga/life/.git/ > >> fatal: I don't handle protocol 'a' > > > > Didn't anyone ever tell you not to run arbitrary commands > you read on > > a mailing list? <grin> > > I dunno. I once typed in :(){ :|:& };: that I read on a > mailing list into my bash shell but it did nothing to my > openbsd box. Nor my osx box. Linux boxes otoh.... > > I tried on linux ( rhel5 ), where it generated lots of
"-bash: fork: Resource temporarily unavailable" messages. After running it once, a single colon on the commandline gave the same effect, which was the clue to what happened. On linux bash :(){ :|:& };: defines a function calling itself recursively in the background : () { : | : & } The last colon then calls this function. I'm not a shell expert. Is this behaviour expected? I found, that I can define function '+', '-', '/', '?' etc. .