Sorry for the long post, but many of these things are linked to one
another.

I have installed NetBSD on a IIsi.  I also have Apache installed on this
machine.  I have the IIsi networked with an ethernet card (crossover
cable) to my PPC 7200/90 (running LinuxPPC).  I am able to 'ping' and
'telnet' between each of the machines.  I am unable to get a browser on
the Linux box to see my IIsi.  I get a 'connection refused by server'
error.  

This is an email from the University's unix help desk.  This is how I
networked the two machines together:
__________________________________________________________________
First you need to edit your /etc/hosts.  (This is necessary in both
NetBSD and Linux.)  Make it look like this:

127.0.0.1               localhost localhost.localdomain
192.26.1.1              penguin.brent.net penguin
192.26.1.2              daemon.brent.net daemon

This file identifies your machines to each other.  For this example,
I've chosen to call the Linux machine "penguin" and the BSD machine
"daemon", and to place them in the domain brent.net.  The IP numbers,
hostname, and domain name are aribitrary.  These machines will never be
seen by the outside world, so there's no danger of interfering with other
people's names or IPs.  It's nonetheless traditional to use IPs beginning
with 192, since those are reserved.  That way if you connect yourself
to the network later and forget to change your IPs, you shouldn't
mess anything up.

The file should look the same on both hosts.

Now the two boxes know each other's IPs, and they can talk to
each other by name . . . once their interfaces are activated
and routing is set up.

To activate the Ethernet interface on the BSD box, issue the command
'ifconfig eth0 inet 192.26.1.2 broadcast 192.26.1.255 netmask
255.255.255.0' This command tells it to set up the device with IP address
192.26.1.2 (daemon's address); the broadcast address is a special IP used
to communicate with all the hosts on the subnet.  In your case, that's
just the Linux box!  On the Linux box, do 'ifconfig eth0 inet 192.26.1.1
broadcast 192.26.1.255 netmask 255.255.255.0'.

Now you're ready to add the route on the BSD box.  Do it like this:
'route add -host 129.26.1.1 dev eth0'.  This command tells BSD to take all
packets heading to the Linux box's address and send them across the
Ethernet interface (where they will go directly over the wire and
into the Ethernet card of the Linux box).  The corresponding command
to run on the Linux box is 'route add -host 129.26.1.2 dev eth0'.
_______________________________________________________________________

In addition to these suggestions, I added the file 'ifconfig.ae0' to my
/etc directory.  'ae' because this is what is identified during startup as
my type of ethernet card.  Within this file I have the following line:
inet 192.26.1.2 netmask 255.255.255.0

And I also subbed out the 'ifconfig eth0 ...' with 'ifconfig ae0 ...' for
the BSD machine.

I followed this email and got networking working (just ping and telnet).
I get an error message when I try to 'route add' on the NetBSD box.  It
tells me 'dev: bad value'.  I am assuming that eth0 is not correct?

Those are my networking issues.

I installed Apache on the IIsi after I installed NetBSD using the NetBSD
installer (Mac Side).  This was the precomplied version in the 'packages'.
All of the files got thrown into different directories so it looked like
it was actually installing it rather than just dumping it into one
directory.  I used 'httpd' to start Apache.  The first couple of times I
did this I would get a file not found message.  I used soft links (ln -s)
to link the directories where I knew apache lived with where Apache though
it should be.  This seemed to work fine.  Now when I type 'httpd' the HD
spins a little, the machine pauses a little and it seems to have started.

These are the files that I changed in Apache:

httpd.conf
-made apache 'inetd'
-set port to 80
-set ServerRoot file to something sane

srm.conf
-set DocumentRoot file to something sane, moved the apache "intro" pages
to that directory so that I would have some content in that directory.

access.conf
- set <Directory /some/sane/directory>

Does this look OK?

I have a feeling that my network hang ups have something to do with my
lack of ability to see things on the BSD machine vis apache.  

Again, sorry that this is long.  If anyone can help (even with parts of
it) I would be greatly appreciative.

Thanks,
Brent

___________________________________________________

ZenCrafters:  Total Enlightenment, in about an hour
___________________________________________________