Solaris Registration Wizard

[gsgatlin]

Hi. Is there any way to get rid of the Solaris
Registration Wizard pop up when you first log in?

I notice these files / dirs are involved:

/usr/lib/breg
/usr/lib/patch/swupdate.jar
/usr/lib/patch /swupna.jar

I am new to Solaris but I've worked with Red Hat Linux a
lot. But I don't know much about solaris style packages.
Is there a way to tell what files go with what packages?
I'd like to do something like a

rpm -qf /usr/lib/patch/swupna.jar

But I don't know the Solaris equivilent. The idea
being that I could use /usr/sbin/pkgrm to remove the
packages resposible for this software poping up
for each user on the system.

Any ideas about how to disable all the pop ups? We want
to do this for students logging in through the GUI on
lab machines since all the package updates will be
handled with command line tools.

As a last resort I thought of doing something like:

\rm -rf /usr/lib/breg > /dev/null 2>&1
\rm -rf /usr/lib/patch/swupdate.jar > /dev/null 2>&1
\rm -rf /usr/lib/patch/swupna.jar > /dev/null 2>&1

But that might break other things?

 

[gsgatlin]

Ok. I ended up doing a:
yes | /usr/sbin/pkgrm SUNWupdatemgru SUNWupdatemgrr SUNWbrg

which seems to solve the issue...

Is this bad? Will this break other stuff besides the Solaris Registration Wizard?

 

[GunnarD]

Disable the registration from coming up when you log-in (without registering).

touch ~userid/.solregis/.disable

 

[gsgatlin]

What if you have thousands of accounts managed by kerberos?
Surely there is some way other than touching a file
in everyone's $home dir?

 

[KenCunningham]

Could you not just write a script to do it - seems like a one-off requirement?

 

[gsgatlin]

If I have to do something like that, the only way I can get away with it is to create it durring some login script.
I am looking under

/etc/X11/gdm/

but its all a mystery to me. I will need to create this
~userid/.solregis/.disable
before /usr/lib/patch/swupdate.jar
and /usr/lib/patch/swupna.jar get run automagically.
(Can't figure out what is starting them in a session, I can only tell its them because of the "ps" command.)

So where can I add the commands to create the .solregis
dir if it doesn't exist in a user's home, then also
touch the .disable file? I would only want to do this for
a user's Xsession, not any login like if they ssh'ed into
a box.

Many thanks for any ideas...
(I don't have access to the cell where user homedir's live,
plus this also needs to happen when "root" logs in through gdm and his home is on the local box.)

 

[coffeysm]

What version of Solaris are you using?

 

[gsgatlin]

uname -a gives me:

SunOS sol10-test3.eos.ncsu.edu 5.10 Generic_118833-24 sun4u sparc SUNW

Its Solaris 10 and the jumpstart is set up with
u2 (I think that means update 2)

 

[gsgatlin]

Ok. Removing those three packages didn't work. It gave me errors on first boot post install.

Loading smf(5) service descriptions: 132/141Feb 7 13:43:34 svc.startd[7]:svc:/system/basicreg:default: Method "/usr/sbin/sconadm register -c -m autoreg" failed with exit status 1.

Many more errors follow.

Also, creating:

/root/.solregis/.disable

did *NOT* work for the root account. The monstrous java app still loads:

/usr/bin/java -jar /usr/lib/patch/swupna.jar -wait

How can I do away with this starting up post install?

Does anyone know? Mucho thanks for any ideas....

 

[coffeysm]

Not sure how Solaris 10 handled the login GUI. But I know on 8 and 9, you can add scripts in the /etc/dt/ directories that run after a user enters their name and password, but before CDE actually comes up.

 

[gsgatlin]

Ok. I had some success finally with the wizard and the notify applet.

What I ended up having to do was run these commands on first boot:

/usr/sbin/sconadm register -N
/usr/lib/cc-ccr/bin/ccr -p cns.swup.autoAnalysis.enabled -v false

I got the info on the first command from this web site:

http://docs.sun.com/app/docs/doc/817-1985/6mhm8o5vo?a=view

The second command came from studying the
/usr/dt/config/Xsession.d/1001.swupnot
and
/usr/bin/swupnot

scripts.

Unfortunatly, these commands won't work if run at install time. (I tried)

Thus, I am using:

at now < /opt/unity/firstboot/commands

in %post of my rpm. (We are using openPKG bolted onto the
side of Solaris 10) This schedules a job to run durring
the install. But since atd isn't running it can't run the
job. So the job actually gets run on first boot when atd
starts for the first time.

So thanks anyways to all the people who helped! =)

Anyone know how to stop the:

"About the Gnome Desktop"

popup starting on first login?