Re: [leaf-devel] Compile host for Bering.

2005-01-15 Thread Jon Clausen
On Sun, 02 Jan, 2005 at 12:49:38 +0100, Jon Clausen wrote:

snip 

 Since upgrading my workstastion to SUSE 9.2 my UML virtual machines won't
 start, and I'm beginning to tire of the complexity of all that.
 
 So I'm now looking at setting up a dedicated system for
 compilation/development.

At some point it occurred to me that the simplest way might be to
'de-usermode' my UML. Long story (very) short:

transfer the filesystem to the target host/partition
(loop mount the slink image, tar up contents, untar on target)

put a (non-uml) kernel on target partition

arrange for the bootloader to recognize the above
(I'm using grub)

edit /etc/fstab on target, to reflect the new situation

edit /etc/inittab on target, to get 'real' terminals (for keyboard/monitor)

boot.

For convenience I've added:

/etc/init.d/ifconf-eth0

#!/bin/sh
ifconfig eth0 10.1.1.111 netmask 255.255.255.0 broadcast 10.1.1.255

symlinked from /etc/rcS.d/S40ifconf-eth0

and installed sshd (unpacked an sshd.lrp, moved files to the proper places)
in order to get network access.

It looks like it's working, so I thought I'd share in case anyone's
interested.

/Jon

-- 
YMMV


---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt

___
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel


[leaf-devel] Compile host for Bering? (glibc, gcc, kernel versions etc...)

2005-01-02 Thread Jon Clausen
I have been using UML (debian slink/woody) for my kernel compiles, but never
been able to successfully compile userland stuff in either environments.

Since upgrading my workstastion to SUSE 9.2 my UML virtual machines won't
start, and I'm beginning to tire of the complexity of all that.

So I'm now looking at setting up a dedicated system for
compilation/development.

I have been looking at the Develping and using LEAF in a virtual
environment howto at:
http://leaf.sourceforge.net/bering/index.php?module=pagemasterPAGE_user_op=view_pagePAGE_id=3MMN_position=3:3

- to try to decide which base system to use. Being basically completely
unfamiliar with Debian (and apt in particular), I'm thinking SuSE 7.3 or 8.x
should be viable alternatives, as long as I manage to set it up with all the
'correct' versions of everything.

Now, the above looks pretty dated, and while I'm aware that the development
environment is pretty static, I'd still like to make sure I don't set up
something that's completely outdated...

So the questions are:
Which versions of
glibc,
gcc,
make,
(other),
should I have in such a system?

TIA
/Jon

-- 
YMMV


---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt

___
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel


Re: [leaf-devel] Bering 1.2: linuxrc, root.dev.mk and logging

2004-08-11 Thread Jon Clausen
On Wed, 11 Aug, 2004 at 06:30:19 -0500, Charles Steinkuehler wrote:
 Jon Clausen wrote:

snip 
 The code seems to do what it's supposed to, but before I submit it here for
 review, it seemed like a good idea to get it straight whether or not there
 would be a problem with mounting /var/log after root.dev.mk runs.
 
 There should be no problem making the root devices prior to mounting 
 /var/log.

O.k. Thanks for confirming.

 In fact, in the latest init scripts (see Bering uClibc or my 
 not-quite-released Bering-CD), the creation of block devices occurs 
 prior to mounting the *ROOT* ramdisk (to allow reading of leaf.cfg and 
 support run-time configuration of ramdisk size).

Right.

So if I contribute something to mount /var/log on disk, that would also work
out-of-the-box-ish with those... (I guess?)

Next on *my* agenda is to decide whether to make

1: A 'unified' log= that wil parse both 
   - log=xM (to replace the original log_size=xM option)
   - log=/dev/hdXn:fstype

or

2: Keep log_size, add log_dev and make them mutually exclusive (perhaps
   with a preference for log_size if both should be present in cmdline)

I like 1: better, but maybe it's a bit too ambiguous?

2: on the other hand is probably simpler to write.

Decisions, decisions... :)

Comments very welcome

