Received the Raspberry Pi
First step, the system on the card
Today I have finally received the raspberry pi and its components by mail and I am preparing for the first step: creating an image of the wheezy raspbian distribution to copy on the memory card.
This is the download site, and these are the instructions to follow to prepare the card in a Linux environment.
- Download the wheezy package from the download site
- Compare the SHA-1 checksum from the download site with your downloaded file by executing this from command line, after entering the directory containing your downloaded file:
sha1sum file.zip
where file.zip is the name of your downloaded file. If the checksums are different you need to start from the beginning. - Unzip the downloaded file by performing
unzip file.zip
the result is a file with name file.img - Insert the SD memory card purchased in an available slot of yourn PC / laptop (laptop in my case)
- Check the file systems mounted by performing
df -h
- Figure out which mount point corresponds to your card, let's say /dev/sdb1, and unmount it by
umount /dev/sdb1
- Now you need to copy the image file to your card, using the linux dd command. In my case this is performed by
dd bs=4M if=2012-12-16-wheezy-raspbian.img of=/dev/sdb
Be careful of what you type above, and be sure of the output file system (/dev/sdb), since this operation is destructive of whatever found on that output file system path. This process might required to be run as super user (sudo) and does not give any diagnostic. Also remove the partition number at the end of the output device (/dev/sdb and not /dev/sdb1), so that the image affects the entire SD card and not only one partition of it. Be prepared to wait for a few minutes. - Before removing the card, from the command line, run sync, to make sure that everything in the write cash is dumped onto the card.
- You can now remove the card. It is ready to be inserted in your Raspberry Pi
In the next step with will fire-up Pi
Email server on Raspberry PI: a seven steps guide
With this first post I start documenting, step by step, the process of setting up an email server based on a Raspberry Pi card, using open source email programs like Postfix, MailScanner, ClamAV , and SpamAssassin.
The aim is to have a low power consumption email server that can run continuosly at home. This task is currently performed by my PC, with a Linux SuSe 12.1 operating system, and with an avarege power consumption of about 70W.
Another advantage is to leave the Raspberry Email Server functioning all the time when on holiday for longer periods of time.
This proces starts today with my purchase of the Raspberry PI card.
This is a list of the items purchased:
- Raspberry Pi Type B Single Board Computer 512MB, £21.60
- Micro USB UK power supply for Raspberry Pi, £ 5.19
- 4GB Class 6 SDHC Flash memory card for Raspberry Pi , £6.49
- HDMI cable for Raspberry Pi, £ 3.39
- Raspberry Pi Type B Case - Clear, £ 3.99
Full cost, VAT include is £ 53.74
Clearly you also need a registered domain, a static IP, and a local nwtework that this email is servicing
As a navigation aid, here are all the seps required:
- Received the Raspberry Pi
- Firing it up
- Essential configuration
- Tips & utilities
- Postfix & POP3 servers
- Secure POP3 with Stunnel
- Protecting with Amavis/Clamav/SpamAssassin
NFS for linux
Setting up a network file system
I found this link for a coprhenesive NFS howto.
Assuming that we want to share some directories on server PC in a local area network with LAN address of 192.168.1.0/255.255.255.0
- On the PC providing the remote file system (server) find and install the nfs server daeomon (on my system, I install nfs-kernel-server)
- Start the system service (Runlevel editor), for service nfsserver and levels 3 and 5
- After starting the service and/or rebooting the server check that there is a process running with name nfsd (for user root)
- Edit /etc/exports and add the line(s) with the directories to export. In my case it is:
/jupiter 192.168.1.0/255.255.255.0(rw)
- Increase the security by adding the following to hosts.deny (check link NFS how to)
- And this to hosts.allow (check link NFS howto_
Now mount the file system on the client machine