Fire up a shell and follow these steps (these command are from http://wiki.dreamhost.com/Bugzilla) in the directory of the domain you want to install Bugzilla in.

mkdir bugs
cd bugs
wget http://ftp.mozilla.org/pub/mozilla.org/webtools/bugzilla-STABLE.tar.gz
tar zxf bugzilla-STABLE.tar.gz
rm bugzilla-STABLE.tar.gz
mv bugzilla*/* .

Next, follow setups 6, 7, 8 and 9 from the Bugzilla Dreamhost wiki.

Now you will need to manually install Module::Build and DateTime::Locale for Bugzilla to work. To do this, first get the latest CPAN download links for the modules.

For Module::Build, you’ll find the download link here: http://search.cpan.org/~kwilliams/Module-Build/
For DateTime::Locale, you’ll find the download at: http://search.cpan.org/~drolsky/DateTime-Locale-0.43/

I’ve used the latest available builds at the time of this writing for the example below. Next, follow these steps in the Bugzilla installation directory:

mkdir tmp
cd tmp
PERL5LIB=/full-path-to-bugzilla-install-dir/lib
export PERL5LIB
wget http://search.cpan.org/CPAN/authors/id/K/KW/KWILLIAMS/Module-Build-0.31.tar.gz
tar xzf Module-Build-0.31.tar.gz
cd Module-Build-0.31
perl Makefile.pl
make
make test
make install
cd ..
rm -rf Module-Build*

# To install DateTime::Locale
wget http://search.cpan.org/CPAN/authors/id/D/DR/DROLSKY/DateTime-Locale-0.43.tar.gz
tar zxf DateTime-Locale-0.43.tar.gz
cd DateTime-Locale-0.43
perl Makefile.pl
make
make test
make install
cd ../..
rm -rf tmp

Re-run ./checksetup.pl and then fix permissions as in the Dreamhost Bugzilla wiki page:

for i in docs graphs images js skins; do find $i -type d -exec chmod o+rx {} \; ; done
for i in jpg gif css js png html rdf xul; do find . -name \*.$i -exec chmod o+r {} \; ; done
find . -name .htaccess -exec chmod o+r {} \;
chmod o+x . data data/webdot

You should now have a working Bugzilla installation at yourdomain.com/bugs.

svn: Commit failed (details follow):
svn: MKCOL of '.../images': 405 Method Not Allowed

Searching around, I managed to find a couple of reasons this could occur — wrong charset or a connectivity problem (proxy discarding the MKCOL command). I’m not behind a proxy so I tried passing a charset parameter but that didn’t really help.

What finally helped was deleting the problematic “images” directory in the repository and re-commiting the directory. I use TortoiseSVN so it was as simple as using the Repo-Browser, right-clicking on the problematic directory and deleting it. The commit went through just fine after this.

Configuring the Ubuntu machine is pretty straightforward. Install and configure rsync and xinetd

There are a couple of changes from the rsyncd.conf you get from the URL above, mainly to avoid permission related problems when trying to rsync from a Windows machine. Here is my complete rsyncd.conf

uid = backups
gid = nogroup
use chroot = yes 
max connections = 5 
pid file = /var/run/rsyncd.pid
log file = /var/log/rsync.log
incoming chmod = Dg=s,Dug=rwx,Do-rwx,Fug=rw,Fo-rwx

[wbackups]
        path = /home/backups/wserver
        comment = Backups from wserver
        read only = false
        auth users = backups
        secrets file = /etc/rsyncd.secrets
        hosts allow = 192.168.1.1

Changes to note from the Ubuntu Wiki example is the “incoming chmod” line and the “auth users” line. I created a separate user called “backups” and store everything under /home/backups. Next, I notified logrotate about the new log being created. To do this, create a file /etc/logrotate.d/rsync with the following:

/var/log/rsync.log {
       weekly
       rotate 4
       compress
       notifempty
       missingok
}

And that is about all you need to do on Ubuntu.

On Windows:

1. Install DeltaCopy
2. Run the DeltaCopy Client, point it to the Ubuntu machine
3. For “Virtual Directory”, my setting was wbackups, defined in the configuration file above
4. Authenticate as the backups user you created

1. Set your rsync options

The rest should be straightforward. The DeltaCopy GUI also allows you to automatically schedule backups.

Most of the Linux users should be familiar with Gnome and KDE since both of them are the most commonly used desktop managers in the various Linux distros. Now, if you are using an old PC with low hardware specs, you might find that the above two desktop environments are too heavy for your computer to handle.

In this case, you will have to consider using an alternative lightweight desktop manager for your Linux. Here are 8 of the best lightweight desktop managers that I personally use and recommend.

Read more

request subnet-mask, broadcast-address, time-offset, routers,
    domain-name, domain-name-servers, host-name,
    netbios-name-servers, netbios-scope;

First of all, Remove domain-name-servers from that list.

Second, add a line to set your custom DNS servers. For OpenDNS, you would do:

prepend domain-name-servers 208.67.222.222,208.67.220.220;

Update: That doesn’t seem to always work. Easier way out would be to edit /etc/resolv.conf and add your DNS records like this:

nameserver 208.67.222.222
nameserver 208.67.220.220

Then run sudo chattr +i /etc/resolv.conf to stop NetworkManager from overwriting the file.

Your settings should now stay between restarts.

DELETE FROM mytable WHERE date < DATE_SUB(NOW(), INTERVAL 30 DAY);

You could also use INTERVAL 1 MONTH.

split --bytes=1024m bigfile.tar small_file_

That command will split bigfile.tar into files that are 1024 MB in size (1GB) and name the various parts small_file_aa, small_file_ab, etc. You can specify b for bytes, k for Kilobytes and m for Megabytes to specify sizes.

To join the files back together on Linux:

cat small_file_* >joined_file.tar

Similarly to join the split files on a Windows machine, use the copy command:

copy /b small_file_* joined_file.tar

In the last two months I’ve been traveling a lot. During the same period my main desktop computer went belly up. I would have been in trouble without rsync at my disposal — but thanks to my regular use of this utility, my data (or most of it, anyway) was already copied offsite just waiting to be used. It takes a little time to become familiar with rsync, but once you are, you should be able to handle most of your backup needs with just a short script.

What’s so great about rsync? First, it’s designed to speed up file transfer by copying the differences between two files rather than copying an entire file every time. For example, when I’m writing this article, I can make a copy via rsync now and then another copy later. The second (and third, fourth, fifth, etc.) time I copy the file, rsync copies the differences only. That takes far less time, which is especially important when you’re doing something like copying a whole directory offsite for daily backup. The first time may take a long time, but the next will only take a few minutes (assuming you don’t change that much in the directory on a daily basis).

Another benefit is that rsync can preserve permissions and ownership information, copy symbolic links, and generally is designed to intelligently handle your files.

Link