[leaf-user] Upgrading Leaf

Tom, You can read this link about some tools for upgrading: http://cvs.sourceforge.net/viewcvs.py/*checkout*/leaf/devel/alexrh/lck/READM E.html?rev=HEAD I didn't upgrade the tools since I uploaded them, though. Cheers Alex -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL

[leaf-user] RE: [leaf-devel] 2.4.26 kernel for wd1100.o

Hi! -Original Message- From: Victor McAllister [mailto:[EMAIL PROTECTED] Sent: Saturday, October 30, 2004 5:30 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [leaf-devel] 2.4.26 kernel for wd1100.o According to Erich Titl's instructions on LEAF. Quote: The Bering

Re: [leaf-user] Upgrading Leaf

On Sun, 2004-10-31 at 01:36, Alex Rhomberg wrote: Tom, You can read this link about some tools for upgrading: http://cvs.sourceforge.net/viewcvs.py/*checkout*/leaf/devel/alexrh/lck/READM E.html?rev=HEAD I didn't upgrade the tools since I uploaded them, though. Thanks, Alex -- I'll add a

[leaf-user] ipsec subnet-to-subnet vpn

Hi All, First of all, thanks to everyone involved with this project. The support from the mailing list archives is great! I've been trying to get an ipsec vpn between two bering-uclibc v2.2.1 routers going. Before boring everyone with the details, I'm wondering if there is a definitive

[leaf-user] lpthread.lrp backup error (Bering Uclibc 2.2.2)

I am getting the following error when I backup lpthread.lrp. Is this something I should be concerned with? Thanks in advance. Creating lpthread.lrp Please wait: \tar: var/lib/lrpkg/libpthread.*: No such file or directory tar: Error exit delayed from previous errors Back-up of lpthread complete

[leaf-user] beep.lrp question

Hello there. I have made a simple sh script to run beep for Bering Uclibc 2.2.2. I want the system to run the script to tell me when it is done booting. Can anyone please tell me where I need to go to do this? The how-to for beep.lrp is not very helpful in this regard? Thanks in advance! Troy

RE: [leaf-user] lpthread.lrp backup error (Bering Uclibc 2.2.2)

I corrected that in: /var/lib/lrpkg/lpthread.list Changed: var/lib/lrpkg/libpthread.* To: var/lib/lrpkg/lpthread.* Scott. - Scott Young Network Integration Solutions Inc. Phone: 780-461-3371 Fax: 780-465-7270 email: [EMAIL PROTECTED] -Original Message- From: [EMAIL

Re: [leaf-user] beep.lrp question

I use Beep for indicating the interfaces are up etc.. /bin/beep -f 600 -n -f 900 -n -f1200 -n -f1800 -f 600 -n -f 900 -n -f1200 - n -f1800 -f 600 -n -f 900 -n -f1200 -n -f1800 I found an article Simple Sounds for Linux By Jay Link ( do a google an yee shal find...) which I used as a rough

RE: [leaf-user] ipsec subnet-to-subnet vpn

Ok great! The setup is pretty straightforward. Please let me know if this helped you out. Here are some commented configs. :) I hope they are clear enough. Let me know if you need some points laid out better. First off, you need the following modules and packages: ipsec.lrp, libm.lrp,

Re: [leaf-user] beep.lrp question

i have a tencendy to put things into the /etc/init.d/rmnologin if it's just a 1 liner that needt to run at the end of the boot sequence. if it was more i'd make a separate /etc/init.d/beep, and add it to beep.lrp's file list to make it backup together with beep you can also do it with the 'up'

RE: [leaf-user] beep.lrp question

Ok lets say I have a little Beep tune written. I call it beep_song and I store it in /etc. It looks like this: {I chmod'ed it +rx} #!/bin/sh beep -f 1000 -r 2 -n -r 5 -l 10 --new beep -f 300.7 -r 3 -d 100 -l 400 beep -f 1000 -r 1 -n -r 5 -l 10 --new So I can play the little beep tune by typing