/Jon
-- 
Just say know!


---
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink  Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285

___
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel


[leaf-devel] Bering 1.2: linuxrc, root.dev.mk and logging

2004-08-10 Thread Jon Clausen
Am I reading /var/lib/lrpkg/root.dev.mk correctly?

AFAICT everything it does sends any output to /dev/null (except possibly the
cd-rom stuff right at the end).

Assuming that it is meant to work silently (ie no logging), then there
shouldn't be a problem with swapping the code in /linuxrc so that /var/log
gets mounted *after* devices are created?

I ask because:

Wanting to log to harddisk, I had to do the above. It worked nice (thread on
leaf-user ends with: Harddisk: device deceased) apart form the fact that
the disk died.

I subsequently got a personal request to explain how I did it.

This all made me think that it would be nice to 'formalize' the
functionality. So I concocted some code to parse a
log_dev=/dev/hdXn:fstype -statement in /proc/cmdline.

Obviously an actual mount can't take place before the device to mount is
created.

The code seems to do what it's supposed to, but before I submit it here for
review, it seemed like a good idea to get it straight whether or not there
would be a problem with mounting /var/log after root.dev.mk runs.

TIA
/Jon
-- 
Just say know!


---
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink  Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285

___
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel


[leaf-devel] Addendum to QD LRP package how-to

2003-07-25 Thread Jon Clausen
http://sourceforge.net/docman/display_doc.php?docid=1460group_id=13751

Section 5:

Trick LRP into thinking your package is installed by editing
/var/lib/lrpkg/packages, and adding your package name to the bottom of the
list. The name here should match the package portion of the files you
created earlier, and will be what your LRP package is backed up as. If you
are using apkg instead, then you can skip this step.

Section 6:

You are now ready to ``create'' your LRP package. Just do a backup of your
package from lrcfg and you will have package.lrp created for you on your
disk drive. If you don't have a backup option for your package, you didn't
do step 5 correctly.

Problem is, step 5 is not enough if you're working on Bering:

One also has to declare the package in the file /var/lib/lrpkg/backdisk in
order for the package to show up in lrcfg.

So I'd suggest adding something like the following to Section 5;

ADDENDUM
Note that if you're working on Bering, you also have to declare your new
package in /var/lib/lrpkg/backdisk, which controls the destination of the
packages. Follow the syntax of the other lines in there.
/ADDENDUM

- or something to that effect.

I should mention that the above is something I noticed while making a
package on Bering 1.0_rc2 (I think), and I haven't checked whether it still
holds true on later releases...

CMIIW

Cheers,
Jon Clausen

-- 
Whatever rocks your boat!


---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01

___
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel


Re: [leaf-devel] The ideas presented so far...

2003-02-03 Thread Jon Clausen
I thought I should add a couple of comments. There's a lot of this
discussion that's basically way beyond me, but welll... :)

On Mon, Feb 03, 2003 at 06:57:24PM -0600, Lynn Avants wrote:
 The biggest problem IMHO with a flat-db would be the ability to
 hand-edit the file(s). If no comments or description fields are used
 it will require a user to locate the variable(s) in the package conf
 file(s), then edit them in the 'db' file.

I may be wrong, but I don't see any reason why comments would be banned
from the flat-db files. I mean it's not that much code needed to 
recognize a # at the beginning of a line...?

So as long as we don't complicate matters by allowing in-line comments,
it should be fine?

---

I like Chad's directory structure idea

---

And finally;

Given a template system, in which the actual config files are built
by reading values from some sort of db and merging those with template
data, consider this:

Would it make sense to have some sort of 'repeatable section' mechanism?

The example I'm thinking of is the interfaces section of dachsteins
network.conf, in which there could be *some* variation in the number of
instances, between individual LEAF boxes...

Could be accomplished by use of tag/tag pairs...

Just 0.02 $CURRENCY

regards,
Jon Clausen


---
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] ML filter base64?

