Project

General

Profile

Actions

Bug #918

closed

pibox-version should update on each boot

Added by Hammel about 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Immediate
Assignee:
Category:
04 - Root File System
Target version:
Start date:
21 Nov 2022
Due date:
% Done:

100%

Estimated time:
Severity:
01 - Critical

Description

In order to support moving an SD card between devices, the pibox-version file should update it's last line to show that hardware it's currently running on, if different than what is already in the file.

Actions #1

Updated by Hammel over 1 year ago

  • Priority changed from High to Immediate
Actions #2

Updated by Hammel over 1 year ago

  • Severity changed from 03 - Medium to 01 - Critical
Actions #3

Updated by Hammel over 1 year ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 20

This should change so that each line has an identifier, as in:

VERSION: PiBox 2.0
HW: rpi2
BUILD: Fri Aug  4 20:58:17 UTC 2023
MODEL: Raspberry Pi 3 Model B Rev 1.2

This way we can avoid changes by line number.

I'm not sure what else uses this. The following command from just above all my sandboxes didn't find it referenced anywhere outside of the pibox build itself.

find pi* ironman appmgr launcher lcdshow libpibox metabuild musicfe pmsui pnc videofe -type f -exec grep -l "pibox-version" {} \;

So for now just make sure the dev system build skeleton handles these changes.

$ cdx
$ find * -type f -exec grep -l "pibox-version" {} \;
configs/buildroot.mk
src/buildroot/skeleton/etc/init.d/firstboot
Actions #4

Updated by Hammel over 1 year ago

  • % Done changed from 20 to 50

It should be noted that this change isn't really necessary unless we change the config.txt too, since RPi3 optimizations exist there that prevent an RPi3 SD from being moved to an RPi2.

If you remove those optimizations then the SD will boot.

Actions #5

Updated by Hammel over 1 year ago

  • Status changed from In Progress to Closed
  • % Done changed from 50 to 100

Changes tested on hardware (both with and without RPi3 optimizations) and they are working.
Changes committed and pushed.

Closing issue.

Actions

Also available in: Atom PDF