> Should the default for makefs not be changed, rather than requiring an > argument?
I'm not fond of that idea, but why not, as long as it gets documented. > 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. 100 was a starting point to start the discussion. Using a larger value will probably cause more miniroot geometries to be updated, but that's a once-in-10-years kind of change anyway. > 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. Indeed. > 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? Well it would be interesting to hear from people using makefs for other purposes. Are there any?