2002-12-04 Thread Jon Clausen
On Wed, Dec 04, 2002 at 10:38:12AM -0800, Mike Noyes wrote:
 On Wed, 2002-12-04 at 08:57, Mike Noyes wrote:
  I'd like to hear some opinions on blocking base64 messages from our
  lists. I see no good reason to allow them, but I may have missed
  something.
  
  Content-Transfer-Encoding: base64
 
 Everyone,
 After reviewing the SPAM that posted to our lists in the last few
 months, I discovered the vast majority of them are base64.
 
 We are now blocking all base64 encoded posts. 

Thanks :)
 
 Please let me know if you experience any problems with this change.
 Thanks.

Sure... ;)


---
This SF.net email is sponsored by: Microsoft Visual Studio.NET 
comprehensive development tool, built to increase your 
productivity. Try a free online hosted session at:
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en

___
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [leaf-devel] Allowing Weblet to change a root file

2002-10-23 Thread Jon Clausen
On Wed, Oct 23, 2002 at 01:08:11PM +, Kelly Brown wrote:

 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? i

Not that I know of.

 Or would I have 
 to compile it elsewhere, and then move it over to leaf?  If this is the 
 case, I only have access to machines running windows or solaris. 

I don't know about either of those. I guess it *is* possible to compile
it somehow, though *my* guess is that solaris would be the best bet...

In any case you might want to have a look at:

http://leaf.sourceforge.net/devel/jnilo/uml.html

- though I have no idea whether it will work on solaris...

 Would 
 anyone be willing to compile the small program above for me?

Look in your inbox ;)

It compiles fine in UML, and looks as if it works. At least in that once
it's 

chown root:root wrapper
and 
chmod a+s wrapper

'ered

execution fails with:

jon@a13-8:~/Projekt/blinder/C/src/KellyBrown ./wrapper
sh: /var/sh-www/cgi-bin/toggle_udp: No such file or directory

Let us know how it goes :)

HTH

Jon Clausen


---
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

2002-10-22 Thread Jon Clausen
On Tue, Oct 22, 2002 at 09:40:26PM -0500, Brad Fritz wrote:
 
  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.

YRC: My problem was a little different, but the same principles apply.

In order to get cron to notice that a new crontab file was installed, I
needed to get the timestamp of the directory /var/spool/cron/crontabs
updated. The directory is owned by root, so I basically had two options:

run sh-httpd as root (not a great ideda), or

make an suid binary that does something in the directory.

I went with option two, and got some help creating a tiny little C
program that creates a file notify in that dir, and erases it again
immediately. This operation had the desired effect, and all was good.

The way it's done, is that the program has paths/filename hardcoded in
it, and takes no arguments, so there is very little possibility of
(direct) misuse. So anyone can execute it, and have cron update it's
knowledge of crontabs on the system.

Adapting that program to do what you need is probably not that
difficult. I'd be happy to take a stab at it, but I'm not really a C
programmer (yet anyway).

 Less secure would be to do the same thing with a setuid shell
 script.

It's my understanding that shell scripts will not work suid. (I did try
that out before turning to C, it never worked, and I seem to remember
seeing an explanation of why it doesn't work somewhere...) CCMIW

 Probably the least secure would be to run weblet as root rather

-and since your host *is* a firewall (which my Blinder system is
*not*), I'd advice against that.

  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.

Sounds reasonable... (?)

HTH
Jon Clausen


---
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] Command recall Oxygen(yes) Bering(no) DF(no)

2002-10-14 Thread Jon Clausen

On Mon, Oct 14, 2002 at 10:36:35AM +0100, Luis.F.Correia wrote:
 Command recall that is used in all Leaf variants uses a patch made by
 someone
 from the LRP community to add 'command history' to the original ASH.
 
 It may be possible that this patch is not functional for long lines.

While we're on the subject:

I've never had command recall work on any of the LEAFs I've built, when
SSH'ing in. Usually works fine at the physical console, just not over
the network. Am I missing something, or can I get that?

Plus command/path completion would be nice :)

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] Command recall Oxygen(yes) Bering(no) DF(no)

