Re: [Leaf-devel] Updating Eigerstein:progress

2001-05-14 Thread David Douthitt
Ewald Wasscher wrote: It appears that busybox more segfaults when compiled with the slink egcc, which is egcs-2.91.60, _and_ only when the lines it is fed don't fit on the screen. Recompiling with gcc-2.7.2.3 solved this. Interesting! I've been compiling busybox these days under Red Hat 6.2

Re: [Leaf-devel] Updating Eigerstein:progress

2001-05-14 Thread Ewald Wasscher
David Douthitt wrote: Ewald Wasscher wrote: It appears that busybox more segfaults when compiled with the slink egcc, which is egcs-2.91.60, _and_ only when the lines it is fed don't fit on the screen. Recompiling with gcc-2.7.2.3 solved this. Perhaps I should try again with gcc-2.95.3, and

Re: [Leaf-devel] Updating Eigerstein:progress

2001-05-14 Thread David Douthitt
Ewald Wasscher wrote: David Douthitt wrote: I've been compiling busybox these days under Red Hat 6.2 using egcs-2.90.29 (egcs release 1.0.3). Perhaps I should upgrade? That's up to you of course, but if your current compiler works properly (I thought your segfualt issues were solved),

Re: [Leaf-devel] Updating Eigerstein:progress

