[leaf-devel] Quick and Dirty LRP Package How-To
Hey everybody, I have gotten to the Quick and Dirty LRP Package How-To and I have gotten stuck at step #6. When I go to back up the changes to create the zebra.lrp it does not show an option for zebra in the Back-up menu. 5. Trick LRP into thinking your package is installed by editing /var/lib/lrpkg/packages, and adding your package name to the bottom of the list. The name here should match the package portion of the files you created earlier, and will be what your LRP package is backed up as. If you are using apkg instead, then you can skip this step. #cat /var/lib/lrpkg/packages initrd root local log modules zebra 6. You are now ready to ``create'' your LRP package. Just do a backup of your package from lrcfg and you will have package.lrp created for you on your disk drive. If you don't have a backup option for your package, you didn't do step 5 correctly. I am pretty sure that I did step #5 correctly. All there was to it was adding the one word, zebra, to the bottom of the list. Are there any other possibilities or is there something obvious that I have missed. Thanks in advance, Eric --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
RE: [leaf-devel] Quick and Dirty LRP Package How-To
Did you create and populate the corresponding zebra.list, zebra.help, etc? -Original Message- From: Eric B Kiser [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 24, 2002 4:29 PM To: [EMAIL PROTECTED] Subject: [leaf-devel] Quick and Dirty LRP Package How-To Hey everybody, I have gotten to the Quick and Dirty LRP Package How-To and I have gotten stuck at step #6. When I go to back up the changes to create the zebra.lrp it does not show an option for zebra in the Back-up menu. 5. Trick LRP into thinking your package is installed by editing /var/lib/lrpkg/packages, and adding your package name to the bottom of the list. The name here should match the package portion of the files you created earlier, and will be what your LRP package is backed up as. If you are using apkg instead, then you can skip this step. #cat /var/lib/lrpkg/packages initrd root local log modules zebra 6. You are now ready to ``create'' your LRP package. Just do a backup of your package from lrcfg and you will have package.lrp created for you on your disk drive. If you don't have a backup option for your package, you didn't do step 5 correctly. I am pretty sure that I did step #5 correctly. All there was to it was adding the one word, zebra, to the bottom of the list. Are there any other possibilities or is there something obvious that I have missed. Thanks in advance, Eric --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Docbug, how do I? was:(Quick and Dirty LRP Package How-To)
On Tue, Sep 24, 2002 at 11:01:43AM -0500, Charles Steinkuehler wrote: I am pretty sure that I did step #5 correctly. All there was to it was adding the one word, zebra, to the bottom of the list. Are there any other possibilities or is there something obvious that I have missed. The newer backup scripts I wrote for Dachstein (and I think are used by Bering) require you also add your package to an additional file: /var/lib/lrpkg/backdisk The backdisk file includes some switches for backup location filesystem...the format should be pretty obvious. Once added to the backdisk file, your package should appear in the backup menus. I fell victim to the same thing a couple months ago. I've been wanting to suggest a change in that particular piece of documentation for a while, but... Question: How does one go about submitting a suggestion for a change in the existing documentation? Do I submit it as a bug f.x.? Reason I ask, is that I've been *so* d*mn busy over the summer, that I've never had time to look into how anything works... :( TIA Jon Clausen --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] embedded hardware
On 2002.09.24_11:34:52_+, Joey Officer wrote: I found this interesting bit of hardware (http://mail.martinapparatus.com/Redirect/www.nagasaki.com.tw/1-products/emb edded.htm) for an embedded device. I'm awaiting pricing back from the vendor. Has anyone else worked with an embedded solution, as opposed to building routers from old hardware? Sure, please search the list archive (both leaf-devel and leaf-user). It should come up with a lot of hits. Additionally you can look at: http://www.leaf-project.org/links.php?menu=2 for some embedded device links. Joey Officer Sales Operations Martin Apparatus, Inc. 800-784-6806 x11 [EMAIL PROTECTED] -- H. D. Lee --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
