Peter Tribble wrote: > On Thu, 2006-05-04 at 20:58, Dave Miner wrote: >>> I noticed something new during a network (upgrade) install from b37 to b38. >>> The install showed "wait for Java environment initialization" (don't >>> remember the exact words), then waited for (felt like) 2 minutes >>> before moved on. >>> >> Yes, it takes a long time, and it's working as expected. What's >> happening is that it's installing the JRE packages into the miniroot >> environment since some of the user interfaces are implemented in Java >> and therefore need the JRE to execute. This delay has been there for a >> quite a while, it's just that as of build 38 we're printing a message >> that something's happening - many people thought that it was just hung >> after configuring devices. >> >> Why do we do it this way? It has to do with space issues on the first >> CD; storing the compressed package and adding it was a convenient way to >> free up space when the CD becomes too full. We'll need to do more >> extensive redesign to eliminate it, but for now this keeps the train on >> the track. > > Also in build 38 I notice that X is simply unpacked > from bzipped cpio files in Solaris_11/Tools/miniroot_extra > > (Was this new in build 38, or is it just the > message that's appeared again?) >
It's new. Bought us 70 MB or so on CD1, as we were getting over the manufacturing size limit on SPARC. > Using gzip rather than bzip, as noted before, could > significantly reduce the delay at this part of the boot > sequence. > Noted, but the miniroot doesn't have gzip right now, so it's probably just going to stay as-is. My inclination is that we're going to just leave that bzip2/gzip issue alone unless we end up with a need to do more serious surgery for the S10 updates, and the Caiman projects that we'll be doing to redesign the installer will address it instead. Dave
