Raspberry Pi Downloads - Software for the Raspberry Pi
Raspberry Pi Downloads - Software for the Raspberry Pi
Bitcoin, Ethereum price Monitoring on your raspberry Pi
Install Software | PiMiner Raspberry Pi Bitcoin Miner
Installing Samourai Dojo on a Raspberry Pi 4 - Bitcoin on
Install bitcoin-core for Linux using the Snap Store
What if Bitkey but for Monero
I just learned about bitkey, and boy am I impressed. Like my actual point is that I think a critical fatal flaw in the crypto economy and bitcoin network is the reliance on centralized hardware manfufactures whose proprietary closed garden systems and also of course centralized exchanges. I think it's just a matter of time before Trezor and LedgerNano become targets, or some rouge intelligence agent releases to the darknet some tool to crack them or compromise them.
BitKey is a bootable system image based on Debian containing everything you need to perform highly secure air-gapped Bitcoin transactions. You don't need to install it to a hard drive because it runs live from RAM. You just write the ISO image to a USB drive or burn it to CDROM.
I'm a die hard open source linux open system advocate, and I think that bitkey is the right step in the right direction. And my point being, anyone who's a developer could make some version of their own to be audited by the public community. Eventually we would have a handful of publically trusted builds by different developers, and this could be done for the major cryptos, or any crypto, but especially monero since it barely has hardware support. But the design of bitkey being an iso image on a cd rom or a usb, set to maximum privacy with two computers and a third device that scans QR codes. (on a side note there are security issues with QR codes, so that is one area for improvement). I'm trying to imagine a world where people can't get safe devices, can't get hardware wallets, and need an open source alternative to compromised desktops. Obviously something as advanced as a linux OS build spread across three devices for airgapping has a learning curve, but UI can increase over time. We have to remember there are a lot of tyrants in this world who want the monero and btc network to fail, want the fungibility and privacy and cash like nature fail, want to backdoor everything, they want to know if you're hungry, if you need to take a shit, before you even know, Minority report shit, but sadly unironically, and increasingly so. Windows is the devil obviously, Apple even more so. We need a world moving towards Linux, RVISC chips, raspberry pis. Even the best intentions of cypherpunk and monero are very very vulnerable without the hardware to back it up. So there really needs to be a move towards this.
Vertnode - An automated solution for installing Vertcoin node(s) on Single Board Computers
Hello Vertcoin Community, Eager to contribute to the Vertcoin Community I began creating step by step walkthrough guides on how to get a Vertcoin node up and running on a Raspberry Pi, Raspberry Pi Zero and Intel NUC. Along with information to get a Vertcoin node up and running was also optional steps to install p2pool-vtc. I decided that while this step by step guide might be helpful to a few, a setup script may prove to be useful to a wider range of people. I have this script to a point where I think it may be productive to share with a bigger audience, for those who are brave and have this hardware sitting around or like to tinker with projects; I invite you to test this setup script if you are interested, if you run into errors any sort of verbose console output of the error proves to be extremely helpful in troubleshooting. The script was designed to produce a “headless” server... meaning we will not be using a GUI to configure Vertcoin or check to see how things are running. In fact, once the server is set up, you will only interact with it using command line calls over SSH. The idea is to have this full node be simple, low-power, with optimized memory usage and something that “just runs” in your basement, closet, etc. Why run a headless node on a Single Board Computer?
You want to support vertcoin. Running a node makes the network more robust and able to serve more wallets, more users, and more transactions.
You are building or using applications such as mining that must validate transactions according to vertcoin’s consensus rules.
You are developing vertcoin software and need to rely on a vertcoin node for programmable (API) access to the network and blockchain.
The idea is to have this full node be simple, low-power, with optimized memory usage and something that “just runs” in your basement, closet, etc. Required: USB Flash Drive 6GB - 32GB Please note that the script was designed for Single Board Computers first and looks for an accessible USB Flash Drive to use for storing the blockchain and swap file, as constant writing to a microSD can degrade the health of the microSD. Supports
Raspberry Pi 3 B+ | ARM Cortex-A53 1.4GHz | 1GB SRAM |
Raspberry Pi Zero (W) | Single Core ARMv6 1 Ghz | 433MB RAM |
All of the hardware listed above is hardware that I have personally tested / am testing on myself. The plan is to continue expanding my arsenal of single board computers and continue to add support for more hardware to ensure as much compatibility as possible. Functionality
Installs Vertcoin full node to Single Board Computer
Installs p2pool-vtc (Optional)
Installs LIT and LIT-AF (Optional)
It is worth noting that LIT can be ran with multiple configurations, the ones displayed in the Post Installation Report reflect values that run LIT with the Vertcoin Mainnet. Please be aware that the Vertcoin Testnet chain has not been mined 100% of the time in the past, if you make transactions on the Vertcoin testnet that do not go through it is likely because the chain has stopped being mined. BE CAREFUL WITH YOUR COINS, ONLY TEST WITH WHAT YOU ARE OKAY WITH LOSING IF YOU USE THE MAINNET.
Recommended: Use Etcher to install the chosen OS to your microSD card / USB flash drive.
If you intend on installing Ubuntu Server 16.04 to your Intel NUC please use Etcher to install the .iso to your USB flash drive. https://etcher.io/ PLEASE NOTE THIS SCRIPT MAY GIVE AN ERROR. THIS IS THE NATURE OF TESTING. PLEASE REPORT YOUR ERRORS IF YOU WANT THEM TO BE FIXED/RESOLVED. THANK YOU FOR BETTERING THE DEVELOPMENT OF THIS SCRIPT.
You can use different clients to ssh into your node. One option is using PuTTY or Git Bash on Windows which is included in the desktop version of Git. If you are using Linux you can simply open a new terminal window and ssh to the IP address of your node (hardware you intend installing the Vertcoin node on). You will need to know the IP address of your node, this can be found on your router page. ssh 192.168.1.5 -l pi For example, this command uses ssh to login to 192.168.1.5 using the -l login name of pi. The IP address of your node will likely be different for you, in this example I am logging into a Raspberry Pi which has a default login name of pi. A brief list of commands that can be used to check on the Vertcoin node status: vertcoin-cli getblockchaininfo | Grab information about your blockchain vertcoin-cli getblockcount | Grab the current count of blocks on your node vertcoin-cli getconnectioncount | Grab the current count of connections to your node. A number of connections larger than 8 means that you have incoming connections to your node. The default settings are to make 8 outgoing connections. If you want incoming connections please port forward your Raspberry Pi in your Router settings page. vertcoin-cli getpeerinfo | Grab the information about the peers you have connected to / are connected to vertcoin-cli getnettotals | Grab network data, how much downloaded/upload displayed in bytes tail -f ~/.vertcoin/debug.log | Output the latest lines in the Vertcoin debug.log to see verbose information about the Vertcoin daemon (ctrl+c to stop) Thank you to all who have helped me and inspired me thus far, @b17z, @jamesl22, @vertcoinmarketingteam, @canen, @flakfired, @etang600, @BDF, @tucker178, @Xer0 This work is dedicated to the users of Vertcoin, thank you for making this possible. 7/20/2018 Thank you @CommodoreAmiga for the incredibly generous tip <3 You can reach me @Sam Sepiol#3396 on the Vertcoin Discord, here on reddit or @ [email protected]
gpg: packet(13) too large gpg: read_block: read error: Invalid packet gpg: no valid OpenPGP data found. gpg: Total number processed: 0
My fear is that the gpg on my pi os (stretch) is too old and too strict with it's parsing rules, but it doesn't look that easy to update gpg on the pi. (Build from source on the pi?) Any advice? I'll pass it along to Damian to update his tutorial.
Hi Redditors. I am going to post in this thread my experiences in getting my Desktop (Debian) machine running Armory in watch-only mode, and coupling that with an offline Raspberry Pi (which holds my private keys) for signing the transactions previously made in watch-only mode. I actually compiled Armory from source directly on my Pi. This guide is probably more for the bitcoin 'power user', as to run Armory online, and broadcast the signed transactions, you need to have a bitcoin full node running (bitcoind). Basic requirements:
Online machine - running a full node (bitcoind)
Raspberry Pi - I used an old Pi 1 Model B with just 512Mb memory, and 2 USB slots.
2x USB thumb-drives. One for wallet backups, the other for transferring unsigned tx's to the rPi, and signed tx's back to the Desktop.
Armory 0.96.4 for the Raspberry Pi 1, Model B (512Mb RAM, 2xUSB) (compiled from github sourcecode on the Pi itself!)
Using the Pi as an offline complement to a Debian Desktop "watch-only" Armory install.
Desktop Debian Armory watch-only talks to my full node, bitcoind, which is also on the Debian desktop.
I'll post the guide in digestible sections...
I should begin by saying I installed source code from git, and got Armory to build the DB on my desktop initially, WITHOUT creating a wallet.. (This allowed me to debug what was going on a little!)
Go to Bitcoin.org, select Armory.. It leads to a Download from Git: https://github.com/goatpig/BitcoinArmory/releases Followed the procedure for Linux Debian verify code, compile, install, all straight-forward.. Began by running bitcoind, and telling Armory where to find it. This is the command I used, obviously it was all on one line and didn't include the arrows/explanations!:
python ArmoryQt.py \ --satoshi-datadir=/BlockChain/chain20180414/blocks \ # <-----(where my bitcoind blocks live) --datadir=/ArmoryDataDi \ # <-----(this is instead of ~/.armory) --dbdir=/ArmoryDataDidatabases # <-------(again, non std. place used for Armory's databases.. my choice.)
So, on the Desktop, after the initial "build databases" (NB the initial "Build Databases" took about 1.5h and my two CPUs were maxed the whole time, Temps up to 62C. Not ideal; Im not in a rush!) I then wanted to import a watch-only wallet. Before I did this, I took a full backup of the Armory data dir: /ArmoryDataDi (or ~/.armory in a default installation). I'd hate to have to make Armory do another full sync with the bitcoind node!
Next step: offline wallet (with Private Keys) is on a Raspberry Pi. I downloaded the source and managed to compile it on the pi itself! :) Though there were some gymnastics needed to setup the Pi. My Pi is running Raspbian based on Wheezy.. quite old! I did the following on the Pi:
apt-get update apt-get upgrade (<---took about an hour!) apt-get install autotools-dev apt-get install autoconf
Then I followed the instructions exactly as I had done for my Debian Desktop machine, EXCEPT: I had to increase the Pi's swap space. I upped it from 100Mb to 400Mb. The compilation took 7 hours, and my poor SD card got a thrashing. But after compilation, I put the Swap back to 100Mb and Armory runs ok with about 150Mb of memory (no swap needed). Swap increase on the Pi: use your favourite editor, and open the file /etc/dphys-swapfile add/change the following line:
Then, REBOOT the Pi:
sudo shutdown -h -P now
Once the compilation was done on the Pi, put the swap back, rebooted and created an Armory wallet. I added manual entropy and upped the encryption 'time' from 250ms to 2500ms - since the Pi is slow, but I'll be happy to wait for more iterations in the Key Derivation Function. Once the wallet was created, it obviously prompts you for backup. I want to add a private key of my own (i.e. import), so don't do the backup until this is over. I import my Private Key, and Armory checks that this corresponds to a Public Key, which I check is correct. This is the point now where the Pi storage medium (e.g an SD card) has to be properly destroyed if you ever get rid of it. I had thought that now would be a good time to decide if your new wallet will generate Segwit receiving addresses, and also addresses used to receive 'change' after a transaction.. But it seems Armory WON'T let you switch to P2SH-P2WPKH unless your Armory is connected to a node offering "WITNESS" service. Obviously, my Pi is offline and will never connect to a node, so the following will not work on the Pi:
x Use File Settings Fee and address types.
x Set the "Preferred Receive Address Type" to P2SH-P2WPKH
x Also Set the "Change Address" to P2SH-P2WPKH for left-over loose change!
NB: I thought about setting this on the Debian "watch-only" wallet, but that would surely mean doom, as the Pi would not know about those addresses and backups might not keep them.. who knows... So, end result:- no segwit for me just yet in my offline funds.
--If anyone can offer a solution to this, I'd be very grateful--
Ok, now this is a good point to back up your wallet on the Pi. It has your imported keys. I choose a Digital Backup - and put it on a USB key, which will never touch the internet and will be stored off-site. I also chose to encrypt it, because I'm good with passwords.. NB: The Armory paper backup will NOT back up your imported private keys, so keep those somewhere if you're not sweeping them. It would be prudent to have an Armory paper backup anyway, but remember it will likely NOT help you with that imported key. Now for the watch-only copy of the wallet. I want to get the "watch-only" version onto my Desktop Debian machine. On the Pi, I created (exported to a USB key) a "watching-only" copy of my wallet. I would use the RECOMMENDED approach, export the "Entire Wallet File". As you will see below, I initially exported only the ROOT data, which will NOT capture the watching-only part of the Private Key I entered manually above (i.e. the public Key!). Now, back on the Debian Desktop machine... I stopped all my crontab jobs; just give Armory uninterrupted CPU/memory/disk... I also stopped bitcoind and made a backup prior to any watch-only wallet being imported. I already made a backup of Armory on my Desktop, before any wallet import. (this was needed, as I made a mistake.. see below) So on the Debian Desktop machine, I begin by firing up bitcoind. my command for this is:
I know from bitter experience that doing a scan over the blockchain for a new wallet takes a looong time and a lot of CPU, and I'd like it to play nicely; not gobble all the memory and swap and run my 2xCPUs both at 100% for four hours... So... I aim to run with --ram-usage=X and --thread-count=X (For me in the end, X=1 but I began with X=4) I began with --ram-usage=4 (<--- = 4x128Mb) The result is below...
TypeError: cannot concatenate 'str' and 'int' objects
It didn't recognise the ram-usage and carried on, crippling my Debian desktop PC. This is where it gets dangerous; Armory can gobble so much memory and CPU that the windowing environment can cease up, and it can take over 30 minutes just to exit nicely from bitcoind and ArmoryDB. So, I ssh to the machine from another computer, and keep an eye on it with the command
I'd also be able to do a "sudo reboot now" if needed from here.
So, trying to get my --ram-usage command recognised, I tried this line (added quotes):
Loading Armory Engine: Armory Version: 0.96.4 Armory Build: None PyBtcWallet Version: 1.35 Detected Operating system: Linux OS Variant : ('debian', '9.4', '') User home-directory : /home/ Satoshi BTC directory : /BlockChain/chain20180414 Armory home dir : /ArmoryDataDi ArmoryDB directory : /ArmoryDataDidatabases Armory settings file : /ArmoryDataDiArmorySettings.txt Armory log file : /ArmoryDataDiarmorylog.txt Do wallet checking : True (ERROR) ArmoryUtils.py:3723 - Unsupported language specified. Defaulting to English (en) (ERROR) ArmoryQt.py:1833 - Failed to start Armory database: cannot concatenate 'str' and 'int' objects Traceback (most recent call last): File "ArmoryQt.py", line 1808, in startArmoryDBIfNecessary TheSDM.spawnDB(str(ARMORY_HOME_DIR), TheBDM.armoryDBDir) File "/BitcoinArmory/SDM.py", line 387, in spawnDB pargs.append('--ram-usage=' + ARMORY_RAM_USAGE) TypeError: cannot concatenate 'str' and 'int' objects
So, I edit the Armory python file SDM.py:
if ARMORY_RAM_USAGE != -1: pargs.append('--ram-usage=4') #COMMENTED THIS, SO I CAN HARDCODE =4 # ' + ARMORY_RAM_USAGE)
Running it, I now have acknowledgement of the --ram-usage=4:
(WARNING) SDM.py:400 - Spawning DB with command: /BitcoinArmory/ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/BlockChain/chain20180414/blocks" --datadir="/ArmoryDataDi" --dbdir="/ArmoryDataDidatabases" --ram-usage=4
Also, even with ram-usage=4, it used too much memory, so I told it to quit. It took over 30 minutes to stop semi-nicely. The last thing it reported was:
ERROR - 00:25:21: (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
But that didn't seem to matter or corrupt the Armory Database, so I think it's ok. So, I get brave and change SDM.py as below, and I make sure my script has a command line for --ram-usage="ABCDE" and --thread-count="FGHIJ"; the logic being that these strings "ABCDE" will pass the IF criteria below, and my hardcoded values will be used...
if ARMORY_RAM_USAGE != -1: pargs.append('--ram-usage=1') #COMMENTED THIS, SO I CAN HARDCODE =1 # ' + ARMORY_RAM_USAGE) if ARMORY_THREAD_COUNT != -1 pargs.append('--thread-count=1') #COMMENTED THIS, SO I CAN HARDCODE =1 #' + ARMORY_THREAD_COUNT)
So, as usual, I use my script and start this with: ./StartArm.sh (which uses command line:)
(this forces it to use my hard-coded values in SDM.py...) So, this is the command which it reports that it starts with:
(WARNING) SDM.py:400 - Spawning DB with command: /BitcoinArmory/ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/BlockChain/chain20180414/blocks" --datadir="/ArmoryDataDi" --dbdir="/ArmoryDataDidatabases" --ram-usage=1 --thread-count=1
Again, this is where it gets dangerous; Armory can gobble so much memory and CPU that the windowing environment can cease up. So I ssh to the machine and keep an eye on it with:
So, on the Debian Desktop PC, I inserted the USB stick with the watch-only wallet I exported from the Pi. Start Armory... Import "Entire Wallet File" watch-only copy. Wait 4 hours.. YAY!!! After running Armory for about 30m, the memory usage dropped by 400m... wierd... It took ~2 hours to get 40% completion. After 3.5 hours it's almost there... The memory went up to about 1.7Gb in use and 900Mb of Swap, but the machine remained fairly responsive throughout, apart from a few (10?) periods at the start, where it appeared to freeze for 10-30s at a time. (That's where my ssh session came in handy - I could check the machine was still ok with a "free -h" command) Now, I can: Create an unsigned transaction on my Desktop, Save the tx to USB stick, Move to the Pi, Sign the tx, Move back to the Desktop, Broadcast the signed tx.
My initial Mistake: This caused me to have to roll-back my Armory database, using the backup. so you should try to avoid doing this.. On the Pi, I exported only the ROOT data, which will NOT capture the watching-only part of the Private Key It is RECOMMENDED to use the Digital Export of Entire Wallet File from the Pi when making a watch-only copy. If you just export just the "ROOT data", not the "Entire Wallet File", you'll have problems if you used an imported Private Key in the offline wallet, like I did. Using the ROOT data text import, after it finished... my balance was zero. So,. I tried a Help->Rescan Balance (Restart Armory, takes 1minute to get back up and running) No Luck. Still zero balance. So, I try Rescan Databases.. This will take longer. Nah.. no luck. So, I tried again, thinking it might be to do with the fact that I imported the text "root data" stuff, instead of following the (Recommended) export of watching-wallet file. So, I used my Armory backup, and wound back the ArmoryDataDi to the point before the install of the (zero balance) wallet. (you should not need to do this, as you will hopefully use the RECOMMENDED approach of exporting the "Entire Wallet File"!)
Got my Bitcoin/LN Node up and running on testnet. Have a few questions.
Bare with with me as I'm still new to fully understanding how Bitcoin and the LN work. And I'm an even bigger newbie when it comes to Linux, which is why I installed 'Raspberry PI Desktop'. I wanted to closely follow the guide mentioned below (with a few changes as to accommodate the i686 processor). I had some old hardware laying around and decided to attempt a Bitcoin/LN Node setup using the following guide: https://github.com/Stadicus/guides/blob/masteraspibolt/README.md My Hardware Specs:
Asus Eee PC Atom Netbook - Processor: Intel Atom N270 (i686) 1.6 GHz / RAM: 2 GB / Hard Drive: SSD 4GB (lol...) / Supports SD Memory Card and SDHC Memory Card.
500 GB Portable 2.5" WD Hard Drive
32GB SD Memory Card
I downloaded the "Debian Stretch with Raspberry PI Desktop" disk image on the 32GB SD Memory Card. I then tried to do an install to the 4GB SSD, but I don't think the 4GB was enough disk space because the system install would stop/error at around 32%. After several failed attempts I decided to just "Run with persistence" from the SD card, which worked. After about a day and a half (breaks in between), I finally got testnet up and running. I'll be staying on testnet for a while until I familiarize myself with everything, with that said, I'm hoping some of you Linux and Bitcoin savvy people can answer a few questions/concerns. TL;DR: I setup a Bitcoin/LN Node on testnet, and have a few questions below. Linux Related:
On boot/reboot I get this message below, should I be concerned? I'm not sure what it means, how can I stop this message? I'm able to just hit Ctrl+D, which the system continues booting normally afterwards.
"No Caching mode page found" and "Assuming drive cache: write through" "After logging in type 'journalctl -xb' to view system logs, 'systemctl reboot' to reboot or ^D to try again to boot into default mode." Bitcoin/LN Related:
Is the LN wallet the same as my Bitcoin Node wallet? (I don't see the step where I created a wallet on the "Bitcoin" section using the guide I mentioned at the top of this post. But I do see the step of creating the LN wallet in the "Lightning" section by using the following command - "lncli --network=testnet create".)
Do I need to unlock my wallet every time I restart? Is this required to use the LN? (I noticed when I restart my system and do a "sudo journalctl -f -u lnd", It prompts me for my wallet password, or create a new one.)
What are the characters at the end of the command below(np2wkh) when creating a new address? Do I generate a new address every time I want to receive a payment? ("lncli --network=testnet newaddress np2wkh")
Why does my LN wallet balance display differently than what I requested from a faucet? (The testnet faucet says 0.01 max, which I sent to my wallet address. But my LN wallet displays as "total_balance 199637".)
If I need to restart my node, is there a correct way of doing so? How do I make sure i don't affect open channels?
I know I have other questions, but I can't remember them off the top of my head right now. Thanks
Hey guys! I'm fairly new to this sub and to having a home lab in general and I found this community to be so kind and helping, I wanted to give back what I've learned. I'm seeing a lot of questions asked around on improvements and on what to do with x extra hardware so I thought it would be nice to have a thread to regroup that.
I'll put here some stuff I gathered and the most common questions I've seen, feel free to contribute and i'll update the post along.
oVirt -> Viurtualization
Hurrcane Electric DNS -> Dynamic DNS
No-IP -> DynamicDNS
SpiceWorks -> Misc
ERPXE -> Backup
Homelab Dashboard Posts about dashboards have been growing lately and here are some of the best that were kind enough to provide us with their sources.
Pi-hole Prevents ads from even reaching you by blocking dns queries. Works as a relay between your isp's dns server (or whichever you choose). Can also work as a local dns.
RetroPie From their website: The RetroPie Project is a collection of works that all have the overall goal to turn the Raspberry Pi into a dedicated retro-gaming console.
raspnode Tutorials for installing cryptocurrency nodes on a Raspberry Pi. Participate in the Bitcoin, Litecoin, or Ethereum network. Full nodes, SPV wallets, cold storage, offline transaction signing.
flightradar24 is a flight tracking service that provides you with real-time info about thousands of aircraft around the world.
The Plane Finder is the easiest and most accurate way to share your ADS-B and MLAT data with us.
PiAware is the world's largest flight tracking data company and provides over 10,000 aircraft operators and service companies as well as over 12,000,000 passengers with global flight tracking solutions.
CouchPotato is an wesome PVR for usenet and torrents. Just fill in what you want to see and CouchPotato will add it to your "want to watch"-list. Every day it will search through multiple NZBs & Torrents sites, looking for the best possible match. If available, it will download it using your favorite download software.
SickBeard is a PVR for newsgroup users (with limited torrent support). It watches for new episodes of your favorite shows and when they are posted it downloads them, sorts and renames them, and optionally generates metadata for them.
SickRage Automatic Video Library Manager for TV Shows. It watches for new episodes of your favorite shows, and when they are posted it does its magic.
FlexGet is a multipurpose automation tool for content like torrents, nzbs, podcasts, comics, series, movies, etc.
sabnzbd makes Usenet as simple and streamlined as possible by automating everything we can.
nzbget is a binary downloader, which downloads files from Usenet based on information given in nzb-files.
headphones is an automated music downloader for NZB and Torrent, written in Python. It supports SABnzbd, NZBget, Transmission, µTorrent and Blackhole.
= Virtualization =
XenServer is an open source project and community managed by Citrix. The project develops open source software for securely running multiple operating systems and applications on a single device, enabling hardware consolidation and automation to reduce costs and simplify IT management of servers and applications.
Proxmox is a complete open source server virtualization management software. It is based on KVM virtualization and container-based virtualization and manages KVM virtual machines, Linux containers (LXC), storage, virtualized networks, and HA clusters.
VirtualBox is a general-purpose full virtualizer for x86 hardware, targeted at server, desktop and embedded use.
SmartOS is a hypervisor lean enough to run entirely in memory, powerful enough to run as much as you want to throw at it.
KVM is a full virtualization solution for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-V).
oVirt is free, open-source virtualization management platform. It was founded by Red Hat as a community project on which Red Hat Enterprise Virtualization is based.
= Monitoring =
Nagios is a powerful monitoring system that enables organizations to identify and resolve IT infrastructure problems before they affect critical business processes.
OMD avoids the tedious work of manually compiling and integrating Nagios addons while at the same time avoiding the problems of pre-packaged installations coming with your Linux distribution
Pandorafms is the most flexible monitoring software in the market. With a single tool, Pandora FMS can monitor everything: infrastructure, applications, services, and business progress.
PRTG Monitoring is a network monitoring software that is powerful and easy to use. Free for 100 sensors.
Zabbix is the ultimate enterprise-level software designed for real-time monitoring of millions of metrics collected from tens of thousands of servers, virtual machines and network devices.
Observium is a low-maintenance auto-discovering network monitoring platform supporting a wide range of device types, platforms and operating systems.
LibreNMS is a fully featured network monitoring system that provides a wealth of features and device support.
Cacti is a complete network graphing solution designed to harness the power of RRDTool's data storage and graphing functionality.
Munin surveys all your computers and remembers what it saw. It presents all the information in graphs through a web interface.
ZenOSS is an award winning, open source monitoring product that automatically discovers resources, without the use of agents, and provides visibility across all aspects of your IT environment whether physical, virtual or in the cloud.
AlienVault OSSIM is an open source security information and event management system. OSSIM combines Snort, OpenVAS, Nagios, OSSEC, and other tools into a single portal with log collection and correlation.
Graylog Centralize and aggregate all your log files for 100% visibility. Use our powerful query language to search through terabytes of log data to discover and analyze important information.
= Media Center =
Plex organizes your video, music, and photo collections and streams them to all of your screens.
Kodi, if a free and open source (GPL) software media center for playing videos, music, pictures, games, and more.
Emby brings all of your home videos, music, and photos together into one place.
OpenMediaVault is the next generation network attached storage (NAS) solution based on Debian Linux. It contains services like SSH, (S)FTP, SMB/CIFS, DAAP media server, RSync, BitTorrent client and many more.
PlexPy is a tool to easily monitor and receive notify playback events from Plex.
MediaGoblin is a free software media publishing platform that anyone can run. You can think of it as a decentralized alternative to Flickr, YouTube, SoundCloud, etc.
= Remote access =
Guacamole is a clientless remote desktop gateway. It supports standard protocols like VNC and RDP.
Chrome Remote Desktop allows users to remotely access another computer through Chrome browser or a Chromebook.
mRemoteNG is a fork of mRemote, an open source, tabbed, multi-protocol, remote connections manager. mRemoteNG adds bug fixes and new features to mRemote.
= VOIP =
Elastix is an Open Source Software to establish Unified Communications. About this concept, Elastix goal is to incorporate all the communication alternatives, available at an enterprise level, into a unique solution.
Asterisk is an open source framework for building communications applications. Asterisk turns an ordinary computer into a communications server.
FreePBX is a web-based open source GUI (graphical user interface) that controls and manages Asterisk (PBX)
= Networking =
pfSense is an open-source firewall/router computer software distribution based on FreeBSD.
Open vSwitch is a production quality, multilayer virtual switch licensed under the open source Apache 2.0 license.
SophosUTM Complete Unified Threat Management protection for your network, web, email, applications, and users.
SohposXG is a fully equipped software version of the Sophos XG firewall, available at no cost for home users.
feeloadbalancer is offering the Free LoadMaster to help small companies and developers by providing them with a robust and proven load balancing option.
NetWorx is a simple and free, yet powerful tool that helps you objectively evaluate your bandwidth consumption situation.
VyOS is a community fork of Vyatta, a Linux-based network operating system that provides software-based network routing, firewall, and VPN functionality.
freeIPA is an integrated Identity and Authentication solution for Linux/UNIX networked environments.
Metiix Blockade Network-Wide Malware, Tracking, & Ad Blocking (Can also run on Raspbian)
OpenVPN is an open-source software application that implements virtual private network (VPN) techniques for creating secure point-to-point or site-to-site connections in routed or bridged configurations and remote access facilities. It uses a custom security protocol that utilizes SSL/TLS for key exchange.
Smoothwall is a Free and Open Source firewall that includes its own security-hardened GNU/Linux operating system and an easy-to-use web interface.
ClearOS is an operating system for your Server, Network, and Gateway systems. It is designed for homes, small to medium businesses, and distributed environments. ClearOS is commonly known as the Next Generation Small Business Server, while including indispensable Gateway and Networking functionality.
DriveBender is the class leading storage pooling technology for Microsoft Windows. Developed by Division-M, Drive Bender allows for file redundancy via file duplication, and unlike RAID, does not require any proprietary drive format or complicated setup. (Now free)
CloudExtender is local Windows storage, powered by the cloud... with optional, state of the art TNO (trust no one) file encryption built right in. Create a Windows drive or folder that maps directly to your favorite storage platform in minutes.
SnapRAID is a backup program for disk arrays. It stores parity information of your data and it recovers from up to six disk failures.
flexRAID is a family of storage data protection products that provide great flexibility and various innovations. The current product line includes: RAID over File System (RAID-F) Transparent RAID (tRAID).
freeNAS is an operating system that can be installed on virtually any hardware platform to share computer data storage over a computer network.
Rockstor is a free and open source NAS(Network Attached Storage) solution. It's a software solution and can be installed on any hardware or a virtual machine satisfying these minimum requirements.
nas4free The NAS4Free operating system can be installed on virtually any hardware platform to share computer data storage over a computer network.
Xpenology is the name of a Linux boot image, which allows to run operating system Sinology DSM on almost any hardware (not just Synology).
owncloud is a self-hosted file sync and share server.
openFiler provides a simple way to deploy and manage networked storage.
openATTIC openATTIC combines open source storage tools in such a way that their entire functionality can be managed through a central interface. Carefully matched components ensure both stability and security. Its open interface enables you to integrate openATTIC to provisioning, monitoring and backup systems.
= Cameras =
iSpy is the world’s most popular open source video surveillance application.
ZoneMinder is intended for use in single or multi-camera video security applications.
motioneyeOS is a Linux distribution that turns your single board computer into a video surveillance system.
Blue Iris is security camera manager. It's not free (60$ for the full version) but it was highly recommended and there doesn't seem to be any comparable free alternatives.
= Documentation =
DokuWiki is a simple to use and highly versatile Open Source wiki software that doesn't require a database.
gollum is a simple, Git-powered wiki with a sweet API and local frontend.
BookStack is a simple, self-hosted, easy-to-use platform for organising and storing information.
phpIPAM is an open-source web IP address management application (IPAM).
Paperwork aims to be an open-source, self-hosted alternative to services like Evernote ®, Microsoft OneNote ® or Google Keep ®.
afraid Free DNS Hosting, Dynamic DNS Hosting, Static DNS Hosting, subdomain and domain hosting.
No-IP's mission is to provide useful, reliable and powerful services that help home users, small and large businesses and even fortune 500 companies take control over all aspects of their DNS and domain services.
xapi-back is a simple backup tool for XenServer or XCP – xen hypervisors using xapi toolstack. xapi-back is a command line tool with simple and clear interface (command + options). Tool is written in python.
Hi everyone! I ran into Ethereum several months ago while reading about bitcoin and the blockchain and was quite impressed by some videos explaining the project (most of them by Vitalik himself). During this time I've tried to educate myself on this breakthrough technology. And at this point, I'd like to get a little more involved. I think that one easy way to contribute to this fascinating project is by running a full Ethereum node, so let me share some stuff of my experience of setting up an Ethereum node on Raspberry Pi 3. While doing some research about the best Ethereum client for my raspberry Pi 3 I realized that pretty much there are no ARM nodes on the network (according to ethernodes.org). Shouldn't be precisely the opposite? ARM devices such as Raspberry Pi have a good performance, are cheap and power-efficient. I looked into "EthEmbedded"  (great project, by the way) but it is mainly focused on Geth and Eth clients and you need to run the Ethereum clients manually. It's built on top of Ubuntu mate (and we need to keep things light). Besides, I was looking something more Flash & Play :-). So, I compiled Parity from source on my raspberry Pi 3 (which is the most efficient Ethereum client out there ) and gave it a try. I was really surprised with the overall performance and thought that it would be great to get an Ethereum node up and running easiest way possible. So, I built a custom Raspbian image which runs Parity as a boot up service and starts syncing the blockchain with no user interaction. This is what I got so far: A custom  Raspbian  image with Ethcore Parity 1.3  integrated. The image is generated using pi-gen  (plus a couple of files for Parity installation) Some remarks:
Parity was compiled from source according to Ethcore official documentation 
Parity binary is deployed through a debian package  (based on the official Ethcore Ubuntu x86 package plus some minor modifications )
MicroSD partition is resized automatically on first boot (this is a default Raspbian feature)
Parity runs as a Systemd service (as "pi" user) and it is started right after the network goes up. The Systemd option "Restart=always" is enabled for keeping Parity alive in case the process dies or gets killed
This is a Raspbian Lite Image (no Xorg environment) to save as much resources as possible.
Installation is pretty much flash and play. The idea is to quickly set up an Ethereum node even by non tech-savvy users.
Once the full blockchain is synced, Parity cpu load rarely goes beyond 40% which I think it's an outstanding performance for this kind of devices (Ethcore team did an amazing job here).
You can get the current Parity output by running "sudo systemctl status parity"
SSH is enabled by default so you can connect remotely to the Raspberry
Final thoughts: I think there are several reasons to try to increase Ethereum ARM nodes in the coming months:
Light clients are around the corner and this may affect the total number of Ethereum full nodes.
Share economy: Devices like Raspberry Pi's should be key components of web3 and IoT infraestructure. Conventional x86 computers are a waste of resources for this kind of tasks
POS: There's no much information regarding PoS but it would be great to use this kind of devices for the stake process (don't know if this is possible at all)
Let's do this. Mine is up and running :-) TL;DR: If you want to contribute to the Ethereum network, get a Raspberry pi 3, install the OS image into your microSD card, connect the ethernet cable and power on your device. This is it, flash and play :-), you are already running an Ethereum node!
Help please, Staking reddcoin on Raspberry Pi (Raspbian Stretch with desktop)
Hello, I could really use some help setting up a reddcoin wallet on the Raspberry pi. I've tried executing the following 2 guides, but unfortunatly they keep giving me errors. Guide1: https://www.reddit.com/reddCoin/comments/2b8wqm/tutorial_compiling_and_running_the_reddcoin/ Guide2: http://d-lindemann.de/2017/09/reddcoin-staking-mit-raspberry-pi/ instead of using the recommended "Raspbian (Debian Wheezy). The image file name is 2014-06-20-wheezy-raspbian.img." i'm using the latest " Raspbian Stretch with desktop Image with desktop based on Debian Stretch Version: November 2017 Release date: 2017-11-29 Kernel version: 4.9" Also instead of using Reddcoin v184.108.40.206 i decided to go with the* Reddcoin V220.127.116.11 (latest version todate)* every step untill step 6 seems to work fine, but then after executing command: make -f makefile.unix" the following error message appears:
make: makefile.unix: No such file or directory make: *** No rule to make target 'makefile.unix'. Stop.
However this did not seem to clear my issue. reading on they talk about it being an issue with libssl in debian 9. with the following link. (at this point i'm noticing how the further i go, the less ground is beneath me to stand on.. and i'm not a good swimmer in unix). anyways final post there says the following code should fix it: https://github.com/peercoin/peercoin/commit/5b09830e5de0f5105534e69dbf4acffb3255869b But what do i do with this link i have no idea. and that's kinda where my progress halts as i cannot for the life of me find out what to do next to troubleshoot this issue. So TL:DR I'm trying to use the make command in ~/reddcoin/src however it's giving me BIGNUM errors preventing me from making progress. I'm using PI model B+, Raspbian stretch latest version plz halp...
[Guide] Setting up Trezor + Electrum 2.02beta + armory on a Raspberry Pi 2. Cold offline signing for $40
Having just received my Pi 2, I am happy to report that a fresh Raspbian install, on an 8 GB Class 10 MicroSD card : Electrum / Armory / Trezor / BTChip all work with my Single Board Computer setup script (it also works for Pi B, Pi B+ Raspbian and BeagleBone Black Debian & ubuntu, also tested on Odroid C1 Ubuntu 14.4) The full "!" installation takes about 40 mins on Pi 2, which is at least twice as fast as on the Pi B+ / BBB Notes
on the first run of raspbian, choose the first raspi-config option, "Expand root partition to fill SD card", and then reboot. You should see >2.9Gb free space and >7Gb total space in PCManFM. Edit: Use the Odroid desktop tool to expand the partition also. Edit 2: on odroid and raspbian you need to expand and reboot twice to take effect.
for my btchip HW-1 to work with python/electrum 2.02b I needed to run ./btchip-c-api/bin/btchip_setTransportHID and power cycle
armory 0.92.3-beta works on Pi 2, despite being built for the ARM6
btchip HW-1 HID keyboard seed replay requires > 1.4.13 firmware to avoid clipping on Pi B/B+/BBB. No issue on Pi 2.
unfortunately wheezy raspbian's Chromium is still at v22, which was due to ARM6. Hopefully a newer ARM7 Chromium will be added to the distro.
on Jesse raspbian apt-get chromium / chromium-browser is completely broken
BBB Debian is limited to Chromium 37, enough to run Greenaddress (WinHID mode)
BBB Ubuntu 14 runs Chromium 40, with some screen glitching.
raspistill -o scan.jpg plus picamera plus qtqr works well. Maybe I'll add Wolfram qr decoding to a future update.
ODROID C1 has arrived and partially works. Using the latest Feb Ubuntu 14.04 distro, Trezor / btchip / electrum 2.02b / Chromium 40 Greenaddress mostly work. I'm doing some troubleshooting with Nicolas - I had to git clone https://github.com/walac/pyusb.git, despite having pip installed pyusb already, and needed to alternate between ./btchip_setTransportHID and ./btchip_setTransportWinUSB for electrum and greenaddress.
Armory's Raspberry Pi 0.92 offline bundle releases work on BBB Ubuntu and Pi B/B+/2 Raspbian wheezy.
Tested, step-by-step tutorial to run a 21 Bitcoin Computer as a virtual machine
Many thanks to ButtcoinEE and ecafyelims for initial pointers, but if I understood correctly, both users said they hadn't actually tried it themselves. So here comes a tutorial based on something I actually tried. Best of all: You don't even need a Raspberry Pi! We'll run it as a virtual machine. The first step is to get a Debian 8 (Jessie) installation up and running. You might want to install that inside a VMWare/Virtualbox machine. I'll be using Vagrant here ( https://www.vagrantup.com/ ) which makes it easy to manage virtual machines like that and already has a Debian 8 image in the catalog. So get Vagrant for your platform and then do something like this:
vagrant init ARTACK/debian-jessie vagrant up
You should now be able to SSH into the machine:
Now that we have a Debian up and running, let's first get some packages we'll need later:
sudo su # become root apt-get update apt-get upgrade apt-get install apt-transport-https git cython3 python3-setuptools
It'll complain about a missing GPG key, but you can just ignore that. We should be able to do 'apt-get install two1' now, but it complains about a missing package 'python3-sha256'. The reason for that is probably, that we are doing this on a x86 architecture, where the packages are slightly different than the Raspberry Pi's ARM architecture. So we'll just manually install the package and have it ignore the dependency errors:
We'll have to extract the credentials for the specific network they use from 21's zerotier package:
mkdir credentials cd credentials wget https://apt.21.co/pool/z/ze/zerotier-one_1.1.0-1_armhf.deb ar x zerotier-one_1.1.0-1_armhf.deb tar xf data.tar.xz cp valib/zerotier-one/updates.d/ZeroTierOneInstaller-linux-armv6l-1_1_0 /valib/zerotier-one/updates.d/
Before we join the network, we need to lock down our machine. That's actually a bit tricky, as these Vagrant images aren't really designed with security in mind, but rather only to be used for local testing. I think it should be enough to do:
Note that you won't be able to use 'vagrant ssh' any longer afterwards, as we just deleted the standard Vagrant key-based login. You'll have to use 'ssh [email protected]' instead. Now we are ready to join the network:
wget https://gist.githubusercontent.com/balajis/6d495bb40fb157a58677/raw/21-join.py python3 21-join.py python3 21-join.py # might have to try this twice as well ifconfig zt0 # will show your new IP within the VPN
The 21 tools have a concept of both an on-chain balance and an off-chain balance - the latter being managed by 21's server. You can deposit to your on-chain balance, but currently the only way to increase the off-chain balance is by mining or by receiving payments from others. Without the mining chip it's therefore a bit tricky to increase that off-chain balance. I hear that a feature request is being considered, to allow moving funds from on-chain to off-chain. That's all! If you want to give it a shot, you should probably move fast, as 21 has some DRM in the works, as per this comment: https://www.reddit.com/Bitcoin/comments/3tnjz7/tutorial_turn_your_35_raspberry_pi_into_a_21/cx7tih3 . This was brought to you by https://coinado.io/ - cloud torrenting for command line fans. Check us out - we are also big on micropayments! ;-)
Trying to set up a BU node, but need a hand setting signals
Just a little bit of preamble for now, TL:DR below. I first got into Bitcoin back in about 2012/13 whilst studying Comp Sci. Now I'm a Computing Science teacher in an English High School. In February I found my old wallet.dat file and discovered that when I stopped looking at BTC back after selling about 1 BTC to pay a parking ticket back in 2013 (Price was about £36/BTC and the ticket was about £30) that the tiny "worthless" fraction of a BTC now had some value and I've been working hard to invest it and make it grow. I've also been trying to get my head around the whole scaling debate just now and feel that SegWit just doesn't feel like the right solution, so I'm in the process of setting up a few nodes. One on my server, one on a Raspberry pi at home and one on a server at the school I teach at (since I was able to convince the network admin that it was a fun project that I could use for some teaching). This is where I hit the issues. On these three machines I've got the BU client installed, but can't figure out how to get them to signal something other than a 16MB blocksize. From the GUI on my desktop it's easy enough, but just can't find out how to it on the headless machines. Any guidance would be appreciated. TLDR: Got a few headless BU Nodes syncing up and want to set the Excessive Bytes value, but can't figure out how. All three are running on various Debian releases. Any advice would be appreciated. Thanks
So I recently I became quite interested in mining and cyptocurrencies in general. So interested in fact that I bit the bullet and decided to buy myself a GAW Fury. I then spent some time doing research on how to set up a GAW or Zeus ASIC on Linux, in particular on a Raspberry Pi, and have found most guides to be awful. The reason they are so bad IMHO is that they assume quite a bit of prior knowledge, either with Linux or mining, and give very little instructions. So I have tried to put together a guide that requires very little prior knowledge. It is my aim that anyone could get their shiny new asic up and mining in no time using this guide. Anyway, I present...
The Complete Noobs Guide to Setting Up a Zeus or Gaw ASIC on Debian/Ubuntu/Raspberry Pi
About Cyrptocurrencies and Their Jargon
If you are new to cryptocurrencies and how they work I suggest taking a look at this series of KhanAcademy videos. They are for Bitcoin but the theory is the same. I found them very helpful when it came to understanding what mining actually does and the mechanics of cyrptocurrencies. Also take a look at sircamm22 his info found here, is great and breaks down a large number of concepts. I slightly disagree with no. 21 regarding preordering. Just exercise common sense.
If you are new to Linux you could follow along by simply typing in the commands. However I highly recommend taking the time to learn what you are doing. This course is a great place to start.
By the end of this section you will have your device turned on, fully setup and connected to the internet with. Note: Commands to be typed into the command line will be displayed like this:
echo Hello World
For laptops and desktops already running Ubuntu or Debian I will assume you have setup your internet setup as part of the installation. If not: There are plenty of guides out there and the installation/setup process is very easy. A good place to start for Ubuntu is here. Now open up a terminal window. Ctrl + alt + t on a standard Ubuntu installation. If you plan on using this PC without a monitor I would suggest installing an SSH Server. These commands will be discussed later on in the guide.
sudo apt-get -y install openssh-server sudo service openssh-server start
The Raspberry Pi Foundation has put together a great guide in PDF format. Use NOOBS it will save you a lot of trouble. NB: Some SD cards don't support NOOBs but will work fine if the image is put on using a different method. Here is a great guide for setting up the Raspberry Pi SD card from Elinux.org. In fact it's a great place to start for anything RPi related. Raspberry Pi hub at Elinux. Once the SD card is setup you will need to insert it into the Raspberry Pi and boot. Install Raspbian from the NOOBs menu and wait. Follow this guide by Adafruit for first time setup. You will need to enable SSH Server. I suggest not starting the desktop on boot. It can be easily run from the command line by typing startx. Follow this guide by Adafruit to setup your network. Found here. No need to do this if you set up previously in the first time config. We will also at this point want to setup ssh. Again I will point you to an Adafruit guide. Once done exit back to a standard command line interface. This can be done in LXDE by using the power off menu located in the bottom right corner.
If you want to the Raspberry Pi or PC without a monitor go ahead and SSH into your device. So now you should be staring at a command line interface whether on the device with a monitor or via SSH. First things first lets make sure we are all up to date. This will update our package list from the repositories and upgrade them to the newest version. "-y" Will simply say yes to any prompts.
sudo apt-get update && sudo apt-get -y upgrade
We are going to need to install some useful tools. Git-core is how we will clone and download BFGMiner from GitHub and Screen allows multiple command line instances and means if we exit out of ssh session or quit Terminal on Ubuntu, BFGMiner will continue to run.
sudo apt-get install git-core screen
We also need to download some other tools/dependencies to ensure that BFGMiner will compile successfully.
Once the download has completed move into the bfgminer directory.
The following steps may take a while. Now run autogen.sh
You will need to make the configure script execuitable.
sudo chmod +x ./configure
Now configure bfgminer
sudo ./configure CFLAGS="-O3" --enable-scrypt
Now lets make!
sudo make install
One more thing...
If you haven't already plug in your ASIC. Just confirm your system is recognising the ASIC.
Its output should look similar to this (no need to type this in):
Bus 001 Device 005: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Yep there it is our ASIC listed as device 005. There is no need to install any drivers, unlike in windows, as they come in the kernel. Now lets actually start BFGMiner. You will want to start a screen session to ensure BFGMiner doesn't quite when you exit. "-S" is the option for starting a new screen session. You can replace "miner" with anything you like.
screen -S miner
Now you can run the commands below. Here is a sample of what you should type. You will need to replace somethings with your own values.
Where: URL:PORT is the address and port of the pool you wih to use. Now I won't suggest a pool. I will leave that decision up to you. If you do wish to mine DOGE take a look at this site for a list of pools and comparisons. USERNAME this is the username you use on the pool. Every pool is different. Check your pool's website for details. PASSWORD same as above. Specific to your pool, not every pool requires one. CHIPCOUNT this is specific to which ASIC you are using. For GAWMiner ASIC's:
War Machine: 256
Black Widow: 64
For ZeusMiner ASIC's:
Hurricane X2: 48
Hurricane X3: 64
Thunder X2: 96
Thunder X3: 128
Now to make sure you don't stop mining when you exit ssh or terminal. Press:
ctrl + a + d
To come back to the BFGMiner screen simply run:
screen -r miner
Start on Boot
First off you will want to make sure you have BFGMiner running correctly. Ensure you have the miners set up properly and your pool correctly configured. Start a BFGMiner instance, detailed above. Once the instance has started and you are happy with how everything is working press "s" on your keyboard to enter the settings menu. Now press the "w" key. Don't press enter. We want to specify where our config will go. Type:
Substitute USERNAME for your user. On a standard RPI install its pi. On ubuntu it's what you set during the instillation. Now press the enter key to return back to the main BFGMiner screen. Press "q" on your keyboard to exit BFGMiner. You should now be back in the command line. Now we want to edit a file called rc.local. Any commands in this file will be executed on boot.
sudo nano /etc/rc.local
Depending on your system this file may already contain some commands. Be careful not to delete them. After the last command and before "exit 0" type the following on one line:
Where USERNAME = your username Hit ctrl + x then y to save and exit nano. The above command will create a new screen session and run bfgminer using the config we created earlier. All while as our username so that we can easily reattach. Lets reboot to ensure it is working correctly:
Once rebooted and logged in, show all running screen sessions:
Reattach to the session. You only need to use the numbers before the first dot. e.g Mine looks like: 2480..hostname (13/07/14 12:02:09) (Detached). So I type:
screen -r 2480
Verify everything worked as expected. Then ctrl + a + d to exit. You have now setup BFGMiner to restart on reboot.
If you are using a Raspberry Pi and it loses power it will automatically reboot on receiving power again. For standard desktop PCs there is an option in some BIOS/UEFI to turn the computer on when it receives power. Consult your motherboard's manual and manufacturer's website.
Congrats you've done it. You have managed to successfully get your shiny new asic mining away. I do plan to make another guide detailing how to setup and use StarMiner a ready to go RPi mining distro. So I hope this is helpful for you guys. I have seen lots of posts asking the exact same questions again and again and I have tried to answer these as best I can. I am still learning about this stuff so if there is something I have missed or a mistake I have made please tell me. Anyway good luck. And I'll see you at the moon. Cheers Frogsiedoodle Edit 1: Layout and formatting. Edit 2: Added instructions for screen which I initially forgot. Edit 3: Removed 1 unneeded dependency Edit 4: Added section on start on reboot and power failure.
File > New > Hardware wallet. Both Trezor and btchip work as they do on OSX, apart from the Pi's slow CPU taking ages to generate the HD tree and Sync. Limitations At this stage a Pi is too slow to receive btchip's 2fa OTP confirmation code, with the auto-type saturating the text buffer. I'm confident Nicholas can fix this in firmware. Edit: an ipad2 + Apple CCK is too slow to buffer the seed about 1/4 times. Edit 2: an iPhone5/retina iPad mini + Lighning to USB camera cable works with btchip with iOS 8.1 with selected text editors. You can use btchipPersoWizard.py to restore a BIP39 mnemonic, however btchip's HW1 is unable to support on-device BIP39 seed+passphrase, but this feature might be added to the electrum plugin later. I don't know if greenaddress CRX will work on piper, there doesn't seem to be an official armhf build available from google, and the latest sudo apt-get install chromium version is v22 whereas Chrome is at v38. (it might be possible to download https://github.com/greenaddress/WalletCrx and pack/drag-drop the extension manually in developer mode)
user-circle-based rights management: Browsable file sharing rights to circles. For example Browsable music directorys only to family, Browseable picture directory to only Friends, Browsable CC-media to all RS-Friends, non-browseable files as anon share to all friends and friends of friends.
Find new friends in public chat lobbys. depending on your
post your public-certificate as link into the chatroom or share it for example with cryptobin.org in a separate chat like crypto.cat
ChatServer / IntroServer for making new Friends
paste your certificate to the chatserver and copy the certificate of the chatserver and add it to your friends. After that the chatserver will connect as a friend. No data transfedownloading, the chatserver advertises only public chatlobbys
#1 chatserver F2F-fr IntroServeChatserver to get access to 4 chatlobbys (Chatserver FR, Chatserver DE, Chatserver ES, Chatserver EN) from the chatserver. The F2F-fr chatserver discards every ~3 days all his certificates and you have to re-enter your certificate to the chatserver if you want to rejoin.
#2 Chatserver RetroShare-Chatserver- acts on a FIFO Basis and keeps only the last 100 entered certificates as a friend to connect with. There is no need for reconnect every three days. Better is to connect to both. he will kick you if another 100 user add their certificate
Installing OpenBazaar on Raspberry Pi 3 (Raspbian "Jessie") Is A Pain - and does not work
Hello, hope to get help in this Bitcoin community which should have the main users of OpenBazaar. I cannot get this run. Installing on Ubuntu or Linux Mint is utmost simple with the downloadable debian packages (*.deb). In short:
The server installation completed, but the openbazaar server daemon cannot be stopped with "python openbazaard.py stop", the CPU load remains at 100%.
The installation of the client fails due to several failures of the "sudo npm install" commands...
For the Raspberry Pi (Raspbian Linux) I find various different tutorials on the web, all of which are somehow different and incomplete and of different age (so not sure what Openbazaar and what Raspbian version they refer to). I get one error after another. After several hours I am giving up now. I have installed so many other packages that are allegedly required for OpenBazaar (in one tutorial or another)... but it still does not work. Not to mention the need to separately install the OpenBazaar Server and Client and the different configuration options, and no tutorial that really explains everything in a proper way how all components work together and what to do depending on the use-case. This is a shame. OpenBazaar should FIRST run on the Raspberry, because the Raspberry is a low-power-consumption device that can run 24/7 with an electricity bill of only 5-10 EUR per year. And OpenBazaar as a decentralized marketplace is designed for exactly this mode of operation - always online! No way would I use a normal computer for this. Has anybody successfully managed to install OpenBazaar (1.1.3) on "Raspian Jessie"? Is a tutorial available that really works completely? Or even better, a debian package? Actually I was inspired buying a Raspberry Pi because of OpenBazaar in the first place, and now I am stuck. A good tutorial should include best practice recommendations on all parts, including:
The exact HW version and SW version of the Raspberry/Raspbian, and the SW version (git sha1 hashes) of the installed git packages (see below)
Folder where to install OpenBazaar Client and Server respectively (best practice)
The sha1 hash of the OpenBazaar git version used for the successful installation that the respective tutorial is referring to
"git tag -l", etc. (so a user has the chance to use the very same version (tag) to avoid surprises due to installing anothenewer (unstable?) version compared to the tutorial's author).
"git checkout "
Information / best practice of the sequence of starting server and/or client, and for which use case!
Finally, what I am desperately missing is information how to backup and restore OpenBazaar configurations and move them from one computer to another. For example, I have installed OpenBazaar on my Linux Mint PC some weeks ago and created an account and a listing already, of course with OpenBazaar ID. Needless to say that now that I install OpenBazaar on my Raspberry, I want to use the same account there (instead of on my computer), such that information is not lost.
I believe the criticism around Unity could be divided into two broad categories (1) fear of change and (2) critcism about the design/stability of Unity. Back when we originally released Unity into Ubuntu, there was a lot of (1) and some (2). With Ubuntu 12.04 there is a little (1) and not much (2). Unity in 12.04 is significantly faster, better designed, and better executed and I most of the responses I have seen to 12.04 have been praising Unity.
In terms of fear of change, there will always be some folks who don't like it: that is fine; we have many wonderful options for desktops in Ubuntu. Some folks though feel like we are "dumbing down Linux"; I thoroughly disagree with that notion. Linux should be for everyone, not just Linux geeks, and we want Ubuntu to bring Free Software to everyone, not just a fiefdom populated by those with significant technical skills. What's the process of implementing Ubuntu for Android like? What do you expect the response to it to be, and how are device manufacturers responding to it? Is Canonical trying to become the Apple of Linux? What other strategies are you implementing to help Linux go mainstream?
"I fear Canonical hasn't been listening to the specific concerns of its community when it comes to Unity in particular. It's not that I'm afraid of change, or that it's unstable, it's that it's ugly, unwieldy to use, and non-configurable. The lack of control and configuration coupled with the fact it's been forced down our throats is what really seems to irk the community".
I would consider myself a power user, I am regularly switching applications and it works fine. But here's the thing: this is all personal opinion. It works well for me, perfect! It doesn't work well for you, well you can either help us fix it or use something else. Perfect! Either way, we all get to use Free Software. :-)
"Sure, maybe it's time for Ubuntu to move on and try this really ambitious move to dumb down linux for old people, alienating its previous userbase, but it's a damn shame because I used to really like Ubuntu". I always hate to see the term "dumbing down" because it is exclusionary: Ubuntu is for everyone...not just for people with a certain level of expertise. The difference is...for a novice user, they require simple defaults otherwise we lose them, a more technically savvy can dive below the surface and install additional configurability.
Yes, the convergent device (Ubuntu on Android) is a key area of focus. Canonical engineers have been continuing to build it out and our business team has been working with various handset makers to sign agreements. I believe there are a few deals underway.
As for people taking it and baking it into custom ROMs, I don't see why this couldn't happen in the future. It is unlikely to be one of our standard releases as most people don't install new OSs on their phones, but I am sure the software will be available for integration some time.
The Humble Indie Bundle release has gone really well. We had nearly 10000 downloads in 72 hours, and the downloads are continuing. A number of previous games are in the Ubuntu Software Center and we are working on others too.
As for Quickly and game development: I would love to see that, we just need a community member to contribute to this. If you (or someone else) wants to help, I would be happy to help you get connected to the right person.
Big, professional, signed artists with major labels.
Newer artists with smaller labels, still probably working part time.
For the big artists, the traditional music industry (make music, sell it, go on tour, sell overpriced merch and tickets etc) works well. This is because for these artists the music companies work like VCs: they put lots of money into different projects and every so often they get a Justin Bieber.
For smaller artists, they are typically working with small labels with barely any marketing budget. This means they sign their value (their music) to a label who often doesn't have the resources to bring the artist up to a higher level.
I believe that for smaller artists, the Creative Commons is the way to go. We did this with Severed Fifth: we grew a community, raised $5000 in funding to record our album, and gave it away for free so others can use it. Our music has appeared in all kinds of music videos on YouTube, in games and elsewhere.
The challenge is for smaller artists who work full time on their music. For weekend warriors like me, money is not that of a deal as I have a job, so giving music away for free is fine. If you are relying on getting paid at a show and need to sell that merch, giving away your music is a big deal, so I understand how some folks are resistant to it.
I think flavors and derivatives are awesome, and we are very supportive of them. Part of the reason we divide up Ubuntu engineering into Kernel, Foundations, and Desktop is to ensure that the Kernel and Foundations output can be useful for flavors and derivatives too.
What does your job entail as a Community Manager? My job is divided into a few different areas. Firstly I build strategy around where we need to build growth and focus on our community (e.g. most recently a strong strategic focus is app developers). Secondly, I manage a team of five community managers who work on different areas (Daniel Holbach (developers), David Planella (app devs / translations), Jorge Castro (cloud), Michael Hall (app devs and upstreams), and Nicholas Skaggs (QA)). Thirdly, I work to ensure Canonical staff members are working with the community and that the values and needs of the community are well served. Finally, I work directly with the community to resolve issues, focus on certain areas, and respond to questions from the community and press.
Each of the technologies you highlighted have been successful, but not neccessarily the most popular. In technology I don't think popularity neccessarily means success. As an example, bzr serves our community really well, so does Launchpad, but I agree it has seen limited wider success. I think Canonical manages Open Source projects well...Ubuntu has been very successful, but I think it boils down to what people want...people want Ubuntu, but in many cases people want git instead of bzr.
I am glad we are continuing to invest: we have big, hairy, goals. To achieve them we need growth, focus, and strong teams, and I think we have these. We will break even, but this is a game that needs a lot of upfront investment and passionate people.
I have worked with him since I joined Canonical. He is a cool guy, very technically savvy, with a strong vision, and a strong loyalty to people who are loyal to him. He is very passionate about the community and sits on our Community Council and Technical Board and often gets involved in community matters.
I would love to do another LugRadio show. We just need to figure out a way of getting the team together, which mainly involved me getting to England to record a show. Maybe we could try a G+ thing sometime. :-)
Absolutely! Right now it is very Ubuntu centric as we are building for what we know, but the system supports accomplishments from other projects too. If someone wants to build an Accomplishments Collection for Fedora, FreeBSD, or whatever, the system supports it. You can read more about creating accomplishments at Link to wiki.ubuntu.com
The only piece of the core system that is very Ubuntu specific is that it uses Ubuntu One. If someone wants to submit a branch to support other backends we would be happy to review. :-)
I guess you would love to see available on the Ubuntu Software Center mainstream popular games even if they have DRM and some other important applications like Photoshop, Autocad and etc... But if we fill the desktop with a lot of these things at the end what would be the difference between an Ubuntu desktop and a OSX desktop? Don't you think that open source should create open alternatives and try a different approach?
That's better, thanks for presenting your question more politely.
When we introduced Unity we knew that chunks of it needed more sheening and refinement. What was important to us was to ensure that Unity was in good shape for Ubuntu 12.04, our next LTS, this is why we dropped in a few releases early to give our users a chance to play with it, share their experiences, share their concerns, and give us a chance to fix these outstanding problems.
Now, as you say, some folks were not happy with Unity. I think part of this was that those early Unity releases has a pretty tiny amount of QA applied: they were crashy, and when Unity crashed, it would take compiz down with it too. To remedy this we built an automated testing lab, and hired someone on my team to build a community of manual testers. I think most would agree that the Unity in 12.04 is much higher quality.
When we introduced Unity originally some folks just didn't like the design. This is always tough: design is emotional, and so is change, so a change with a new design is really emotional. Now some of the feedback at this time was constructive: it highlighted specific deficiencies in the design, problems in the implementation and other things. The design and engineering teams read all of this feedback with interest and reacted to much of it in future releases.
Some folks just didn't like Unity for the fact it was "different" and "why didn't you guys just keep shipping GNOME 2". For us to bring Free Software to more and more people we need to constantly evolve, and Unity was a step along that evolution. We have expanded our target demographic to not just Linux enthusiasts but general consumers too, and we found that GNOME 2 did not serve general consumers as well...as such Unity was designed to bridge that gap.
Now, of course, Unity is not perfect. There is still lots of work to be done, and many improvements to be made, but I think we are on the right track.
One thing I can assure you is that Canonical did not ignore this feedback: quite the opposite, but we did focus on the constructive feedback as opposed to the rantings on social media networks. Ubuntu is a shared project, our community is an integral part of the project, but we have to have a platform of respect and collaboration to do good work...and this is why we focused on the feedback from those who wanted to engage as opposed to yell.
I think many new community managers don't build enough strategy into the plans. They have generalized plans around "growth" and "awareness". If you are working professionally for a company, this lack of meat on the bone doesn't give the company or the community enough assurances around the work.
Today, not really. Our primary focus is on the collaborative contributor community. This is changing as we focus more and more on user communities (e.g. the app dev community who only want to use Ubuntu as a platform).
We are not ignore Linux enthusiasts...we are just not focusing purely on them. Some people presume that just because we don't have everything that a Linux enthusiast needs we are "ignoring" them. We want to build a system for everyone, and that requires a delicate balance.
As I said earlier, for a novice user if we include too much configurabilty that doesn't make sense or is not properly designed, user testing shows that it makes Ubuntu less useful. Technically savvy people can install and add additional configurability where desired. This is why I think it is better to have a simple Unity by default and then allow people to tune and tweak it with additional tools like MyUnity where needed. This way you get the best of both worlds: a simple out of the box experience, yet Linux enthusiasts can hotrod their system to get more if they want.
Aren't you heartily sick of every public discussion you take part in getting hijacked by the small, but excessively vocal, minority of people of just can't deal with people doing some actual work to try and improve the Linux desktop experience (i.e Unity) and prepared to do anything active about their own problems? There is definitely a vocal minority, but my take on this has been that every opinion and critique is fair so long as it is respectful, accurate, and preferably in the interests of finding a solution. Some folks have tried Ubuntu 12.04 and still don't like Unity and have a list of reasons why, and they fairly and respectfully share those views: that kind of discourse is wonderful...it helps us improve.
Without wishing to push my book, I think it will be helpful for you. Just make sure you get the new 2nd Edition: there is lots of other good content in there.
My advice for getting started is to study the work of other community managers, and listen and learn from their experience. Community management is a skill that is passed on between different people, and that kind of observational work is useful in seeing patterns and approaches to the profession.
Outside of our current funding, I am not sure we will be able to commit to further funding. What I would love to see is LoCo Teams supporting themselves more and more with Kickstarter campaigns and donations drives to help cover any other expenses. :-)
Part of the original plan was to have human-awarded accomplishments. The classic use case we have here is something such as an Ubuntu contributor wanting to thank someone for some great work that cannot be auto-detected with the current system. We would give them the ability to award a trophy to this person so it appears in their My Trophies view.
For your parachute jump example, we could potentially set up a system where a set of people can issue trophies when they see proof of something. For example, you send someone a photo of you doing the jump and then they award the trophy.
This would be great for bucket lists (e.g. visiting a set of landmarks) and then getting trophies for each one you visit.
It is all possible, we just need more hands on deck to write the code. :-)
Raspberry Pi OS (previously called Raspbian) is our official operating system for all models of the Raspberry Pi.. Use Raspberry Pi Imager for an easy way to install Raspberry Pi OS and other operating systems to an SD card ready to use with your Raspberry Pi:. Raspberry Pi Imager for Windows; Raspberry Pi Imager for macOS; Raspberry Pi Imager for Ubuntu Install Bitcoin Core on the Raspberry Pi 3/B+. sudo apt-add-repository ppa:bitcoin/bitcoin; sudo apt-get update; sudo apt-get install bitcoind; After running the aforementioned commands, you must configure your router for port-forwarding at your Raspberry Pi local-IP address- to that run, ifconfig -a. If you want to run a full node on the Bitcoin network, you might want to do so on a computer that doesn’t use so much power and is very inexpensive. The Raspberry Pi is an obvious choice for that. Here’s a tutorial on how to install the newest version ofBitcoin Core on the Raspbian OS, which is based on the Debian GNU/Linux distribution. If Bitcoin is a free open source peer-to-peer electronic cash system that is completely decentralized, without the need for a central server or trusted parties. Users hold the crypto keys to their own money and transact directly with each other, with the help of a P2P network to check for double-spending. Note for future bitcoin upgrades: Here we're basically changing the bitcoin Dockerfile to use the bitcoin image compatible with Raspberry Pi 4 instead of the Desktop compatible version in the default Dockerfile. The above is for Bitcoin v0.18.1. For future bitcoin upgrades, here's how you can find which filename & hash to put in there:
Hey Everyone! This is a tutorial on how to setup a fully functioning bitcoin miner using a Raspberry pi. Raspberry pi's are extremely useful for programming and for bitcoin mining. Enjoy. Alexander J. Singleton provides a screencast for Raspberry Pi set-up and configuration introducing Bitcoin-mining as part-1 of a 2-series tutorial- please refer to the following GitHub-gist for ... In this video I show you how to create a bitcoin wallet on a raspberry pi ... Installing the Electrum Bitcoin in Debian 9 (Stretch) - Duration: 12:55. Rex Kneisley 1,977 views. Make Your Own 15.6" Full HD Screen for 32 bucks for use with Raspberry Pi, DSLR, Video camera - Duration: 12:00. Alex Eames 799,549 views DIY Bitcoin Lottery with a Raspberry Pi - Duration: 7:33. SeanHodgins 35,864 views. 7:33. Build a Desktop Arcade Machine with Raspberry Pi 3 and Retropie: Super Turbo Pro Edition - Duration: 27:15.