From: Christopher.Vance@adfa.oz.au Christopher.Vance@adfa.oz.au
Subject: New installation
Date: Thu, 16 Mar 1995 19:48:30 -0500 [thread overview]
Message-ID: <19950317004830.hdU9vThb5Xc52L9qFgXYW7hPfIbaIVeKQSYGPM2vSZ8@z> (raw)
I've just received a CD-ROM for the first time. I don't have any dedicated hardware available for file or cpu servers, and am hoping to use u9fs as a file server on a Unix machine which has lots of other things to do to.
My computer centre copied the CD-ROM onto a Solaris Sun for me, but all the files lack the appropriate filenames, ownerships, and permissions.
I have compiled u9fs, but am unsure whether it's configured properly.
I hope to correct the file names by borrowing a CD-ROM drive, running 9sscd on my Sparc ELC, and writing the corrected information to u9fs. A quick look at the code for u9fs (to an untrained eye) suggests it obeys wstat syscalls.
In the mean time, I want to get the floppy 9dos version working. (I don't want to ask my computer centre to install a privileged program without checking it out first, so I've got the server running on my [Solaris] Sun with read-only access to the partition holding the files.)
I'm using a 486dx2/66 with a 3c509 ethernet card.
By comparing the floppy versions of /rc/bin/termrc and /lib/ndb/local with those copied off the CD-ROM I've discovered the need to add my pc's ethernet and ip address to local, and to send 'add tcp udp il' to /net/cs. When I try telnet, however, I get timed out, and when I try running arpd with debugging or check /net/arp/stats, I get only misses, no hits.
Any hints what I should look for? Should I try snooping the ethernet to see what packets are really there? Or is there yet another subtle something I've missed in the way things are supposed to work.
-- Christopher
next reply other threads:[~1995-03-17 0:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-03-17 0:48 Christopher.Vance [this message]
1996-01-27 17:57 New Installation R.D.Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19950317004830.hdU9vThb5Xc52L9qFgXYW7hPfIbaIVeKQSYGPM2vSZ8@z \
--to=christopher.vance@adfa.oz.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).