proc: add basic initrd support #8

Closed
opened 2025-03-19 07:41:03 +00:00 by alnyan · 1 comment
Owner
  • The kernel should support an abstracted in-memory read-write system.
  • Support an image format to be used as a source of this filesystem.
    The filesystem must be minimal enough to be included in a microkernel. One of:
    • tar
    • cpio
    • Roll your own
  • (Optionally) support copy-on-write on non-compressed data.
  • (Optionally) support zstd/zlib-compressed initrd. Not really a requirement, but would be very nice, because some platform have quite strict memory layout requirements on boot
- [ ] The kernel should support an abstracted in-memory read-write system. - [ ] Support an image format to be used as a source of this filesystem. The filesystem must be minimal enough to be included in a microkernel. One of: - [ ] tar - [ ] cpio - [ ] Roll your own - [ ] (Optionally) support copy-on-write on non-compressed data. - [ ] (Optionally) support zstd/zlib-compressed initrd. Not really a requirement, but would be very nice, because some platform have quite strict memory layout requirements on boot
alnyan added the
scope
kernel
label 2025-03-19 07:41:03 +00:00
alnyan added this to the Kernel project 2025-03-19 07:41:03 +00:00
alnyan moved this to In Progress in Kernel on 2025-03-26 16:31:35 +00:00
alnyan moved this to Done in Kernel on 2025-03-26 16:31:38 +00:00
Author
Owner

Won't do: kernel will load an init program from a binary blob embedded inside the kernel itself. The init will then handle the rest.

Won't do: kernel will load an `init` program from a binary blob embedded inside the kernel itself. The `init` will then handle the rest.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: alnyan/zing#8