This brings up a question for me: Is there currently a way to instruct the bootstrap process to skip certain tasks done outside the $root of the openpkg installation?
At the moment, it seems the answer is "no", and that it's an all-or-nothing affair by installing as non-root (i.e. rc hooks, /etc/shells, user acct creation, etc. are skipped if you're not root). However, as root it would be nice to pass command line args to the bootstrap script to tell it to "skip /etc/shells", "skip crontab entries", etc. I've gotten around this under Solaris by writing a Sun package wrapper that runs the bootstrap as non-root, but creates just the external pieces I want. -- Vinod On Thu, Feb 13, 2003 at 09:59:04PM +0100, [EMAIL PROTECTED] wrote: ... >It is a good idea, though I also view growing of the bootstrap as a hefty >disadvantage. That should be kept as simple as possible, and might outweigh >the easier macro usage you mentioned. In any case, I'll leave the decision >up to Ralf the bootstrap architect. Currently the bootstrap causes problems when used on a network where the openpkg users are on an LDAP server since there's nothing in the /etc/... files on the local system. Running the binary bootstrap script then inserts the files with the next available user and group IDs. The extra entries then need to be removed from the files, and the permissions for the new instance fixed using ``rpm --setugids openpkg'' which is a bit of a PITA. Bill -- ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List [EMAIL PROTECTED]
