Return-Path: X-Original-To: apmail-geronimo-dev-archive@www.apache.org Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F22A09010 for ; Wed, 21 Sep 2011 03:09:20 +0000 (UTC) Received: (qmail 28003 invoked by uid 500); 21 Sep 2011 03:09:20 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 27958 invoked by uid 500); 21 Sep 2011 03:09:20 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 27945 invoked by uid 99); 21 Sep 2011 03:09:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Sep 2011 03:09:20 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rwonly@gmail.com designates 209.85.218.54 as permitted sender) Received: from [209.85.218.54] (HELO mail-yi0-f54.google.com) (209.85.218.54) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Sep 2011 03:09:12 +0000 Received: by yia13 with SMTP id 13so1070340yia.13 for ; Tue, 20 Sep 2011 20:08:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=rQH68PBSJLDLzA/vm8CAlKTZDcP2CQGRiwNxRk4kSU0=; b=SOhXX4Bb4MpbYOBngt3kFm6aVqVPnHxKUm0qH72/pLFFaxRY9bLsJ1LIzOBJ6SQ7d6 KI7U+7gsE+Fk4jgOXbeOUxb0VuYvSae4YA+msveku0uyDi9lBn8ploanrPotYLLKEg+5 g/RMpow3Sr2cjgK1fowfFctWqBXU8oj0vg64A= Received: by 10.236.123.43 with SMTP id u31mr1260552yhh.97.1316574531075; Tue, 20 Sep 2011 20:08:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.147.136.15 with HTTP; Tue, 20 Sep 2011 20:08:31 -0700 (PDT) In-Reply-To: References: From: Rex Wang Date: Wed, 21 Sep 2011 11:08:31 +0800 Message-ID: Subject: Re: Geronimo directory structure & permissions To: dev@geronimo.apache.org Content-Type: multipart/alternative; boundary=20cf300e550b3ebed304ad6ae5ac X-Virus-Checked: Checked by ClamAV on apache.org --20cf300e550b3ebed304ad6ae5ac Content-Type: text/plain; charset=ISO-8859-1 If we want to continue maintain such complexity in 3.0? Hard drive is pretty cheap nowadays. And I think currently the part that looks a little bit wasting space is karaf "copy" the artifacts from repository to cache when start.. -Rex 2011/9/21 Forrest Xia > This idea is like the multiple instances feature we had in 2.1 branch, but > not supported in trunk now. > > Geronimo 2.1.x support copying "var" folder to add more instances with a > same installation, but G trunk code does not support that feature now. > > Do we have a user scenario to mandate that feature for 3.x? > > Regards, > Forrest > > > On Wed, Sep 21, 2011 at 1:55 AM, Jarek Gawor wrote: > >> Hi, >> >> In Geronimo binary install which directories do we consider read-only >> vs. write/read? The idea is that the read-only directories could be >> shared among multiple installations to save some space and reduce >> maintenance. >> >> Here's what I identified so far: >> >> read-only: >> - bin >> - jsr88 >> - schema >> - lib >> >> read/write: >> - deploy >> - hotbundles >> - etc >> - var >> >> The repository/ directory is a little weird because parts of it could >> be considered read-only and some write. I wonder if maybe we should >> have separate repository directories one for Geronimo bundles and >> another one for applications. >> >> Thanks, >> Jarek >> > > -- Lei Wang (Rex) rwonly AT apache.org --20cf300e550b3ebed304ad6ae5ac Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable If we want to continue maintain such complexity in 3.0? Hard drive is prett= y cheap nowadays.

And I think currently the part that looks a little= bit wasting space is karaf "copy" the artifacts from repository = to cache when start..

-Rex

2011/9/21 Forrest Xia <forre= stxm@gmail.com>
This idea is like the multiple instances feature we had in 2.1 branch, but = not supported in trunk now.

Geronimo 2.1.x support copying "var= " folder to add more instances with a same installation, but G trunk c= ode does not support that feature now.

Do we have a user scenario to mandate that feature for 3.x?

Rega= rds,
Forrest


=
On Wed, Sep 21, 2011 at 1:55 AM, Jarek Gawor <jg= awor@gmail.com> wrote:
Hi,

In Geronimo binary install which directories do we consider read-only
vs. write/read? The idea is that the read-only directories could be
shared among multiple installations to save some space and reduce
maintenance.

Here's what I identified so far:

read-only:
=A0- bin
=A0- jsr88
=A0- schema
=A0- lib

read/write:
=A0- deploy
=A0- hotbundles
=A0- etc
=A0- var

The repository/ directory is a little weird because parts of it could
be considered read-only and some write. I wonder if maybe we should
have separate repository directories one for Geronimo bundles and
another one for applications.

Thanks,
Jarek




--
Lei Wang (R= ex)
rwonly AT apache.org=
--20cf300e550b3ebed304ad6ae5ac--