--- Raj Mathur <[EMAIL PROTECTED]> wrote:
> From man bash:
>: [arguments]
> No effect; the command does nothing
> beyond expanding
> arguments and performing any specified redirections.
> A zero exit code
> is returned.
>
> So effectively a no-op returning true. I us
On Tuesday 08 Jan 2008, Viksit Gaur wrote:
> --- tuxdna <[EMAIL PROTECTED]> wrote:
> > :(){ :|:& };:
> > :
> > : is a Bash Shell's no-op ( no operation ) literal,
> >
> > which can be used
> > as 'true' also.
>
> Hmm, I've never heard the character : referred to as
> such. Perhaps someone can comme
Hullo,
Responses inline.
--- tuxdna <[EMAIL PROTECTED]> wrote:
>
> :(){ :|:& };:
>
> : is a Bash Shell's no-op ( no operation ) literal,
> which can be used
> as 'true' also.
Hmm, I've never heard the character : referred to as
such. Perhaps someone can comment on this, although I
doubt this
> I would like to know why,
> [shell]$ :(){ echo "in background"& }
> works?
> [shell]$ :(){ echo "in background" } -- NOTE: no ampersand( & ) here!
> does not work?
Interesting fork-bomb - probably the shortest possible.
The ":" could have been any char usable as a variable like say "_" but
: lo
Hi,
I got following cute little code at http://en.wikipedia.org/wiki/Fork_bomb :
:(){ :|:& };:
I tried to figure out how it does what it is intended to. Here are my insights:
: is a Bash Shell's no-op ( no operation ) literal, which can be used
as 'true' also.
| is pipe
& is to create processes
