Re: No such file or directory

[Jeffery Douglas Waddell <jeff@xxxxxxxxxxxxx>]

Hello,

A couple of quick words.

On Tue, 10 Nov 1998, Richard Lohman wrote:

-->Date: Tue, 10 Nov 1998 15:13:33 -0800 (PST)
-->From: Richard Lohman <rjlohman@yahoo.com>
-->Reply-To: klug@klug.armintl.com
-->To: klug@klug.armintl.com
-->Subject: Re: No such file or directory 
-->Resent-Date: Tue, 10 Nov 1998 19:21:44 -0500
-->Resent-From: klug@klug.armintl.com
-->
-->The glibc solution seems to be on the right track.

good.

--> Unfortunately (as
-->is so often the case) unlocking one door has revealed yet another
-->locked door. In the README, there is a line that I am to type in
-->presumably to indicate the location of the libraries (I tried their
-->automated approach, and it failed):
-->
-->export LD_LIBRARY_PATH=/path_to_lib_files:$LD_LIBRARY_PATH
-->
-->upon issuing this command two things happened. 1) The office setup
-->script started to run (good), but being a presumed x application,
-->could not since XWindows wasn't loaded.

Easy fix, start xwindows before you issue the command above.  In the
resulting xterm (which is usually running a bash shell) do the above
export and then run the office setup script from that shell.  Next, to
make things easier for yourself write a quick shell script that does the
following.

#/bin/sh
export LD_LIBRARY_PATH=/path_to_lib_files:$LD_LIBRARY_PATH
runwhateverofficeappyouwanttorunhere

put this shell script (modified to your liking) in the /usr/local/bin
directory under whatever name you like and do a 

chmod +x /usr/local/bin/whateveryounamedit

Then you can just do a whateveryounamedit in an xterm after you startx.

There are plenty of other ways to do this (including symbolic links and
other fun stuff) but this is a quick hack that will get you going and will
preserve your libc5 apps runability.

--> 2) startx will, after entering
-->the above line, no longer execute.

Yep it's based on libc5 and your hitting the glibc first which it doesn't
grok if you know what I mean.  You can always run startx from a different
shell that hasn't messed with the LD_LIBRARY_PATH environment variable, or
you can set the LD_LIBRARY_PATH environment back to it's original and then
startx.

--> I thought this whole thing a bit 
-->odd, though, as in the instructions, it is quite explicit that the
-->setup executable is executed from the command line.

You mean a shell prompt ;)

--> To a DOS/Windows
-->guy, this seems odd because you just can't run a windows-app from dos.
-->

You've been brain washed.  Not only can you run "windows" apps from a
terminal command line, you can display the resultant windows
half way across the world on another machine!!!!!!  Network Transparency
and Client/Server architectures are a WONDERFUL thing.

-->    Any ideas? Again, TIA!
-->

Given above.

-->:Rich
-->

Jeff Waddell
jwaddell@ix.netcom.com