3 ms·
One limitation of this system as it currently exists seems to be that you need a working i386 NetBSD host to built the filesystem. It might not be worth the eff
by yjftsjthsd-h 6y ago
One limitation of this system as it currently exists seems to be that you need a working i386 NetBSD host to built the filesystem. It might not be worth the effort once pkgin gets involved, but in theory I would expect this to be perfectly possibly to get around; after all, NetBSD's own build.sh is perfectly happy to build a full system image for ex. i386 NetBSD from source on ex. an amd64 Linux host. Or, if you didn't want to deal with cross-compiling, perhaps it would make things easier to build a Fakecracker VM that itself builds root filesystems, analogously to building docker images from a container using dind.
- pwdisswordfish2 6y ago"One limitation of this system as it currently exists seems to be that you need a working i386 NetBSD host to build the filesystem." One does not need a NetBSD host. This is not the most time/space efficient method I can think of, but it's the easiest to explain... On Linux host: 1. Download for x in gnusrc sharesrc syssrc src;do ftp ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-9.0/source/sets/$x.tgz&& tar xzf $x -C /;done 2. Compile toolchain mkdir /usr/obj PATH=/bin:/sbin:/usr/bin:/usr/sbin ./build.sh -m i386 tools 3. Make filesystem Using makefs instead of vnconfig + mount + newfs has the advantage that makefs is part of the toolchain while vnconfig is not makefs root.img fakecracker
- anthk 6y agoWouldn't that crap out /usr/include?
- deleted 6y ago[deleted]
- yjftsjthsd-h 6y agoNope; all the netbsd source tarballs extract to [/]usr/src
- yjftsjthsd-h 6y agoYep, with a tiny bit of fiddling this does indeed work:) Thanks!