Comments (7)
I'm not quite sure what you mean. Could you clarify the advantage of zero padded binaries?
from bootimage.
I needed to play around with binary sizes a bit for bochs to load my kernel (https://github.com/64/solstice/blob/master/scripts/bochs.sh) so it might be better to support this inside bootimage if possible
from bootimage.
Currently bootimage generates a "just enough" disk size. Qemu treats it as a bootable disk and works as expected.
When we develop a file system, we need a place to read and write from. Currently, bootimage neither supports adding custom files to the bootimage other than the kernel, nor supports empty space.
Adding custom file support enables us to load them dynamically from our kernels.
Adding empty space (by padding zeros) enables us to have some space to write from kernel for files and other stuff as a persistent storage.
from bootimage.
I needed to play around with binary sizes a bit for bochs to load my kernel (https://github.com/64/solstice/blob/master/scripts/bochs.sh) so it might be better to support this inside bootimage if possible
I never really used bochs, but sounds reasonable.
from bootimage.
@vinaychandra Thanks for clarifying!
Adding custom file support enables us to load them dynamically from our kernels.
We had something like this before the rewrite, but it was never finished so we removed it again. I think this would need to be implemented in the bootloader
crate, since bootimage
does no image generation.
Adding empty space (by padding zeros) enables us to have some space to write from kernel for files and other stuff as a persistent storage.
So QEMU treats the loaded image as a hard disk, which allows a file system driver to write to the image file?
from bootimage.
I think this would need to be implemented in the bootloader crate
I don't know which crate should be implemented where but my point would be to not autoload these extra files (like we do for kernel) but leave them on the bin file so that we can load them dynamically as required.
So QEMU treats the loaded image as a hard disk, which allows a file system driver to write to the image file?
Yes, that is my understanding. See Image types
from bootimage.
I don't know which crate should be implemented where but my point would be to not autoload these extra files (like we do for kernel) but leave them on the bin file so that we can load them dynamically as required.
Sounds reasonable. I think it could be implemented by putting it into a separate ELF section that is not loaded. We could pass the file offset in the boot info to tell the kernel the disk location of the file.
Yes, that is my understanding. See Image types
Interesting!
Note that I'm very busy for the next four weeks, so I won't have time to implement it.
from bootimage.
Related Issues (20)
- Bootimage command claims it can report version, but doesn't. HOT 1
- debug sections stripped HOT 3
- Cannot run tests on CLion HOT 2
- Fails to link with `rust-lld` with an out of range error in latest Rust Nightly HOT 3
- Failing to find bootloader dependency when it's conditionally included
- Doesn't work with newer versions of the bootloader crate HOT 1
- Failing to build HOT 1
- Failed to run example-kernels HOT 3
- While compiling dependencies, I get the error of missing std HOT 1
- Trying to install bootimage yields errors HOT 6
- Support for aarch64 and riscv HOT 1
- How to create .iso? HOT 2
- Kernel command line flags
- linking with `rust-lld` failed: exit status: 1 HOT 4
- Can't Install bootimage with cargo install bootimage HOT 3
- Can't install bootimage HOT 10
- Quiet in Cargo.toml HOT 1
- Add to AUR HOT 1
- Error: Failed to find kernel binary in cargo metadata output HOT 1
- cargo test --quiet passes invalid option --quiet to qemu HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bootimage.