[INFRA-230] Images for Raspi should be stored? Created: 01/Nov/18 Updated: 05/Apr/19 |
|
| Status: | Open |
| Project: | Software Development Infrastructure |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | yuki.moritani | Assignee: | yuki.moritani |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
At the teleconf. earlier this week, Jim pointed out we should store image files of Paspi somewhere (on Gthub?) for maintenance.
If we use Github, LFS might be recommended. |
| Comments |
| Comment by cloomis [ 01/Nov/18 ] |
|
Maybe. I do not think that any of those require any kernel drivers, just a basic OS and some tweaks for the union mounts, some udev stanzas, and a couple of user/group additions. In any case we need to save the prescription for the tweaks. ics_ansible/misc/debian-preseed might be a place to start? Perhaps we could make a single Raspian/whatever image, onto which we add one of the program products? Yes, we do need a spare plug-in SD card at the summit. |