posted that wrong...hmmm....lets try again...is it possible to run more than one wallet on a raspberry pi?
Yes it is. What do you want to achieve then Ill tell you how to do it.
thanks for the offer....probably could achieve a lot more than what I could think of..but to start...use it to operate some wallets for coins that offer pos...like this one spx, xra , ioc for instance.
You can run multiple wallets on a Pi for different coins and even multiple wallets fo the same coin but his second option is more complex to setup. Most of the time you can run about 3 wallets on your Pi depending ont he model. The latest Pi2 has a 1Ghz Arm7 CPU and 1 GB of memory and will give you 3 wallets safely.
You get 2 types of wallets and 2 build methods and 3 deployment methods which each has its own nuances and impacts on resource usage on the Pi.
The types of wallets are the headless daemon wallet with no graphical display and the Qt wallet which is the graphical wallet that you are used to in Windows. In Pi world you do not need the Qt wallet as the command line wallet does everything you need to do, but if you want to work in a familiar "windows" environment you can use the Qt wallet. Getting a Qt wallet depends on how the Qt environment is setup and if the dev has created a project file for a basic wallet using Qt4 then you are in luck since the mainstream OS for Pi (Raspbian) has Qt 4.8.2 with which you can create a GUI wallet easily. If the dev created a more fancy wallet he would have used Qt5 and then you are out of luck, since dependencies for Qt5 is not readily available yet. You can DIY Qt5 and build a static Qt5 wallet on Pi but trust me that you do not want to go there. I seldom go for the GUI wallets anyway because it servers no real purpose apart from seeing stuff visually and I run the command line wallets most of the time.
The first build method is to provide a static built binary where all code that is needed in the process to run the wallet is in the binary file. This is the least pure method to do in Linux, but since Pi's are very consistent from one to the next it is possible to get away with this. Binaries are larger though since all dependency code is in the file. The second build method is a hybrid where your script just downloads the dependencies but you provide an already compiled binary that is dynamically linked to the dependency files. The binary will call the dependency files whenever it needs some code from it.
In order to deploy you can write a script to compile it on users Pi which is the most pure way to work on Linux but prone to errors since many devs are sloppy with their code and dont do basics like create a src/obj folder or have incorrect permissions on certain critical build files which will all cause the build process to fail. The second method is to just deliver the wallet built with one of the 2 build methods but require a working and updated OS installation from the user, or you can provide the whole operating system with wallet installed to the user. The pro side of delivery method three is that the user does not have to install the OS himself, but the downside is that you are then limited to the wallet they give you and the environment may not be setup for you to easily install a 2nd and 3rd wallet.
It is a long introduction but necessary to explain my recommendation to you properly for running multiple wallets on your Pi. In your case my recommendation would be to install a fresh copy of Raspbian on at least an 8 GB card and update it. Then use the hybrid method of a dynamically built wallet to save space and since most coins require the same dependency files. Then compile the 3 headless daemon wallets you want to run dynamically and set them up properly and off you go. It should run fine on a Pi2.
If you let me know the coins you want to run, depending on if I feel generous or not, I will help you build the wallets and set them up.
