X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from ncopa-desktop.alpinelinux.org (3.203.202.84.customer.cdi.no [84.202.203.3]) (using SSLv3 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nc@alpinelinux.org) by mail.alpinelinux.org (Postfix) with ESMTPSA id 56DCEDC076F for ; Wed, 1 May 2013 12:29:09 +0000 (UTC) Date: Wed, 1 May 2013 14:29:05 +0200 From: Natanael Copa To: alpine-devel@lists.alpinelinux.org Subject: [alpine-devel] alpine 2.6.0_rc1 is out - what do do with scst and vserver isos Message-ID: <20130501142905.2661cf85@ncopa-desktop.alpinelinux.org> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.17; x86_64-unknown-linux-gnu) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi, I have uploaded the 2.6.0_rc1 isos. I wonder if we can kill the alpine-scst iso now? 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? -nc --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---