Solaris

smc IS a graphical gui... you can administrate everything via commandline! so why use smc?

Because there are multiple people who will be using this procedure I am writing to install a software package on Solaris servers.

Some of them know AIX, but not Solaris. We will be under a time crunch.
It would be much easier if they could get into a menu driven admin console, should a problem happen.

As Regis Philbin says, "It's always easy......when you know the answer".

no such thing you're looking for. however, what duke said seems to be your best option. i would say think about the "time crunch" and take it from there. xming runs on thousands (do i dare say hundreds of thousands) of servers. however, a simple procedure to do what the other AIX admins need to do might not be so hard. then again, depends on the complexity of your motives. also, if they are AIX admins, i would think they are willing to explore another flavor of unix. i know i always am.

o and almost forgot... what package you trying to add to solaris?

pkgadd.... ??

are you building from source?

This is a proprietary software package and it is already made, Client.x.x.x.x.SPARC.pkg.

It's not a question of wanting to explore and learn other OSs. We just want to have the feature as an additional option.
smc will not be used in the install procedure.
However, it would be a nice additional tool to have, to diagnose problems and troubleshoot a system in the event a problem occurs, for those who are not Solaris experts.

No sense in going through all that trouble of creating a system interface tool, and then never even using it.
If only Windows users were so unwilling to be hand-held...........

i see what you mean. althought this seems like it might be moving away from topic but my shop deals with way to many types of hardware and OSs. HP, AIX, Linux (suse, rhel), windows 2k,2k3, solaris 10, ios, force 10 (whatever os that is), avocent style linux, blah blah blah... point is we solved many problems have having a "wiki" of each OS and the basics for trouble shooting a common issue as well as the basic commands that might lead you to getting to the root of the cause. i've solved several AIX issues and honestly won't know what to do if you put me infront of an AIX box w/o that wiki page.

id say your best bet at this point is to just write the procedure.

I hate also to stray from the topic, but this is right in line with what we are doing.

One of the reasons I wanted smc is because the SPARC install package contains a straight tarball, which includes among a list of files samgr-client/root/, samgr-client/install/ and samgr-client pkgmap and pkginfo.

Although I do not currently have clearance to actually install this client yet, I do understand that

# pkgadd -d <install package>

is the syntax to install from a Solaris package. But I don't see any particular file in this tarball which is the package itself, or which by reasonable english would make you assume it is.
There are two SPARC package files:

Client.2.2.1.3.SPARC.pkg.tar
CommerConf.2.3.1.1.SPARC.pkg.tar


I can't find any definitive explanation on the web, or in a Solaris book (although I've only found one so far).



All I can assume is I tar -xvf both of these tarballs from root, then execute

# pkgadd -d $PWD


From the root directory.
Is this how Solaris SPARC packages are installed?
Smc I assume, would walk you through creating this command.
The creators of this package, of course, are awol.


Thanks for any advice.