From owner-freebsd-embedded@FreeBSD.ORG Fri Jan 2 15:47:32 2009 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 6CC3A1065689 for ; Fri, 2 Jan 2009 15:47:31 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id AD3338FC12 for ; Fri, 2 Jan 2009 15:47:29 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n02FJnHT065857 for ; Fri, 2 Jan 2009 10:19:50 -0500 (EST) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id n02FJn2E090929 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 2 Jan 2009 10:19:49 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200901021519.n02FJn2E090929@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 02 Jan 2009 10:19:44 -0500 To: freebsd-embedded@freebsd.org From: Mike Tancsa In-Reply-To: <7.1.0.9.0.20070704124538.26bfe960@sentex.net> References: <7.1.0.9.0.20070704124538.26bfe960@sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Subject: Re: Strange nanobsd issue 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, 02 Jan 2009 15:47:47 -0000 At 12:10 PM 7/4/2007, Mike Tancsa wrote: >I ran into a rather strange problem I dont understand. With my >nanobsd image, if I comment out > >hint.sio.0.flags="0x10" >or >hint.uart.0.flags="0x10" >from /boot/device.hints > >I get the RAM disks mounted twice ?! > >eg. > ># df >Filesystem 1K-blocks Used Avail Capacity Mounted on >/dev/ad0s1a 245239 98076 127544 43% / >devfs 1 1 0 100% /dev >/dev/md0 4526 1784 2380 43% /etc >/dev/md1 27990 124 25628 0% /var >/dev/md2 4526 1788 2376 43% /etc >/dev/md3 27990 436 25316 2% /var > >/boot.config is empty and /boot/loader.conf has > >hw.ata.ata_dma=0 >hw.ata.atapi_dma=0 >beastie_disable="YES" # Turn the beastie boot menu on and off >#comconsole_speed="19200" >#console="nullconsole" >autoboot_delay="4 > >having nullconsole doesnt seem to matter any. The device.hints >modification seems to be the single thing that effects this behavior. I accidentally found a work around to this issue while playing with a firewall console on a box with no serial ports. If I add to my stock NANOBSD image the boot loader option boot_multicons="YES" dcons_load="YES" The double mount issue goes away.... I havent found much documentation about multicons/dcons and its implications. Apart from a bit of RAM it uses for the kernel, are there any disadvantages of using it to work around the double mount issue ? ---Mike