From owner-freebsd-current@freebsd.org Mon Apr 25 04:17:01 2016 Return-Path: Delivered-To: freebsd-current@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 E3357B1B4C7 for ; Mon, 25 Apr 2016 04:17:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A87051BA5 for ; Mon, 25 Apr 2016 04:17:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ig0-x22f.google.com with SMTP id u10so573845igr.1 for ; Sun, 24 Apr 2016 21:17:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=56d6+vwnNdDaJFDfFv/oZdYjTpevGgUAbHeaI4/ycAE=; b=JpdNEhAb55K8mXqC68U9vo5tIDDMa6fMVyPjiLpSLszmy0+yvZhXJgvRd1YRxyABkQ ytO/kEYL6ztKHSFcWpNMkfBrYttKPjzXFCwPPxSAddKEyw6poo7Zn4ay4n4mKMc/hKhJ 6ehxc7+yUvSJGTRfGAtxbB/IHB1c3TU+RF5l3G2A59wjUhG7PBXn8FAZUG9iVCWYfRWn /6Y8czzd66D9ZiRrFG94FLvkdLKYfAQse07pLe2rpFEx/c1HoxGGRt8+cr76xbun82xD FGMywvvFrarXD0E0D5SbEYUuBL67P5E4bNIvODfDy3rqVeX119f9r3KG+rqH0/cRXZOd ZmBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=56d6+vwnNdDaJFDfFv/oZdYjTpevGgUAbHeaI4/ycAE=; b=csoDgplvbOudqDmIjiXkYe/tleTh5J+zBrG9AxL3YwHIVnasjM/El/fwH3gqLWgLyJ 6VzgDdyhaIHBrYmu/S9rwLbOIUKeJaky73htJnBY8IARGqJPXjDkdf4ByAZ5GBVAtvBT gTmkpu/I14axfWh/S2T3mP2r5jUnLVdghiPuCYrtQHJna2JWDq9pY4vz0GeGhxjZHJlj IbkftUkAi5k/WbHeAnDVvwdAXv4yIBFOdRmLvAESbmUwLsIljNLd0HNUXL+c3Mu+uTZw em+KcjcPboCY0KnM24qPURW0/UfXgZpvMKMkdOendf14u8CXGH7M7PYAMl8CsWFqBwRT ofdw== X-Gm-Message-State: AOPr4FVQIZSFwvIdho52xSq9islu7VLrZYzgVPuD+UzV/9bcbIjpHammbVppjTQXvNi9KvSEKxUZQKQCQBOCNw== MIME-Version: 1.0 X-Received: by 10.50.247.147 with SMTP id ye19mr3229103igc.16.1461557821065; Sun, 24 Apr 2016 21:17:01 -0700 (PDT) Sender: wlosh@bsdimp.com Received: by 10.79.104.197 with HTTP; Sun, 24 Apr 2016 21:17:01 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: References: <76093.1461096570@critter.freebsd.dk> <5716AD65.8070007@shrew.net> Date: Sun, 24 Apr 2016 22:17:01 -0600 X-Google-Sender-Auth: 8f-UVP3MVyPUO3oFvBhdhmssVxE Message-ID: Subject: Re: NanoBSD (Was Re: [CFT] packaging the base system with pkg(8)) From: Warner Losh To: Daniel Eischen Cc: FreeBSD Current Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2016 04:17:02 -0000 On Sun, Apr 24, 2016 at 12:14 PM, Daniel Eischen wrote: > On Sun, 24 Apr 2016, Warner Losh wrote: > > On Sun, Apr 24, 2016 at 6:34 AM, Daniel Eischen >> wrote: >> >> On Sat, 23 Apr 2016, Warner Losh wrote: >>> >>> On Sat, Apr 23, 2016 at 7:51 AM, Daniel Eischen >>> >>>> wrote: >>>> >>>> [CC trimmed] >>>> >>>>> >>>>> On Fri, 22 Apr 2016, Warner Losh wrote: >>>>> >>>>> >>>>> I personally will be refraining from engaging further. I plan on seeing >>>>>> what gaps there are by adding support to NanoBSD for packages. I'll be >>>>>> busy >>>>>> with that. In talking to Glen and others, we've already identified a >>>>>> few >>>>>> easy gaps to fill. Once they've done that, I'll get going on NanoBSD >>>>>> with >>>>>> the goal to be able to use it to build a bootable system of any >>>>>> architecture from packages with no root privs. I expect to find >>>>>> issues, >>>>>> but >>>>>> I don't expect to find any issue that's intractable. I expect after >>>>>> the >>>>>> issues are resolved, the end product will be better for everybody. >>>>>> >>>>>> >>>>>> Thank you for working on NanoBSD. Do you think it would be possible >>>>> to add support for optionally building dump(8) images instead of dd? >>>>> >>>>> >>>> >>>> What do you mean by that, exactly? It would be relatively easy to add >>>> a step that runs dump on the _.disk.image file and squirrel that away. >>>> Last orders the code currently calls it, I believe. Is it something as >>>> simple >>>> as this, or is there some more complexity that I'm failing to understand >>>> or grasp? >>>> >>>> >>> Perhaps I'm missing something, but when last_orders() is called, >>> isn't the disk already unmounted and 'mdconfig -d -u' already >>> run? >>> >> >> >> dump 0f - _.disk.image > ~/foo.dump >> >> worked for me just now. Is there some reason that it wouldn't work for >> you in last orders if you tossed a NANO_DISKIMGDIR in front of it >> and last orders would work for you. You could even pipe it into some >> compression program... >> > > Huh, I didn't know you could do that on the image file. > I feel dumb, now ;-) Don't feel too dumb. If I specify foo.dump as the filename, dump kinda loses its mind when it gets to the end of file. Not sure why. Warner