From owner-freebsd-hackers@freebsd.org Tue Feb 21 13:20:09 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 C4C48CE646E for ; Tue, 21 Feb 2017 13:20:09 +0000 (UTC) (envelope-from t@tomoyat1.com) Received: from mail.tomoyat1.com (tomoyat1.com [133.130.119.65]) (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 9B4231177 for ; Tue, 21 Feb 2017 13:20:09 +0000 (UTC) (envelope-from t@tomoyat1.com) Received: from tomoyat1.com (60-56-201-126f1.shg1.eonet.ne.jp [60.56.201.126]) by mail.tomoyat1.com (Postfix) with ESMTPSA id BE580176E for ; Tue, 21 Feb 2017 13:20:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tomoyat1.com; s=tomoyat1; t=1487683201; bh=T4q913wNbVOxYy0ZjCSo71HkcOQPqPZmzLX47e/sNNI=; h=Date:From:To:Subject:Message-ID:From:Sender:To:CC:Subject: Message-Id:Date; b=kaBtiWyu9gwxXP6/VBEBrKXwC5d/pSdd93UGAipfVAdAYAspYwJCFy8vqZDB/9msZ Y5AVvZsc520rQw6Fna1VZYp6SanW4ZAGkDOVfQrnxmNVge64SksSaQ3NwO9Gvetc/L N5TBjMhK+7nOjuQf2ce9JNR1o2Gq9KhV/3O+H1qw= Date: Tue, 21 Feb 2017 22:20:00 +0900 From: Tomoya Tabuchi To: freebsd-hackers@freebsd.org Subject: Re: GSoC Project Involving the reimplementation of beadm(1) Message-ID: <20170221132000.GA11545@tomoyat1.com> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20170220131509.GA31623@tomoyat1.com> <20170220134910.GC15630@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170220134910.GC15630@zxy.spb.ru> User-Agent: Mutt/1.5.24 (2015-08-30) 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: Tue, 21 Feb 2017 13:20:09 -0000 On Mon, Feb 20, 2017 at 04:49:10PM +0300, Slawa Olhovchenkov wrote: > 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. That is interesting. I'll try and see if I can reproduce that, and observe what's going on. > > 2. Need to control what put under beadm. Does this mean to hold back on feature bloat, or to distinguish between ZFS clones created by beadm and ones that were not? If you mean the latter, I'll take a look at the current behaviour when manually created ZFS clones are involved. > > All of this don't need to rewrite all beadm, IMHO. Thank you for your views. Tomoya