From owner-freebsd-arm@freebsd.org Thu Jul 11 19:11:43 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F29015DB9B6 for ; Thu, 11 Jul 2019 19:11:43 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D9A9E8D2D1; Thu, 11 Jul 2019 19:11:42 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-wm1-f48.google.com (mail-wm1-f48.google.com [209.85.128.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 85191194E7; Thu, 11 Jul 2019 19:11:42 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-wm1-f48.google.com with SMTP id a15so6693894wmj.5; Thu, 11 Jul 2019 12:11:42 -0700 (PDT) X-Gm-Message-State: APjAAAV63wHCnEoNwEd5RBBFzAQ76zDNhSIpIuS5EV6YVZLy3kPizpdO tC8KNkKTlDcdmciYzHel9crNmK7neq8e2nBh26w= X-Google-Smtp-Source: APXvYqzGNUMtuZoxhUFWzeutJiqY8l5yEaGzHPGJsISU/yelwhv8/AB0bf7sOc5gPMGVLQerXNmoWzycSShlGlj4Kic= X-Received: by 2002:a05:600c:c6:: with SMTP id u6mr5583615wmm.153.1562872301257; Thu, 11 Jul 2019 12:11:41 -0700 (PDT) MIME-Version: 1.0 References: <94eaa9c9-f826-b039-30c5-9161d163131a@net-art.cz> In-Reply-To: <94eaa9c9-f826-b039-30c5-9161d163131a@net-art.cz> From: Kyle Evans Date: Thu, 11 Jul 2019 14:11:29 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Few of my articles about FreeBSD on ARM To: Alex Samorukov Cc: Ian Lepore , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: D9A9E8D2D1 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.976,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jul 2019 19:11:43 -0000 On Thu, Jul 11, 2019 at 1:30 PM Alex Samorukov wrote: > > > On 11/07/2019 18:20, Ian Lepore wrote: > > > > [... snip ...] > > For the busybox stuff... are you aware of bsdbox? I don't know much > > about it, except that it existw. > > > > https://github.com/freebsd/freebsd/tree/master/tools/bsdbox > Looks interesting, but seems to be abandoned long time ago. There is > also toybox, which is a busybox-like but with a better license. Busybox > seems to be most active and commonly used in the Linux/embedded > projects, thats why i started with it. I will try to submit my patches > to upstream after finishing them. > May I ask what gives you this impression? bsdbox is actively used in freebsd-wifi-build by myself and at least a couple of others. It doesn't see a whole lot of active commits because unlike with Busybox, it's a crunch setup much like rescue -- there's not a whole lot to bsdbox specifically other than adding another PROG from base to build in. There are some programs that would be nice to have, but they just haven't been added yet for one reason or the other- most likely being that they just don't get used much in the limited environments that it's currently used in. Thanks, Kyle Evans