From owner-freebsd-embedded@FreeBSD.ORG Mon Oct 18 11:06:55 2010 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 D81801065673 for ; Mon, 18 Oct 2010 11:06:55 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C52E98FC13 for ; Mon, 18 Oct 2010 11:06:55 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o9IB6tio029294 for ; Mon, 18 Oct 2010 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o9IB6tYg029292 for freebsd-embedded@FreeBSD.org; Mon, 18 Oct 2010 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 18 Oct 2010 11:06:55 GMT Message-Id: <201010181106.o9IB6tYg029292@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-embedded@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org 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: Mon, 18 Oct 2010 11:06:55 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o misc/136889 embedded [nanobsd] [path] nanobsd error reporting and other ref o misc/52256 embedded [picobsd] picobsd build script does not read in user/s o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ppp/* after c 3 problems total. From owner-freebsd-embedded@FreeBSD.ORG Tue Oct 19 00:23:20 2010 Return-Path: Delivered-To: embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A566F106564A for ; Tue, 19 Oct 2010 00:23:20 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from vps.hungerhost.com (vps.hungerhost.com [216.38.53.176]) by mx1.freebsd.org (Postfix) with ESMTP id 783A78FC13 for ; Tue, 19 Oct 2010 00:23:20 +0000 (UTC) Received: from smtp.hudson-trading.com ([209.249.190.9] helo=gnnmac.hudson-trading.com) by vps.hungerhost.com with esmtpa (Exim 4.69) (envelope-from ) id 1P7vNV-0003dZ-2G; Mon, 18 Oct 2010 15:28:13 -0400 Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: George Neville-Neil In-Reply-To: <20101015232651.GA21557@freebsd81-1.ip-plus.net> Date: Mon, 18 Oct 2010 15:28:12 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20101015232651.GA21557@freebsd81-1.ip-plus.net> To: Patrick Oeschger X-Mailer: Apple Mail (2.1081) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vps.hungerhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - neville-neil.com X-Source: X-Source-Args: X-Source-Dir: Cc: embedded@freebsd.org Subject: Re: FreeBSD on Gumstix Overo / Beagle Board (TI OMAP3530) 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: Tue, 19 Oct 2010 00:23:20 -0000 On Oct 15, 2010, at 19:26 , Patrick Oeschger wrote: > anybody interested in porting freebsd to > - gumstix overo = (http://www.gumstix.com/store/catalog/index.php?cPath=3D27)? > - beagle board (http://beagleboard.org/project)? >=20 > both boards are based on texas instruments OMAP35x (ARM Cortex based) > guess both boards would be fun to run freebsd on it > especially the gumstix 'stick' which is really small (see link) > running at 600mhz and offers (onboard): > - 256mb ram > - 256mb flash > - microSD slot > - bluetooth / wlaa > - 600mhz TI OMAP3530 processor >=20 Yup, definitely interested. I've redirected this to the = embedded@freebsd.org alias where such boards are frequently discussed. Best, George PS I'm waiting for the latest beagle board (XM) to arrive. From owner-freebsd-embedded@FreeBSD.ORG Thu Oct 21 12:19:26 2010 Return-Path: Delivered-To: embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7AE0106566C for ; Thu, 21 Oct 2010 12:19:26 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from ftp.translate.ru (ftp.translate.ru [80.249.188.42]) by mx1.freebsd.org (Postfix) with ESMTP id 95ADF8FC1C for ; Thu, 21 Oct 2010 12:19:26 +0000 (UTC) Received: from desktop.home.serebryakov.spb.ru (89.112.15.178.pppoe.eltel.net [89.112.15.178]) (Authenticated sender: lev@serebryakov.spb.ru) by ftp.translate.ru (Postfix) with ESMTPA id D58E113DF46 for ; Thu, 21 Oct 2010 16:01:54 +0400 (MSD) Date: Thu, 21 Oct 2010 16:01:52 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <1054626238.20101021160152@serebryakov.spb.ru> To: embedded@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: Subject: NanonBSD & chrooted named (with zones in /var) - is here any good solution? 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: Thu, 21 Oct 2010 12:19:26 -0000 Hello, Embedded. What is proper, NanoBSD-canonic, way to add named to NanoBSD installation? /etc is overwritten from /cfg (after /conf/base), but /var is only created from /conf/base, and typical "edit, mount /etc, copy to /etc, unmount /etc" pattern will not work here, and it will be overwritten after slice upgrade. I could put all named chroot tree into DATA slice, but it is not elegant, because it should be mounted r/w. Maybe, here is good customization for this? --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-embedded@FreeBSD.ORG Thu Oct 21 13:19:18 2010 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 6D2DE106566C; Thu, 21 Oct 2010 13:19:18 +0000 (UTC) (envelope-from fb-embedded@psconsult.nl) Received: from mx1.psconsult.nl (unknown [IPv6:2001:7b8:30f:e0::5059:ee8a]) by mx1.freebsd.org (Postfix) with ESMTP id 1F4078FC1A; Thu, 21 Oct 2010 13:19:17 +0000 (UTC) Received: from mx1.psconsult.nl (psc11.adsl.iaf.nl [80.89.238.138]) by mx1.psconsult.nl (8.14.4/8.14.4) with ESMTP id o9LDJBnK032644 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Oct 2010 15:19:16 +0200 (CEST) (envelope-from fb-embedded@psconsult.nl) Received: (from paul@localhost) by mx1.psconsult.nl (8.14.4/8.14.4/Submit) id o9LDJB4X032643; Thu, 21 Oct 2010 15:19:11 +0200 (CEST) (envelope-from fb-embedded@psconsult.nl) X-Authentication-Warning: mx1.psconsult.nl: paul set sender to fb-embedded@psconsult.nl using -f Date: Thu, 21 Oct 2010 15:19:11 +0200 From: Paul Schenkeveld To: freebsd-embedded@freebsd.org, embedded@freebsd.org Message-ID: <20101021131911.GA32168@psconsult.nl> References: <1054626238.20101021160152@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1054626238.20101021160152@serebryakov.spb.ru> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: Subject: Re: NanonBSD & chrooted named (with zones in /var) - is here any good solution? 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: Thu, 21 Oct 2010 13:19:18 -0000 On Thu, Oct 21, 2010 at 04:01:52PM +0400, Lev Serebryakov wrote: > Hello, Embedded. > > What is proper, NanoBSD-canonic, way to add named to NanoBSD > installation? /etc is overwritten from /cfg (after /conf/base), but > /var is only created from /conf/base, and typical "edit, mount /etc, > copy to /etc, unmount /etc" pattern will not work here, and it will be > overwritten after slice upgrade. What sort of nameserver do you want, a recursive nameserver without authority over any zone could run completely r/o. You need to set WITHOUT_BIND_MTREE while building NanoBSD and manually create the contents of /etc/namedb and copy them over to /cfg/namedb as well. An authoritative nameserver with only zones for which it is master and which you maintain manually could perfectly live in the /etc of a NanoBSD image. Build it like the recursice nameserver above. An authoritative nameserver with zones for which it is slave usually wants writable backing store to copy zones received from a master. This could be done similar to the setup for a recursive or master nameserver as described above but the cached zones will not be copied to /cfg/namedb automatically. Often this is not a problem if it only serves a handful of zones as it will check the serial number of any zones in the slave subdirectory (provided you synchronized to /cfg at some point) and transfer those from the master that are out of date (or not present at all). For nameservers with master zones that need to be changed frequently or by some sort of front-end tool and for nameservers with many slave zones the pure NanoBSD model with r/o root on flash and /etc and /var in a memory disk is not the perfect solution. Some people use NanoBSD on large servers that also have harddisks in them, in such cases creative solutions can be designed to place named data on real hard drives but I get the impression that you are talking about hardware without spinneng drives, right? > I could put all named chroot tree into DATA slice, but it is not > elegant, because it should be mounted r/w. If your drive is a flash disk mounting the data slice r/w for named to write to it completely ignores the whole reason why NanoBSD works the way it works, never automatically write to the flash drive to prevent it from wearing and guarantee that on power-up you always start with a known-to-be-good configuration. > Maybe, here is good customization for this? HTH. Regards, Paul Schenkeveld From owner-freebsd-embedded@FreeBSD.ORG Thu Oct 21 13:19:18 2010 Return-Path: Delivered-To: embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D2DE106566C; Thu, 21 Oct 2010 13:19:18 +0000 (UTC) (envelope-from fb-embedded@psconsult.nl) Received: from mx1.psconsult.nl (unknown [IPv6:2001:7b8:30f:e0::5059:ee8a]) by mx1.freebsd.org (Postfix) with ESMTP id 1F4078FC1A; Thu, 21 Oct 2010 13:19:17 +0000 (UTC) Received: from mx1.psconsult.nl (psc11.adsl.iaf.nl [80.89.238.138]) by mx1.psconsult.nl (8.14.4/8.14.4) with ESMTP id o9LDJBnK032644 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Oct 2010 15:19:16 +0200 (CEST) (envelope-from fb-embedded@psconsult.nl) Received: (from paul@localhost) by mx1.psconsult.nl (8.14.4/8.14.4/Submit) id o9LDJB4X032643; Thu, 21 Oct 2010 15:19:11 +0200 (CEST) (envelope-from fb-embedded@psconsult.nl) X-Authentication-Warning: mx1.psconsult.nl: paul set sender to fb-embedded@psconsult.nl using -f Date: Thu, 21 Oct 2010 15:19:11 +0200 From: Paul Schenkeveld To: freebsd-embedded@freebsd.org, embedded@freebsd.org Message-ID: <20101021131911.GA32168@psconsult.nl> References: <1054626238.20101021160152@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1054626238.20101021160152@serebryakov.spb.ru> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: Subject: Re: NanonBSD & chrooted named (with zones in /var) - is here any good solution? 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: Thu, 21 Oct 2010 13:19:18 -0000 On Thu, Oct 21, 2010 at 04:01:52PM +0400, Lev Serebryakov wrote: > Hello, Embedded. > > What is proper, NanoBSD-canonic, way to add named to NanoBSD > installation? /etc is overwritten from /cfg (after /conf/base), but > /var is only created from /conf/base, and typical "edit, mount /etc, > copy to /etc, unmount /etc" pattern will not work here, and it will be > overwritten after slice upgrade. What sort of nameserver do you want, a recursive nameserver without authority over any zone could run completely r/o. You need to set WITHOUT_BIND_MTREE while building NanoBSD and manually create the contents of /etc/namedb and copy them over to /cfg/namedb as well. An authoritative nameserver with only zones for which it is master and which you maintain manually could perfectly live in the /etc of a NanoBSD image. Build it like the recursice nameserver above. An authoritative nameserver with zones for which it is slave usually wants writable backing store to copy zones received from a master. This could be done similar to the setup for a recursive or master nameserver as described above but the cached zones will not be copied to /cfg/namedb automatically. Often this is not a problem if it only serves a handful of zones as it will check the serial number of any zones in the slave subdirectory (provided you synchronized to /cfg at some point) and transfer those from the master that are out of date (or not present at all). For nameservers with master zones that need to be changed frequently or by some sort of front-end tool and for nameservers with many slave zones the pure NanoBSD model with r/o root on flash and /etc and /var in a memory disk is not the perfect solution. Some people use NanoBSD on large servers that also have harddisks in them, in such cases creative solutions can be designed to place named data on real hard drives but I get the impression that you are talking about hardware without spinneng drives, right? > I could put all named chroot tree into DATA slice, but it is not > elegant, because it should be mounted r/w. If your drive is a flash disk mounting the data slice r/w for named to write to it completely ignores the whole reason why NanoBSD works the way it works, never automatically write to the flash drive to prevent it from wearing and guarantee that on power-up you always start with a known-to-be-good configuration. > Maybe, here is good customization for this? HTH. Regards, Paul Schenkeveld