I do not understand where busybox may at fault. You have a system with bb as base, you use dialog and you see something is odd with the display.
where is busybox in that equation ? re, wh Peter Scheie schrieb: > 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. For the record, I also booted the ISO on read > hardware and dialog had the same problem there. Another data point: My > build system is a Centos 5 virtual machine running on VirtualBox. The > above behavior is what I see when logged into the vm's console. If I > ssh to the vm, and then chroot into the build directory, dialog looks > fine. The difference, of course, is that TERM=xterm in the SSH session, > whereas when I'm working at the console, TERM=linux. > > Any suggestions as to what might be wrong or where to look? Thanks. > > Peter > > _______________________________________________ > busybox mailing list > [email protected] > http://lists.busybox.net/mailman/listinfo/busybox > > _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
