From owner-freebsd-ports Mon Sep 14 16:14:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15428 for freebsd-ports-outgoing; Mon, 14 Sep 1998 16:14:32 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15398 for ; Mon, 14 Sep 1998 16:14:25 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.7/8.7.3) id QAA03530; Mon, 14 Sep 1998 16:13:21 -0700 (PDT) Date: Mon, 14 Sep 1998 16:13:21 -0700 (PDT) Message-Id: <199809142313.QAA03530@vader.cs.berkeley.edu> To: rvb@sicily.odyssey.cs.cmu.edu CC: ports@FreeBSD.ORG, jkh@time.cdrom.com In-reply-to: (rvb@sicily.odyssey.cs.cmu.edu) Subject: Re: /usr/ports/filesystems From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * From: rvb@sicily.odyssey.cs.cmu.edu * I wanted to propose that we introduce a new directory under ports to * place file systems related ports. My main reason for suggesting this * was to create a logical place to put the CODA pieces: coda_client, * coda_server and some coda_doc related pieces. But I thought other * ports could go there as well, afs -- when it exists. Also /net/ is * a rather overused place, so perhaps samba belongs in filesystems and * perhaps the crypto fs (cfs -- currently in security). cfs should probably stay in security, but I agree with everything else. (Especially if it encourages someone to make an afs port. :) * Lastly, I prefer the longer name, filesystems, to something like fs * which I think is too cryptic. I think filesystems is fine in this case. I'm all for saving letters but it doesn't have to go all the way down to 2 bytes. ;) Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message