Tom, will you do two things for me
1. Make an archive of the /etc directory as follows
cd / #changes you back to the root directory
tar -cvf oldetc.tar /etc # If it does nothing, try /etc/*
gzip oldetc.tar
This should give you oldetc.tar.gz Can you stick that on the net, or
email it to me direct?
2 Report the output of
cc --version
strace --version
check your /lib and /usr/lib for files named libc.so.<something>
Use ls, if it's there - much better than dir
ls libc.so.*
ls -a show hidden files
ls -l long listing
ls -F show Function (executable, directory, symlink, etc)
Apparently your system is so old that no virtual record of io ports and
interrupts is available. They'll have to be found other ways. I have
that from the horses mouth. To quote the aforementioned
It's running Unix, and it's running a really _old_ flavor of Unix. If
you dig around in it's init scripts you will likely see sh coding so
primitive it will remind you of pictures of cavemen hunting deer
scratched onto cave walls. 1985 is a _lot_ longer ago in terms of
computing technology than most people realize. In 1985 people were
still arguing over whether magic bytes and bangpath (#!) were the
correct way of making shell scripts execute. There simply is no handy
interface to let you see system internals like if you had /proc around.
Cross your fingers and start looking for header files relating to the
binaries you execute to use the testing hardware, and if you're really
lucky the binary might respond to -v or --verbose. You're probably
going to have to flat out reverse-engineer it.
I'm assuming that if you're looking for the ioports and interrupts that
there's either an 8-bit ISA card in the machine, or a rudimentary devel
environment on it. If there's anything like a compiler on it, you
/might/ be able to bootstrap gcc into it and get strace running. If you
can take the ISA card out and put it into a x86 box, it might actually
be faster to poke at the few interrupts and IO ports it could be using
to figure it out. You can also try poking around in the machine's
BIOS. Machines from that period of time tended to have some pretty raw
interfaces for calling a bootstrap from the hard disk, and you might be
able to reach some hardware diagnostics from within that. Expect to
mash alphabet keys on each boot until something happens--or make a
thorough of use of Google and you might find some hardware manuals.
--
With best Regards,
Declan Moriarty.
--
Author: Declan Moriarty
INET: [EMAIL PROTECTED]
Fat City Hosting, San Diego, California -- http://www.fatcity.com
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB CHIPDIR-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
