From owner-freebsd-arch Tue Mar 12 1:17:23 2002 Delivered-To: freebsd-arch@freebsd.org Received: from hal-5.inet.it (hal-5.inet.it [213.92.5.24]) by hub.freebsd.org (Postfix) with ESMTP id 42C3237B41B for ; Tue, 12 Mar 2002 01:17:14 -0800 (PST) Received: (from root@localhost) by hal-5.inet.it (8.11.1/8.11.1) id g2C9HDU26086 for ; Tue, 12 Mar 2002 10:17:13 +0100 Received: from acampi.inet.it(213.92.1.165) by hal-5.inet.it via I-SMTP-4.0.5-100 id s-213.92.1.165-WlMyyk; Tue Mar 12 10:17:13 2002 Received: by acampi.inet.it (Postfix, from userid 1000) id BB47A15537; Tue, 12 Mar 2002 10:17:12 +0100 (CET) Date: Tue, 12 Mar 2002 10:17:12 +0100 From: Andrea Campi To: Garance A Drosihn Cc: Poul-Henning Kamp , Harti Brandt , arch@FreeBSD.ORG Subject: Re: Increasing the size of dev_t and ino_t Message-ID: <20020312091712.GB8071@webcom.it> References: <4252.1015867433@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.27i Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > > >But you could do me a favour: Write up a piece of text > >which gives enough info for somebody like me to setup > >and test AFS/ARLA in my lab... > > Hmm. This is a very reasonable request, but I am not > sure I have a good answer... > > Does your lab have reasonably-fast connectivity to the > internet at large? If so, then I could see about writing > something for setting up a machine as an AFS client and > having it pretend it is part of some already-existing AFS > cell. I do not actually use OpenAFS or ARLA on my freebsd > systems, but I certainly do want to figure that out. Sadly, now that there is interest my company has stopped its AFS pilot test so I don't have much time, and I no longer have an AFS server running. However, I could help you prepare this documentation. Either that or, if you (Poul) and I could "meet" online (IRC, ICQ, whatever) it would be probably easier to walk you through it. It's 20 minutes at most (with a working client and server). > If you do not have a fast network connection, then you > would need to set up your own AFS server. I do not know > how to do that, and I am pretty sure it is not something > that someone could do in an afternoon. The AFS cell at > RPI has 600-gigabytes of disk space in it, so I haven't > had much of an urge to start my own server! On the other > hand, I would really really like to get at that 600-gig > from FreeBSD clients. The server is still a problem, yes. Garance, don't you know of any anonymously accessible systems? I'm sure there are a few but don't think I wrote them down anywhere. :( That would save us quite a bit of time; it's something an experienced admin could set up in an afternoon with appropriate hardware at hand, but it would take you a couple of days starting from scratch, just to figure out all the messy documentation. Again, if you decided to just do that I could help. > There is a web site for openafs, at www.openafs.org. That > has downloadable client installations forMacOS 10, some > versions of Windows, Linux, Solaris, IRIX, AIX, and > Tru64 Unix. That web site does not have a client for the > Net,Open, or FreeBSD's. Most of the BSD's probably go with > the ARLA port for their AFS client. I never got OpenAFS working on -current but I heard someone is working on that. Note also that the kernel module is designed to be sort-of compatible between different implementation, so that you could use it witk either the OpenAFS or arla client. > Unfortunately, I noticed that someone else just mentioned > that the ARLA port is broken on current -- and here I just > switched to running current. Sigh... Yes, that's me. I think we should take this offline until we have something interesting to add ;-) > > -- > Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu > Senior Systems Programmer or gad@freebsd.org > Rensselaer Polytechnic Institute or drosih@rpi.edu > Bye, Andrea > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message