[leaf-devel] [patch] caveats section in guide/user-bering/budiskonchip.xml
Attached is a patch to add a "caveats" section to the Bering user guide chapter on booting from a DiskOnChip. It includes firmware incompatibility notes sent to me by John Cussans. I tried to check it in myself, but it looks like I no longer have cvs write access to that document. If someone could apply this patch, I would be grateful. Thank you. --Brad Index: budiskonchip.xml === RCS file: /cvsroot/leaf/doc/guide/user-bering/budiskonchip.xml,v retrieving revision 1.6 diff -u -w -r1.6 budiskonchip.xml --- budiskonchip.xml26 Jun 2003 18:26:31 - 1.6 +++ budiskonchip.xml23 Apr 2004 15:51:54 - @@ -24,13 +24,16 @@ +0.6 +2004-04-23 +BF +added caveats section with firmware notes from John Cussans + + 0.5 - 2002-10-20 - BF - -initial revison +initial revision @@ -50,8 +53,21 @@ floppy drive during setup. Comments on this section should be sent to Brad Fritz at -bradfritz at users.sourceforge.net. This is revision -$Revision: 1.6 $. Please include the revision number with any comments. +bradfritz at users.sourceforge.net. + + + +Caveats + +In August 2003, John Cussans reported that M-Systems firmware +version 5 and later is incompatible with the MTD drivers distributed +with Bering versions 1.0, 1.1 and 1.2. The incompatibility was +indicated by the error message Sorry, we don't support +UnitSizeFactor of != 1 yet. The error was generated in +response to the command insmod ntfl.o. Preparing +the DoC with firmware versions 1.23 or 4.2 using M-Systems' +DFORMAT utility was reported to work around the +incompatibility. @@ -233,7 +249,8 @@ Thanks to... Jacques Nilo and Eric Wolzak for creating Bering, all the LEAF -developers for their contributions, and Mike Noyes for his support of the -LEAF project and great work to encourage continuous improvement. +developers for their contributions, Mike Noyes for his support of the +LEAF project and great work to encourage continuous improvement, and +the contributors who have sent me updates and corrections. \ No newline at end of file signature.asc Description: Digital signature
[leaf-devel] [patch] minor POSIXness.mail getopts "-v" bug
Bering-uClibc 2.1, and possibly several other LEAF variants, have
a bug in POSIXness.mail triggered when the "-v" option to the mail
command is used. Here's an example of the bug in action:
firewall# mail -v -s "This is a test" [EMAIL PROTECTED] < /dev/null
[..]
4: 250 RCPT TO:<[EMAIL PROTECTED]>
5: 354 DATA
6: 354 Date: Sun, 25 Jan 2004 04:50:54 +
6: 354 From: [EMAIL PROTECTED]
6: 354 Subject:
6: 354 To: This is a test [EMAIL PROTECTED]
6: 354 X-Mailer: POSIXness Mail
[..]
Notice that the "Subject" header line is blank and the subject has
been prepended to the "To" header line. The problem is the "v" in
getopts optstring should not be followed by a colon since "-v" does
not take an argument. The bug is only triggered when "-v" is used.
The trivial patch attached fixes the problem for me.
--Brad
--- POSIXness.mail.orig 2004-01-24 23:45:13.0 -0500
+++ POSIXness.mail 2004-01-24 23:45:39.0 -0500
@@ -188,7 +188,7 @@
user=${user:-root}
smtpserv=${MAIL_SERVER:-mail}
- while getopts v:a:b:c:d:h:s: opt ; do
+ while getopts va:b:c:d:h:s: opt ; do
case "$opt" in
a) att="$OPTARG" ;;
b) bcc="$OPTARG" ;;
signature.asc
Description: Digital signature
[leaf-devel] broken cvs tarball at http://leaf-project.org/
Looks like the "Tarball" link under "CVS Repository" in the menu sidebar at http://leaf-project.org/ is broken. It links to: http://cvs.sourceforge.net/cvstarballs/leaf-cvsroot.tar.gz but the correct URL seems to be: http://cvs.sourceforge.net/cvstarballs/leaf-cvsroot.tar.bz2 --Brad --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Shorewall-devel] Re: [leaf-devel] Where do we go from here?
Tom, On Thu, 27 Mar 2003 11:40:11 PST Tom Eastep wrote: > On Thu, 27 Mar 2003, Tom Eastep wrote: > > > > > And note that this only works for files that contain shell commands like > > /etc/shorewall/shorewall.conf, /etc/shorewall/params, > > /etc/shorewall/start, etc. It does not work for files such as > > /etc/shorewall/rules or /etc/shorewall/masq which are read and processed > > by Shorewall. > > It took just a few minutes to hack out some code to make it work in the > other cases as well -- will be included in 1.4.2. Awesome! Thank you, Tom. --Brad --- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Where do we go from here?
Tom, On Wed, 26 Mar 2003 13:20:06 PST Tom Eastep wrote: > Before I wrap up 1.4.2 and begin thinking about 2.0, is there anything > else that people believe is needed that can't wait until 2.0? I would > prefer that you not request integration with other products in 1.4 as I > believe that the structure of 2.0 will make such integration easier. One feature that I would find useful is the ability to include configuration directives from arbitrary files. That ability would make management of several firewalls with common rulesets more convenient. An example to help clarify: shorewall/params.mgmt: MGMT_SERVERS=1.1.1.1,2.2.2.2,3.3.3.3 TIME_SERVERS=4.4.4.4 BACKUP_SERVERS=5.5.5.5 - end params.mgmt - shorewall/params: # Shorewall 1.3 /etc/shorewall/params [..] ### INCLUDE params.mgmt# proposed INCLUDE directive to source # auxiliary file # params unique to this host here #LAST LINE - ADD YOUR ENTRIES ABOVE THIS ONE - DO NOT REMOVE - end params - shorewall/rules.mgmt: ACCEPT net:$MGMT_SERVERS $FWtcp22 ACCEPT $FW net:$TIME_SERVERSudp123 ACCEPT $FW net:$BACKUP_SERVERS tcp22 - end rules.mgmt - shorewall/rules: # Shorewall version 1.3 - Rules File [..] ### INCLUDE rules.mgmt # proposed INCLUDE directive to source # auxiliary file # rules unique to this host here #LAST LINE -- ADD YOUR ENTRIES BEFORE THIS ONE -- DO NOT REMOVE - end rules - I primarily use Shorewall with the Bering LEAF variant, so it would be nice to have something like that in the 1.4 series. I scanned the docs and mailing list archives looking for similar features or related requests and didn't see any; apologies if this has already been discussed previously. If not, would anyone else find such a feature useful? --Brad --- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Java on Bering
On Thu, 13 Mar 2003 16:47:56 +0530 S Mohan wrote: > I want to run a Java App on Bering and build a dedicated, robust embedded > box for a specific purpose. How do I do this? Is java available as an lrp on > Bering? I doubt there are pre-made LEAF packages available, especially if you want Sun's JRE. IIRC, Sun's licensing makes redistribution a pain. The easiest path might be to use Bering-uclibc + libc225.lrp[1] + Sun's JRE binary. Be prepared though...it's huge: You have chosen to download Java(TM) 2 Runtime Environment, Standard Edition 1.4.1_02 * Download j2re-1_4_1_02-linux-i586.bin . Filesize = 22,954,988 bytes. Depending on the apps you want to run, you might be able to get away with one of the open source VMs like kafee[2]. (I'm pretty sure there are others, but the names escape me at the moment.) Another approach, if size is an issue and you don't need the full J2SE API, would be to use the Micro Edition stuff[3]. There are also compilers, like gcj[4], available that can produce native machine code. Good luck. --Brad [1] http://cvs.sf.net/cgi-bin/viewcvs.cgi/leaf/bin/bering-uclibc/packages/ [2] http://kaffe.org/ [3] http://java.sun.com/j2me/ [4] http://gcc.gnu.org/java/ --- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] module tarball for Bering-uClibc 1.1
Thank you Eric... On Fri, 07 Feb 2003 08:59:42 GMT Eric Spakman wrote: > > Does anyone have a module tarball available that is compatible > > with the stock Bering-uClibc 1.1 kernel? > Brad, > > I'm at work and using webmail, so I can't cc to the list. I am copying them back in to archive the URL. Hope that is okay. > The kernel and modules are uClibc independent, Right. > you can use the modules from Jacques for this. If you're using > the latest CVS 1.1 uClibc image I am. > you must use the new kernel modules, which can be found at: > http://leaf.sourceforge.net/devel/jnilo/bering/1.1/ Thank you! That was the link I was missing. --Brad > Eric --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] module tarball for Bering-uClibc 1.1
Good evening, Does anyone have a module tarball available that is compatible with the stock Bering-uClibc 1.1 kernel? I didn't see one in CVS, but I may have overlooked it. I am building a kernel and modules using the instructions[1], but a ready-made tarball would make it easier to play with the Bering uClibc 1.1 image (and help squash bugs). --Brad [1] http://cvs.sf.net/cgi-bin/viewcvs.cgi/*checkout*/leaf/src/bering-uclibc/configs/kernel/2.4.20/kernel.txt --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] New ML archive
Mike, On 17 Jan 2003 08:07:51 PST Mike Noyes wrote: > Everyone, > Our lists are now being archived at MARC in addition to SF and the Mail > Archive. Excellent! MARC has a very thorough search algorithm. In my opinion, even better than mail-archive and definitely better than Sourceforge. There's nothing more frustrating than searching for a post you know exists with a phrase you know it includes and not finding it. That has happened to me several times with mail-archive and all the time with the Sourceforge archive. Thanks for letting us know and getting us on MARC, if that was the case. --Brad --- This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will allow you to extend the highest allowed 128 bit encryption to all your clients even if they use browsers that are limited to 40 bit encryption. Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] weather balloon running Bering
This http://speed.vpizza.org/~jmeehan/balloon/ article about a fellow who launched a weather balloon running Bering on a Soekris net4511 was recently linked to from the Soekris tech list[1] and Slashdot[2]. Thought some of you might find it interesting. --Brad [1] http://lists.soekris.com/pipermail/soekris-tech/2003-January/001578.html [2] http://science.slashdot.org/science/03/01/15/1829244.shtml?tid=159 --- This SF.NET email is sponsored by: A Thawte Code Signing Certificate is essential in establishing user confidence by providing assurance of authenticity and code integrity. Download our Free Code Signing guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] uClibc dhcpd.lrp missing newline in dhcpd.exclude.list
Arne, Eric, and KP, On Wed, 15 Jan 2003 22:21:17 +0100 kapeka wrote: > Am Dienstag, 14. Januar 2003 06:53 schrieb Brad Fritz: > > > I did find one very minor problem with the dhcpd package in the > > uClibc 1.1 image. /var/lib/lrpkg/dhcpd.exclude.list was missing > > a newline at the end. > > It's been that easy to fix and it's cvs. Thank you for the quick fixes. > If you like to fix it yourself next time, Mike will add write > permisson for cvs leaf/bin/packages/uclibc if you ask him. Cool. I will keep that in mind. --Brad --- This SF.NET email is sponsored by: A Thawte Code Signing Certificate is essential in establishing user confidence by providing assurance of authenticity and code integrity. Download our Free Code Signing guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] unstripped Bering 2.4.20 modules
On Wed, 15 Jan 2003 07:56:00 +0100 Jacques wrote: > Le Mardi 14 Janvier 2003 17:37, Brad Fritz a écrit : > > Looks like many (or all?) of the Bering 2.4.20 modules [..] > > are not stripped. Was that intentional? [..] > Hi Brad > Your suggestion would indeed save space but I would not recomment it. > It will work for some modules, won't for some others. > It would have to tested case by case because doing so globally you might be > stripping symbols needed for relocation and/or modules parameters. That is > what I rembered from some experiments I did along this line some months ago. > So it's probably safer to leave that option to the end user (some lines > could be added along these lines in the modules section of the install guide) > > with a strip.lrp package. > strip with --strip-unneeded flag would be safer but would save less space. I did not realize that some of the symbols in kernel modules where necessary for everything to work properly. My testing was pretty limited (just the 3c509 module). Thank you for the explanation. --Brad --- This SF.NET email is sponsored by: Take your first step towards giving your online business a competitive advantage. Test-drive a Thawte SSL certificate - our easy online guide will show you how. Click here to get started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] unstripped Bering 2.4.20 modules
Looks like many (or all?) of the Bering 2.4.20 modules at http://leaf.sf.net/devel/jnilo/bering/latest/modules/2.4.20 are not stripped. Was that intentional? Stripping them would save a fair amount of space: brad@blacklab:/tmp$ ls -s1 /tmp/*.o 16 /tmp/3c509.o 76 /tmp/hostap.o 4 /tmp/hostap_crypt.o 8 /tmp/hostap_crypt_wep.o 64 /tmp/hostap_cs.o 56 /tmp/hostap_pci.o 60 /tmp/hostap_plx.o brad@blacklab:/tmp$ strip /tmp/*.o brad@blacklab:/tmp$ ls -s1 /tmp/*.o 12 /tmp/3c509.o 60 /tmp/hostap.o 4 /tmp/hostap_crypt.o 4 /tmp/hostap_crypt_wep.o 44 /tmp/hostap_cs.o 40 /tmp/hostap_pci.o 44 /tmp/hostap_plx.o --Brad --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Bering uclibc /etc/init.d/lshd restart broken
Variant: Bering uClibc v1.1 Package: lshd Looks like there is an "rm -f $PIDFILE" missing in the "restart" case of /etc/init.d/lshd . Without it the pid file is not removed when lshd is stopped and it fails to restart with the error: Pid file '/var/run/lshd.pid' already exists. lshd seems to be running already. in /var/log/daemon.log. --Brad --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] uClibc dhcpd.lrp missing newline in dhcpd.exclude.list
First let me say congratulations and thank you to everyone who contributed directly and indirectly to the uClibc version of Bering. Wow! I was able to fit shorewall, pump, dnscache, tinydns, pcmcia_orinoco, the 3c509 module, dhcpd, weblet and lshd (which supports public key authentication) all on a single 1680kb floppy! Truly amazaing. I did find one very minor problem with the dhcpd package in the uClibc 1.1 image. /var/lib/lrpkg/dhcpd.exclude.list was missing a newline at the end. That caused /tmp/EXCLUDE to get buggered up and dhcpd to get rolled into root.lrp. Should be an easy fix. Thank you everyone. --Brad --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] busers.html ToC out-of-sync with contents
On Fri, 10 Jan 2003 23:16:13 +0100 you wrote: > Le Vendredi 10 Janvier 2003 20:13, Brad Fritz a écrit : > > > The subsections in busers.html : > > > do not match those in budiskonchip.html : > OK fixed. Thanks for spotting the bug. Thank you, Jacques. --Brad --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] busers.html ToC out-of-sync with contents
On Fri, 10 Jan 2003 20:03:29 +0100 Jacques Nilo wrote:
> Le Vendredi 10 Janvier 2003 18:00, Brad Fritz a écrit :
> > FYI mostly for Jacques...
> >
> > I just noticed the User Guide table of contents at
> >
> > http://leaf.sourceforge.net/devel/jnilo/busers.html
> >
> > is out-of-sync with (at least) the DoC chapter which causes the
> > name anchor links to fail.
> Brad: I am not too sure to understand what you mean by the "the name anchor
> links to fail". What is the problem ? I do not see anything wrong from here..
Sorry, I should have been more clear...
The subsections in busers.html :
10. Installing and booting Bering from a M-Systems DiskOnChip
10.1. Objectives
10.2. Step 1: prepare the boot floppy
10.3. Step 2: apply bug fixes
10.4. Step 3: configure Bering for DoC booting
10.5. Step 4: prepare the DoC
10.6. Step 5: reboot
10.7. Thanks to...
do not match those in budiskonchip.html :
10. Installing and booting Bering from a M-Systems DiskOnChip
10.1. Objectives
10.2. Step 1: prepare the boot floppy
10.3. Step 2: configure Bering for DoC booting
10.4. Step 3: prepare the DoC
10.5. Step 4: reboot
10.6. Thanks to...
("Step 2: apply bug fixes" has been removed.)
A side effect is that the hypertext links in busers.html to name
anchors, that is the hrefs that look like:
10._ Whatever
^^^
have the wrong #AEN___ values and thus don't jump to the correct
places in budiskonchip.html. Most (all?) browsers will just dump
you at the top of the page instead.
--Brad
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] busers.html ToC out-of-sync with contents
FYI mostly for Jacques... I just noticed the User Guide table of contents at http://leaf.sourceforge.net/devel/jnilo/busers.html is out-of-sync with (at least) the DoC chapter which causes the name anchor links to fail. --Brad --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] freeswan and Bering 2.4.20 kernel
Jacques, On Sun, 15 Dec 2002 23:41:46 +0100 Jacques wrote: > The full story is here: > http://leaf.sourceforge.net/article.php?sid=65 Very cool! Thank you, Jacques. Quick question... It looks like freeswan support is included as well, even though the freeswan patch isn't listed in the patches directory[1]. Is that correct? If so, is it v1.99 with the patches in the the bering/latest/development/freeswan-1.99 directory? Thanks. --Brad [1] http://leaf.sf.net/devel/jnilo/bering/latest/development/kernel/2.4.20/ --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] [ leaf-Patches-641523 ] patch to fix typos in qmail.xml
On Wed, 20 Nov 2002 14:39:40 PST leaf-Patches-641523 wrote: > I noticed a few typos in qmail.xml[1] for the qmail.lrp > howto[2]. > The attached patch would fix the ones I noticed. The direct link to the unified diff is http://sf.net/tracker/download.php?group_id=13751&atid=313751&file_id=35816&aid=641523 --Brad --- This sf.net email is sponsored by: Battle your brains against the best in the Thawte Crypto Challenge. Be the first to crack the code - register now: http://www.gothawte.com/rd521.html ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Unable to do a partial backup on Bering rc4
Luigi, On Thu, 31 Oct 2002 16:53:16 +0100 Luigi wrote: > sed: Couldn't open file TMP_/tmp/EXCLUDE > Creating sshd.lrp Please wait: \tar: /tmp/EXCLUDE: No such file > or directory > rm: cannot remove `/tmp/EXCLUDE': No such file or directory > > I'm not strong on sed&scripting, but it seems the line #42 of > lrcfg.back.script need to be modified from: > w '"TMP_$EXCLUDE"' > to >w '"$TMP_EXCLUDE"' > or >w '"$EXCLUDE"' > > (as in rc3) > > Please comment and advice. Looks like a typo in applying the partial backup fix proposed by Eric W. in http://www.mail-archive.com/leaf-user@;lists.sourceforge.net/msg10133.html This is untested, but "$TMP_EXCLUDE" should be the proper fix to make partial backups work as expected. --Brad --- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] spamassassin and recent spam (was: Multimedia Design at 5$ per hour)
On 23 Oct 2002 17:29:59 MST Mike wrote: > Here is what SF may do in the future. > > Exim SpamAssassin at SMTP time > http://marc.merlins.org/linux/exim/sa.html For what it's worth, I run spamassassin locally and it caught the "Multimedia Design at 5$ per hour" email. Details below my signature. I occasionally get a few false positives, but overall spamassassin does a great job for me. --Brad Message-Id: <[EMAIL PROTECTED]> Subject: [leaf-devel] Multimedia Design at 5$ per hour [..] X-Spam-Status: Yes, hits=8.3 required=5.0 tests=DEAR_FRIEND,DEAR_SOMEBODY,FRONTPAGE,KNOWN_MAILING_LIST, MAILTO_LINK,MAILTO_TO_REMOVE,MAILTO_WITH_SUBJ, MAILTO_WITH_SUBJ_REMOVE,NO_REAL_NAME,ONE_TIME,ONLY_COST, REMOVE_IN_QUOTES,SAFEGUARD_NOTICE,SPAM_PHRASE_08_13, SUBJ_REMOVE,TABLE_THICK_BORDER,THIS_AINT_SPAM version=2.42 X-Spam-Flag: YES X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.42 (1.115.2.14-2002-10-04-exp) X-Spam-Prev-Content-Type: multipart/related; boundary="=_14xqDMtp_WDF85ecG_MR" X-Spam-Report: Detailed Report SPAM: Start SpamAssassin results -- SPAM: This mail is probably spam. The original message has been altered SPAM: so you can recognise or block similar unwanted mail in future. SPAM: See http://spamassassin.org/tag/ for more details. SPAM: SPAM: Content analysis details: (8.30 hits, 5 required) SPAM: NO_REAL_NAME (1.3 points) From: does not include a real name SPAM: SUBJ_REMOVE(0.7 points) BODY: List removal information SPAM: THIS_AINT_SPAM (0.4 points) BODY: Claims "This is not spam" SPAM: REMOVE_IN_QUOTES (0.4 points) BODY: List removal information SPAM: DEAR_FRIEND(0.4 points) BODY: How dear can you be if you don't know my name? SPAM: ONE_TIME (0.3 points) BODY: One Time Rip Off SPAM: ONLY_COST (0.2 points) BODY: Only $$$ SPAM: DEAR_SOMEBODY (0.1 points) BODY: Contains 'Dear Somebody' SPAM: SPAM_PHRASE_08_13 (1.4 points) BODY: Spam phrases score is 08 to 13 (medium) SPAM:[score: 10] SPAM: TABLE_THICK_BORDER (0.4 points) BODY: HTML table has thick border SPAM: SAFEGUARD_NOTICE (1.0 points) BODY: Contains signature of unregistered spam tool SPAM: FRONTPAGE (0.4 points) BODY: Frontpage used to create the message SPAM: MAILTO_LINK(0.2 points) BODY: Includes a URL link to send an email SPAM: MAILTO_WITH_SUBJ_REMOVE (0.6 points) URI: Includes a URL link to send an email with the su bject 'remove' SPAM: MAILTO_WITH_SUBJ (0.4 points) URI: Includes a link to send a mail with a subject SPAM: MAILTO_TO_REMOVE (0.2 points) URI: Includes a 'remove' email address SPAM: KNOWN_MAILING_LIST (-0.1 points) Email came from some known mailing list software SPAM: SPAM: End of SpamAssassin results - --- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Allowing Weblet to change a root file
Kelly, On Wed, 23 Oct 2002 13:08:11 GMT Kelly Brown wrote: > Brad, > > Thank you so much for pointing me in the right direction. Glad to help. > I have my shell script, "toggle_udp", which checks to see if > ip_masq_udp_dloose is set to 0, and if so, it sets it to 1 (and vice-versa). > > I also just found a little C code snippet on google that I think should do > what I want. This is what I have: > [C code that looks like it will work snipped] > Now my only problem is, how do I compile this to run on Leaf? Is there a > compiler available and small enough to work on the system? Or would I have > to compile it elsewhere, and then move it over to leaf? Stock Dachstein and Bering distributions both use glibc 2.0.7 . Often LEAF developers compile under Debian slink, sometimes running under UML[1] or VMWare. > If this is the > case, I only have access to machines running windows or solaris. Would > anyone be willing to compile the small program above for me? That would make it tough. It's probably possible to cross-compile from one of those platforms for a x86 glibc 2.0.7 target system, but just thinking about setting up the development environment makes my head spin. ;) Sounds like Jon hooked you up with a compiled version, so hopefully you're set now. --Brad [1] http://leaf.sf.net/devel/jnilo/uml.html --- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Re: draft Bering DiskOnChip user guide chapter
Marck, On Tue, 22 Oct 2002 10:32:58 -0400 Mark Meade wrote: > Hi Brad, > > Your instructions look great -- well written and concise. Thank you for taking the time to read my work and make suggestions. > One suggestion: the mtd modules in 2.4.18 won't work with any DiskOnChip > devices formatted with newer revisions of the M-Sys DFORMAT utility (5.x or > later). An earlier version (4.2 -- still available at www.m-sys.com) is > needed to insure compatibility with 2.4.18 modules. > > The failure occurs when loading the nftl.o module. This issue has been > fixed in newer versions of the DiskOnChip modules. I will note this in the instructions. Do you know if partitioning and formatting a DFORMAT 5.x formatted DoC with fdisk/mkfs makes any difference? Will using GRUB eliminate this issue? > The DFORMAT command creates one FAT partition by default, so running fdisk > and mkfs.msdos may not be necessary. That is what I figured. My DoC was already formatted. I will add a note to that section to say it may not be necessary. > Regarding the "mounting twice" problem: I tried this today (with newer > versions of the modules), and it seems to work fine. I'm assuming that > simply mounting the DoC twice, in two different places, is similar to what's > going on in the root.linuxrc script; for instance: > > mount /dev/nftla1 /mnt/doc1 > mount /dev/nftla2 /mnt/doc2 Actually, the same partition is mounted twice like this: mount /dev/nftla1 /mnt/doc1 mount /dev/nftla1 /mnt/doc2 If you are able to test that scenario with newer drivers than are included with 2.4.18, I would like to hear what happens. Can you also tell me what version of the the modules you're using. > Also, it's possible to replace the proprietary M-Sys DoC firmware with the > GNU GRUB bootloader. There are two compelling reasons to consider this > option: > > 1) GNU GRUB is licensed under the GPL > 2) The M-Sys firmware takes up considerably more memory than Grub > > Disadvantages to this option include the additional steps required to build > and burn the Grub firmware, and also the DoC support is not yet part of the > main Grub source tree. > > If anyone is interested, the procedure to do this is documented at: > > http://lists.infradead.org/pipermail/linux-mtd/2002-October/006166.html It appears the linux-mtd archives are unavailable right now. At the least I will add a link for the curious as a footnote in my instructions. If I can make time to try it out, I will incorporate the GRUB instructions into optional steps in the DocBook instructions. Thanks again, Mark. --Brad --- This sf.net emial is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ad.doubleclick.net/clk;4699841;7576301;v?http://www.sun.com/javavote ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Allowing Weblet to change a root file
Minor typo correction below... On Tue, 22 Oct 2002 21:40:26 EST I wrote: [snip] > > I made a tiny little script to do this, but it doesn't work. It runs, but > > the ip_masq_udp_dloose file never changes [snip] > I think the most secure solution would be to write a minimal > C program that sets ip_nonlocal_bind and run it setuid root. "ip_nonlocal_bind" should be "ip_masq_udp_dloose". Sorry about that. --Brad --- This sf.net emial is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Allowing Weblet to change a root file
Kelly, On Tue, 22 Oct 2002 14:58:30 GMT Kelly Brown wrote: > Hi guys, > > I'll admit right up front that I'm not very knowledgeable in regards to > Linux, so I hope I don't come off sounding TOO foolish. I do a lot of web > development, so I do know my way around a unix/linux environment somewhat. > I'm more used to working in a cgi environent with perl or php, so this stuff > is a tiny bit different for me. None of this sounds foolish to me. It sounds like you are already on the right track and just need a bit of help to fix the root cause of the problem. > Anyhow, what I want to do basically is use weblet to run the following line: > > echo "1" > /proc/sys/net/ipv4/ip_masq_udp_dloose > > and alternately: > > echo "0" > /proc/sys/net/ipv4/ip_masq_udp_dloose > > I essentially want to allow someone on the local network to be able to > toggle loose UDP routing on and off at will through a web interface. ssh would be a more secure way to do this, and with a little work, could be made very easy for authorized users to use. (As simple as clicking on an icon that runs plink.exe and typing a password.) That said and my conscious clear :), you should be able to make weblet do this too. > I made a tiny little script to do this, but it doesn't work. It runs, but > the ip_masq_udp_dloose file never changes and I'm GUESSING it's because > weblet isn't allowed to touch it because it's owned by root. It works fine > if I run the script through the command prompt (logged in as root), just not > through the web interface. Sounds like a very good guess to me. If you wanted to verify, you could do something like this: homefw: -root- # pwd /var/sh-www/cgi-bin homefw: -root- # cat set_loose_udp_routing.wrap #!/bin/sh sh -x set_loose_udp_routing $@ 2>> /tmp/test.log where "set_loose_udp_routing" is the real script. I did some testing (using ip_nonlocal_bind since my test Bering box does not have ip_masq_udp_dloose) and this is what I found: homefw: -root- # tail -n 2 /tmp/test.log + echo 1 set_loose_udp_routing: cannot create /proc/sys/net/ipv4/ip_nonlocal_bind: permission denied homefw: -root- # ls -al /proc/sys/net/ipv4/ip_nonlocal_bind -rw-r--r-- 1 root wheel [..] /proc/sys/net/ipv4/ip_nonlocal_bind > How could I get around this? I think the most secure solution would be to write a minimal C program that sets ip_nonlocal_bind and run it setuid root. There was some discussion of this awhile back on leaf-user or leaf-devel surrounding Jon Clausen's "blinder" project, IIRC. Less secure would be to do the same thing with a setuid shell script. Probably the least secure would be to run weblet as root rather than sh-httpd as described at http://www.mail-archive.com/leaf-user@;lists.sourceforge.net/msg07465.html (That posting should get you close to the discussion of the setuid C program too.) > I tried using both chmod and chown on > ip_masq_udp_dloose to allow weblet access, but nothing happens. The > commands act as if they worked, but the permissions don't change. It seems > a bit odd to me. Not positive, but I think that's probably because it is part of the /proc pseudo filesystem. --Brad --- This sf.net emial is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ad.doubleclick.net/clk;4699841;7576301;v?http://www.sun.com/javavote ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Re: draft Bering DiskOnChip user guide chapter
On Tue, 22 Oct 2002 16:46:53 -0400 Mark Meade wrote: > Brad Fritz wrote: > > Just to confirm, can you mount the same partition, e.g. nftla1 , > > twice simultaneously with the versions in 2.4.19? I only ask > > because your original test was mounting two separate partitions > > simultaneously (nftla1 and nftla2). > > Doh! That was a typo. My original test *was* mounting one partition twice > -- the nftla2 should have been nftla1. Sorry about that. > > Yes, the nftl module in 2.4.19 can mount a DoC partition more than once. Ahh! It all makes sense now. Thank you. > Is the mount command part of busybox in Bering? I was a little concerned > that this problem may be related to differences in the mount executable. It is, at least under rc3: homefw: -root- # ls -l `which mount` lrwxrwxrwx[..]12 Sep 15 20:06 /bin/mount -> /bin/busybox I suspect it was the driver not the bb mount applet. I say that because bb mount can mount IDE devices multiple times simultaneously. I don't know enough about bb mount and the nftl drivers to say for certain though. --Brad --- This sf.net emial is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ad.doubleclick.net/clk;4699841;7576301;v?http://www.sun.com/javavote ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Re: draft Bering DiskOnChip user guide chapter
Thank you for the additional information, Mark. Just one final question inline... On Tue, 22 Oct 2002 16:10:56 -0400 Mark Meade wrote: > > Actually, the same partition is mounted twice like this: > > > > mount /dev/nftla1 /mnt/doc1 > > mount /dev/nftla1 /mnt/doc2 > > > > If you are able to test that scenario with newer drivers than are > > included with 2.4.18, I would like to hear what happens. Can you > > also tell me what version of the the modules you're using. > > With unmodified modules from 2.4.19, I can mount the DoC twice, read and > write to either mount point, and everything seems fine. I believe that > nftlcore.c is newer than the version included in 2.4.18. Just to confirm, can you mount the same partition, e.g. nftla1 , twice simultaneously with the versions in 2.4.19? I only ask because your original test was mounting two separate partitions simultaneously (nftla1 and nftla2). I suspect the answer is yes, but I want to be sure before I pass that information on. (Jacques may not want to add my kludge of a patch to linuxrc if we know newer drivers fix the same problem as the patch.) --Brad --- This sf.net emial is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ad.doubleclick.net/clk;4699841;7576301;v?http://www.sun.com/javavote ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] draft Bering DiskOnChip user guide chapter
I recently installed Bering on a M-Systems DiskOnChip 2000 and documented the process for inclusion in the Bering User's Guide. The most recent draft in HTML is at http://fritzfam.com/brad/leaftmp/budiskonchip DocBook source is also available[1]. If anyone has comments or suggestions to share, please send them my way so I can incorporate them. Thank you. --Brad [1] http://cvs.sf.net/cgi-bin/viewcvs.cgi/leaf/devel/bradfritz/bering_contrib/doc/ --- This sf.net emial is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ad.doubleclick.net/clk;4699841;7576298;k?http://www.sun.com/javavote ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] syslinux and grsecurity (was: write protected DOM/ADM)
On Mon, 21 Oct 2002 23:41:57 +0200 you wrote: > Hello everybody > > Success, I got the SST/Apacer ADM modified for write protection working. > Anyone interested in the details here is a link to what I did > http://luna.think.ch/leaf/ADM. Very nice work! One think puzzled me though. You stated: I could not syslinux with my favorite bering floppy, grsecurity just did not want to let me do that. Dachstein might work better or else use DOS. I am curious how syslinux failed. I just installed Bering to a DiskOnChip and used syslinux 1.42 from http://leaf.sourceforge.net/devel/thc/files/kwarchive/fdisk.lrp under Bering 1.0-rc3 to make the DoC bootable. I didn't run into any grsecurity problems. Do you remember the details of how syslinux failed? --Brad --- This sf.net emial is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ad.doubleclick.net/clk;4699841;7576298;k?http://www.sun.com/javavote ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Bering rc3 /dev/nftla* wrong major number bug
On Wed, 16 Oct 2002 20:06:01 +0200 Jacques wrote: > Le Mercredi 16 Octobre 2002 07:34, Brad Fritz a écrit : > > Jacques, do you already have a volunteer for a User's Guide > > chapter on running Bering from DoC? > > No, but I would welcome one. Send me your contrib off-list following the > structure of a Bering user's guide chapter. ASCII file is fine if you do not > want to take care of XML formatting. I am working on docbook formatted version now. I will send you a copy off-list when it is ready for review. I would also like to track the document in CVS. I will add it somewhere under leaf/devel/bradfritz unless you would prefer it reside in a different location of the LEAF CVS repository. --Brad --- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Bering DoC: how to avoid mounting /dev/nftla1 twice in /linuxrc
While trying to get Bering to boot from a DoC, I ran into a hurdle that has been discussed before but never resolved in a way that would prevent new DoC users from struggling with it. The Bering rc3 modules for MTD DiskOnChip and NFTL do not allow concurrent mounting of the same device in multiple locations. That causes Bering to hang during boot if the DoC boot device (usually /dev/nftla1) reappears in PKGPATH. Robert Sprockeels was the last person to post about this problem[1], and it looks like Simon Blake[2] and Bao Ha[3] have also written about it. So far I have seen mention of two possible workarounds: 1) Add "umount $MNT" to line 217 of /linuxrc (Simon's fix) 2) Try newer doc2000 and nftl drivers in hopes that they support concurrent mounting. (Mark Meade suggested[1] that support might be in newer versions.) and used a third of my own (probably poor) design: 3) Add the following else block to the 'if [ -n "$PKGPATH" ]' condition in /linuxrc. Plus signs indicated inserted lines. done IFS=$OIFS + else + bootfs=`cat /var/lib/lrpkg/boot.fstype` + rdevlist="/dev/boot:+$MNT:-$bootfs,$rdevlist" + devlist="$devlist,/dev/boot:+$MNT:-$bootfs" fi rdevlist=`echo $rdevlist |sed 's/,$//'` devlist=`echo $devlist |sed 's/^,//'` and remove the PKGPATH setting in syslinux.cfg on the DoC. Does anyone have other suggestions or comments about the three presented? #2 looks the most promising, but I have not seen concrete evidence that concurrent mount support is really included and haven't had time to compile Bering MTD drivers from CVS yet. It would be cool if a fix were incorporated into an upcoming Bering release. With this and the /dev/nftl* major number issues fixed, it would be possible to write fairly simple directions for booting Bering from DoC. (I have notes that I could convert to a DocBook draft.) --Brad [1] http://www.mail-archive.com/leaf-user@lists.sourceforge.net/msg10188.html [2] http://sourceforge.net/mailarchive/message.php?msg_id=1655640 [3] http://www.mail-archive.com/leaf-user@lists.sourceforge.net/msg04341.html --- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Bering rc3 /dev/nftla* wrong major number bug
Apologies if this has already been reported. I searched leaf-user and leaf-devel and didn't see it. As noted at http://lists.infradead.org/pipermail/linux-mtd/2002-October/006181.html the /dev/nftla* entries are incorrect. They have major number 3 but should have major number 93. Jacques, do you already have a volunteer for a User's Guide chapter on running Bering from DoC? --Brad --- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] UML Questions
On Thu, 10 Oct 2002 23:12:15 -0400 Eric Kiser wrote: > Brad, > > [snip from below] > it *seems* > like you should be okay unless you try to back up two instances > simultaneously (or perform other simultaneous write operations to > /dev/ubd0) > [/snip] > > I ran simultaneous full back ups and timed it so that I did both, backing up > the same file on both at the same time and backing up different files at the > same time. When I rebooted both UML routers they came up fine. I was unable > to find any problems. I may have misunderstood your setup. Are you using a single Bering file system image for both UML instances (like I assumed), or are you using multiple copies of the file system, one for each UML instance? Your test results seem to indicated the latter, but "I...used the exact same script for each instance of Bering UML" suggests to me the former. Either way, it's hard to argue with success. If it works as you expect and fits your needs, life is good, right? --Brad > [snip from below] > It also seems like you could overwrite a package > backup from one instance with a later backup from a second > instance > [/snip] > > This I have also tested and it did not cause a problem. I just did a simple > name change on each router and then backed one up and then the other. I then > rebooted both and they came up with the new names just as I had set them. > > Let me know if you think of anything else that might cause a problem and I > will go ahead and test it. > > Regards, > Eric > > -Original Message- > From: Brad Fritz [mailto:[EMAIL PROTECTED]] > Sent: Thursday, October 10, 2002 1:23 PM > To: Eric B Kiser > Cc: [EMAIL PROTECTED] > Subject: Re: [leaf-devel] UML Questions > > > > On Thu, 10 Oct 2002 11:03:33 -0400 Eric Kiser wrote: > > > Just wanted to close this issue with a little more finality. I decided not > > to mess with the COW files right now and used the exact same script for > each > > instance of Bering UML. > > Since Bering runs from a ram disk and the boot file system is > typically not mounted except during package backups, it *seems* > like you should be okay unless you try to back up two instances > simulaneously (or perform other simultaneous write operations to > /dev/ubd0). It also seems like you could overwrite a package > backup from one instance with a later backup from a second > instance (which may be desirable, depending on what you are > trying to accomplish). All that is untested speculation though. > > > I backed up all my files in case something went wrong. > > I booted up two Bering UML file systems and made some changes. > > Saved changes. > > Backed up /etc. > > Rebooted Bering UML file systems. > > Checked changes. > > Everything seems to be working fine. > > Cool. > > > If I find any bugs in this later then I will post back to the list. > > Please do. > > --Brad > > > Regards, > > Eric Kiser --- 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] UML Questions
On Thu, 10 Oct 2002 11:03:33 -0400 Eric Kiser wrote: > Just wanted to close this issue with a little more finality. I decided not > to mess with the COW files right now and used the exact same script for each > instance of Bering UML. Since Bering runs from a ram disk and the boot file system is typically not mounted except during package backups, it *seems* like you should be okay unless you try to back up two instances simulaneously (or perform other simultaneous write operations to /dev/ubd0). It also seems like you could overwrite a package backup from one instance with a later backup from a second instance (which may be desirable, depending on what you are trying to accomplish). All that is untested speculation though. > I backed up all my files in case something went wrong. > I booted up two Bering UML file systems and made some changes. > Saved changes. > Backed up /etc. > Rebooted Bering UML file systems. > Checked changes. > Everything seems to be working fine. Cool. > If I find any bugs in this later then I will post back to the list. Please do. --Brad > Regards, > Eric Kiser --- 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] UML Questions
Hello Eric, On Wed, 09 Oct 2002 20:03:47 -0400 Eric Kiser wrote: > Hi All, > > I am working with bering1.0-rc3 and using it in a UML environment. I wanting > to be able to boot up multiple bering file systems and be able to modify > them and save the changes. In the UML documentation it says that if you use > the same copy of a file system to do this then you will corrupt it. What I > am trying to figure out is how to this without one uml load writing over > another one. > > Here is my script: > > #! /bin/sh > > ./linuxuml-2.4.18-21\ > ubd0=bering_fs \ > initrd=initrd.lrp \ > root=/dev/ram0 \ > init=/linuxrc \ > boot=/dev/ubd0:minix\ > PKGPATH=/dev/ubd0 \ > devfs=nomount \ > LRP=root,etc,local,log,modules > > If I use this script multiple times then won't I have multiple copies of > bering_fs using ubd0 and ram0? > I modified the script so that ubd0 became ubd9 and ram0 became ram9 but I > was unable to get through the boot sequence. Should this have worked? I am at the edge of (and possibly beyond) my understanding of UML here, but I believe ubd0 and ram0 are devices internal to each UML environment. If I am correct, you should be able to run multiple UML instances all using ubd0 and ram0. > Any help is appreciated. Please let me know if there is more information > needed that I have overlooked. I was able to get two copies of UML to boot simultaneously using the UML Copy-On-Write layer[1]. Here is a diff of my two start scripts: < ./linuxuml-2.4.18-45 ubd0=cow0,bering_fs \ --- > ./linuxuml-2.4.18-45 ubd0=cow1,bering_fs \ (Notice the first argument to the ubd0 parameter in each.) Aside from the different "ubd0" parameters, my start scripts are nearly identical to yours. Here's one for reference: #!/bin/sh ./linuxuml-2.4.18-45 ubd0=cow0,bering_fs \ initrd=initrd.lrp \ root=/dev/ram0 \ init=/linuxrc \ boot=/dev/ubd0:minix \ PKGPATH=/dev/ubd0 devfs=nomount \ LRP=`cat packages.minimal` I haven't done any testing beyond booting the two instances, so I am not 100% positive I didn't screw something up that would come back to haunt me later. In other words, don't blame me if the above advice causes your computer to start smoking or blow up. ;) If I am reading the howto correctly, it looks like you can also merge the COW file with its backing file into a new file system image. Good luck! --Brad [1] http://user-mode-linux.sourceforge.net/UserModeLinux-HOWTO-7.html --- 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] Linux Virtual Server using LEAF Bering RFC
On Wed, 18 Sep 2002 06:55:56 +0700 H. D. Lee wrote: > Great. May be this will be a good reason to incorporate IP_VS into > Bering or Dachstein kernel. Even if it's not included, the build-from-source approach being discussed should make it easy for interested parties to roll their own kernel and modules. > > If it would be helpful, I could > > upload the (completely untested) kernel and modules, along with > > the build script I used to download patches and apply them to the > > stock 2.4.18 kernel, to my devel subdirectory in CVS. Let me > > know if that would be useful to you. > > Sure it would help. I would like to have such a script to automate > the work. So far I have been doing it manually. The kernel should help > me examine different result of patches version for testing. Thanks Brad. Posted to http://fritzfam.com/brad/leaftmp/make_bering_ivs_kernel temporarily. As time allows, I am going to re-write it using GAR or David's ports-like system (or both). Once I do, I will check it into cvs.sf.net under leaf/devel/bradfritz . --Brad > -- > H. D. Lee --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source & Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Linux Virtual Server using LEAF Bering RFC
On Tue, 17 Sep 2002 22:28:47 +0700 H. D. Lee wrote: > List, > > I am on a very early step of a project to build Linux High Availability > with Load Balancing Clusters using LVS[0] and other tools. I will use > LEAF Bering or Dachstein for the directors. Sounds interesting. > Is there any chance that future releases of Bering or Dachstein have > IP_VS support compiled in? Even building as modules, IP_VS have several > kernel symbols that should be in the kernel. > > Any comments or suggestions? I cannot answer your question about whether it will be included, but I can say that the linux-2.4.12-ipvs-0.8.2 patch applies cleanly over the stock Bering rc3 patched kernel[1]. The IPVS kernel, including IPVS debugging support, is only 44 bytes larger than the stock kernel after UPX compression. $ ls -l ../*.upx -rw-r--r--[..] 495299 Sep 17 11:42 ../Bering_1.0-rc3-ipvs.upx -rw-r--r--[..] 495235 Sep 17 11:26 ../Bering_1.0-rc3.upx "make modules" is running now. If it would be helpful, I could upload the (completely untested) kernel and modules, along with the build script I used to download patches and apply them to the stock 2.4.18 kernel, to my devel subdirectory in CVS. Let me know if that would be useful to you. --Brad [1] with the exception of non-essential Documentation/Configure.help file > [0] http://www.linuxvirtualserver.org/ --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source & Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] UML Bering - sh: can't access tty; job control turned off
On Mon, 09 Sep 2002 13:54:44 -0400 Eric Kiser wrote: > Hi Brad, > > Thanks for all the information. I did notice that in your boot sequence it > showed that you are using mconsole (version 2). Mine shows mconsole (version > 1). Where did you get yours? I used the .rpm off of the UML site. It's part of the debian testing uml-utilities package: $ dpkg -S uml_mconsole uml-utilities: /usr/share/man/man1/uml_mconsole.1.gz uml-utilities: /usr/bin/uml_mconsole $ dpkg -l uml-utilities | grep "^ii" ii uml-utilities 20020729-1 User-mode Linux (utility programs) Looks like it's a fairly recent (7/29) release. > [snip] > I'd be happy to send you copies of my bering_fs or initrd.lrp files offlist > if that would help. > [/snip] > > That would be fantastic. Will do. --Brad --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] UML Bering - sh: can't access tty; job control turned off
Eric, On Mon, 09 Sep 2002 11:18:57 -0400 Eric Kiser wrote: > Okay, I must be doing something wrong and just don't realize it. I have > followed the direction listed in the online documentation multiple times and > I am still not getting anywhere. I did quite a bit of searching over the > weekend for the message "sh: can't access tty; job control turned off" but > all that I turned up was dead ends and wonderfully irrelevant information > like "upgrade your mail server". Given the fact that I did not find an > answer that helped me that mail server link was definitely the most > entertaining. To the ignorant mind (that would be me) it just so completely > seemed to have nothing to do with my problem. Here is what I have tried... > > Bering_1.0-rc3_img_bering_1680.bin > with both linuxuml-2.4.18-21 and -45 > > and... > > Bering_1.0-rc2_img_bering_1680.bin > with both linuxuml-2.4.18-21 and -45 > > I did differ from the instructions in that I named my file system bering_fs > instead of Bering_fs and (note the upper case B was recommended in the docs) > I used the username uml_dev instead of leafuml (if this is the problem then > I will proceed with kicking my own ass just to make up for annoying everyone > with these messages). > > Here is a copy of my startuml script (notice I did maintain the lower case > 'b' in bering_fs and 'yes' I did modify the script when I changed > kernels)... > > #! /bin/sh > ./linuxuml-2.4.28-45 ubd0=bering_fs initrd=initrd.lrp root=/dev/ram0 > init=/linuxrc boot=/dev/ubd0:minix PKGPATH=/dev/ubd0 devfs=nomount > LRP=root,etc,local,log,modules > > After the message: > sh: can't access tty; job control turned off > > I get the # prompt where I typed exit and got: > Kernel panic: Attempted to kill init! > > If none of this is helpful to anyone could someone at least confirm that > they have managed to get rc2 or rc3 running with either of the -21 or -45 > kernels by following the direction as posted in the on line docs. I have run rc3 under -45 by following Jacques' instructions. I don't remember finding any problems with the docs, but it's been over a month and I could have forgotten if there were. I am sure I would have reported any significant problems to Jacques on leaf-devel. I am running UML under debian testing with a custom 2.4.18 kernel. $ ls -l total 4152 -rw-r--r--1 brad brad 2048000 Aug 17 10:20 bering_fs -rwxr-xr-x1 brad brad 410442 Aug 17 10:20 initrd.lrp -rwxr-xr-x1 brad brad 1777972 Aug 17 10:20 linuxuml-2.4.18-45 -rw-r--r--1 brad brad 73 Aug 17 18:05 packages -rwxr-xr-x1 brad brad 424 Aug 17 18:29 test I start it with a "test" script: $ cat test #!/bin/sh ./linuxuml-2.4.18-45 eth0=tuntap,tap0 \ eth1=tuntap,tap1 \ eth2=tuntap,tap2 \ ubd0=bering_fs \ initrd=initrd.lrp \ root=/dev/ram0 \ init=/linuxrc \ boot=/dev/ubd0:minix \ PKGPATH=/dev/ubd0 devfs=nomount \ LRP=`cat packages` $ cat packages root,etc,local,modules,shorwall,dnscache,weblet,libz,sshd,ntpclnt,dhcpd I have also included a log of the UML startup below my signature. Have you tried setting VERBOSE=1 and DEBUG=1 in /linuxrc in your initrd.lrp image? They might give you more context for the " can't access tty" error. Let me know if there's anything I can do to help. I'd be happy to send you copies of my bering_fs or initrd.lrp files offlist if that would help. --Brad tracing thread pid = 16344 Linux version 2.4.18 (root@debian) (gcc version 2.95.4 20011002 (Debian prerelease)) #8 Sun Jul 28 13:01:33 CEST 2002 On node 0 totalpages: 8192 zone(0): 8192 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: eth0=tuntap,tap0 eth1=tuntap,tap1 eth2=tuntap,tap2 ubd0=bering_fs initrd=initrd.lrp root=/dev/ram0 init=/linuxrc boot=/dev/ubd0:minix PKGPATH=/dev/ubd0 devfs=nomount LRP=root,etc,local,modules,shorwall,dnscache,weblet,libz,sshd,ntpclnt,dhcpd Calibrating delay loop... 618.52 BogoMIPS Memory: 29892k available Dentry-cache hash table entries: 4096 (order: 3, 32768 bytes) Inode-cache hash table entries: 2048 (order: 2, 16384 bytes) Mount-cache hash table entries: 512 (order: 0, 4096 bytes) Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes) Page-cache hash table entries: 8192 (order: 3, 32768 bytes) Checking for host processor cmov support...Yes Checking for host processor xmm support...No Checking that ptrace can change system call numbers...OK Checking that host ptys support output SIGIO...No, enabling workaround Checking that host ptys support SIGIO on close...No, enabling workaround POSIX conformance testing by UNIFIX Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Starting kswapd devfs: v1.10
Re: [Leaf-devel] PID racing Bering rc3
Eric, On Sun, 25 Aug 2002 22:35:10 +0200 Eric wrote: > Hello Developers , > > I use a Bering RC3 on a 486 DX 66 with 3 nics, which I administer > with ssh. > Recently I noticed a fast increasing of the pid numbers, that I couldn't > understand. > After rebooting I stopped all services except for ssh [lots of snipping from here down] > # ps aux;date > PID Uid VmSize Stat Command > >> 27529 root936 Rps aux > Fri Aug 23 17:32:25 UTC 2002 > # ps aux ;date > PID Uid VmSize Stat Command > >> 2848 root936 Rps aux > Fri Aug 23 17:32:29 UTC 2002 > # ps aux ; date > PID Uid VmSize Stat Command > >> 7410 root936 Rps aux > Fri Aug 23 17:32:34 UTC 2002 > firewall: -root- > # ps aux ; date > PID Uid VmSize Stat Command > >>30678 root936 Rps aux > Fri Aug 23 17:32:39 UTC 2002 > > Does somebody has the same things occuring ( > perhaps an Kernel /modules issue ? > Or is there another explanation. > I booted with an older version rc1 to verify that > I didn't have an issue with my box ( permanently > pressed Keyboard or something like that ;) ) > > 2075 root Rps aux > 2076 root Rps aux > 2077 root Rps aux > > so this is normally On a hunch, I did some digging for information about grsecurity and randomized PIDs. I couldn't find a good link, but based on http://lists.jammed.com/sectools/2001/10/0092.html and other tidbits about a fix for SMP problems with grsecurity random PIDs, I think this is a feature of the grsecurity patch. Can anyone confirm? --Brad --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] openssl: flurry of changes ???
On Fri, 09 Aug 2002 09:48:08 CDT mds wrote: > Anybody care to shed light on the flurry of changes in openssl since > last week? I don't have the full scoop, but I think these include fixes to the vulnerabilities found during the DARPA CHATS audit of OpenSSL. A search for "openssl" at http://securityfocus.com/ will turn up a lot of info including the original advisory and descriptions of the bugs. There were at least 3 separate vulnerabilities, so that might be the reason for multiple openssl releases (although that's pure speculation on my part). The openssl-announce mailing list is archived at http://www.mail-archive.com/openssl-announce@openssl.org/ It has announcements for 0.9.6e-g and 0.9.7-beta3. I haven't read them yet though. --Brad --- 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] Compiling problems
On Thu, 25 Jul 2002 16:26:28 CDT Shaun Feakes wrote: > Hi, > > I am having real difficulties compiling applications for LEAF, this is > due to my setup, I am sure. > Redhat 7.3 using glibc2.0 compat from Redhat 6.x to produce binaries > for 5.x (Should work with linux 2.2.x) > > Anyway, I just can't seem to get this working correctly for anything that > uses glibc, Just in case you haven't already seen it, Dave Douthitt's developer guide[1] has a link to a RedHat doc that might be worthwhile: http://www.redhat.com/support/wpapers/glibccompat/ > so I am going to build a machine for development, but I can't > find a Debian 2.1 iso image (I believe this is the preferred linux# to use.) > Does anyone know where I can get this image from? >From a SF mailing list archive search of leaf-user[2] for "slink iso": ftp://debian.uchicago.edu/debian-cd/archive You may also want to look into Jacques' "Developing and using LEAF in a virtual environment"[3] if you don't want to maintain a separate slink install. I believe he said it's a bit dated, but the concepts should all still be valid. --Brad [1] http://leaf.sourceforge.net/pub/doc/guide/developer.rtf or google HTML version: http://216.239.37.100/search?q=cache:QrTnNa9gTA4C:leaf.sourceforge.net/pub/doc/guide/developer.rtf [2] http://sourceforge.net/mailarchive/message.php?msg_id=1691048 [3] http://leaf.sourceforge.net/devel/jnilo/uml.html > Thanks for any help > Shaun. --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] Perl help
On 17 Jul 2002 10:24:21 PDT Mike Noyes wrote:
> Brad,
> Thanks for the proof. The broken pipe may have been a coincidence, but I
> thought I should check before trying this again.
Almost always better to be safe than sorry, I suppose. :)
> My diff doesn't look right (diff output below). The same thing happened
> last night when going from rev 1.1 to 1.2. Strange, the diff seems to be
> offset. Am I doing something wrong? I'll try the change in Emacs and see
> if the diff changes.
>
> [Leaf-cvs-commits] CVSROOT enforce_naming,1.1,1.2
> http://www.mail-archive.com/leaf-cvs-commits%40lists.sourceforge.net/msg00039
>.html
>
>
> CVSROOT]$ diff enforce_naming ~/CVSROOT/enforce_naming
> 26c26
> < # $Id: enforce_naming,v 1.3 2002/07/17 02:44:55 mhnoyes Exp $
> ---
> > # $Id: enforce_naming,v 1.4 2002/05/04 16:12:18 moorman Exp $
> 32a33
> > # 3. Verify that all filenames, except Makefile, are lowercase
> 46a48,54
> > $exit_val = 1;
> > }
> >
> > # Verify that all files are lowercase, except Makefiles
> > if ((substr($_, 0, 8) ne "Makefile") and (lc($_) ne $_)) {
> > print "All filenames must be completely lowercase except";
> > print "Makefiles. ($directory/$_)\n";
>
Looks okay to me. The next line after the last "print" line
inserted is another "$exit_val = 1" line. Even though your
diff looks different than mine, the resulting code is the same.
I also double-checked the r1.1 to r1.2 diff[1] from last night,
and I don't see anything wrong or any changes that should have
resulted in the broken pipe error.
What was the context of the broken pipe message?
--Brad
[1]
http://cvs.leaf-project.org/cgi-bin/viewcvs.cgi/leaf/CVSROOT/enforce_naming.diff?r1=1.1&r2=1.2
---
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] Perl help
On 17 Jul 2002 09:11:44 PDT Mike Noyes wrote:
> Hmm, then what did I do wrong in rev 1.2? I used vi to dd out the lines
> below, and you ended up with a broken pipe from the server last night.
I am not sure about the broken pipe, but if you need more
evidence it *should* work, see below. My apologies for the
long lines. Any chance the broken pipe was a coincidence
or an artifact of the check-in of enforce_naming.pl rather
than the code changes?
$ ./enforce_naming.pl dummy FOO BAR makefile cvs
All Makefiles must have proper case (M should be upper-case). (dummy/makefile)
Creation of files named CVS or cvs is prohibited. (dummy/cvs)
$ ./enforce_naming.pl.orig dummy FOO BAR makefile cvs
All filenames must be completely lowercase except Makefiles. (dummy/FOO)
All filenames must be completely lowercase except Makefiles. (dummy/BAR)
All Makefiles must have proper case (M should be upper-case). (dummy/makefile)
Creation of files named CVS or cvs is prohibited. (dummy/cvs)
$ diff ./enforce_naming.pl.orig ./enforce_naming.pl
51,56d50
< # Verify that all files are lowercase, except Makefiles
< if ((substr($_, 0, 8) ne "Makefile") and (lc($_) ne $_)) {
< print "All filenames must be completely lowercase except ";
< print "Makefiles. ($directory/$_)\n";
< $exit_val = 1;
< }
--Brad
> Any enlightenment is appreciated.
>
> > > # Verify that all files are lowercase, except Makefiles
> > > if ((substr($_, 0, 8) ne "Makefile") and (lc($_) ne $_)) {
> > > print "All filenames must be completely lowercase except
>";
> > > print "Makefiles. ($directory/$_)\n";
> > > $exit_val = 1;
> > > }
> > >
> > > leaf/CVSROOT/enforce_naming rev 1.3
> > > http://cvs.leaf-project.org/cgi-bin/viewcvs.cgi/leaf/CVSROOT/
---
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] Introduction for Brad Fritz
Hello, everyone. I am another of the new developer invitees. At Mike and David's suggestion I would like to introduce myself, but first let me say that it is an honor to be a member of such a great group. Thank you for inviting me. I'm a 26 year old software developer. Most of my projects are web applications, the majority of them written in Java. I also help maintain a handful of small networks in the Kansas City area. My first experience with LEAF, technically LRP at the time, was with Eigerstein, and I currently have four Dachstein and Bering firewalls deployed for my clients. All of them are very happy by the way, thanks to all of *your* hard work. One of them is using a 10 year old recycled Packard Bell 486 to protect several machines on his T1. It was up for 218 days before I powered it down to plug it into a UPS. It's been up for 95 days since. Have I mentioned that I love Linux?! :) My free time is fairly limited right now, but I hope to answer leaf-user postings when I have useful information to contribute. I also hope to get X running on my Bering/glibc 2.2 Ipaq IA-1 [1] soon-to-be-mp3-jukebox-frontend and post the setup details. Thanks again everyone. Sincerely, Brad Fritz key fp: BEF3 1F93 9399 FD8B A7AA 932D B9A6 D18E 7E69 9F03 [1] http://athome.compaq.com/showroom/static/ipaq/intappliance.asp msg05069/pgp0.pgp Description: PGP signature
Re: [Leaf-devel] Bering and glibc 2.2.x
On Tue, 04 Jun 2002 10:02:25 EDT Steven Nickle wrote: > I saw in the archive, that several people are running Bering with glibc > 2.2.x. Is there documentation on the conversion or packages available? > > It would make my development effort easier. The best docs I have seen so far are Simon Blake's at http://www.wix.net.nz/LEAF/ . That link is in the message[1] I referred to in my reply to your leaf-users posting last night. I used Simon's instructions to upgrade Bering on my Ipaq IA-1 to glibc 2.2 and didn't have any problems. If you have specific questions after reading Simon's documentation, post them here and I'll do my best to answer. --Brad [1] http://sourceforge.net/mailarchive/message.php?msg_id=1567978 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] RE: Booting Bering from /dev/hda2
Taking a shot in the dark here... On Fri, 17 May 2002 12:59:54 PDT you wrote: > Yes, I have the correct modules loaded. Including ide-mod, ide-probe-mod, and ide-disk stored in initrd's /boot/lib/modules and listed in /boot/etc/modules ? If so, does the output when they load look right? Here's an example: LINUXRC: Bering - Initrd - V1.0-rc2 Using /boot/lib/modules/ide-mod.o Uniform Multi-Platform E-IDE driver Revision: 6.31 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller on PCI bus 00 dev 39 VP_IDE: chipset revision 6 VP_IDE: not 100%% native mode: will probe irqs later Using /boot/lib/modules/ide-probe-mod.o hdc: LEXAR ATA_FLASH, ATA DISK drive ide1 at 0x170-0x177,0x376 on irq 15 Using /boot/lib/modules/ide-disk.o hdc: 32128 sectors (16 MB) w/1KiB Cache, CHS=502/2/32 Partition check: hdc: hdc1 > The same set of LRP files will boot > correctly from the disk drive of the computer in question, but the > partitions won't extract any of the modules. That doesn't rule out problems with the ide-* modules in initrd. > Yes, I've read the following documentation: > LEAF "Bearing" installation guide (used it to modify the linuxrc to > isolate the problem) > Developing and using LEAF in a virtual environment (used it to setup a > development environment for LEAF) Not sure, but I think Luis might have been referring to Jacques' user's guide, particularly "Booting Bering from different boot-media" at http://leaf.sourceforge.net/devel/jnilo/bubooting.html . > The main problem seems to be that LINUXRC complains that it can't mount > the boot device, when in the syslinux.cfg file it seems to be correctly > defined as "boot=/dev/hda1:msdos". It's probably the result of some It's > probably a minor error on my part. That would be consistent with not loading the ide-* modules (or having IDE disk support compiled into your kernel). If you do have the ide modules loaded, posting the output when the modules are loaded would help with further debugging. --Brad ___ Hundreds of nodes, one monster rendering program. Now thats a super model! Visit http://clustering.foundries.sf.net/ ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] Admin script help
On 13 Apr 2002 08:33:44 PDT Mike Noyes wrote:
> Anyone,
> Is there a way to get tar to return the date of the most recent file in
> a tarball?
>
> Example:
> $ tar tvzf leaf/devel/ddouthitt/packages/cal.lrp
> -rwxr-xr-x root/root 9648 2001-12-17 06:42:08 usr/bin/cal
> -rw-r--r-- root/root32 2001-12-17 06:42:21
> var/lib/lrpkg/cal.list
>
> Desired output: 2001-12-17
If you can't get tar to tell you directly,
tar tvfz $TARBALL_FILE \
| awk '{print $4}' \
| sort -n \
| tail -n 1
might work for you.
--Brad
___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] snort.lrp --with-mysql
On Tue, 29 Jan 2002 11:58:07 PST Chat wrote: > New to the list :) using Dach 102 LRP-CD . Need snort.lrp (1.8.3 :) > compiled with mysql (./configure --with-mysql) in order to connect to > DEMARC central database from my new LEAF node NIDS :) [..] > Appreciate your help as i really dont want to make a debian > developement pc just for this, thank you ! Chat, If no one volunteers to compile it for you, you may want to check out Jacques' "Developing and using LEAF in a virtual environment" at http://leaf.sourceforge.net/devel/jnilo/uml.html . It discusses how to use user-mode linux to run a virtual system. The section entitled "Using a virtual Debian/slink development box" [1] probably has everything you need to know. It's pretty slick, and Jacques has even provided a Debian slink filesystem complete with gcc and friends that should make compiling snort a breeze. I just gave it a test run on my (Mandrake) system, and it looks like it should work like a dream. --Brad [1] http://leaf.sourceforge.net/devel/jnilo/uml03.html ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[Leaf-devel] /etc/POSIXness.conf missing in Dachstein-pr4
Looks like /etc/POSIXness.conf is needed by the "mail" command on Dachstein-pr4, but is missing. (Thanks for the offline heads-up on /etc/POSIXness.conf, Charles.) [root@wml ds_tmp]# mount -t msdos -o loop dachstein-pr4-1680.bin /mnt/ [root@wml ds_tmp]# tar vxfz /mnt/root.lrp bin/POSIXness [root@wml ds_tmp]# grep -e MASTCONF -e POSIXness.conf bin/POSIXness MASTCONF="/etc/POSIXness.conf" [ -f "$conf" ] && source $MASTCONF [root@wml ds_tmp]# for p in `ls /mnt/*.lrp`; do echo $p; \ tar tvfz $p; done | grep POS root/root 2186 2001-05-24 18:31:31 bin/POSIXness root/root 0 2001-09-27 10:42:48 lib/POSIXness/ root/root 3887 2001-05-26 07:39:03 lib/POSIXness/POSIXness.linuxrouter root/root 5242 2000-08-13 17:29:35 lib/POSIXness/POSIXness.mail root/root 3257 2000-08-13 17:29:35 lib/POSIXness/POSIXness.system root/root 2181 2000-08-13 17:29:35 lib/POSIXness/POSIXness.text (permission output stripped to prevent wrapping) Great job with Dachstein, Charles! I converted my home firewall over the weekend and, POSIXness mail aside, things are working great. --Brad Fritz [EMAIL PROTECTED] ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
