[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

[leaf-user] Bering-uClibc, Openswan and ifconfig

2011-02-09 Thread Michal Kepien
Greetings, I'm trying to get Openswan running on a test Bering-uClibc 4.0 beta 2 installation. Unfortunately, the init scripts for IPSec rely heavily on ifconfig, which is not included in the system by default. I've been searching both for a Bering-uClibc package containing ifconfig and for a

Re: [leaf-user] Bering-uClibc, Openswan and ifconfig

2011-02-09 Thread KP Kirchdoerfer
Am Mittwoch, 9. Februar 2011, um 18:13:11 schrieb Michal Kepien: > Greetings, > > I'm trying to get Openswan running on a test Bering-uClibc 4.0 beta 2 > installation. Unfortunately, the init scripts for IPSec rely heavily on > ifconfig, which is not included in the system by default. I've been >