Enclosure – Raspberry Pi by SparkFunElectronics
So in Part One, we took an old external had drive, and added it as storage to a Raspberry Pi. In Part Two, we took that Raspberry Pi and shared the new folders on the local network. In this final tutorial, I’ll show what all of this has been for, and show you how to create your own Home Theater Raspberry Pi.
File Folders by One Way Stock
In part one of our tutorial, we discussed how to mount an external hard drive or USB drive on to our Raspberry Pi (or any other Linux based) computer. In this tutorial we will discuss how to share folders from that computer to your local network. I am doing this so I can share the media files I have on my external hard drive, and access them from many places on my network, such as my laptop, my android phone, and my Raspberry Pi running XBMC. You can use this tutorial to share files in a similar way.
Hard disk dissection by Roberto F.
I’ve got a Raspberry Pi, and I’ve got an old external hard drive. So what can I do with them? I decided I was going to create a networked shared drive from them, so in this first tutorial, I will show you how to mount the drive on a Linux operating system. Doing this is easy, but can get a little tricky when you attach and remove drives on the fly.
Copyrights vs. human rights by opensourceway
Under these Acts, every person making a link to such a site would have to check the millions of other pages on that site to ensure that nobody, anywhere, is breaching copyright. Even search results would be covered under the proposed law. And if a website like ours were to be prosecuted for linking to another site where copyrighted material was hosted, our domain could be confiscated and our IP address added to a USA-wide blacklist, even though we are not US-based.
So far, so ridiculous. It’s censorship and shifting of responsibility on a grand scale. But despite a loud chorus of opposition to the Acts from legal experts, internet experts, journalists, website owners like us, human rights activists (want to publicise the next Arab Spring using Twitter, Facebook, YouTube or another site that potentially infringes? You’ve just provided the powers that be with an instant excuse and mechanism to shut you down) and ordinary people who just surf the web, the Acts stand a genuine chance of being pushed through. Lobbyists like the Motion Picture Association of America (MPAA), the Recording Industry Association of America (RIAA) and the movie and music studios have much louder voices and deeper pockets than we individuals on the internet do; but by joining together on January 18 we hope that we can make enough of an impact to be noticed by those voting on the legislation, and by the news outlets that they read and watch.
So on January 18, this blog intends to join the planned shutdown organised by Reddit. This site will be unavailable from 8am EST to 8pm. We encourage those of you who can to join us – and if you’re a US citizen, please call or email your representative.
Arduino Uno by Snootlab
A few months ago, my local maker-space (091 labs) presented a few informal tutorials on Arduino. Having seen it mentioned online, I decided to bite the bullet and drop by to learn more. Shortly later I purchased the Experimenter’s Guide for Arduino, which was used during the tutorials. Being further interested in Arduino and it’s capabilities, I subsequently bought the Arduino Cookbook
dependencies by jonathanvlarocca
In this post we discuss the various mechanisms of Inversion of Control (IoC) including Dependency Lookup and Dependency Injection. We look at the differences between the various IoC approaches and present the advantages and disadvantages of each.
A Real Screen Shot
If you do much shell scripting, then handling shell interrupts is something you should consider. As a user is interacting with your script, they may decide to interrupt it by typing Ctrl-C, for example. Typically this will interrupt your shell script execution, forcing it to exit.
Depending on what your shell script is doing, this could leave behind temporary files, or leave other files in a broken state. It would be useful if you could trap the interrupt, and handle it safely, before exiting the script.
This can be achieved on most shells using the ‘trap’ command. The trap command takes the following syntax:
trap [OPTIONS] [[ARG] SIGSPEC ... ]
The ARG is the command to be executed on signal delivery, while SIGSPEC is the name of the signal(s) to trap. Options include -h for help, -l to list signal names, or -p to print all defined signal handlers.
For example, to always return a ‘user aborted’ error code, the following line in your script could be used. Whatever value given to $exit_user_abort would be returned.
trap 'echo "`basename $0`: Ouch! User Aborted." 1>&2; exit $exit_user_abort' 1 2 15
The numbers 1, 2 and 15 at the end of this example define which interrupts we’re interested in trapping. These numbers correspond to different kinds of interrupts. A short list is given here, but you can use ‘trap -l’ for a complete list.
| Signal Number | Signal Name | Explanation |
|---|---|---|
| 0 | EXIT | exit command. Script has executed successfully. |
| 1 | HUP | Hang Up. The user session has disconnected. |
| 2 | INT | Interrupt. Ctrl-C (or other shell interrupt signal) has been given. |
| 3 | QUIT | Quit. Ctrl-\ (or other shell quit signal) has been given. |
| 6 | ABRT | Abort signal. |
| 15 | TERM | Terminate. Kill command has been issued against your script. |
If your trap runs several commands, it’s possibly neater to call a shell function than list the commands in-line, as above. For example:
trap funcname 1 2 15
funcname
# Function to handle interrupts
{
echo "`basename $0`: Ouch! User Aborted." 1>&2
exit $exit_user_abort
}
