Casper.Dik at Sun.COM wrote: >> No, at this time those do not exist. That's deliberate. In many >> (most) cases, Jumpstart finish scripts exist to work around gaps in >> the feature set or implementation. We want to understand what the >> real requirements are and build those into the product. > > Don't try that; after reading a large part of the AI opensolaris > autoinstallation documentation I can only conclude that people have > read the jumpstart installation but they have no idea how jumpstart > is used in practice. > > First of all, everyone who uses jumpstart in a large environment > doesn't actually need to do anything when a new client is installed. > > Secondly, in a past live, I used the begin/finish script to customize > *everything* in a system.
Seconded. E.g., at Solaris System Test we perform several hundreds of different JumpStart installations (and upgrades) every week on a lab of ~400 machines. Install begin/finish scripts give us the flexibility to implement any customization we need, often being creative to work around bugs in various development builds which actually allows us to install the system and don't just pronounce the build dead in the water and drop testing. This functionality is absolutely essential for us. Lack of begin/finish script functionality would have a huge impact on productivity of many teams in the company, forcing them to implement various home brew workarounds since their requirements are unlikely to change. regards, -- Lubomir Sedlacik /salo/ // Software Engineer, Solaris System Test
