RE: [Leaf-devel] [OT?] Portland? was Upcoming Conferences
On that note, it dawns on me to ask, Any of you in the Portland area? I live in
Scappoose and work in Vancouver WA.
Richard Amerman
-Original Message-
From: Chad Carr [mailto:[EMAIL PROTECTED]]
Sent: Wed 7/17/2002 9:28 PM
To: Mike Noyes
Cc: [EMAIL PROTECTED]
Subject: Re: [Leaf-devel] [OT?] Upcoming Conferences
On 17 Jul 2002 15:23:22 -0700
Mike Noyes [EMAIL PROTECTED] wrote:
On Wed, 2002-07-17 at 15:12, David Douthitt wrote:
[US Conferences, that is]
Anyone going to DefCon 10 in Las Vegas, NV, Aug 2-4, or to
11th Usenix Security Symposium, Aug 5-9, in San Francisco, CA?
Just wondering... Interesting that they're so close together
in time and space :-)
David,
I'm registered for LinxWorld (exhibits only). Moscone Center, SF Aug.
13-15.
Anyone going to O'Reilly OSCON in San Diego? If so maybe I'll see you
there.
--
Chad Carr [EMAIL PROTECTED]
---
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
áË ë^¨¥Ë)¢{(ç[É8bAzEÊzÚ yé!y«Þm§ÿí)äç¤r¿±òÞi÷^½éfj)b
b²ÒÞi÷^½éeËl²«qç讧zØm¶?þX¬¶Ë(º· ~àzwþX¬¶ÏåËbú?æuëÞ
[Leaf-devel] korn shell script
hi all, Is there anybody who knows wether korn shell scripting is compatible with ash? Reason I ask is because mij dns registrar has a dynamic subscription type. Which updates your ip by using a korn shell script. If not is there somebody in here with both korn ash shell scripting that would like try to convert it? Thanks in advance Kim - This mail sent through Tiscali Webmail (http://webmail.tiscali.be) --- 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] korn shell script
Kim At 12:12 18.07.2002, you wrote: hi all, Is there anybody who knows wether korn shell scripting is compatible with ash? up to e certain degree, it certainly is Reason I ask is because mij dns registrar has a dynamic subscription type. Which updates your ip by using a korn shell script. does it work? and if not, why cheers THINK Püntenstrasse 39 8143 Stallikon mailto:[EMAIL PROTECTED] PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16 --- 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] korn shell script
Aanhalen Erich Titl [EMAIL PROTECTED]: At this point it is not working. For various reasons. So far I changed the obvious /usr/bin/ksh to /bin/sh on line 1. I replaced all instances of print with echo. There are a lot of [] in the script which apparently are not tolerated by ash. The script makes use of lynx to call a php frontend at their site and I can't get lynx to work (error opening terminal: xterm). And the script makes use of elif and I have no clue wether ash supports that. if then ... elif then fi fi Maybe I should attach the original script? Kim Kim At 12:12 18.07.2002, you wrote: hi all, Is there anybody who knows wether korn shell scripting is compatible with ash? up to e certain degree, it certainly is Reason I ask is because mij dns registrar has a dynamic subscription type. Which updates your ip by using a korn shell script. does it work? and if not, why cheers THINK Püntenstrasse 39 8143 Stallikon mailto:[EMAIL PROTECTED] PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16 --- 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 mail sent through Tiscali Webmail (http://webmail.tiscali.be) --- 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] korn shell script
On Thu, 2002-07-18 at 07:12, [EMAIL PROTECTED] wrote: Aanhalen Erich Titl [EMAIL PROTECTED]: At this point it is not working. For various reasons. So far I changed the obvious /usr/bin/ksh to /bin/sh on line 1. I replaced all instances of print with echo. There are a lot of [] in the script which apparently are not tolerated by ash. Kim, We have a ash 0.3.4-6 man page available. http://leaf-project.org/pub/doc/man/ash.1_0.3.4-6.html Maybe I should attach the original script? Please include it in-line instead of attaching it. Thanks. -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- 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] [OT] Speaking of Licensing
Charles, Thanks for your input :) Comments and more questions inline; On Tue, Jul 16, 2002 at 09:42:02AM -0500, Charles Steinkuehler wrote: What do I do with my blinder.lrp (it's getting closer to releaseability)... licensing-wise? Pretty much whatever you want :) Heh... :) The majority of the code is written by myself. But there *are* snippage IMHO, writing code is a lot like writing books. Everyone copies everyone else's ideas, but you need to stay away from actually plagerizing something. Of course, trying to define exactly how much modification makes something entirely yours vs. a modified version of another author's code (or story, or whatever) is a pretty blurry line... Agreed... Does anyone have any good links on the subject? Saddly, no. Please share with the list if you find some good references. Bummer :( I *was* kind of hoping for a reference to the GPL in 'human readable' format... If I find anthing useful, I'll post it. Personally I'd be only happy to see people using this thingie, but I ... Most of the open-source licenses are pretty strong about continuing to credit previous authors (one of the biggest sins in the open-source world is to deny credit to someone whose work you have built on). I Which makes perfect sense. And since I'm all for giving credit where credit's due, that's all fine. doubt you found any major pieces of code that are reproduced in your new blind application (ie your work is basically original, not derrived), so you probably don't have to worry too much about licensing, but it would still maybe be nice if you included references to some of the material you used as references. Yeah, this is what I intend to. Of course, if a big chunk of your code is lifted from somewhere, you will definately need to acknowledge that fact, and consider any licensing implications. No *big* chunks, tiny ones, but still. BTW: I consider the weblet code (cgi-bin scripts) to be GPL'd, although there is no license specified. I guess I haven't worried about it too much because: O.K. - Adding licensing notices and author credits takes space, and I was trying to make everything as small as possible Smallness is not so much of a concern for me right now. One of the rationales for this app, is that it sits on a dedicated box, *well* shielded from public access. So after I ripped out most of the functions from the Bering system, there was plenty space... At this point, smallness is more of a matter of code optimization/reuse and speedy execution (the less code that runs, the faster it goes, hopefully ;) - I'm not particularly worried about recieving ongoing credit for the cgi-bin stuff...it wasn't that much work. O.K. But you won't *mind* it if I give you credit for it? - The shell-script stuff is pretty much open-source anyway...it's kind of hard to release a closed-source shell script :-) lol... Yeah, you're right about that ;) NOTE: There *IS* a GPL notification at the start of sh-httpd, it was a bit more work :) And that is what it takes? So I basically 'just declare' my stuff to be GPL'ed (providing it lives up to any requirements) and that's that? Or rather: Considering that the whole thing consists of a number ~(10 - 12) scripts/C-programs, do I need to put the 'notice' in each one? Or is it sufficient to put it in, say, a README, packaged with the rest? Also there's the matter of the source for the C-exes. As was mentioned in the 'bering=GNU?' thread, it seems kind of overkill to put that in the .lrp... So is it sufficient to post it on a website, or is it better/preferred that I make a 'developer' tarball, with everything in it, and make *that* available for download as well? As for packaging in general, my intention is to makes the blinder.lrp available, as a standalone package. That is, *not* to make complete floppy images. So that anyone who wants to use it, will have to get a Bering/(whatever) image, and strip that to make space and subsequently install the blinder.lrp to it. The rationale being that anyone who's about to build/use such a system, may as well get to know LEAF in the process, plus it makes my life much easier. AND I avoid any licensing issues in the process... Thanks again for the response... 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] korn shell script
Kim At 16:12 18.07.2002, you wrote: Aanhalen Erich Titl [EMAIL PROTECTED]: At this point it is not working. For various reasons. So far I changed the obvious /usr/bin/ksh to /bin/sh on line 1. makes sense I replaced all instances of print with echo. There are a lot of [] in the script which apparently are not tolerated by ash. The script makes use of lynx to call a php frontend at their site and I can't get lynx to work (error opening terminal: xterm). maybe wget will do what you want And the script makes use of elif and I have no clue wether ash supports that. from man ash .. An if command looks like if list then list [ elif list thenlist ] ... [ elselist ] fi HTH erich THINK Püntenstrasse 39 8143 Stallikon mailto:[EMAIL PROTECTED] PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16 --- 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] [OT] Speaking of Licensing
On Wed, 2002-07-17 at 01:18, Jon Clausen wrote: Charles, Thanks for your input :) Comments and more questions inline; On Tue, Jul 16, 2002 at 09:42:02AM -0500, Charles Steinkuehler wrote: What do I do with my blinder.lrp (it's getting closer to releaseability)... licensing-wise? Pretty much whatever you want :) Heh... :) Jon, Please consider using GPL or MIT. They are both listed in our project trove listing. If you don't find either of those licenses to your liking, any OSI approved license is acceptable for hosting on SourceForge. LEAF project trove on SF http://sourceforge.net/projects/leaf * Development Status: 5 - Production/Stable * Environment: Console (Text Based), No Input/Output (Daemon) * Intended Audience: End Users/Desktop, System Administrators * License: GNU General Public License (GPL), MIT License * Operating System: Linux * Programming Language: C, C++, Unix Shell * Topic: Firewalls, Monitoring # Help Choosing an Open Source license http://sourceforge.net/docman/display_doc.php?docid=778group_id=1 -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- 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] [OT] Speaking of Licensing
On Wed, 2002-07-17 at 01:18, Jon Clausen wrote: On Tue, Jul 16, 2002 at 09:42:02AM -0500, Charles Steinkuehler wrote: NOTE: There *IS* a GPL notification at the start of sh-httpd, it was a bit more work :) And that is what it takes? So I basically 'just declare' my stuff to be GPL'ed (providing it lives up to any requirements) and that's that? Or rather: Considering that the whole thing consists of a number ~(10 - 12) scripts/C-programs, do I need to put the 'notice' in each one? Or is it sufficient to put it in, say, a README, packaged with the rest? Jon, I think it's acceptable to place it in a LICENSE file. Embedded releases can't practically include full license text, so I think linking is acceptable. Note: IANAL. Also there's the matter of the source for the C-exes. As was mentioned in the 'bering=GNU?' thread, it seems kind of overkill to put that in the .lrp... So is it sufficient to post it on a website, or is it better/preferred that I make a 'developer' tarball, with everything in it, and make *that* available for download as well? As for packaging in general, my intention is to makes the blinder.lrp available, as a standalone package. That is, *not* to make complete floppy images. So that anyone who wants to use it, will have to get a Bering/(whatever) image, and strip that to make space and subsequently install the blinder.lrp to it. The rationale being that anyone who's about to build/use such a system, may as well get to know LEAF in the process, plus it makes my life much easier. AND I avoid any licensing issues in the process... I'm going to reverse my recommendation in the post below. http://www.mail-archive.com/leaf-devel%40lists.sourceforge.net/msg05257.html CVS is the preferred place for source, and the alternate is a source tarball. -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- 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] [OT] Speaking of Licensing
At 08:42 AM 7/18/02 -0700, Mike Noyes wrote: [...] Considering that the whole thing consists of a number ~(10 - 12) scripts/C-programs, do I need to put the 'notice' in each one? Or is it sufficient to put it in, say, a README, packaged with the rest? Jon, I think it's acceptable to place it in a LICENSE file. Embedded releases can't practically include full license text, so I think linking is acceptable. Note: IANAL. I remember this topic being debated on the Debian lists about a year ago. The question there was a tiny bit different -- some people were arguing that having a single licenses file for the distribution as a whole was insufficient to comply with the GPL, and that each individual .deb binary package needed to include an actual copy of the license text (each one that used the GPL, that is; there are other DFSG-compliant licenses, of course). I don't know (or at least don't recall) how this debate played out in principle. I do know that the proposed change to the contents of .deb files actually distributed as part of Debian (there are unofficial .deb packages around too) was not made. The distro does include one copy of each of the various DFSG-compliant licenses in its base package set, though; certainly at least the CD-based LEAF versions could manage this (I haven't looked but I bet they already do). I never see the full text of licenses included in the actual source code files themselves, though an accompanying LICENSE file is fairly common with the source packages. -- ---Never tell me the odds!-- Ray Olszewski-- Han Solo Palo Alto, California, USA [EMAIL PROTECTED] --- --- 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] Re: [leaf-user] gzip doesn't work as a filter
Le Jeudi 18 Juillet 2002 18:32, Brad Fritz a écrit : On Thu, 18 Jul 2002 11:13:48 CDT Russ Price wrote: Brad Fritz wrote: I'm using RC3. Here's what I get: # gzip --help BusyBox v0.60.3 (2002.06.08-17:56+) multi-call binary # gzip foo.txt bar.txt.gz # ls -l bar.txt.gz -rw-r--r--1 root root0 Jul 18 11:09 bar.txt.gz Hmm. From http://leaf.sourceforge.net/devel/jnilo/biabout.html : 1.5. Changelog Current version: 1.0-rc3 - June,16 2002 [snip] - Busybox updated to 0.60.3: saves 10k and ls command output is now in colour :-) Maybe part of that 10k came out of gzip. ;) I didn't see the busybox config file posted under http://leaf.sourceforge.net/devel/jnilo/bering/rc3/ , so we may need the Bering crew to step in for futher diagnosis. Here is the response: There is indeed a bug in the 0.63 version of busybox as far a gzip is concerned. I was indeed the first one to notice it since backup was not working any more :-(. But you can fix it easily (I did it in the backup script but forgot /bin/savelog firewall: -root- # gzip --help BusyBox v0.60.3 (2002.06.08-17:56+) multi-call binary Usage: gzip [OPTION]... FILE firewall: -root- # echo foobar foo firewall: -root- # gzip foo - foo.gz NOTICE the - before firewall: -root- # ls -l foo* -rw-r--r--1 root root7 Jul 18 20:16 foo -rw-r--r--1 root root 27 Jul 18 20:17 foo.gz firewall: -root- # So the fix in /bin/savelog is to replace the line: $COMPRESS $newname.0 $newfile by $COMPRESS $newname.0 - $newfile Then save root.lrp That's all folks ! Will be corrected in rc4. Thanks for spotting the bug Jacques --- 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
