Sarah Jelinek wrote: > > >> Ethan Quach wrote: >>> 5.1 >>> >>> Why do we need to set dummy values for timezone, timeserver, and locale? >>> This indicates to me that the sysidtools are going to run before the >>> dwarf GUI runs. Why? The individual sysidtools don't run outside of >>> the GUI. The orchestrator is going to dictate which sysidtools run and >>> when. So we could: > > >>> a) fully populate a sysidcfg with the data gathered from the >>> GUI and the data from the default sysidcfg file, and then run >>> all the sysidtools to configure the apporiate files. >>> >>> b) not run the sysidtools at all, and create new functions in >>> the orchestrator to configure the system with the data. >>> >>> c) a mixture of both. > > > My thoughts on this were that we have not disabled the sysidtools fully > in any release of the installer to date. So, doing this by modifying the > install scripts to not run the sysidtools might be problematic.
But the install scripts are already *not* running the sysidtools for GUI mode in the existing installer (minus the keyboard and locale items). The GUI application itself, manually execs the sysidtools after having generated a complete sysidcfg file and placing it into /etc/sysidcfg. > We are > not running any of the existing sysidtool functionality with Dwarf. The > thought was that we would go through the same sequence with Dwarf as we > do today with the installer, This would be (a) above. > but mute the UI screens by having a > sysidcfg file for all configuration attributes. This is the part thats not needed since they don't run before the GUI. > > I have no issue with not running the sysidtools, but am concerned about > what this type of change means to Dwarf and thought it would be more > straightforward to create the dummy sysidcfg file. > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://opensolaris.org/mailman/listinfo/caiman-discuss