2001-05-14 Thread Mike Noyes
David Douthitt, 2001-05-14 11:19 -0500 Ewald Wasscher wrote: David Douthitt wrote: I've been compiling busybox these days under Red Hat 6.2 using egcs-2.90.29 (egcs release 1.0.3). Perhaps I should upgrade? That's up to you of course, but if your current compiler works properly (I

Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-30 Thread KP Kirchdörfer
Am Montag, 30. April 2001 03:08 schrieben Sie: [EMAIL PROTECTED] wrote: On 23 Apr 2001, at 19:47, Ewald Wasscher wrote: KP Kirchdörfer wrote: Unfortunately I do experience segfaults now with busybox more. It seems that when it gets an input line longer than approx. 78 (don't know the

Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-30 Thread Ewald Wasscher
[EMAIL PROTECTED] wrote: On 30 Apr 2001, at 2:08, Ewald Wasscher wrote: [EMAIL PROTECTED] wrote: On 22 Apr 2001, at 14:34, Ewald Wasscher wrote: 22-4TODO: update all binaries to the _latest_ versions available? Is this a good idea? That will probably use some additional diskspace

Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-29 Thread ssrat
On 25 Apr 2001, at 21:02, KP Kirchdörfer wrote: Is the only choice between Scylla (vi-mode) and Charybdis (wasting disk space)? e3ws, e3vi, e3ne, e3em, et al, are just links to e3; in Oxygen you need to be careful as the actual binary is e3.bin, with a shell wrapper and all the links point to

Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-29 Thread ssrat
On 23 Apr 2001, at 19:47, Ewald Wasscher wrote: KP Kirchdörfer wrote: 21-4updated busybox to version 0.51 I'm running eigerstein with busybox 0.51 (and replaced most of the POSIXness links and other progs with busybox and tinylogin), but as long as we see the seg fault in 'busybox

Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-29 Thread Ewald Wasscher
[EMAIL PROTECTED] wrote: On 22 Apr 2001, at 14:34, Ewald Wasscher wrote: replace gunzip with zcat My understanding is that zcat is: #!/bin/sh gunzip -c $1 Of course, but it's also an alias for the gunzip applet in busybox. 22-4add e3 (the pre 1.5 from oxygen) as the

Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-29 Thread Ewald Wasscher
[EMAIL PROTECTED] wrote: On 23 Apr 2001, at 19:47, Ewald Wasscher wrote: KP Kirchdörfer wrote: 21-4updated busybox to version 0.51 I'm running eigerstein with busybox 0.51 (and replaced most of the POSIXness links and other progs with busybox and tinylogin), but as long as we see

Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-29 Thread ssrat
On 30 Apr 2001, at 2:08, Ewald Wasscher wrote: [EMAIL PROTECTED] wrote: On 22 Apr 2001, at 14:34, Ewald Wasscher wrote: 22-4TODO: update all binaries to the _latest_ versions available? Is this a good idea? That will probably use some additional diskspace Yes, definitely. Fixes

Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-25 Thread George Metz
On Mon, 23 Apr 2001, Eric Wolzak wrote: The problem was that the exclude option overrides the include option. Snip! I used the following command tar -c -v `cat $INCLUDE` -X $EXCLUDE | gzip $DIR/$PACKAGE.lrp So, uh, call me stupid and feel free to point and laugh and stuff, but can't

Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-25 Thread KP Kirchdörfer
Am Montag, 23. April 2001 20:41 schrieben Sie: KP Kirchdörfer wrote: 22-4add e3 (the pre 1.5 from oxygen) as the default editor Is this a version of e3, which don't make a backup of the original file? This feature of e3 is just wasting space, especially within lrcfg. I just

Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-24 Thread Ewald Wasscher
Eric Wolzak wrote: Too bad. Probably I won't have much luck, but I'll try anyway :-) be carefull with root.lrp. I used tar and everything did backup fine. Only root caused a real trouble. I experimented with this for some time a summary of my post: The problem was that the

Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-24 Thread KP Kirchdörfer
Am Dienstag, 24. April 2001 09:25 schrieb Ewald Wasscher: I use it.also without problem this is my busybox list: basename, busybox, cat, chgrp, chmod, chown, clear, cp, cut, date,dd, df, dirname, dmesg, du, dutmp, echo, egrep, expr, false,fdflush,find, free, grep, gunzip, gzip, halt,

Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-24 Thread KP Kirchdörfer
Am Montag, 23. April 2001 20:41 schrieben Sie: KP Kirchdörfer wrote: Am Sonntag, 22. April 2001 15:31 schrieb Ewald Wasscher: 21-4updated busybox to version 0.51 I'm running eigerstein with busybox 0.51 (and replaced most of the POSIXness links and other progs with busybox and

Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-24 Thread Ewald Wasscher
Ewald Wasscher wrote: I compile on a debian slink install with all of the updates. The compiler I used was egcc which is gcc-2.91.60 iirc. Duh, that means glibc-2.0.7 of course Ewald Wasscher ___ Leaf-devel mailing list [EMAIL PROTECTED]

Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-24 Thread KP Kirchdörfer
Am Dienstag, 24. April 2001 20:06 schrieben Sie: KP Kirchdörfer wrote: I'm running eigerstein with busybox 0.51 (and replaced most of the POSIXness links and other progs with busybox and tinylogin), but as long as we see the seg fault in 'busybox more' it's not ready for prime time -

Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-23 Thread Ewald Wasscher
KP Kirchdörfer wrote: Am Sonntag, 22. April 2001 15:31 schrieb Ewald Wasscher: 21-4updated busybox to version 0.51 I'm running eigerstein with busybox 0.51 (and replaced most of the POSIXness links and other progs with busybox and tinylogin), but as long as we see the seg fault

Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-23 Thread Charles Steinkuehler
Might I add to the TODO-list, to include Seawall? What does Charles think about that? For most home-users the default Eigerstein firewall rules will be sufficient I suppose. For an updated EigerStein image, the current firewall scripts should remain, or migrate to something like my

Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-23 Thread Eric Wolzak
Ewald wrote KP Kirchd=F6rfer wrote: Am Sonntag, 22. April 2001 15:31 schrieb Ewald Wasscher: 21-4updated busybox to version 0.51 I'm running eigerstein with busybox 0.51 (and replaced most of the POS= IXness links and other progs with busybox and tinylogin), but as

Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-22 Thread Ewald Wasscher
Charles Steinkuehler wrote: Wow! Progress!!! Below you'll find a list of all the changes I have made so far in the process of producing an updated version of Eigerstein2BETA. Feedback is of course appreciated. I also wonder if it's possible to compile tinylogin with md5 passwords (good

Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-22 Thread KP Kirchdörfer
Am Sonntag, 22. April 2001 15:31 schrieb Ewald Wasscher: 21-4updated busybox to version 0.51 I'm running eigerstein with busybox 0.51 (and replaced most of the POSIXness links and other progs with busybox and tinylogin), but as long as we see the seg fault in 'busybox more' it's not