Dave Miner wrote: > Most of the distribution construction is done using the slim_install > cluster, but there are certain packages which must be installed > separately and in a defined order (SUNWcs, SUNWcsd) because of the way > actions are ordered. > > In the case of, say, automated installation using a user-defined package > list, we might also opt for the individual invocations for the same > reason, since we can't tell a priori whether the listed packages would > be affected by similar problems.
I anticipate the creation of a simple base package that contains everything needed to install any other packages successfully. In particular, that list is right now something like this: /etc/passwd /etc/group /etc/ft/ftpusers /etc/name_to_major /etc/driver_aliases /tmp /usr Since ON still delivers partially populated editable files, those files need to be in place before actions that create entries in those files are executed. Since user and group actions should be executed ahead of file creates/updates (to permit delivery of a package that contains a new user and files owned by that user), a pkg install of any packages that contain user or group actions must be preceded by a pkg install that creates the skeleton group/passws/ftpuser files. We may in the future resolve this by making image-create of a full image install the needed package automatically. - Bart -- Bart Smaalders Solaris Kernel Performance [EMAIL PROTECTED] http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird." _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
