From owner-freebsd-embedded@FreeBSD.ORG Fri Nov 25 23:56:09 2011 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 952521065672 for ; Fri, 25 Nov 2011 23:56:09 +0000 (UTC) (envelope-from milu@dat.pl) Received: from jab.dat.pl (dat.pl [80.51.155.34]) by mx1.freebsd.org (Postfix) with ESMTP id 513E88FC0C for ; Fri, 25 Nov 2011 23:56:08 +0000 (UTC) Received: from jab.dat.pl (jsrv.dat.pl [127.0.0.1]) by jab.dat.pl (Postfix) with ESMTP id 74235BD; Sat, 26 Nov 2011 00:37:11 +0100 (CET) X-Virus-Scanned: amavisd-new at dat.pl Received: from jab.dat.pl ([127.0.0.1]) by jab.dat.pl (jab.dat.pl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 7NuSgQBZoK5u; Sat, 26 Nov 2011 00:37:08 +0100 (CET) Received: from snifi.localnet (178-36-46-201.adsl.inetia.pl [178.36.46.201]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by jab.dat.pl (Postfix) with ESMTPSA id 4C57FA0; Sat, 26 Nov 2011 00:37:08 +0100 (CET) From: Maciej Milewski To: freebsd-embedded@freebsd.org Date: Sat, 26 Nov 2011 00:37:37 +0100 Message-ID: <15200024.qyaoOkNKT3@snifi> User-Agent: KMail/4.7.3 (Linux/3.1.1-1-ARCH; KDE/4.7.3; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: Subject: Re: tplink TL-WR1043ND access point is now ready (was Re: svn commit: r227926 - head/sys/mips/conf) X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2011 23:56:09 -0000 Dnia sobota, 26 listopada 2011 00:01:34 Stefan Bethke pisze: > Is there a read-write filesystem for the flash, or are we limited to an > archive in the cfg flash partition? For now it's only this cfg part. > I see that you went to some lengths creating your own config framework. Why > did you choose to not use the standard? I think that size and eventually building speed(during wireless development) > I haven't looked at nanobsd in ages, and I did see in the last status report > that there is another attempt at creating an OpenWrt-like setup. I'm > currently running about six or seven OpenWrt routers (mostly at the > extended family), and I'm interested in eventually replacing OpenWrt with > FreeBSD. Any guesses where a trimmed-down but fully functional (incl. > ports) distribution might emerge? NanoBSD is fine for many setups but it needed some tweaks to make crosscompiled images and it needs space which is rather short on such devices. greetings, Maciej Milewski