2002-10-14 Thread Jon Clausen

On Mon, Oct 14, 2002 at 10:24:40AM -0500, Charles Steinkuehler wrote:

  While we're on the subject:

 Command recall works fine for me via ssh.  I use putty when in windows
 (just plain ol' ssh on linux).  I do set my putty keyboard settings and
 terminal type to linux, but that's more to get the back-space  delete
 keys working properly...I've never had a problem with up-arrow in
 either ash or bash.

g so I just tried it with an xterm... works beautifully... hmmm goes
to check the settings in kterm... change around a bit... works... Feel
kind of stupid... all that time I've been typing, typing, typing...

DOH!
 
 I also have tab command/path completion, but then, I typically run bash
 off the CD...gotta love all that extra space :-)

Gotta try that out some day ;)

Thanks,

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] Help needed: new chapters in Bering doc

2002-10-09 Thread Jon Clausen

On Wed, Oct 09, 2002 at 07:59:07AM +0200, Jacques Nilo wrote:
 We have three new pieces for the Bering documentation that will be released 
 with rc4 coming out shortly.
 
 We would welcome proofreading, comments and suggestions before release.

Great stuff! I like the page about time in particular. That's something
I always wanted... ;)

I'll try to stay out of the content, more or less... So this is mostly
just proofreading. Comments inline:
 
 1 chapter in the Bering installation guide:
 http://leaf.sf.net/devel/jnilo/bisystem.html

Proofreading:
10.3: If you want to add an hard-disk... 
- If you want to add a hard-disk...

10.9: PLease refer to...
- Please refer...

Suggestion:
10.8: Maybe mention ssh along with smtp/nntp towards the end?

 2 chapters in the Bering user's guide:
 http://leaf.sf.net/devel/jnilo/butime.html

13.1: ...Jeff Newmiller from which...
- ...from whom...

13.9: Miscellaneous

g) maybe add some reason? Or just elaborate slightly more...?

h) Does backing up etc.lrp save stuff if one chooses to go with
ntpdate.lrp? (I guess not, but it ought to be a little clearer imho)

i) great ;)

 http://leaf.sf.net/devel/jnilo/bumail.html

14.1: ... a help...

14.2:
! If you want to send mail...:
ACCEPT  fw  net 25  tcp

...well, I might want to send it to an *internal* host ...(?)

14.3:
After changing the cronjob is updated automatically.

Maybe it's just me, but some punctuation might be good:

After changing, the cronjob is updated automatically.

-or even a small mention of *how* cron sees that something's changed
(that the timestamp on the directory is updated)

You can edit the multicron file as above or (probably a better idea)
insert a new file with the syntax as before for each additional
purpose.

Might be better phrased as something like:

To add jobs to be run, you can edit the multicron file. A better idea
might be to put them in (a) separate file(s) in /etc/cron.d/ (keeping
the syntax)

...or something

Also this might be a good place to mention /var/spool/cron/crontabs/ -in
case somebody would like to run a userland cronjob. And if that gets
added, then a note on the fact that userland crontabs don't have the
user -field.

I know this is not supposed to be a new manpage, but having been through
a bunch of cron-related stuff recently, I think it would be great to
'spell it out' just a *little* more.

MHO, HTH, TIA a.s.o. ;)

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



[leaf-devel] Docbug, how do I? was:(Quick and Dirty LRP Package How-To)

2002-09-24 Thread Jon Clausen

On Tue, Sep 24, 2002 at 11:01:43AM -0500, Charles Steinkuehler wrote:

  I am pretty sure that I did step #5 correctly. All there was to it was
  adding the one word, zebra, to the bottom of the list. Are there any
  other possibilities or is there something obvious that I have missed.
 
 The newer backup scripts I wrote for Dachstein (and I think are used by
 Bering) require you also add your package to an additional file:
 /var/lib/lrpkg/backdisk
 
 The backdisk file includes some switches for backup location 
 filesystem...the format should be pretty obvious.  Once added to the
 backdisk file, your package should appear in the backup menus.

