The CD now boots directly from the ISO 9660 filesystem instead of using
MBR partitioning with Minix file systems. This saves some space on the
CD and reduces memory requirements by some unknown amount as the root
ramdisk is completely eliminated.
The setup is also modified to be more NetBSD-like (unpacking sets
tarballs instead of blindly copying the CD contents). This allows
massive space savings because only the base system used for installation
is stored uncompressed and more modularity (to be exploited at a later
time). The sets themselves are to be refined, but are enough for now.
Those two steps are melded together because copying the CD contents with
isofs as the root filesystem results in some failed tests in
minix-posix, probably due to some obscure corner-case bugs in isofs.
Having a read-only root filesystem outputs some error messages because
it isn't properly supported. Ramdisks on /var and /tmp are used to
mitigate this, but the clean solution would involve union mounts,
something Minix 3 doesn't support for the time being.
Change-Id: Ib4700d9f10c5b4b297e0994b5338847951fc79b4
- Fix for possible unset uid/gid in toproto
- Fix for default mtree style
- Update libelf
- Importing libexecinfo
- Resynchronize GCC, mpc, gmp, mpfr
- build.sh: Replace params with show-params.
This has been done as the make target has been renamed in the same
way, while a new target named params has been added. This new
target generates a file containing all the parameters, instead of
printing it on the console.
- Update test48 with new etc/services (Fix by Ben Gras <ben@minix3.org)
get getservbyport() out of the inner loop
Change-Id: Ie6ad5226fa2621ff9f0dee8782ea48f9443d2091
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
