Lukas Oboril wrote: > Hi Michael > > On 1/23/08, *michael schuster* <Michael.Schuster at sun.com > <mailto:Michael.Schuster at sun.com>> wrote: > > Hi Lukas et al, [...] > > No changes were made to the system. > > Tue Jan 22 21:10:39 PST 2008: *** command output ends *** > > Tue Jan 22 21:10:39 PST 2008: KBE setup FAILED > > it's fairly easy to manually do the installation, but it's not quite as > trivial to find out if other packages are missing.
> please post your /etc/user_attr. This could be a problem, I know it's > sound crazy, but .... Here's some of what's gone on so far, and the conclusion that brings me to: On the machine I tested this on initially (my x86 laptop), I managed to re-run kbe-install without an error after having shut it down, carted it around half the Bay Area, restarted it, etc. I also added 'set -x' to the beginning of install_pkgs() and 'set +x' to the end. I then run it *again* with those modifications backed out. At that time, I assumed that having completely logged out and back in did the trick, ie that profile changes are only relevant when you do a proper login. A few messages on this list seem to support this thought (http://www.opensolaris.org/jive/thread.jspa?threadID=50168&tstart=0). Today, I tried the same experiment on a Sparc machine with Nevada build 81. The only profile I have set is "Software Installation"; the profile definitely is active (more see below), but I repeatedly get this error: > Installing package KBEenv > > The following files are already installed on the system and are being > used by another package: > * /opt/kdebld <attribute change only> > > * - conflict with a file which does not belong to any package. > > Installation of <KBEenv> was suspended (administration). > No changes were made to the system. > KBE setup FAILED note: in between runs of kbe-install, I always ran kbe-remove. no re-login has helped so far. I also noted something else: > for a test I did the following: > 1) $ profiles > Software Installation > Basic Solaris User > All > > 2) in a different terminal, as root, change the profiles entry in > /etc/user_attr from > profiles=Software Installation; > to > profiles=Software Installation,IP Filter Management; > > 3) in the initial terminal, run 'profiles' again: > > $ profiles > Software Installation > IP Filter Management > Basic Solaris User > All > > (this is without re-login or anything). > > now, the question: does this mean that a profile is active the moment > it's in user_attr, ie, that I don't need to log in after the profile has > been added, to make it active for a given shell? I sent this to the person who helped me understand the whole profile stuff last week, he told me: > Yes. Profiles (authorizations, ....) all take place immediately. > (Except for a few things that are process attributes that are > only inherited from the login shell: defaultpriv, and limitpriv.) so ... I think I need to revisit some of my conclusions, or, in short, back to square 1. Michael -- Michael Schuster Recursion, n.: see 'Recursion'
