ieatpenguin

This is a very simple thing to do, it isn’t however as simple as one might think if you are coming from a Windows background, and are used to mapping a network drive from the Tools menu. As a note this is a guide for Ubuntu, although I have it working fine on both Ubuntu and Fedora, use the appropriate package manager/command line for Fed and the rest is the same.

First, we need to make sure that samba is installed:

sudo apt-get install smbfs

Next, we need to make a directory to mount the drive too. As an example, I’ve just reinstalled my Ubuntu (and Fedora) distribution, and so want to map the music drive on my server. I chose /media/ as the logical place to stick my network drives:

sudo mkdir /media/music

Next we need to tell the file system table where the drives are, and where to mount them. We also need to include our login credentials (will cover this later).

gksudo gedit /etc/fstab

Scroll to the bottom of the file and add the following:

#Mounting Network Drives
//SERVER/SHARE-NAME /MOUNT-POINT smbfs credentials=/credentials-file-location

To make the above make a bit more sense, here is my configuration:

//192.168.1.50/Music /media/music smbfs credentials=/home/russell/credentials.smbcredentials
//192.168.1.50/Videos /media/videos smbfs credentials=/home/russell/credentials.smbcredentials
//192.168.1.50/Software /media/software smbfs credentials=/home/russell/credentials.smbcredentials

What this will do is to check within the credentials file (more on this at the bottom) your username and password for your server (I am running a Windows Home Server as an example).

Next, we need to make the filesystem mount the drive, which we do simply with:

sudo mount -a

Finally, we need to make that credentials file. Simply navigate to your chosen directory (I stuck it in my /home/russell directory for ease), create a new file with the following information:

username=username
password=password

And save it with the same filename you gave the /fstab/. Thats it.

Have had an interesting morning delving into Bash, on MSN with Jasper, which is not something I get to do often enough.

The upshot was a nice and fairly sophisticated rsync script to backup some files, which I won’t paste here as it’s Jaspers baby.

However, I did think up a [much] simpler script to enable a quick and dirty backup of any particular folder to any particular media.

#!/bin/bash
sudo rsync -av --progress --delete --log-file=/dir/$(date +%Y%m%d)_rsync.log /dir /media/dirBackup

You can of course exclude certain files from the backup with:

--exclude "/dir/.jpg"

Naturally, no one wants to type it out everytime and so lets make it into an executable script:

sudo chmod +x /path/rsync-backup.sh

So you now have an executable script you can call whenever you want, or you can of course create a cron job and have it run automatically.

---

Here’s a slightly more sophisticated backup script that revolves on a weekly basis, and then clears out any backups that are older then this.

#!/bin/sh
# directory to backup
BDIR=/home/$USER

# excludes file
EXCLUDES=$HOME/cron/excludes

# name of the backup machine
BSERVER=server

# password on the backup server
export RSYNC_PASSWORD=

# lets get down to it
BACKUPDIR=`date +%A`
OPTS="--force --ignore-errors --delete-excluded --exclude-from=$EXCLUDES
      --delete --backup --backup-dir=/$BACKUPDIR -a"

export PATH=$PATH:/bin:/usr/bin:/usr/local/bin

# the following line clears the last weeks incremental directory
[ -d $HOME/emptydir ] || mkdir $HOME/emptydir
rsync --delete -a $HOME/emptydir/ $BSERVER::$USER/$BACKUPDIR/
rmdir $HOME/emptydir

# now the actual transfer
rsync $OPTS $BDIR $BSERVER::$USER/current

If, like me, you are a fan of Ubuntu and a fan of keeping up to date, then you will have [fairly]recently upgraded to Ubuntu 8.04, or Hardy Heron.

If, like me, you have an nvidia chipset, and networking drivers on your motherboard, chances are you will be using Forcedeth drivers when booting a fresh install/upgrade. This can cause problems with the ethernet controller, rendering your NIC non-working.

Based on a motherboard running the Nvidia Nforce2 570 chipset.

Here is a fix:

Open a terminal and set:

This will hopefully get your network up and running (if you’ve had problems). This works on the current session.

However, who wants to type that in every time you boot your computer? A few options here: You can either put it into a boot-time run script, or you can edit your config to automatically set it when the kernel runs it, which is what I’ve done:

added the parameters line:

and then made the changes to the system (assuming you are still logged in as root, otherwise sudo su/password):

Thats it.