olvwm on SS-2, solaris 2.3

olvwm on SS-2, solaris 2.3

Post by rob van den ber » Tue, 21 Mar 1995 20:01:12



Being a person that likes to use a lot of windows concurrently, I have
decided to get olvwm
for my SparcStation-2 running Solaris 2.3 ( Nothing special
installed). When I try to start openwindows
I get the following error message before openwin bails out:

ld.so.1: olvwm: fatal: libolgx.so.3: can't open file: errno=2

libolgx is present, so what am i missing? Help would be valued
muchisimo.

regards, rob

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

schubertstrasse2                Voice/Fax: +49 8106 301316
85591 Vaterstetten
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 
 
 

olvwm on SS-2, solaris 2.3

Post by Casper H.S. D » Wed, 22 Mar 1995 06:44:21



Quote:>Being a person that likes to use a lot of windows concurrently, I have
>decided to get olvwm
>for my SparcStation-2 running Solaris 2.3 ( Nothing special
>installed). When I try to start openwindows
>I get the following error message before openwin bails out:
>ld.so.1: olvwm: fatal: libolgx.so.3: can't open file: errno=2
>libolgx is present, so what am i missing? Help would be valued
>muchisimo.

The FAQ maintainer cheated and added this to the FAQ:

+5.24) I have an application that compiled fine, but when I run it I get:
    fatal: libfoo.so.2: can't open file: errno=2

    You need to add -R<wherethelibraryis> to the link command line.
    E.g.,:

        cc -L/usr/openwin/lib -R/usr/openwin/lib xprog.c -lX11

    --- end of excerpt from the FAQ

Questions marked with a * or + have been changed or added since
the FAQ was last posted

The most recently posted version of the FAQ is available from
ftp.fwi.uva.nl in directory /pub/solaris

 
 
 

1. Q: Archive TurboDAT 4324 / Solaris 2.3 SS 10

We have an Archive TurboDAT 4324, compression enabled by DIP-switch,
3.8 mm. Is is connected to SPARC 10 running an unpatched Solaris 2.3.
If we use the DAT, the following message appears in the syslog:


        Error for command '<undecoded cmd 0x4d>'        Error Level: Fatal
        Requested Block 0, Error Block: 0
        Sense Key: Illegal Request
        Vendor 'ARCHIVE': ASC = 0x77 (<vendor unique code 0x77>), ASCQ = 0x79, FRU = 0x0

        DAT soft error reporting failed

Generally, it is easier to write DATs. But reading gets tricky. E.g.
tar terminates immediately with an I/O error. Sometimes it helps to
rewind the tape; but in some cases it is neccessary to insert a fresh
tape, WRITE on it, then re-insert the old one and then... we can read
it!

In addition, dumping from a remote SunOS 4.1.3_U1 hosts makes problems.
I do not know the correct arguments to dump, e.g. blocking factor,
density or size. We currently use Audio DAT (ok, there are discouraged --
but is this the real problem?).

SUN could not help us, the FAQs gave no info, so I ask The Net.
Perhaps somebody has suggestions for us or some support e-mail address
from Archive.

Please e-mail. I will post a working solution if I get one.

Joerg Eisenreich

2. ctrl-alt-del and raw keyboard mode

3. Solved: Archive Python 4324RP DAT / Solaris 2.3 SS 10

4. SMP Problems on Proliant 8000

5. Olvwm for Solaris 2.3

6. illegal instruction signal

7. Looking for Virtual Desktop (olvwm) for Solaris 2.3

8. Cernhttpd looking up a proxie ?

9. olvwm / Solaris 2.3 / OpenWindows 3.3

10. olvwm for Solaris 2.3

11. HELP: Solaris 2.3 <---> Solaris 2.3 PPP link problems

12. HELP: Solaris 2.3 <---> Solaris 2.3 PPP link Problems

13. 2.3 -> 2.4 upgrade hangs on SS 5