I'm curious what you might be encountering, because I have installed the latest versions of Raspbian on my oldest RPi devices and I haven't experienced any issues.
Supported Python Versions can be found here: enter link description here
The answer is: it depends.
In general: before you move, make a backup. In that way you do not loose any data.
The rest depends a bit on how different the set-up will be in the new location and what the server actually does. If it is just an in-house server, and the IP plan is the same and the SSID/PSK are the same, it should just work. If anything changes,...
The apt-get update command requires to write some system directories hence you have to run it as a root user. Or, you can run it by other users (such as pi) with sudo before the command.
sudo apt-get update
In addition, if you still get this E: Unable to lock directory /var/lib/apt/lists/ error, you can remove the apt lock file and see if that ...
Running different versions of python is not an issue of the hardware, means version of a Raspberry Pi. It is an issue of the version of the Raspbian distribution. A specific python version is integrated into the distribution with its shared libraries and tested that it runs there without dependency and version problems. Raspbian Stretch comes with python 3.5,...
I fixed the issue by having the computer that I was trying to ping the pi with plug into the router directly instead of having it plugged into a network switch that was plugged into the router.
As for the device being stuck in DORMANT mode, I fixed that using the following command: ip link set wlan0 mode default
Because you started with a fresh flashed Raspbian Buster image so just enable WiFi as described at Wireless connectivity from the Raspberry Pi Foundation. If this doesn't work then you should have a look at the hardware of your RasPi or at the device from which you try to connect.
My solution -- create a shell script to easily switch between AdHoc mode and internet connected mode
This does not configure OLSRd, it just creates an AdHoc network that you can connect to.
Shell script just copies the locally stored config files over to the location of the active config files
sudo cp /home/pi/adhoc_config/interfaces /etc/network/
The debug messages you are asking about are on a stage where only the boot loader is running but not even the kernel is loaded. So there is no chance to have logging to a file because there is nothing what managed it. But you can enable the boot loader to output messages to the serial debug console. For this you need an USB to TTL (RS232) serial cable. An ...
It is known that the Raspberry Pi 3 may have problems with some devices to boot. But you can use a special bootcode.bin-only boot mode. This will use a SD Card containing only the file bootcode.bin. Once bootcode.bin is loaded from the SD card, the Pi continues booting using USB host mode. How to setup this you can look at Raspberry Pi boot modes.
You have eth0 and wlan0 both connected to the same router and both connections are working as you can see if you ping its ip addresses. But the kernel can only use one connection at a time if you use a stateful tcp connection. This is the case with ssh. It starts a password enabled authenticated session on one connection to its destination ip address, e.g. ...