From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <940a30e216cbf845003a6cfc1f96bc43@plan9.bell-labs.com> From: "Russ Cox" To: 9fans@cse.psu.edu Subject: Re: [9fans] hardware support for the fs kernel In-Reply-To: <20030313095950.S24866@cackle.proxima.alt.za> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Date: Thu, 13 Mar 2003 10:45:49 -0500 Topicbox-Message-UUID: 7f85e6f4-eacb-11e9-9e20-41e7f4b1d025 > Unless my reading of the Fossil documentation deceives me, fossil > gets its own namespace to serve, in which case it could also I don't know what you mean by this, but I think you're confused. As far as file service is concerned, fossil is conceptually identical to the worm fs but with long file names. > Another benefit would be the ability to serve arbitrary media: the > old fileserver, in my particular case, could not serve the contents > of the two CD-ROM changers, fossil will be better geared to do so. No. See above. Fossil is just a file server. > Good point, wouldn't be hard to rename it "mntold9p", although > renaming "srv" to "mnt" is right out of the question. I find having > to resort to "-u none" all the time (am I misunderstanding the > documentation?) a little restrictive and irritating. It probably > ought to have been the default. It's a throwaway program, meaning I can't wait to throw it away. Russ