We originally set out to do this because we were having problems getting an older model laser printer, specifically a Konica Minolta PP1350W, to work with MacOS High Sierra (10.13). With previous versions of MacOS we’d been able to connect the printer directly to the computer, and with some fiddling with drivers and other software, get it to work. But newer versions of MacOS seem to be far less tolerant of this, and we had a spare Raspberry Pi, so the idea came to us to use the Raspberry Pi as a bridge between the printer and any computers on the local network from which we wanted to be able to print. The bonus is that the printer is no longer tethered to a single machine, but instead can potentially be used by any computer on the local network.
You do not need to have a Raspberry Pi to make this work – any computer that can run Linux will do. And of course the Raspberry Pi or other Linux computer can be used for other purposes besides this. We do not guarantee that this technique will work for every older printer out there, but this will work with a surprising number of them.
Looking to take your Python code from the world of command lines and into the convenience of a GUI? Have a Raspberry Pi with a touchscreen that’s going to waste because you don’t have the time to learn a GUI SDK? Look no further, you’ve found your GUI package.
Note: Scroll down the page for instructions and sample usage. This really does seem like an easy way for Python users to add GUI interfaces to their Python scripts. The author has said in a Reddit post that “It’s based only on tkinter. Zero package dependencies. And it’s a single .py file. That means not much can go wrong.” And that it “Works in Windows, Linux, Mac. Running on my Pi board that has 3.4 installed on it.”
This tutorial explains how to boot your Raspberry Pi 3 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 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.