On Thursday, 09.04.2015 at 13:28, Justin Cormack wrote: > On 9 April 2015 at 13:26, Martin Lucina <[email protected]> wrote: > > > >> > 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. > > Best not to - Linux switched from filesystem based initrd to initramfs > which is a compressed cpio archive, so you dont need any filesystem > drivers. Hence why I was thinking about tar - you can just untar to > the rumpfs and you dont need to configure block or fs drivers on your > kernel at all.
Good point. FWIW, a BSD-licensed licensed FUSE implementation of SquashFS does exist: https://github.com/vasi/squashfuse -mato
