On Fri, Dec 06, 2002, Vinod Kutty wrote: > As I play with openpkg towards the goal of deploying it on production > systems, one issue that's come up is what the bootstrap touches outside > the openpkg root dir. I built the > openpkg-1.1.1-1.1.1.sparc64-solaris2.8-oo.sh and corresponding .rpm from > source. > > I noticed that things like /etc/shells, user accounts, /etc/rc?.d > symlinks, etc. are handled inside this script. > > It also appears that as long as I run as non-root, none of those actions > will be performed. However, if I want to customize the install (e.g. I > want only the /etc/rc?.d stuff), what's the best strategy? > > Is there a list of what root privs are required for when running the above > .sh script? Or is my best bet to read through the script? Is there > anything different in terms of file permissions that might result from not > running as root? (I'm using an acct 'opkg' which I specified in the > --user= argument when running openpkg*src.sh). > Hello Vinod,
Please excuse the delay. I'm only responding now because its been almost a week since your post. I'm not the expert who can guide you through dealing with the bootstrap scripts. Your wish is a rather advanced one, in that you would first have to rewrite parts of the very complex bootstrap process. Theoretically, after changing the passwd entry bootstrap code you could give a already-existing user name at bootstrap time to get rid of the change to /etc/passwd. Also theoretically, you could simply remove the crontab changing code if your users promise to never use the dependent rc.<package> sections. This is just a drop in the bucket of considerations and assumptions you will have to make though, and I believe you will find yourself dealing with a lot of side effects from making these code changes yourself. I am personally not that brave. By the way, you don't have to build the bootstrap script from source as root. Any user can do that, but to install it you need root priveleges of course. From the handbook at http://www.openpkg.org/doc/handbook/openpkg.html The bootstrap script also establishes a sort of context or environment in which OpenPKG runs. Specifically, initial configuration involves the operating system and some of its more common control facilities. The three main points of contact at which OpenPKG interacts with the operating system are the file system (1) with its owner and group attributes, the root cronjob (2) typically modified at /etc/crontab or crontab -e, and the init script (3) usually found at /etc/init.d. I hope that helps, and good luck in your endeaver. Regards, Michael -- [EMAIL PROTECTED] Development Team, Application Services Cable & Wireless Deutschland GmbH
msg00229/pgp00000.pgp
Description: PGP signature
