From cse.psu.edu!9fans-outgoing-owner Mon Sep 4 23:23:32 1995 Received: by cannon.ecf.toronto.edu id <594>; Mon, 4 Sep 1995 23:10:16 -0400 From: Steve Kotsopoulos To: 9fans@cse.psu.edu Subject: setting up u9fs server [was Does Plan9 support NCR53c810 ?] Message-Id: <95Sep4.231016edt.594@cannon.ecf.toronto.edu> Date: Mon, 4 Sep 1995 23:10:07 -0400 Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu Status: RO "H.-P. Guenther" wrote: > Well, some time ago I've read that you can make a Unix box to a > dedicated Plan9 file server and hook up several Plan9 workstations > onto the same Ethernet as the file server. Is this still supported? > I glanced through the web pages at ftp://plan9.att.com/plan9/* and > couldn't find any hints on that. What I have here is a Unix box and a > Pentium connected via Ethernet, and I wonder if that would be > possible. And how would I go about it? > > [ The program u9fs is still supplied, so you can export Unix filesystems > to plan 9. The difficulty is how to set up the authentication -- mod ] With the new release, this is easier to do than in the past. First, you must compile and install u9fs on a Unix system. I used a spare disk, mounted as /plan9, and have 'u9fs /plan9' in inetd.conf to run u9fs chrooted to the empty disk. Also note that you must copy /etc/passwd and /etc/group and /etc/hosts.equiv to /etc under the chroot area. The /plan9/etc/passwd should have entries for bootes and none. The /plan9/etc/group should have entries for bootes, map, doc, font and none. The /plan9/etc/hosts.equiv should have an entry for your PC. /plan9 should be writable by user 'none', for the install process. As someone has already pointed out, a real plan9 file server will give you better performance ... so you'll want to run u9fs on the system holding the disk (NOT on an NFS client) or performance will be even worse since you'll be going through 2 distributed file systems. Next, boot up the PC plan9, and follow the directions for "3b. Install CD-ROM to network file server"; give it the address of your Unix u9fs server as the file server, and choose the option which says you will be using a TCP file server. At that point, you should check the u9fs logfile, to see that you don't get any error messages. If all goes well, you should see a scrolling window listing all the files as the get copied from the CDROM (this step took 4 hours & 400Meg for me). After you've done that, it's time to setup your network database and boot up your terminal, telling it to use tcp to connect to the file server. Since user 'none' shouldn't own any files, you should chown all the files to 'adm' or 'sys'. For authentication, setup a cpu server using the TCP file server ... which I plan to do this week (barring further interruptions), or you could try the Unix authentication server recently announced here. Steve From cse.psu.edu!9fans-outgoing-owner Fri Sep 15 13:39:27 1995 Received: from plan9.cs.york.ac.uk ([144.32.33.120]) by psuvax1.cse.psu.edu with SMTP id <34064>; Fri, 15 Sep 1995 13:11:59 -0400 From: forsyth@plan9.cs.york.ac.uk To: 9fans@cse.psu.edu Date: Fri, 15 Sep 1995 13:22:07 -0400 subject: faster u9fs Message-Id: <95Sep15.131159edt.34064@psuvax1.cse.psu.edu> Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu Status: RO if your unix tcp/ip implementation has the TCP_NODELAY option, try enabling it in u9fs: int one = 1; setsockopt(fd, IPPROTO_TCP, TCP_NODELAY, &one, sizeof(one)); you'll have to scour the heap of include files in /usr/include to find the one with the TCP_NODELAY option in it. i found it made a difference on our rs/6000 systems. 9P uses many small reply messages, which are subject to the delay. (the system waits to see if more data turns up to make the packet really worthwhile, but in this case it just makes it less responsive.) From cse.psu.edu!9fans-outgoing-owner Fri Sep 15 10:21:19 1995 Received: from phantom (localhost) by phantom.cegelecproj.co.uk (5.0/SMI-SVR4) id AA01470; Fri, 15 Sep 1995 14:25:54 +0100 Message-Id: <9509151325.AA01470@phantom.cegelecproj.co.uk> X-Mailer: exmh version 1.6.1 5/23/95 To: 9fans@cse.psu.edu Subject: terminal not sending auth requests X-Face: Iqsa(US9p?)Y^W+6Ff[Z]rM"uFE) lFDjag1e]\/#2 X-Planation: X-Faces can be viewed with Faces from cs.indiana.edu. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Sep 1995 09:25:53 -0400 From: Steve_Kilbane Content-Length: 768 Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu Status: R I've been trying to boot a terminal using u9fs as the root server, and Pace's IL implementation for the auth server. However, the terminal doesn't appear to be making any attempt to contact the auth server. I suspect that because the root is a TCP address, and the auth server is an IL address, the IL system isn't getting configured. This doesn't make a lot of sense to me, because a quick glance at the code reveals that the tcp and il config() routines both do the same thing. However, if I give an il!a.b.c.d address for root, and w.x.y.z for auth, then the terminal does an arp for the auth address. If I change the root address to tcp!a.b.c.d, then the arp isn't attempted, and the terminal immediately complains that it can't contact the auth server. steve From cse.psu.edu!9fans-outgoing-owner Fri Sep 15 12:08:21 1995 Received: from plan9.att.com ([192.20.225.252]) by colossus.cse.psu.edu with SMTP id <45660>; Fri, 15 Sep 1995 11:44:22 -0400 From: presotto@plan9.att.com To: 9fans@cse.psu.edu Date: Fri, 15 Sep 1995 10:45:01 -0400 Subject: re: terminal not sending auth requests Message-Id: <95Sep15.114422edt.45660@colossus.cse.psu.edu> Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu Status: RO The thing that doesn't get configured is a way to call the auth server when the boot method is tcp. It doesn't need the auth server to talk to u9fs since u9fs uses ruser() to accept or reject. However, if you log in as anything either than 'none' then the kernel tries to check whether your key/password works. If you want to use u9fs as your main file system and have an auth server you can call up via il, you could change in /sys/src/9/boot/ip.c: int authtcp(void) { return -1; } to int authtcp(void) { return authil(); } I'ld assumed using tcp for file service implied no auth server, i.e., that you were logging in as 'none' to get Plan 9 installed and would never really run that way (u9fs isn't the worlds fastest file server by a long shot). Bad assumption especially not that there's a Unix auth server. From cse.psu.edu!9fans-outgoing-owner Fri Oct 27 23:27:24 EDT 1995 Received: from plan9.ecf.toronto.edu ([128.100.8.9]) by colossus.cse.psu.edu with SMTP id <78418>; Fri, 27 Oct 1995 23:06:02 -0400 From: steve@plan9.ecf.toronto.edu To: 9fans@cse.psu.edu Date: Fri, 27 Oct 1995 23:01:55 -0400 Subject: sendmail versus u9fs Message-Id: <95Oct27.230602edt.78418@colossus.cse.psu.edu> Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu I'm using u9fs as my main file server. According to mail(1), mailbox files must be append-only, but that's not possible with u9fs. This resulted in all new messages being written to the beginning of my mbox, instead of getting appended. The following patch works around the problem: cpu% cd /sys/src/cmd/upas/send cpu% diff /p/cd/sys/src/cmd/upas/send main.c 363a364 > Bseek(fp, 0, 2); 367a369 > Bseek(fp, 0, 2); From 9fans@cse.psu.edu Sat Oct 28 10:50:08 EDT 1995 Article: 722 of comp.os.plan9 Xref: cannon.ecf comp.os.plan9:722 Newsgroups: comp.os.plan9 Path: cannon.ecf!utnut!cs.utexas.edu!academ!bcm.tmc.edu!news.msfc.nasa.gov!newsfeed.internetmci.com!tank.news.pipex.net!pipex!sunsite.doc.ic.ac.uk!nntp0.brunel.ac.uk!strath-cs!dcl-cs!bath.ac.uk!ccsis From: steve@ecf.toronto.EDU (Steve Kotsopoulos) Subject: Re: Unix as file server Message-ID: <95Oct26.153639edt.9813@cannon.ecf.toronto.edu> Sender: ccsis@bath.ac.uk (Icarus Sparry) Reply-To: 9fans@cse.psu.edu Organization: Plan 9 mailing list Date: Thu, 26 Oct 1995 11:36:35 GMT Approved: plan9mod@bath.ac.uk Lines: 21 > Two things I would have liked to know before setting up a unix machine > as a plan9 file server: > - When renaming the files after the cdrom read, find, sed, join, sed, > sort the file of mv commands in reverse lexicographic order to > rename the directories *after* renaming the files they contain. > - When setting your ~plan9/etc/passwd file, translate the ~adm/users > file to /etc/passwd format *but_don't* give the uid 0 to the none user. If you have a pc with a cdrom, it's better to follow the instructions I posted here about a month ago, also available at http://www.ecf.toronto.edu/plan9/info/u9fs > Now I would like to know how to use 9auth to perform authentification. > Any pointer would be appreciated. see http://www.ecf.toronto.edu/plan9/info/u9fs for a patch to ip.cc and http://www.ecf.toronto.edu/plan9/info/unixauth for a Unix-based auth server I've collected 9fans messages and some of my notes at http://www.ecf.toronto.edu/plan9/info/