Date: Thu, 16 Dec 2010 13:47:44 +1100 (EST) From: Ian Smith <smithi@nimnet.asn.au> To: =?ISO-8859-1?Q?Samuel_Mart=EDn_Moro?= <faust64@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: boot, rc script and logs Message-ID: <20101216125341.P83735@sola.nimnet.asn.au> In-Reply-To: <AANLkTinRDa89gH5jXMeDkTbdu9yrLGcNev7YK15dUauw@mail.gmail.com> References: <20101214180343.F008310656F6@hub.freebsd.org> <20101215140116.M83735@sola.nimnet.asn.au> <AANLkTinRDa89gH5jXMeDkTbdu9yrLGcNev7YK15dUauw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-189344276-1292465235=:83735 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Transfer-Encoding: 8BIT Content-ID: <20101216130741.B83735@sola.nimnet.asn.au> On Wed, 15 Dec 2010 15:42:29 +0100, Samuel Martín Moro wrote: > On Wed, Dec 15, 2010 at 4:57 AM, Ian Smith <smithi@nimnet.asn.au> wrote: [..] > > > Dec 14 13:26:47 camtrace13 kernel: ^[[m > > > Dec 14 13:26:47 camtrace13 kernel: ^[[39;49m^[[=1S > > > Dec 14 13:26:47 camtrace13 kernel: > > > > > ^[[39;49m^[[m^[[H^[[J^[[17d^[[36m^[[44m^[[1m^[[J^[[H^[[K^[[B^[[K^[[B^[[K^[[B^[[K^[[B^[[K^[[B^[[K^[[B^[[K^[[B^[[K^[[B > > * > ^[[37m^[[**47m˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙** > > ˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙[[m^[[30m^[[47m˙˙[[m^[[**36m^[[44m^[[1m^[[K^[[B* > > > err.. we may have a encoding problem. Indeed. I originally quoted yours from a digest, which are text-only, US-ASCII. Your reply has your name in ISO-8859-1, but both text and HTML parts in UTF-8. I expect this reply (with your i-acute correct) will be text-only, ISO-8859-1. pine does its best, but gmail confuses it; I don't know if not also sending HTML parts to the list may help, as mailman drops non-plaintext attachments, including HTML, anyway. > but I'm quite sure it only is clearscreen, colors, and tputs stuff > > > > ^[[37m^[[47m˙˙[[m^[[30m^[[47m^[[68X^[[74`˙˙[[m^[[30m^[[40m^[[1m > > > ^[[36m^[[44m^[[K^[[B ^[[37m^[[47m˙˙[[m^[[30m^[[47m Checking DB > > > 1/2^[[20X^[[74`˙˙[[m^[[30m^[[40m^[[1m ^[[36m^[[44m^[[K^[[B > > [..] > > > Dec 14 13:26:48 camtrace13 kernel: Starting slim. > > > Dec 14 13:26:48 camtrace13 kernel: Starting > > > > > You'll need to rework this somehow so dialog's stdout isn't written to > > /dev/console, though that may seem necessary if you want it coming up on > > the VTY0 boot screen. It may involve decoupling this task from running > > 'inline' as a boot script somehow, or else making sure that output is > > redirected to a log or temporary file instead of directly into dialog. > > > mmmmkay. > It's now fixed. > OUT=`/sbin/conscontrol | /usr/bin/sed -n 's;^Configured: .*\(tty[^,]*\).*$;/dev/\1;p'` > (is it always /dev/ttyv0? in doubt, I'll trust conscontrol) > [...] $DIALOG [...] >$OUT Ah, bien. Yes I think it'll always be ttyv0 at that time, but that's an elegant solution. Thanks, we've both learned something! cheers, Ian --0-189344276-1292465235=:83735--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101216125341.P83735>