Hello List! First, thanks to developers for bringing up version 4.
Testing Bering-uClibc_4.0-beta2_i486_syslinux_ser.tar.gz on PCEngines WRAP I noticed some strange behaviour which was annoying. Never before since version 2 have I noticed such a behaviour although I am testing Beta 2 in an exactly the same environment. 1. On boot, a fresh Beta 2 stops at "boot:" prompt and seems to wait forever. My syslinux is ver. 3.63. The docs say that setting syslinux parameter TIMEOUT to 0 disables timeout (this is the default value) indicating that the boot sequence should start automatically. On previous versions of uClibc Bering it did, on Beta 2 it does not, at least not on my setup. Changing this parameter to anything else than 0 enables auto-boot after the timeout. Here is a link to a snapshot of a HyperTerminal in the waiting state: http://www.erjavec.info/uClibcBering/Startup.jpg with the following syslinux.cfg configuration: -------------------- SERIAL 0 19200 DISPLAY syslinux.dpy TIMEOUT 0 APPEND reboot=bios console=ttyS0,19200n8 VERBOSE=1 DEFAULT /syslinux/linux initrd=/initrd.lrp rw root=/dev/ram0 LEAFCFG=/dev/sda1:vfat -------------------- This is OK for me but a new user might have problems with it when switching from a serial console to SSH console. 2. When editing config files, either in lrcfg or directly from a command line (with edit), I am getting inserted 3 characters, sometimes 5 at the very beginning of the first edited file. The common part of the strings is ';3R'. This happens in all cases: through HyperTerminal, through TeraTerm Pro (both serial), and through SSH terminal. Link: http://www.erjavec.info/uClibcBering/ssh-file-editing.jpg Link: http://www.erjavec.info/uClibcBering/editor-HyperTerminal.jpg Previous versions of uClibc Bering never did that to me. There seems to be something wrong also specifically in the serial communications, since HyperTerminal receives strange characters when quitting an edited file or when hopping between the menus in lrcfg. Eventually it drops out of lrcfg onto the command line. See snapshot: http://www.erjavec.info/uClibcBering/HyperTerminal-communication.jpg Since other users did not report that, it could be also something that I did wrong or my WRAP, although before I never noticed it with other uClibc Berings on the same hardware. 3. I'd appreciate an info on when asterisk package would be available for ver 4.0. Or, alternatively, if there is going to be available a compatibility library for using ver 3.x packages on 4.0 (as it used to be in ver 3.x for packages 2.x). Cheers, and thank you for keeping the excelent Bering platform alive, Tom ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
