From owner-freebsd-afs@FreeBSD.ORG Sat Dec 13 15:24:40 2008 Return-Path: Delivered-To: freebsd-afs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB8001065670 for ; Sat, 13 Dec 2008 15:24:40 +0000 (UTC) (envelope-from shadow@gmail.com) Received: from mail-gx0-f13.google.com (mail-gx0-f13.google.com [209.85.217.13]) by mx1.freebsd.org (Postfix) with ESMTP id 45A458FC23 for ; Sat, 13 Dec 2008 15:24:40 +0000 (UTC) (envelope-from shadow@gmail.com) Received: by gxk6 with SMTP id 6so1449530gxk.11 for ; Sat, 13 Dec 2008 07:24:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=skqXnqT7VNrKoKVWvabbaJZi/FP0HSsMA5DsGgR3Ujc=; b=DmHZX9JauhuS3J3DP53rXXxhaQoTdAWGIXKW/2J05+w4TVroB8h0U1abjIwwNv1514 aUtkEe7apTzoC1XtKmrtYJIaQzSnk//inKMjbVKifn2sXHFdoiCmdmy2RYht8C+35314 P8JXl+s1Nw+rqM3AcOt1OyNE6+g6U2YBjMVpg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=W+8TNkQUac+EvQ0qlCZWKCCZQOBG1X4PiVjyO54BDQfbDF3BBrkuc8L7h6BDaesW+C DlplCWn8AmiJLwDDeSw946VMbd0rGAmevnQVkA0jpoyFddnAoR5lt8OAumIiQso/5od/ rMHv2dtTwaPG0nxhBetCiCoMPHHMITkTIXlmk= Received: by 10.150.156.9 with SMTP id d9mr1765532ybe.46.1229181879653; Sat, 13 Dec 2008 07:24:39 -0800 (PST) Received: by 10.151.153.1 with HTTP; Sat, 13 Dec 2008 07:24:39 -0800 (PST) Message-ID: Date: Sat, 13 Dec 2008 10:24:39 -0500 From: "Derrick Brashear" To: "Boris Samorodov" In-Reply-To: <60600083@bb.ipt.ru> MIME-Version: 1.0 References: <493ACAC4.5020806@linuxbox.com> <22B6C509EF7C4AB0A2D8350C31BB8D5D@valentine> <57098597@bb.ipt.ru> <26695644@bb.ipt.ru> <20081213004251.GA88954@keira.kiwi-computer.com> <42451957-717C-4CA3-97D9-E2ACABE55E34@pingpong.net> <60600083@bb.ipt.ru> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Tony Jago , Alec Kloss , "" , "Jason C. Wells" Subject: Re: OpenAFS port X-BeenThere: freebsd-afs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: The Andrew File System and FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2008 15:24:40 -0000 I don't believe there are conflicts between client objects, and server objects. An independent client and server port should be possible. But if not, why a metaport and not say openafs-base that both client and server depend on? On Sat, Dec 13, 2008 at 8:19 AM, Boris Samorodov wrote: > Palle Girgensohn writes: > > 13 dec 2008 kl. 03.27 skrev "Tony Jago" : > > > >> I think that we probably don't need more then one port. Yes, I know > >> I was the one what originally proposed the meta port but I have > >> changed my mind :) The reason we had a server and a client port > >> originally was that the server was the only bit working and the > >> kernel model was set not to compile. The client was was arla client. > >> Now that both the openafs server and client are supported by the > >> openafs team I can see no reason why it shouldn't be all in one > >> port. The port should have separate rc variable to allow the > >> administrator to only start the client or the server if they choose > >> to. openafs_client_enable="YES" and openafs_server_enable="YES" for > >> example. This gets around all the conflicting file problems. The > >> kernel module need only be loaded if the client is required. This > >> would seem to be a much easier and cleaner solution. > > > > As long as nothing conflicts with arla, I also suggest an all in one > > installation. Keeps it simple, which is always important. > > I'd vote for that myself if and only if we speak about a ports > subsystem. But there are packages as well. And for those who prefer > using packages I'd rather give an opportunity. > > Said that I propose following ports: > . net/openafs (server+client) > . net/openafs-server; > . net/openafs-client. > > One of them will be a master port (I don't figure out which one, > but that will be either openafs or openafs-server). All of them > will conflict each other, i.e. only one of them can be installed > at a machine. > > That way we may give all users their chance. > > Opinions? Thanks! > > > WBR > -- > Boris Samorodov (bsam) > Research Engineer, http://www.ipt.ru Telephone & Internet SP > FreeBSD committer, http://www.FreeBSD.org The Power To Serve > -- Derrick