On Fri, Apr 09, 2004 at 09:44:21AM -0800, Tom HARROLD enlightened us
thusly
> Hi Declan, The following is my boot-up of the system that I work on:
>
> STS Prom Monitor, M68CPU (Non-MMU) version 2.5 Preparing to boot -
> press ESC to abort ... Standby REGULUS 4.2B 07/04/85 #11482 No MMU
> Copyright Alcyon Corp. @(#) Series 6000 version of Sat Sep 15 12:20
> 1990 initializing printer driver ... done. initializing mag-tape
> driver(ctcm) ... done. initializing tester driver ... done.
> initializing phi driver ... done. initializing dma driver ... done.
> sys/non/wst 297k/1751k/201 initializing omti driver ... done.17
> REGULUS Copyright Alcyon Corp. Login: root password:
> *********************************************************************
> *** Diagnostic Release 4.2.1 Installed on Sat Feb 25 10:00:14 1989
> ***
> *********************************************************************
> *** Release 4.1.10 Installed on Tue Feb 28 06:13:51 1989 *** ***
> Use news(cmd) to review release notes *** root.1> uname -a System
> name: REGULUS Node name: sbe.0001 Operating system release: 07/04/85
> Operating system version: 4.2B Series 6000 version of Sat Sep 15 12:20
> 1990 System does not have a Memory Management Unit. Root device: 10
> /dev/win /dev/rootfs root.2> ps -e PID TTY TIME COMMAND 1 ?
> 0:00 init 17 ? 0:00 /etc/update 21 tty0 0:02 #sh 25 tty0
> 0:02 ps -e 22 ? 0:00 /etc/init c 0 23 ? 0:00 /etc/init
sh is a shell, init is the startup thing, /etc/update and /etc/init are
probably scripts or daemons(read TSRs) which you need. try looking at
them with 'cat', 'more' or 'less'
> d 0 root.3> dir Directory / [bin] [net2.0] rlsnote.nr
> {installtape} {reguluse} [dev] [net] {Makebin}
> {regulus1} {regulus} [doc] [sbe] {initrg}
> {regulus2} {tinstall} [etc] [tmp]
> {installcart} {regulus3} {vbu2} [lib] [u]
> {installdisk} {regulusa} [mnt] [usr]
> {installnet} {regulusb} root.4>
The standard unix hierarchy is as follows
/ bin, /lib, /sbin = Startup binaries, libraries, & service binaries
/usr/bin, /usr/lib, /usr/sbin = Ditto for runtime
/etc = configuration files
/dev = devices; Anything the kernel can find is hooked to /dev/something
/mnt = removable or non automounted drives
The ones I am familiar with also have /var, & /proc
I would have a good hunt in the /doc directory!
>
> As you can see the above directory listing of the root shows 2
> directories of network stuff. It seem to me I should run the
> installnet. On the very little information that I have says I should
> configure the board by selecting the jumpers for it's interrupt vector
> and address select. Now my question is, how do I find out what
> interrupt vector can I use? Is there a UNIX command or program that
> scans the system and spit-out a report on what address and a
> interrupts are being use?
For me, 'cat /proc/pci' ; you don't appear to have /proc :-o. Try this:
cat /etc/mtab will tell you what's mounted. Here's mine # with comments
dec:~$cat /etc/mtab
rootfs / rootfs rw 0 0 # My root filesystem
/dev/root / ext3 rw 0 0
proc /proc proc rw 0 0 # This is the /proc filesystem - a sort of
# notepad for the kernel.
# These are all disk drives
/dev/hda1 /cdos vfat rw,nosuid,nodev,noexec 0 0
/dev/hda5 /ddos vfat rw,nosuid,nodev,noexec 0 0
/dev/hda6 /lfs ext3 rw 0 0
/dev/hda7 /thiz ext3 rw,nodev 0 0
# This is needed for the kernel
devpts /dev/pts devpts rw 0 0
# USB I very much doubt you will have!
none /proc/bus/usb usbdevfs rw 0 0
In whatever they call /proc you may well find files like interrupts,
ioports, and so forth holding all this information. It will be held
somewhere, probably off the / directory (I would not expect in in a
weird little subdir somewhere). They are not regular files, but cat can
read them.
>
> Thank you for the little info on uname and pe commands.
>
> I also learn about this EXOS 201 NIC board is an option, so we were
> lucky to have them included into each systems but no Software manual.
> This board was made by Excelan Inc. which is out of business, even the
> STS-6000 tester where this board goes into it.
>
> I like more help, so far so good little steps here and there is
> helping me to find out more of things of this stuff. Thanks....
--
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).
