Sort-of related to the memory requirements thread... Is there a particular reason why Java is applied to the miniroot after booting as a separate step? I know that Java isn't supposed to be applied if the machine has too little memory, but we seem to have reached the point where the minimum RAM for booting at all is greater than the threshold point... but has not, I think, exceeded the point where it can install Java *successfully*.
I noticed this when Jumpstarting b70 from inside a VMware instance. At 512M of RAM, it will effectively freeze when "Setting up Java". At 256M, it won't try to install Java... but it also won't boot in the first place. 768M is the value I've used to make it successfully pass the Java phase. Keep in mind that this is during a Jumpstart... completely non-graphical. If minimum_boot_ram > min_install_java, is there a reason why it wouldn't be present in the miniroot to begin with? It would seem that going through the trouble of pkgadd'ing it to an in-memory boot image spikes the memory needs significantly. Or, perhaps, during Jumpstart it could not be installed at all? Does anything actually use it? This message posted from opensolaris.org
