Hi Matěj! On Mon, 21 Apr 2025 at 20:48, Matěj Volf <hele...@mvolfik.com> wrote: > > 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?
Yeah, that's the intent I think. > > But I noticed multiple issues with the hdisk: > > [...] > > 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. > Yeah, I think you are mostly right. Ideally, the ramdisk image should only contain the drivers and servers needed to start loading more stuff from the HDD itself (or CD-ROM, depending on setup). As with many other things, this is something we all know should happen, but nobody took it upon themselves to fix the situation yet. This is also the reason why we have the "only build essential binaries" config option, and why it's the default in some configurations. And the reason tools/ew.py has the `-bigmem` option (it's real easy to hit the default ceiling with debug info included). This ticket is related btw: https://www.helenos.org/ticket/869 Since ideally we want to replace the initial ramdisk with regular persistent filesystem. Though I don't really agree with the idea of "global root". IMO that would be going backwards. -- jzr _______________________________________________ HelenOS-devel mailing list HelenOS-devel@lists.modry.cz http://lists.modry.cz/listinfo/helenos-devel
