Run /etc/init.d/networking restart to apply these changes

"file_export_version=3.0" > my_color_prefs.epf
grep -i color >> my_color_prefs.epf
grep -i org.eclipse.wst >> my_color_prefs.epf
grep -i org.eclipse.php.ui >> my_color_prefs.epf

Update 27/10/2009 ( caro-20091027 )

Update 02/02/2010 ( caro-20100202 ) for PDT 2.2

Thanks to timrobles.com

It’s now October 1998. We just got back from the 3rd CIFS conference
in SanJose. The Samba Team was the biggest contingent there.

Samba 2.0 should be shipping in the next few weeks with much better
domain controller support, GUI configuration, a new user space SMB
filesystem and lots of other neat stuff. I’ve also noticed that a
search of job ads in DejaNews turned up 3900 that mention Samba. Looks
like we’ve created a small industry.

I’ve been asked again where the name Samba came from. I might as well
put it down here for everyone to read. The code in Samba was first
called just “server”, it then got renamed “smbserver” when I
discovered that the protocol is called SMB. Then in April 1994 I got
an email from Syntax, the makers of “TotalNet advanced Server”, a
commercial SMB server. They told me that they had a trademark on the
name SMBserver and I would have to change the name. I ran an egrep for
words containing S, M, and B on /usr/dict/words and the name Samba
looked like the best choice. Strangely enough when I repeat that now I
notice that Samba isn’t in /usr/dict/words on my system anymore!

As he did not mention the command he ran to get this word out of the built-in dictionary, I tried some regex and got this one which is most likely the command:

egrep -i “^s[a-z]{0,1}m[a-z]{0,1}b[a-z]{0,1}$” /usr/share/dict/words

On CentOS:

samba
Sambo
sambo
Simaba
simba
SMB
Sumba

On Mac OS X 10.6.1

samba
Sambo
sambo
Simaba

( /usr/share/dict/words, because I ran this on CentOS, Mac )

1. Install packages
   apt-get install subversion libapache2-svn libapache-mod-dav
2. Enable SSL
   a2enmod
   Add “Listen 443″ into httpd.conf if needed.
3. Install SSL
   apt-get install ssl-cert
   mkdir /etc/apache2/ssl
   /usr/sbin/make-ssl-cert /usr/share/ssl-cert/ssleay.cnf /etc/apache2/ssl/site-name.crt
4. Adding Basic Authentication:
   htpasswd2 -c -m /home/path-to/svn/project/.htpasswd username
5. Configure site
   cp /etc/apache2/sites-available/default /etc/apache2/sites-available/site-name
   nano /etc/apache2/sites-available/site-name

   <VirtualHost IP_ADDRESS:443>
   ServerName hostname
   DocumentRoot /home/path-to/svn

   SSLEngine on
   SSLCertificateFile /etc/apache2/ssl/site-name.crt
   SSLProtocol all
   SSLCipherSuite HIGH:MEDIUM

   <Directory “/home/path-to/svn”>
   Options FollowSymLinks MultiViews
   AllowOverride All
   Order allow,deny
   Allow from All
   SSLRequireSSL
   </Directory>

   ### project
   <Location “/svn/project”>
   AuthType Basic
   AuthName “Subversion Login”
   AuthUserFile /home/path-to/svn/project/.htpasswd
   Require valid-user
   </Location>
   </VirtualHost>

   a2ensite $SITENAME
/etc/init.d/apache2 restart

6. Adding repository
   mkdir /home/path-to/svn
   svnadmin create /home/path-to/svn/repos
   chown -R www-data:www-data /home/path-to/svn/repos
   chmod -R g+ws /home/path-to/svn/repos
7. Enabling SVN
   Edit /etc/apache2/mods-available/dav_svn.conf
   DAV svn
SVNParentPath /home/path-to/svn (for multi repositories)
SVNPath /home/path-to/svn (for single repository)For non-anonymous access comment out:
   #<LimitExcept GET PROPFIND OPTIONS REPORT>
#</LimitExcept>
8. Finalization
   /etc/init.d/apache2 restart
9. Initial Import and Checkout
svn import --username username files https://hostname/svn/repos/testdir -m “Testing”
svn co --username username https://hostname/svn/repos

Tar through SSH: tar czpf – dir | ssh user@destination-host tar xzpf – -C /tmp/

Tar with Netcat (fastest):

• On destination-host: nc -l -p 7000 | tar xzpf – -C /tmp/
• On source-host: tar czpf – dir | nc -w 10 destination-host 7000

For the methods with tar command, you can use verbose with the command on the destination host to log the process.