On Sun, May 7, 2023 at 2:35 AM Samuel Thibault <samuel.thiba...@gnu.org> wrote:
> Sergey Bugaev, le mar. 02 mai 2023 17:10:17 +0300, a ecrit:
> > As for the best way to implement this... I have always thought gnumach
> > should have a bootscript directive to expose a multiboot module as a
> > memobj. Then there would be a task, /hurd/ramdisk, that would expose
> > it over the device (and possibly I/O) protocols:
> >
> > module /boot/initrd.img $(initrd-image=vm-object-create)
>
> So to release the content you would just close the port? That looks
> interesting to me indeed.
>
> But do we really need this intermediate translator? libstore already
> has a memobj backend, so it would probably be a matter of passing
> memobj:$(initrd-image=vm-object-create)
Indeed! Wouldn't that be neat? :)
But not memobj:$(initrd-image=vm-object-create); rather like this:
module /boot/initrd.img $(initrd-image=vm-object-create)
module /hurd/ext2fs.static ext2fs other-args -T memobj ${initrd-image}
$(task-create) $(task-resume)
Sergey
