Hi all, another thing I want to ask about as I'm working on smaller
platforms. I started running into issues with the size of the kernel,
because Rust binaries are (famously) quite large.
Now, I noticed that the `./tools/ew.py` command creates hdisk.img from
uspace/dist, which is then mounted by HelenOS. This sounds like the
perfect place to place my programs, since it doesn't need to be
extracted into the ramdisk, and thus the storage should not be limited,
am I right?
But I noticed multiple issues with the hdisk:
- it seems to be built from `uspace/dist`, but this folder is available
in HelenOS even when I remove hdisk.img from the qemu command. So the
folder is clearly included even in image.iso and later extracted into
ramdisk, so this external volume is probably completely unnecessary?
- the label of the FAT volume is not parsed correctly somewhere and is
read as empty, and thus the disk is not auto-mounted. If I make a
partition with mkext4.py, it is automounted as `/vol/HelenOS-rd`
- the file helena.tpf is required for the UI, so it probably cannot be
only in this disk which can potentially be omitted
So I was thinking if the `uspace/dist` folder should be split. I imagine
this folder would contain anything that HelenOS strictly requires, and
everything else, like the web, bithenge tests or python examples, would
go to some new `$helenos_source/uspace/mountdata` folder, from which the
hdisk.img would be built instead. And if we fix the labels (or make this
an ext4 filesystem), we could have it automounted as `/vol/mountdata`.
I'm curious what you think, but maybe noone else ever ran into
kernel-too-big issues, so it's not a pressing issue for you, which I'd
understand.
Best,
mv
_______________________________________________
HelenOS-devel mailing list
HelenOS-devel@lists.modry.cz
http://lists.modry.cz/listinfo/helenos-devel
