Return-Path: X-Original-To: apmail-mahout-user-archive@www.apache.org Delivered-To: apmail-mahout-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6E90EC787 for ; Thu, 3 May 2012 17:23:01 +0000 (UTC) Received: (qmail 5396 invoked by uid 500); 3 May 2012 17:23:00 -0000 Delivered-To: apmail-mahout-user-archive@mahout.apache.org Received: (qmail 5344 invoked by uid 500); 3 May 2012 17:23:00 -0000 Mailing-List: contact user-help@mahout.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@mahout.apache.org Delivered-To: mailing list user@mahout.apache.org Delivered-To: moderator for user@mahout.apache.org Received: (qmail 88779 invoked by uid 99); 3 May 2012 17:18:19 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Message-ID: <20120503171754.39590.qmail@ontrenet.com> Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII"; format="flowed" MIME-Version: 1.0 X-Mailer: MIME::Lite 3.0104 (F2.72; T1.15; A1.47; B3.01; Q3.01) Date: Thu, 3 May 2012 17:17:54 +0000 From: "Darren Govoni" Reply-To: darren@ontrenet.com To: user@mahout.apache.org, darren@ontrenet.com Subject: RE: Re: Re: Mahout + BigDataR Linux X-Virus-Checked: Checked by ClamAV on apache.org Exactly. Start with something like an Ubuntu LTS release. Work your magic on it. Then release the AMI publicly for others to use. Mahout et. al. was born to run in a cloud environment anyway.


------- Original Message ------- On 5/3/2012 12:06 PM Nicholas Kolegraff wrote:
Assumed this question was coming.
I had given this a lot of thought.
I have this crazy notion that nothing should ever be installed and
bootstrapping is really annoying.
I felt it was easier to just launch an AMI.....yet again, why not just
repackage another image.

The automated build nature of what I do requires me to repackage some lower
level libraries so they can link easily and stably (is that a word?) across
multiple packages.
I also have some longer term objectives that will require me to have
complete control over the kernel and packaging.
It just seemed easier to start my own thing for this.

Agree, this could prove insane. If that is the case, it wouldn't be *too*
hard for me to convert this to some package repo

On Thu, May 3, 2012 at 9:53 AM, Darren Govoni wrote:

> A distro would be good and if it was made into an Amazon Machine Image so
> we can spin it up and use it _without_ having to install it, that's a good
> thing too.
>
> So the best approach is always both!
>
>


------- Original Message -------
> On 5/3/2012 11:42 AM Dan Brickley wrote:
On 3 May 2012 18:34, Ted
> Dunning wrote:
>
> Thanks for including Mahout.
>
>
>
> As a point of strategy, wouldn't have better to just build a debian
> package
>
> repository and a script for installing packages? That would allow
> people
>
> to use their own debian or ubuntu based distros for their own
> special needs
>
> such as hardware virtualization or special kernel modules and still
> get the
>
> benefits that you are offering.
>
>
>
> Otherwise, you are sentencing yourself to a life of hard labor
> keeping up
>
> with kernel updates and such.
>

>
I was about to ask the same question... why a whole distro? Unless the
>
whole thing is a highly-tuned and unusual setup, some install scripts
>
are often good enough.
>

>
Dan
>

>

>