From owner-freebsd-hackers@freebsd.org Mon Feb 20 13:49:19 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 78DE9CE5AE8 for ; Mon, 20 Feb 2017 13:49:19 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3CAFA1CF9; Mon, 20 Feb 2017 13:49:19 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cfoL0-0006uz-HH; Mon, 20 Feb 2017 16:49:10 +0300 Date: Mon, 20 Feb 2017 16:49:10 +0300 From: Slawa Olhovchenkov To: freebsd-hackers@freebsd.org, allanjude@freebsd.org Subject: Re: GSoC Project Involving the reimplementation of beadm(1) Message-ID: <20170220134910.GC15630@zxy.spb.ru> References: <20170220131509.GA31623@tomoyat1.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170220131509.GA31623@tomoyat1.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Feb 2017 13:49:19 -0000 On Mon, Feb 20, 2017 at 10:15:09PM +0900, Tomoya Tabuchi wrote: > Hello, > > I am interested in doing a GSoC project this year with the idea "Write a > new boot environment manager" on the ideas list. > (https://wiki.freebsd.org/SummerOfCodeIdeas#Write_a_new_boot_environment_manager) > > I would like to ask a few questions involving this. > First, is there a particular reason why this project is listed in the > ideas list? Aside the fact the current implementation in sh is rather > complicated, I was unable to come up with a reason to justify the > reimplementation. > > Second, is making the new implmentation of beadm(1) platform independent > and promoting it across the various OpenZFS implmentation / communities > as some sort of "standard" implmentation a good idea, or is it > over-zealous / outside of the project scope / intrusive to other > projects. > > As for a late self introduction, my name is Tomoya Tabuchi, and I am a > undergraduate student at Doshisha University in Japan. I will start my > third year in university in April. Don't know about link above. For me, current beadm have some leaks: 1. Don't check cosistency before applay: I am try to enable beadm on 10.1 install and switch to 11.0. fail. 2. Need to control what put under beadm. All of this don't need to rewrite all beadm, IMHO.