From owner-freebsd-hackers Tue Sep 24 15:37:02 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA27084 for hackers-outgoing; Tue, 24 Sep 1996 15:37:02 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA27056 for ; Tue, 24 Sep 1996 15:36:53 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id IAA16553; Wed, 25 Sep 1996 08:36:39 +1000 (EST) Date: Wed, 25 Sep 1996 08:36:38 +1000 (EST) From: "Daniel O'Callaghan" To: Peter da Silva cc: hackers@freebsd.org Subject: Re: UID < 65535? In-Reply-To: <199609241057.FAA18347@bonkers.taronga.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 24 Sep 1996, Peter da Silva wrote: > Joe Greco wrote: > >Maybe it's time to try something else... NFS seems to have so many problems. > >"Adapting the code to fit reality" may not be a trivial exercise - unless > >you don't mind breaking compatibility with everyone else in the world (maybe > >you don't mind doing that as a local site hack).. > > I have a horrible idea. > > How about using HTTP, with local whole-file caching a-la AFS/VICE? It'd > be the obverse of Sun's web-nfs, and allow you to mount anything that'd > serve as a website. > > Yes, it's got even more statelessness problems than NFS, but doesn't AFS > have a similar problem? And you could use header entries to pass just > about any ownership/permission stuffs you want, and let users mount stuff > by providing a password, and use HTTPS for encryption... > > And you could "cd /www/ftp.cdrom.com/pub/FreeBSD2.1.5/..." Just like the alex filesystem which was layered over anon-ftp. Is alex still in use? Archie.au used it extensively in 1990-1993. Danny