I fell victim to the same thing a couple months ago. I've been wanting
to suggest a change in that particular piece of documentation for a
while, but...

Question:
How does one go about submitting a suggestion for a change in the
existing documentation?

Do I submit it as a bug f.x.?

Reason I ask, is that I've been *so* d*mn busy over the summer, that
I've never had time to look into how anything works... :(

TIA

Jon Clausen



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

___
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Multiple upstream links

2002-09-03 Thread Jon Clausen

On Wed, Aug 14, 2002 at 09:06:18PM -0700, Jeff Newmiller wrote:
 On Wed, 14 Aug 2002, Eric B Kiser wrote:
 
 [...]
 
  The best reference for load balancing is Jack Coates site. He does a great
  job of summing up the major concerns with load balancing and offering
  suggestions on how to make it work. There is some great information there
  and it is a quick read. Here is the link...
  
  http://www.leaf-project.org/pub/doc/howto/LRP-Load-Balancing-HOWTO.html
  
  Hope this helps.
 
 Don't forget the SysAdmin article on redundant connections in the January
 2002 issue of SysAdmin magazine, Charles.

FYI:

http://www.samag.com/documents/s=1824/sam0201h/0201h.htm

I'm developing an interest in this type of scenario. How (much more)
complicated does it get if you want to have a DMZ in there as well?

And:

AFAICT from the article, there is little difference in *where* the
uplinks connect to? Or to be a little more specific:

