From owner-freebsd-hackers Thu Feb 12 10:51:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09984 for hackers-outgoing; Thu, 12 Feb 1998 10:51:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nyef.res.cmu.edu (NYEF.RES.CMU.EDU [128.2.88.90]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA09911 for ; Thu, 12 Feb 1998 10:51:28 -0800 (PST) (envelope-from inf@nyef.res.cmu.edu) Received: (qmail 5303 invoked by uid 1000); 12 Feb 1998 18:51:26 -0000 Message-ID: <19980212135126.21661@nyef.res.cmu.edu> Date: Thu, 12 Feb 1998 13:51:26 -0500 From: Marca Registrada To: hackers list FreeBSD Subject: Re: Coda FS: FBSD port done!, but development favors Linux Mail-Followup-To: hackers list FreeBSD References: <19980212185933.22479@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980212185933.22479@follo.net>; from Eivind Eklund on Thu, Feb 12, 1998 at 06:59:33PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Eivind Eklund (eivind@yes.no): > It would take about 15 minutes to create this functionality, and it > has been discussed before. It has been decided against on the basis > of security. This break chroot() completely, and it break the > protection you presently have when > [...] > > If this is what it takes to get Coda, I for one won't use it, but I > can probably create and commit a kernel option that give the access > methods so that others can. > an inodefs is only necessary for a coda server, and only for the partition on which the distributed files are kept. I would say it shoudl be made a totally separate fs, accessible via fopen() calls (I'm hoping Linux-Coda does the same), and of course, the partition containing these files shoudl be root-accessible only, and as there is no directory strucutre on such a partition, only unbound inodes, standard unix tools, such as ls, vi, will have no usability on such a partition, anyway. In short, it's not that a Coda server needs to access files on the 'standard' filesystem via, inodes, but keeps track of it's internal files via inodes, and keeps its own internal directory structure, so that namei only gets in the way. I should find out if there is a final proposal for how this should look to the caller. -- - All we hear is internet gaagaa, internet googoo, internet gaagaa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe hackers" in the body of the message