Clarence Verge wrote:
> Thanks for the "env" command. I learned a lot there.
> One thing was that the path for root doesn't specifically state /root.
> The other was my path was all possible variations on usr/local/bin &
> sbin, and nothing else.
Yes, this is as it should be.
> Typing "which arachne" just got me the message: no arachne in that
> complete path above.
Which most likely means that /usr/bin/arachne doesn't exist.
> Linuxlovers have brainwashed themselves into
> thinking this is good stuff. There has to be a better way !
Packages. If there was an arachne-1.66.rpm, for instance, you
would just do 'rpm -Uvh arachne-1.66.rpm' to install, and
'rpm -e arachne' to delete all arachne associated files.
Most typical Linux users don't use tarballs.
> I re-unzipped with mc, this time electing to unzip to the current
> directory. (root) Then I found the "install" command in the arcn166b
> subdir and hit on it. It went exactly as before, and I saw where it
> had found the necessary libraries and where it changed the ownership
> of arachne-svgalib. I took all the suggested defaults.
I don't know if using mc is the wisest way of doing this.
Since I'm on a new hard drive without any Arachne, I'll copy
the exact steps I take to install and run it, on a fresh install
of Red Hat 6.2 (in some instances, there are shortcuts, but I'll
go the long way around for the sake of clarity) All of these steps
are performed by root in a console. All commands are enclosed by
single quotes and implicitly end with hitting the <ENTER> key.
Additional comments follow double colons.
1) From /mnt/cdrom where I have the tarball stashed,
'cp arachne-1.66b.tar.gz /opt'
:: copy the tarball to the directory I plan to install it from.
:: You could just as easily download it directly to /opt
2) Change to the directory where the tarball is located
'cd /opt'
3) "Expand" the tarball
'tar -xzvf arachne-1.66b.tar.gz'
:: creates the arachne-1.66b subdirectory. In absolute terms, there
:: is now the directory /opt/arachne-1.66b which is filled with all the
:: arachne subdirectories and files
4) Change to that newly created directory and see what's there
'cd arachne-1.66b'
'ls -l'
:: you'll now see directories bin, doc, man, share, and the single
:: file, install
5) Run the install script
'./install'
:: here you'll see some informative messages and some prompts
:: hit <ENTER> key twice when prompted
6) Run it
'arachne'
:: You might get lucky, but I get an odd display. vgalib isn't
:: set correctly yet for this video card. Hit <ESC>
7) Go to where the libvga.config file lives
'cd /etc/vga'
8) edit the vga configuration file
'pico libvga.config'
:: uncomment the chipset VESA line, comment the Microsoft mouse line
:: and uncomment the PS2 mouse line
Clarence, I believe it is necessary to have a mouse line uncommented.
With no mouse "active" in this file, I get very erratic behavior.
(but that might be because a mouse is connected while vga expects
none)
> Finally, I typed arachne (exactly as suggested with no leading "./")
> and got this message:
> /usr/bin/arachne:Line 7 188 illegal instruction /usr/bin/arachne-svgalib$*
> Repeated attempts just changed the 188 to 192 then 194 ....
> Any ideas ? I'm not installing RedHat. <G>
Sorry, I don't know what's causing that. Possibly it's due to the
mouse, or lack thereof? Or maybe there is something else required
that Michael didn't check for in the install script.
- Steve
