Skip to content
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

Improvements #232

Open
3 tasks
gjrtimmer opened this issue Jan 26, 2025 · 4 comments
Open
3 tasks

Improvements #232

gjrtimmer opened this issue Jan 26, 2025 · 4 comments

Comments

@gjrtimmer
Copy link

gjrtimmer commented Jan 26, 2025

This issue is to track several improvements.

The improvements are to rename the current SDCard image to *-sdc.img, indicating that the image can be installed from the SDCard.

This PR will depend on #230 for easy development.

Add a new SDCard image named *-sdcx.img, indicating an image that can run off the SDCard.
Add a package manager, and doing so also allows for installing Python3 for those who need Python3 for Ansible or other purposes.

I intend to create a PR soon with the first changes to the bmc-firmware build process.

@svenrademakers
Copy link
Collaborator

Hi @gjrtimmer perhaps i can help setting up an Community Edition sd card build here on github? i think this feature is long time due..

@gjrtimmer
Copy link
Author

gjrtimmer commented Jan 28, 2025

THat would be a great addition, next to the official builds, so we are taking a ce edition right, we would still keep the images like tpu, sdc and sdcx

@gjrtimmer
Copy link
Author

Regarding the CE edition, I also mentioned this just now in PR #160 if we add only the package manager and allow the install of package on the SDCard as the install location then users have enough storage. This way we do not have to include Python at all.

PR #160 should be placed On Hold while this PR is being worked on.

@gjrtimmer
Copy link
Author

After some additional thinking I think that a community edition would be a great asset, however on priority it would be great to do have automated firmware testing first to accelerate the development. I will also go through all the issues, comment them and see if some can be closed and try to determine the work required for it. Furthermore I think it would be great to create some Projects in the Turing Machine organization to handle releases and the issue tracking across multiple repositories. But this is just my opinion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants