USB boot is available on the Raspberry Pi 3B, 3B+, 3A+ and Raspberry Pi 2B v1.2 models only.
This tutorial explains how to boot your Raspberry Pi from a USB mass storage device such as a flash drive or USB hard disk. Be warned that this feature is experimental and does not work with all USB mass storage devices. See this blog post from Gordon Hollingworth for an explanation of why some USB mass storage devices don’t work, as well as for some background information.
If you’ve ever built a Pi for a kiosk, installation or information display, you’ll find Adafruit’s read-only Pi script invaluable. This script disables all the write-to-SD-card functions, meaning that you can pull the plug without any risk of data loss or corruption. The Adafruit script forces Raspbian to store all its temporary data in memory, […]
The attached script will install shutdown and startup capability using a SPST NO momentary pushbutton
switch connected to GPIO header pins 5 and 6. Pressing the button on a running system will initiate
a graceful shutdown (shutdown -h now). Once shut down, pressing the button will restart the system.
1. Copy install and gpio-shutdown.dtbo to the Raspberry Pi.
… there is a new Raspberry Pi competitor that is quite affordable. In fact, some folks may view it as a Pi-killer. The $30 FriendlyElec NanoPi M1 Plus has an arguably superior design and layout, plus important integrated features like Wi-Fi and Bluetooth. It even has an IR receiver, onboard microphone, 8GB storage, and both power and reset buttons. Best of all? It is ready to run Debian, Ubuntu Core, and Ubuntu Mate from the start.
Hey guys, I thought I would share a short guide I made about configuring x11vnc to automatically launch every time the Pi boots up. I had such a hard time getting it to work and thought I should spread the knowledge. I’m a noob with Linux and the Pi, so I thought this would be really beneficial to any other noobs who are trying to get their Pi to run headless. I am using Raspbian Jessie so I’m not sure how well this will work with other distros.
This short guide assumes you already have a VNC viewer and know how to configure it. These instructions outline how to configure your Raspberry Pi to automatically start the x11vnc server every time it is booted. This way, you will be able to remotely connect to your Pi any time you launch your VNC viewer.
A couple redditors showed interest in how I set up my Pi as a SOCKS proxy and recommended I make a separate post as a tutorial, so I’ll do my best to explain everything.
SOCKS stands for Socket Secure, and is essentially just a middle man for a server and client for send information between. The best description I’ve heard of it is “It’s a poor man’s VPN.” It essentially works the same, but each service has to be configured to work with it (i.e. I have Firefox on my Mac working through my SOCKS proxy but not Chrome and Safari). Why would you want a SOCKS proxy over a VPN? From my experience, it runs better on a Pi, and I can also do multiple things over SSH (such as also run a file server). Having to configure each service to run through it can also be a pro or a con, depending on if you want everything to work through it or not.
There’s really not much to setting everything up; it’s a pretty straightforward process. For those just looking for something short and sweet, here are the basic steps I followed. I’ll go over each more in depth below.
I realized after posting this that it is a repeat post, but those new to the Raspberry Pi might not have seen the original post, so here it is again:
SD cards are said to have a finite life. If you are planning on running a Raspberry Pi 24x7x365, there are some steps that you can take with GNU/Linux to extend the life of the card: here are some ideas.
If you are running Asterisk 13 (or are ready to upgrade to Asterisk 13) and are using it to connect to one or more Google Voice accounts, you can now use oAuth authentication instead of the problematic username/password, without resorting to the use of a pre-built distribution that may contain features you don’t need and don’t want. The details are here:
Also, if you have a Raspberry Pi and would like to make a clean build of Asterisk and FreePBX, the same author (RonR) has provided instructions here. Just be sure to select Asterisk 13 when installing if you want to use the oAuth 2.0 support:
All of the above links are to threads at DSLReports. Note that the install scripts in the last two links can take some time to run, especially on an older model Raspberry Pi where they could take a few hours to complete (I believe you must have a Raspberry Pi 2 at a minimum to use the XiVO build). But when you are through, you’ll have a nice clean install, without the extraneous and mostly non-useful stuff found in a certain pre-built image.