Message-ID: <1367412191.8951.10.camel@df1844j>
Subject: Re: [alpine-devel] alpine 2.6.0_rc1 is out - what do do with scst
 and vserver isos
From: Leonardo Arena <rnalrd@gmail.com>
To: alpine-devel <alpine-devel@lists.alpinelinux.org>
Date: Wed, 01 May 2013 14:43:11 +0200
In-Reply-To: <20130501142905.2661cf85@ncopa-desktop.alpinelinux.org>
References: <20130501142905.2661cf85@ncopa-desktop.alpinelinux.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: list
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Wed, 2013-05-01 at 14:29 +0200, Natanael Copa wrote:
> Hi,
> 
> I have uploaded the 2.6.0_rc1 isos.
> 
> I wonder if we can kill the alpine-scst iso now?

I think yes. We have iSCSI target support (TCM) in default kernel and
its related target-cli util since v2.5 iirc. I'm running a box with TCM
since few months without any problem.


> What do we do with alpine-vserver isos?
> 
> Alternatives:
> 1) we kill it and tell users to use LXC
> 2) we ship it with an old kernel
>   2.1) downgrade to LTS 3.4.y
>   2.2) do nothing, keep the current, outdated 3.6.y
>   2.3) we try port vserver to 3.9 or same as grsec.
> 
> Personally, I think I would prefer alternative 2.1. We still use
> vserver in production (build servers) and we don't have any good
> migration plan for vserver -> LXC.
> 
> I also don't think there are many vserver users that wants the new
> fancy stuff in newer kernels, so i think reverting to an older 3.4.y
> kernel might work. Sticking to LTS kernels saves us for much work.
> 
> What do you think?

+1

- leo



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---