Scenario:
A private (residential) LAN/DMZ is connected via DSL. The capacity of 
the DSL-line is getting close to saturation. The line has already been
'turned up' to the maximum available bandwidth (let's say 2Mbit).

Instead of switching to a different type of uplink that supports higher
bandwidth, but is also
1: expensive to get installed
2: expensive to rent
it would be nice to just get a second DSL-line (possibly from the same
ISP) and bundle the two.

This would make no difference to the router, would it?

At this point I'm just being curious, so this is basically smalltalk,
but a very interesting topic at that...

Thoughts?

Jon Clausen


---
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=sourceforge1refcode1=vs3390

___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel



[Leaf-devel] Is there a lawyer in the house? (long)

2002-07-30 Thread Jon Clausen

Hi all

Hoping that the mail-snafu has blown over, I hope to resume the
licensing discussion WRT my blinder.lrp (and licensing issues in
general):

Since I got the responses on the 'Speaking of Licensing' thread, I've
done a fair amount of reading, and have been reminded why I *loathe*
paperwork :-P

I think it might be practical to split this thread in two 'separate'
subthreads; 

[legal] About the copyrights/-lefts/legalese. What may/must I (not) do
and, 
[practical] on how/where to put notices, source locations etc.

and so:

[legal]
I'm almost finished reviewing the code, and thus far the only piece that
remains unchanged since I found it, is the bit that does the actual
writes to the parport. I put the src at
http://bund.dk/blinder/lptout.c.html 
It does contain a copyright notice, but as I understand it, as long as I
make sure that's kept in place, then it's o.k. use/post the code(?)
I've contacted the author, and am awaiting his reply.
What I'm more uncertain of however, is how this plays out if I
decide to release my work under the GPL?

The only other thing that bears significant resemblance to any 'original'
is the main part of the webinterface. As such it is, in fact, a complete
rewrite of Justins index.html. But I feel that I owe it to him to give
him credits, so I'm going to put an Original design by Justin Ribeiro
(C) bladablada in that.

The rest is so far removed, that I don't think I'll be stepping on
anybody's toes if I declare it my own.

Evenso, I will try to compile a list of references to the material that
I used as guides.

As for choice of license...

Much as I like the idea of releasing under the GPL, it sure looks like
there's a lot of 'overhead' involved, what with section 2(a,b,c)'s
requierements that You must cause the modified files to carry prominent
notices stating that you changed the files and the date of any change.
etc. So that in the (likely) event that I make changes/updates to the
software at a later time, I could spend as much time fulfilling the above
requirements, as I do coding...

How do you guys deal with that?

The MIT-license, otoh, (appealing as it is in it's brevity) does it
(legally) do anything other than make sure you get ongoing credit?
[/legal]

[practical]
The software can be seen as divided between the 'runtime' stuff 
and the configuration stuff (cgi-scripts mostly)

Both 'groups' are made up of a main script, and a number of 'support'
scripts/programs.

so for the .lrp -can I get away with only quoting the full copyright
notice in the 'main' parts, and then make an abbreviated notice in the
'subscripts' pointing to the full quote in the main? (to save space)

Also I don't see any LICENSE files in other .lrps that I've looked at.
Is there a geenral concensus towards Mike's quote that Embedded
releases can't practically include full license text, so I think linking is
acceptable.?

As for source:
Until I get around to learning how to use CVS, this software will only be
available from the download area that I'm about to set up at
bund.dk/blinder/download/

From this location I will make available the blinder.lrp itself and a
tarball of src/everything.

Am I to understand that what Ray meant by 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. is
that said LICENSE file should hold a *full* quote of whichever
license?
[/practical]

PHEW!!!
-sorry, this got somewhat longer than I intended, but I hope it's not
too much... 

TIA
Jon Clausen


---
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31

___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] [OT] Speaking of Licensing

2002-07-18 Thread Jon Clausen

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



[Leaf-devel] [OT] Speaking of Licensing

2002-07-16 Thread Jon Clausen

Hi all

All this talk about the different license schemes lately, has me
wondering...

What do I do with my blinder.lrp (it's getting closer to
releaseability)... licensing-wise?

The majority of the code is written by myself. But there *are* snippets of
code here and there (mainly the C-parts) where I've basically cut/pasted
and slightly modified examples I've found around the web...

I'm not exactly sure if any *code* still survives, but in any case I've
been looking heavily at some of the viewlogs etc. cgi-scripts that come
with the weblet/bering-1rc2...

I'll track down and ask the people who published aforementioned
C-snippets, but what are my options/obligations in general?

Does anyone have any good links on the subject?

Personally I'd be only happy to see people using this thingie, but I
would prolly be pretty upset if someone were to grab the code and
advertise it as theirs... (not that I imagine anyone would *want* to do
that since it's all still pretty sloppy/ugly anyway)

I know this is slightly off-topic, but this is the only developer list
I'm subscribed to, and as such I see this as my best bet at finding out
about this...

If this is inappropriate, please don't hesitate to let me know,
alternatively reply by PM.

TIA
Jon Clausen

P.s: I've now gotten a bit further with both the system itself, *and*
the website: http://bund.dk/blinder/ if anyone's curious :)


---
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



[Leaf-devel] [OT] Speaking of Licensing (2.nd try)

2002-07-16 Thread Jon Clausen

Something is definitely not right... I guess I have to talk to my ISP :(

Anyway, I tried sending this yesterday, and since it hasn't shown up
yet, I'll try once more:

- Forwarded message from Jon Clausen [EMAIL PROTECTED] -

Date: Mon, 15 Jul 2002 15:36:09 +0200
From: Jon Clausen [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [OT] Speaking of Licensing
Mail-Followup-To: [EMAIL PROTECTED]

Hi all

All this talk about the different license schemes lately, has me
wondering...

What do I do with my blinder.lrp (it's getting closer to
releaseability)... licensing-wise?

The majority of the code is written by myself. But there *are* snippets of
code here and there (mainly the C-parts) where I've basically cut/pasted
and slightly modified examples I've found around the web...

I'm not exactly sure if any *code* still survives, but in any case I've
been looking heavily at some of the viewlogs etc. cgi-scripts that come
with the weblet/bering-1rc2...

I'll track down and ask the people who published aforementioned
C-snippets, but what are my options/obligations in general?

Does anyone have any good links on the subject?

Personally I'd be only happy to see people using this thingie, but I
would prolly be pretty upset if someone were to grab the code and
advertise it as theirs... (not that I imagine anyone would *want* to do
that since it's all still pretty sloppy/ugly anyway)

I know this is slightly off-topic, but this is the only developer list
I'm subscribed to, and as such I see this as my best bet at finding out
about this...

If this is inappropriate, please don't hesitate to let me know,
alternatively reply by PM.

TIA
Jon Clausen

P.s: I've now gotten a bit further with both the system itself, *and*
the website: http://bund.dk/blinder/ if anyone's curious :)

- End forwarded message -


---
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] Weblet Enhancements

2002-07-03 Thread Jon Clausen

Hi,

I may be missing something in this, so do CMIIW, but;

On Tue, Jul 02, 2002 at 09:18:31AM -0500, Charles Steinkuehler wrote:
   there is a *=* case which resets the parameter list in sh-httpd, it
   disables constructs like
  
   foo=barbaz=foo
  
   I guess parameters without a value would pass fine
 
  Thanks for the detail...I'll see if I can remember why this was
  specifically added when reviewing the code (hopefully sometime in the
  near future).
 
 OK, I dug out my CGI references, and what I have indicates the command
 line arguments should only be parsed and provided to scripts if the GET
 or HEAD request does *NOT* contain an unencoded equals sign, which is
 why the arguments are cleared if there's an equal sign present.

Knowing nothing at all about any of these issues, I went ahead and built
the form for setting times etc. on my blinder-thingie using how-to's and
a couple of similar pages  as template.
This is on the weblet that comes with bering 1.0rc2. It's GET, plain and
simple, it works nicely, and the sort of string that is passed to my
script by weblet in $QUERY_STRING is:

SelDAY=1SUNUP=0630SUNRISE=30SUNDOWN=2230SUNSET=1ONOFF=1

Just to be sure, I went and checked the script that parses this, and it
does indeed look for the '='s (and the '?'s) in order to break it up.

I looked at sh-httpd, and I see the place in do-cgi() where it checks
for '*=*', but either:

There's something I don't understand, or
It doesn't work as intended... (?)

I just thought I should mention this, in case someone is about to go
over sh-httpd, and passing multiple arguments in this fashion is a
no-no...

 My understanding is cgi scripts recieving data like the above example
 via a GET or HEAD request are supposed to refer to the QUERY_STRING
 variable, which should be properly exported by sh-httpd. 

- or maybe this explains it? 

In any case, FWIW I agree that authentication, however nice it would
be, can't compete with tunneling through ssh... 0.02 currency

Regards,
Jon


---
This sf.net email is sponsored by:ThinkGeek
No, I will not fix your computer.
http://thinkgeek.com/sf

___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Hi there, and (bug?) report

2002-06-26 Thread Jon Clausen

On Wed, Jun 26, 2002 at 06:27:31PM +0100, Luis.F.Correia wrote:
 if you included your package name as the last one, did you produce
 an extra line at the end?
 
 Debian based systems like and extra line at the end.
 
 Or I might also be wrong :)

No,no, you're quite right in that there should be an empty line at the
end (if that's what you meant), at least that's what I learned from the
docs...
But that was exactly one of the things that I checked. 

I did try out a couple of things before I started reading through the
scripts:

- Check that indeed there were empty lines in all the files (.list .conf
  .version and .help)

- Move my package name up among the others listed in 'packages'

- Tried (just for the h*ll of it) to add the package to syslinux.cfg

- shuffle the order in 'packages'

You know, just 'o.k. so what if I push *this* button'... also I did
restore whatever files to their original state before I started down a
new path.
None of it made any difference, but when not even renaming 'packages' to
'packs.safe' had any effect on the backup list... I started thinking
that something might have changed on Bering, that wasn't reflected in
the docs.

I know that some things *did* change, because Dachstein which is what
I've been using 'till now, doesn't have the 'backup floppy' option...

Am I the only one who saw this? 'cause if I am, I must presume something
is amiss wrt to my system...

Nice thing is, that I managed to make the package anyway, and I can now
try it out on a newer Bering... :)

Comments welcome.

Cheers,
Jon

P.S. I posted the first msg *hours* ago... Is this delay normal, or is
there something in my mail setup that's confusing the list server?

I recently switched from Kmail to Postfix/Fetchmail/Procmail/Mutt, and I
wouldn't be surprised if something *is* shady in that department...


---
This sf.net email is sponsored by: Jabber Inc.
Don't miss the IM event of the season | Special offer for OSDN members! 
JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn

___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Hi there, and (bug?) report

2002-06-26 Thread Jon Clausen

On Wed, Jun 26, 2002 at 09:53:35PM +0200, Etienne Charlier wrote:
 Hi,
 
  So either something is weird on my host (bering 1.0rc2), there's a bug
  in the backup scripts somewhere, or the documentation is not quite up to
  par...
 I had the same problem when trying to build a package for openvpn
 ( openvpn.sourceforge.net)
 I think that the documentation doesn't (yet) describe the changes in the

That's pretty much what I suspected. Especially since it worked (well
looked/behaved as such) nicely after I made the change in backdisk
instead of packages...

But other than making the entry in backdisk, should I also be adding it
to packages, or will the system do that when the package gets loaded on
next boot?

Anything else?

So I guess the docs need updating?

And in that case;

Would it be a matter of simply adding a note about this difference in
Dach/Bering? Or are there more things should be added?

TIA
Jon


---
This sf.net email is sponsored by: Jabber Inc.
Don't miss the IM event of the season | Special offer for OSDN members! 
JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn

___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Hi there, and (bug?) report

2002-06-26 Thread Jon Clausen

On Wed, Jun 26, 2002 at 01:53:36PM -0700, Mike Noyes wrote:
 On Wed, 2002-06-26 at 13:37, David Douthitt wrote:
  26 Jun 17:23:24 UTC  Received at my main mailbox (mailbag.com)
  26 Jun 17:26:54 UTC  Received at my main mail redirection
  26 Jun 17:22:04 UTC  Processed at SourceForge (sourceforge.net).
  26 Jun 17:16:48 UTC  Received at SourceForge (sourceforge.net).
  26 Jun 08:57:05 UTC  Received at cybercity.dk.
  26 Jun 08:57:04 UTC  Received at kinkon.
  
  It doesn't appear to be some sort of bad time setting, either on kinkon,
  cybercity.dk, OR sourceforge.net.  I deduce this because:
  
  1) the host cicero0.cybercity.dk (212.242.40.52) and kinkon (212.242.52.118)
 are separate hosts yet have same time (8:57 UTC give or take) and same
 timezone (CEST);
  
  2) hosts beyond cicero0.cybercity.dk are all different timezones except they
 have the same time UTC (after accounting for the U.S. 12-hour clock).
  
  From 08:57:05 UTC to 17:16:48 UTC it remained on cicero0.cybercity.dk 
(212.242.40.52).
  It appears to me that cybercity.dk held your mail for 8.25 hours... (!)
 
 David,
 Nice job. :-)
 
 I should have looked for the machine causing the lag also. I'm keeping
 this analysis as a template for future troubleshooting.

Yeah, I agree... nice analysis :)

I should have guessed, though. Cybercity is my ISP, and
they've been mucking around with the mailsystem since spring... I just
hope they get their act together, soon.

I'm just always nervous that the fault's at my end :-P

Example: I ruined my 170+ days uptime by rebooting my LRP box during
last fall's rash of code/nimda because my adsl was slowing to a crawl,
and I thought something had gone sour in the box. When that didn't help
I called CC, and it turned out that the cisco677 was configured to
respond to port 80 (dunno why) and that *it* was getting bashed by all
that crap... The support person shut off port80, and everythings been
fine ever since (124 days)

note to self: Don't automatically assume that *you're* at fault ;)

Anyway, my next msg arrived in reasonable time, so I guess they're back
on track now... maybe ;-P

Jon


---
This sf.net email is sponsored by: Jabber Inc.
Don't miss the IM event of the season | Special offer for OSDN members! 
JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn

___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel