OK. Thanks guys. >From playing with it and looking at the script, I had managed to figure out that it was possible, but I just didn't know the full impact.
So, I guess if I want to customize the installer's interaction with the OS, the simplest answer is that it's all-or-nothing. I may try and poke around when I feel like digging deeper. Or maybe write a Sun PKG to wrap around it ... hmmmm. In any case, one thing that came up was the following: when installing an RPM as non-root, and the RPM contains files specified as root owned or other ownership/perms (e.g. 'screen' has one root-owned binary, and I think it should be suid), is there any way to get rpm to spit out some kind of warning that it failed to change perms? I tried -vv with -Uh but it didn't give me anything useful (unless I missed it). After installation, "rpm --verify" is a start, but something more informative and during install would be nice. Thanks, -- Vinod On Thu, 12 Dec 2002, Michael Schloh von Bennewitz wrote: > Ralf cleared this up I think. In short, as long as you: > > o Don't use the crontab periodic sections > o Don't use packages that rely on the '-r' user/group > o Don't use an OpenPKG installed shell for OS functions like chpass(1) > o Don't expect your enabled OpenPKG daemons to autostart on booting the OS > > then you should be okay in building, installing, and using OpenPKG with no > special privileges. ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
