Hi Peter,
Kindly make use of the Carriage Return key a little more often. ;-)
I too have been using dialog with Busybox without issues... although I
find many desktop serial terminal emulators seem to be very poor VT100
implementations. Luckily, dialog has --ascii-lines.
On 10/07/10 01:14, Peter Scheie wrote **in a wall of text** (reformatted
by me):
> I've built an ISO image using busybox and a 2.6.18 kernel, and it's
> working fine, that is, it boots and I get a working shell (bash).
>
> Now
> I'm trying to add the dialog utility so I can construct some menus that
> will be used on the console. I added dialog and ncurses to my ISO, but
> while dialog runs, it doesn't look right, in that it appears something
> is wrong with the shadows and edges. I'm not sure if it's something to
> do with ncurses, or termcap, or what.
>
> I found that adding
> usr/lib/locale/locale-archive to the build directory for my ISO (the
> same directory to which I install BB) fixes the problem when I just
> chroot in my build directory and manually call dialog; but when I then
> build an ISO from that, boot it, and manually call dialog, it still has
> the same problem.
I don't think this is a Busybox issue, but rather quite possibly an
environment variable issue. dialog (or rather, ncurses) will be
influenced by a number of environment variables that dictate the
terminal type, terminal encoding and locale information. Check the
following:
- TERM (should be 'linux' on many consoles, vt100 on serial)
- LC_ALL (quite often unset... is in my case on Gentoo/AMD64)
- LOCALE ("C" is default if unset. In my case: en_au.UTF-8)
- LANG (Much the same as ${LOCALE})
--
Stuart Longland (aka Redhatter, VK4MSL) .'''.
Gentoo Linux/MIPS Cobalt and Docs Developer '.'` :
. . . . . . . . . . . . . . . . . . . . . . .'.'
http://dev.gentoo.org/~redhatter :.'
I haven't lost my mind...
...it's backed up on a tape somewhere.
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
