Date: Fri, 02 Jan 2009 10:19:44 -0500 From: Mike Tancsa <mike@sentex.net> To: freebsd-embedded@freebsd.org Subject: Re: Strange nanobsd issue Message-ID: <200901021519.n02FJn2E090929@lava.sentex.ca> In-Reply-To: <7.1.0.9.0.20070704124538.26bfe960@sentex.net> References: <7.1.0.9.0.20070704124538.26bfe960@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200901021519.n02FJn2E090929>