> tl;dr: by removing unneeded MAKEDEV entries, some platforms will end up > with makefs creating a file system with 256 inodes, of which about 250 > are used, and installation will misbehave in interesting ways due to the > lack of free inodes.
Should the default for makefs not be changed, rather than requiring an argument? 100 seem extremely small. Imagine a person installing a machine with 5 drives. Our installer lets people iterate over all their drives. MAKEDEV will create 32 inodes per drive. For 5 drives, that 160 inodes, plus the 10 or so /tmp files created during build... it is way more than the 100 you propose as being satisfactory. Even a person with two drives will use 64 inodes, leaving 36 for the script, but if someone had 3 drives it will blow up. I guess this went quietly off the rails when we switched to using makefs. This "minimalism" decision it makes is not really compatible with our wish to make disk device nodes on the fly. So should it be -f 200, or 250, and/or should the minimum default built-in be changed? Basically 100% of makefs use is for our install media, is it not right to change the default?
