[leaf-user] uClibc Bering 4.0 Beta 2: unusual behaviour

2011-02-09 Thread Tom Erjavec
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 exac

Re: [leaf-user] uClibc Bering 4.0 Beta 2: unusual behaviour

2011-02-09 Thread KP Kirchdoerfer
Hello Tom; Am Mittwoch, 9. Februar 2011, um 13:16:41 schrieb Tom Erjavec: > 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

Re: [leaf-user] uClibc Bering 4.0 Beta 2: unusual behaviour

2011-02-09 Thread Bodo Meissner
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 09.02.2011 13:16, schrieb Tom Erjavec: > 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. > Link: http://www

Re: [leaf-user] uClibc Bering 4.0 Beta 2: unusual behaviour

2011-02-10 Thread Tom Erjavec
On 10.2.2011 5:44, leaf-user-requ...@lists.sourceforge.net wrote: >> 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) >> > in

Re: [leaf-user] uClibc Bering 4.0 Beta 2: unusual behaviour

2011-02-11 Thread Bodo Meissner
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 10.02.2011 13:18, schrieb Tom Erjavec: > > Thanks, kp and Bodo. I will try to look about the emulation type. But > these same terminal setups of either of Teraterm, Hyperterminal or SSH, > work perfectly well with uClibc Bering 3.1 half a meter awa

Re: [leaf-user] uClibc Bering 4.0 Beta 2: unusual behaviour (Bodo Meissner)

2011-02-16 Thread Tom Erjavec
Hi Bodo, I tested the "escape sequence" problem with PuTTY terminal and it works fine. $TERM is set to vt100. It works OK regardless of being set to expect 8859-1, 8859-2 or UTF-8 from Bering. However I have not figured why PuTTY behaves well with 4.0, while others I tried don't. All of them, incl

Re: [leaf-user] uClibc Bering 4.0 Beta 2: unusual behaviour (Bodo Meissner)

2011-02-16 Thread davidMbrooke
On Wed, 2011-02-16 at 14:53 +0100, Tom Erjavec wrote: > Hi David, > with Asterisk I am currently after SIP/eth only. The Outside world at a > later time. Hi Tom. Thanks. That means we probably only need the "asterisk" package, not also DAHDI, bristuff etc. which should be easier to implement and m