RasPBX Installation for Beginners
github.com
github.com
Most of the raspbian-based tutorials or images out there treating the raspberry pi like a normal server are just going to trash the SD or fail because system state is mutating in unexpected ways.
Start building immutable images that hold temporary data strictly in RAM.
Essentially, you start with your Rpi OS, configure it the way you want it - install services etc, and once you are done, just do "sudo raspi-config", select "Performance Options" and under that enable "overlay file system" (also select "read-only /boot" when asked). Reboot when prompted to complete this setup.
This will cause all changes to go to a temporary ramfs - and these changes will be lost on reboot. Most importantly, this means your SDcard won't be written to at all during normal operation. Do note that if you are using one of the older Rpis with 1GB RAM, you might face issues with RAM availability - depending on the amount of changes you make while the overlay is enabled. RPI4 variants with 4GB/8GB ram work really well, though.
If you do need to make persistent changes, just repeat the process starting with "sudo raspi-config", disable the overlay and read-only /boot, reboot, make changes, then renable the overlay. Its is a good idea to do an apt update/upgrade every month of so after disabling overlay.
Another thing you can do is to simply use USB sticks or USB drives as boot media (on RPI4). Those have much better lifetimes than sdcards, and are much faster as well.
While this does not compare to the performance/speed/safety/etc of a fully custom buildroot/yocto image, its a good compromise considering its almost effortless.
Shameless plug: I build such custom OS images for RPI and other SBCs for a living.
I havent seen anyone using a rpi to usb boot other pi's via a usb hub, do you think thats possible? :-)
More importantly - something like this can only be hooked up to _one_ boot device, so the usb hub and multiple pi's are a no go. I don't see any advantage compared to just using a usb stick instead of making a rp0/rpi4 pretend to be a usb stick.
You should look into network booting the multiple pi's - if thats suitable for your use case. You will still need an sdcard in each pi to provide the network bootloader, but once the boot is done, the sdcard isn 't used anymore (until the next boot)
The Buildroot manual is fantastic and it's worth working through the getting started section to get an idea. It boils down to creating a br_external tree that contains everything necessary to create a custom sdcard image as documented here:
https://buildroot.org/downloads/manual/manual.html#outside-b...
Building images from a br_external tree is pretty trivial, see the gitub actions in these example repos:
This builds a raspi4 64 bit image for tvheadend (I'm using this image for a SAT-IP TV dish w/ Kodi clients in my sister's house - so far no complaints about a crashed tv server after 1.5 years of uptime). This image runs the whole rootfs from initramfs w/o mounting a persistent root filesystem. I don't care for the additional ~150MB RAM that is used in this use case:
https://github.com/markuslindenberg/dvbheadend
My most recent buildroot based raspi image builds a 32 bit image pulling binary distribution of openhab and it's recommended jre into the image, running them from a read only root filesystem. I'm using this to reliably run openhab home automation in multiple places. This repo also is a br_external tree and embarrasingly doesn't have a README yet, I really really need to write one becaus I think it's quite useful and mature.
Specifically, I want to have a disk image with two root partitions - by default (ie, what I flash to the SD card) the first partition has a read-only root FS and the second is empty. When an upgrade is ready, the system downloads the update from the internet, writes it to the second partition, and reboots - if the reboot is successful and the system passes health checks, it marks partition 2 as the default. If something goes wrong, it reboots again back into the original partition. (Then when v3 comes out, v2 downloads and writes it to the first partition, etc)
I keep thinking “surely this must be a solved problem?”, but I can find very little information about it; and the few things I can find are proprietary cloud-based management systems, when I’d much rather have my image hard-coded to poll an update-feed-URL that I control myself...
[1]: https://buildroot.org/downloads/manual/manual.html#outside-b...
How does this work?!
Or using something like Signal, where the call is not only better than "HD voice", it's e2ee encrypted? There are other services that offer varying levels of encryption.
Does it really cost lots of money to call someone from one part of the EU to another?
As an American I resent how much I have to pay for cellular data (though things are certainly better than they used to be; I've now got ~4GB for slightly under $20/month) but the concept of having to pay extra charges for calling someone who is ~100 miles away is quite foreign/confusing, especially given the EU is, well....the EU?
Unlimited calling is virtually defacto here, as is free long distance calling. I can call someone 3,000 miles away and it doesn't cost me a dime.
Area codes are so irrelevant these days that nobody really bothers to switch phone numbers even when they move cross-country.
https://blog.wirelessmoves.com/2020/05/xmpp-voice-and-video-...
There's lots of things you can do with these and Freeswitch also works on a Pi2B.
You'll find some telco providers have just taken Asterisk or Freeswitch and recoded it enough to class it as their own, but you could run an entire phone company in a country on Asterisk/Freeswitch if the HW is powerful enough.
If you look at the Caller ID standards, the EU standard is based on the old dialup v.23 baud rate. https://en.wikipedia.org/wiki/Caller_ID#Operation https://en.wikipedia.org/wiki/ITU_V.23
So if you want to do some HW hacking, you could start with any old modem and turn it into your own SPA122, and once you have done that you could look at taking an ADSL router and turn it into a SPA122 of sorts. These are just devices with some hw capabilities but could do more.
Many countries block this, and even make it illegal for international calls. Both for security and financial reasons. Telecom companies around the world have an understanding with other on interconnection charges. Security reason should be obvious - it is easier to track people and collect metadata on foreign calls if everything happens through your network.
E.g. Many countries even block voice calls through Signal, Skype, WhatsApp etc.
Data costs vary a lot across the EU. I pay 70 dollars a month for unlimited data with unlimited speed, for example.
https://ec.europa.eu/commission/presscorner/detail/en/MEMO_1...
Data and voice may not cost more when roaming