Glenn Glazer wrote: > Hi, Darren. > > I have a lot of SVR4 experience, but next to no IPS experience, so take > the following in that context. > > It seems to me that what you are proposing has two important differences > from the SVR4 experience: > > 1) Semanatic: I can control the contents of my system by controlling > when I do installs. I may not (for whatever reason) want the latest and > greatest providers. In this use case, I can reboot my system and > stop/start/restart services arbitrarily many times without changing my > system configuration. I therefore suggest that if you provide a means > to automagically check for new things on service start, you provide a > means for disabling this feature both always and for a given startup. > Otherwise, people may feel that they have been blindsighted by what they > will undoubtably call a "side effect" of service start. >
You mean you want to be able to install new packages, but not have them used or configured? > 2) Performance: outside of test labs, pkg installs happen much less > frequently that server restarts/refreshes. If your post-install scripts > have to phone home to download new functionality, this could very well > be a user-visible delay in service start-up time. Most critically, this > will happen during every restart/refresh, rather than once per system > lifetime and the penalty will be paid whether there is anything to > download or not. During boot, this may not be so obvious, but manual > restarts have the potential to suffer greatly. Why would services "phone home" to download new functionality? - Bart -- Bart Smaalders Solaris Kernel Performance barts at cyber.eng.sun.com http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird."
