- maintboot runs commands outside of the current OS,
with exclusive access to the system and hardware.
This can be useful to run maintenance tasks, like repartitioning, in a controlled environment.
Maintboot builds an appliance on the fly from a list of packages (using supermin). It then loads the appliance with kexec, bypassing the bios, and runs the maintenance script in that new context.
See github.com/g2p/maintboot for installation and usage instructions.
Metadata
Release files for maintboot 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| maintboot-0.1.0.tar.gz | 2.1 kB | Without provenance | Details |
Release files / maintboot-0.1.0.tar.gz
| Download URL | maintboot-0.1.0.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4a1f09ab8e6e7222eebd9ade69a32e4d76d3099a36fcdbc3fc0dcbc29e1c2d51
|
|
BLAKE2b-256 checksum How to use checksums |
52172c74c2951d5cc0d9a4f86c86eb2e0f902435889afa636e0f877fff68f1f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for maintboot 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.