-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implementation of operational system via SBD #9
Comments
Basic update to blank OS, looking at 4.9 installation medium and associated caveats and getting the provisioning mechanism up and running. 4.9 is likely a sensible move, there is an option on 5.10 but this doesn't appear as well founded as 4.9 and is more recent, though will offer longer term support so should be attempted if 4.9 works. |
Starting with 4.9
|
The image replicator processing should be used once the build is finished to flash the eMMC. |
Sent SBD message to test that the setup is still working:
Awaiting email |
Had to get the IMEI set up correctly, SBD now working. RUDICS also verified whilst I was at it, just to make sure the internet endpoint was still available to the ISU:
|
Debian wheezy (original) build as opposed to squeeze is required. The pyremotenode installation on wheezy fails due to the age of the SSL certificates on the system. However, squeeze requires substantial changes to the hardware interfacing for pyremotenode, #17, so the minimal viable installation is working on wheezy as well. |
Command running, producing configuration via the ansible setup at BAS for pyremotenode basic functionality:
|
A basic configuration for the LPM:
|
Two versions created: |
The text was updated successfully, but these errors were encountered: