3
<!-- @(#)notes-solaris2.html 1.1 02 Jun 1995 -->
4
<title>WorkMan notes: Solaris 2</title>
8
<h1>Solaris 2 notes</h1>
14
<li> <a href="#compile">Compiling WorkMan for Solaris 2</a>
16
<li> <a href="#gcc">Using gcc</a>
18
<li> <a href="#volmgr">Using the volume manager</a>
20
<li> <a href="#avoid">Avoiding the volume manager</a>
22
<li> <a href="#audio">Getting sound via the SPARCstation audio output</a>
26
<h2><a name="compile">Compiling WorkMan for Solaris 2</a></h2>
29
WorkMan should compile without modification on Solaris 2.x, provided you
30
make sure the three relevant lines indicated in the Makefile are uncommented.
32
necessary to get it to run properly in conjunction with the volume manager
33
(vold) found in Solaris 2.2 and later.
36
If you're using the SPARCworks compilers from Sun, make sure your search
37
path is set so that "/opt/SUNWspro/bin" (or whatever directory the compilers
38
are in) is searched before "/usr/ucb". Otherwise you'll be using a different
39
set of libraries and include files, and WorkMan won't compile properly.
42
If you get a message like "language optional software package not installed,"
43
your machine probably does not have SPARCworks, and you should talk to your
44
system administrator about getting gcc.
47
<h2><a name="gcc">Using gcc</a></h2>
50
You should be able to compile WorkMan using gcc. Just uncomment the "CC=gcc"
51
line in the Makefile and comment out (or remove) "CC=cc".
54
Gcc version 2.6.0 is known to compile WorkMan on Solaris 2.4 without any
55
special handholding; older versions of Solaris and/or gcc apparently have
56
some trouble with the include files in /usr/openwin/include. If you get
57
compiler errors about OpenWindows include files, you should probably run the
58
"fixincludes" utility that comes with gcc, giving it the correct command line
59
arguments so it fixes /usr/openwin/include.
62
<h2><a name="volmgr">Using the volume manager</a></h2>
65
If you're running the volume manager -- you probably are -- you can get it to
66
start WorkMan when you insert a music CD. Assuming you've installed WorkMan
67
in /usr/openwin/bin, add the following line to /etc/rmmount.conf,
68
<em>before</em> the action_filemgr line:
71
action cdrom action_workman.so /usr/openwin/bin/workman
75
You should already have "action_workman.so" -- it comes with Solaris. With
76
that line in place, a WorkMan window should appear on your screen when you
80
Note that the volume manager doesn't know whether you're running a window
81
system, so if you put in a music CD when you're not running OpenWindows (or
82
there's one in the drive when the system boots up) you'll have to eject it
83
with the "eject" command and reinsert it to get the WorkMan window to appear.
86
Also, WorkMan will be running as root or as nobody, not as you, since the
87
volume manager runs without regard to who happens to be logged in on the
88
console. As a result, you'll probably want to edit your .Xdefaults file and
89
add the "workman.db.shared" and "workman.db.personal" resources to tell
90
WorkMan where to find its database files. For example, if /users/jane is
91
your home directory, you'd probably add:
94
workman.db.shared: /users/jane/.workmandb<br>
95
workman.db.personal: /users/jane/.workmanrc
99
Then run "xrdb -merge $HOME/.Xdefaults" to load the new settings into your
100
X server. You should only have to run that command once; .Xdefaults is read
101
automatically when you start the window system.
104
If you do use the volume manager to start WorkMan, you may find you have to
105
run "xhost hostname" (where hostname is the name of your machine) to give
106
root-owned processes the right to connect to your X server.
109
You'll also find that setting environment variables has no effect on
110
WorkMan when it's started by the volume manager, even if you set them before
111
you start the window system. To see why, realize that environment variables
112
are inherited by new processes from their parents. The volume manager is
113
started at system boot time, before you've logged in; it's what runs
114
WorkMan, so WorkMan only gets whatever variables were set when vold was
115
started. Setting variables in your .cshrc, or manually in a window, does
116
not magically cause them to be set in preexisting processes or those
119
<h2><a name="avoid">Avoiding the volume manager</a></h2>
121
If all that sounds too confusing and you'd like to avoid the volume manager
122
altogether, you can start WorkMan by hand as long as you do it after you've
125
<h2><a name="audio">Getting audio output from the workstation</a></h2>
127
(Note: This section only applies to the SPARCstation 5, and possibly the 20.
128
On other machines, hook up a cable from the CD player's headphone jack to
129
the computer's microphone input.)
132
Version 1.3 of WorkMan adds code to control the audio hardware on the SS5.
133
It only works if there is a physical connection inside the machine between
134
the CD player's internal audio output and the internal audio input on the
135
workstation. Instructions for making that connection are included with the
136
CD-ROM drive; don't ask me.
139
The code was added by <stevep@ctc.ih.att.com>, who has this to say:
142
I'm sure there will be problems with it, as people use hardware
143
configurations I didn't imagine. I'll be happy to try to deal with them.
146
The use of audiocontrol, audiotool, gaintool, or the like in conjunction
147
with this is highly recommended. Upon initialization, it switches the
148
codec input to the internal CD player, and turns the monitor gain up to
149
full (necessary). Thereafter, anytime WorkMan begins a play operation,
150
it checks the state of the codec and enforces the following conditions:
155
precision: 16 bits<br>
156
sample rate: 44100<br>
157
monitor gain: max<br>
158
input port: internal cd player
161
It does NOT "own" /dev/audio, nor does it check state other than when
162
beginning a "play". This allows other processes to do things with the
163
audio system. Please note that most other things will leave the chip in
164
a relatively pathetic state (8-bit ulaw mono at 8000 samples/sec);
165
pausing and resuming will correct this.
168
This all comes about because the headphone jack on the CD drawer sounds
169
awful (lots of processor noise; apparently, Sun doesn't believe in
170
shielding). The headphone jack out the back sounds MUCH better, but one
171
has to go through the audio chip to get there.
176
Please send mail directly to him if you have problems with this aspect of
181
<a href="install.html">To the install page</a>
183
<h5>Last update: 02 Jun 1995</h5>