Redirecting the output of commands run with sudo requires a different approach. For instance consider sudo ls > /root/somefile will not work since it is the shell that tries to write to that file. You can use ls | sudo tee -a /root/somefile to append, or ls | sudo tee /root/somefile to overwrite contents.

From https://help.ubuntu.com/community/RootSudo

Most new code is checked into the trunk.  In general, our developers try to never “break the tree”.  Anyone who checks in code which causes the trunk builds to fail will be the recipient of heaping helpings of trash talk and teasing until he gets it fixed.  The trunk should always build, and as much as possible, the resulting build should always work.

Most new code is checked into the trunk. The trunk is the place where active development of new features is happening.  The trunk could be described as “basically unstable”. In our situation, the stability of the trunk build fluctuates over the months during our development cycle.

During the early and middle parts of a development cycle, the trunk is often not very stable at all.  As we approach alpha, beta and final release, things settle down and the trunk gets more and more stable.

At the moment of release, a branch gets created.  This branch becomes our maintenance tree for that release.  Our current maintenance branch is called “3.0″, since that’s the current major version number of our product.  When we need to do a bug fix or patch release, it is done in the maintenance branch.  Each time we do a release out of the maintenance branch (like 3.0.2), we apply a tag.

After the maintenance branch is created, the trunk once again becomes “basically unstable”.  Developers start adding the risky code changes we didn’t want to include in the release.  New feature work begins.  The cycle starts over and repeats itself.

From http://www.ericsink.com/scm/scm_branches.html

ls . | xargs -i -t cp ./{} /path/to/new/directory

See example 12-6 at http://www.homepage.montana.edu/~unixuser/051905/abs-guide/moreadv.html

Open a new screen

screen

Detach from the screen

This does not interrupt whatever is running in the screen.

Press Ctrl-A then D.

Reattach to a screen you’ve already opened

screen -r

If you’ve opened multiple screens, a list will be displayed:

There are several suitable screens on:
	1681.ttys004.braeburn	(Detached)
	1686.ttys004.braeburn	(Detached)

Just use the process ID of the screen to resume the right one:

screen -r 1681

1. Install SIMBL: http://www.culater.net/software/SIMBL/SIMBL.php
2. Install the Snow-Leopard-friendly version of the TerminalColors plugin for SIMBL: http://github.com/timmfin/terminalcolours
3. Install the IR_Black theme and set it as default in Terminal.app preferences: http://blog.infinitered.com/entries/show/6
4. Turn on CLI color in your .bash_profile:

   export CLICOLOR=1;

5. Bonus round: set yourself a colourful bash prompt: http://devblog.bluefuton.com/2008/05/coloured-bash-prompt-in-os-x/

http://www.w3.org/TR/2002/WD-css3-border-20021107/#the-border-radius

border-top-left-radius: 1em;
border-top-right-radius: 1em;

You can produce the same result using proprietary attributes in Firefox 3.5 and Safari 4:

/* Firefox */
-moz-border-radius-topleft: 1em;
-moz-border-radius-topright: 1em;
 
/* Safari */
-webkit-border-top-left-radius: 1em;
-webkit-border-top-right-radius: 1em;

Source: http://www.css3.info/preview/rounded-border/

cp dir/* anotherdir/

If you try to do this with a particular large number of files, you may encounter the ‘argument list too long’ error. In this case you can use:

find . -exec cp {} /path/to/anotherdir/ \;

More approaches at: http://www.linuxjournal.com/article/6060