On Thursday, 09.04.2015 at 13:12, Justin Cormack wrote: > On 9 April 2015 at 13:01, Martin Lucina <[email protected]> wrote: > > On Wednesday, 01.04.2015 at 10:26, Justin Cormack wrote: > >> 3. Adding a file system to the image. I was looking that this before, > >> with my lightweight libuntar (25k) to untar an in memory image to the > >> root file system. The nice way to do this is to allow the user to > >> append the archive to the binary, then use the elf size to find the > >> offset, so you don't need to patch the file. This has the advantage of > >> working anywhere, and can also be used for data not just > >> configuration. > > > > Does NetBSD have any equivalent of SquashFS? This is used heavily in the > > embedded world on Linux, comes with good toolsets, supports compression and > > developers understand it. > > > > I'd prefer to re-use a known good solution rather than reinventing our own. > > No.
:-( > > Regarding appending the fs to the resulting binary, you'd need to do more > > than just that. Haven't checked, but afaik eg. the Xen loader will not load > > the extra parts without them being part of the ELF header. > > > > Hmm, Xen knows how to supply an initrd/initramfs, as do most other > bootloaders; doesnt make sense in userspace though. That would be the way to go then. For userspace, it should just be a matter of implementing the same functionality in the franken setup code. The question remains what to put in the initrd; I've looked through the filesystems in -current and don't see any obvious choices. -mato
