RE: [Leaf-devel] [OT?] Portland? was Upcoming Conferences

[Richard Amerman]

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


áŠËë^™¨¥ŠË)¢{(­ç[É8bžAžzEž•Ê&zÚ yé!y«Þžm§ÿí†)äç¤r‰¿±òÞi÷^½éfj)bž   
b²ÒÞi÷^½éeŠËl²‹«qç讧zØm¶›?þX¬¶Ë(º·~Šàzw­þX¬¶ÏåŠËbú?•æŸuëÞ

Re: [Leaf-devel] [OT?] Upcoming Conferences

[Chad Carr]

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

Re: [Leaf-devel] CVS structure ???

[Mike Noyes]

On Wed, 2002-07-17 at 15:50, Michael D. Schleif wrote:
> [2] Since cvs does not retain group, mode nor ownership attributes, [1]
> is further complicated and requires another kludge to correct directory
> and files attributes.

Michael,
This should only be an issue when exporting for public distribution. The
recommended solution is a script to export, configure, and package your
release.

# Exporting For Public Distribution 
http://cvsbook.red-bean.com/cvsbook.html#Exporting_For_Public_Distribution

-- 
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] CVS structure ???

[Mike Noyes]

On Wed, 2002-07-17 at 15:50, Michael D. Schleif wrote:
> I've been considering using whatever structure I settle on as my
> development environment.  I have cvs setup on my own network and hope to
> integrate leaf development into my other development projects.  However,
> cvs doesn't lend itself to this end for several reasons:
> 
> [1] Each sandbox includes cvs directories under each directory in the
> project.  So, rolling up the hierarchy directly into an LRP is
> cumbersome.  cvs export only adds to the kludge.

Michael,
I believe a module alias will solve this problem.

> [2] Since cvs does not retain group, mode nor ownership attributes, [1]
> is further complicated and requires another kludge to correct directory
> and files attributes.

This is a problem. CVS only tracks the x bit of files. I think there is
a workaround, but I can't remember it right now.

> [3] I still have not figured out how to force synchronization between
> cvs revision numbers and project source revision numbers.

You can't. Tags allow you to indicate release versions.

> [4] All of this makes inclusion of /package/.lrp an
> absolute must!
> 
> If anybody has overcome any of these obstacles, I'd appreciate
> enlightenment . . .

I hope some of this information was useful.

-- 
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] CVS structure ???

[Michael D. Schleif]

David Douthitt wrote:

[ snip ]

> My model has been the following:
> 
> archives/
>   .tar.gz
>   .bz2
>   ...
> 
> iproute2/
>   distinfo
>   Makefile
>   patches/
> .diff
> .diff
> ...
>   work/ {temporary dir; created and used to compile within}
>   binaries/ {temporary dir; created and stores binaries ONLY (no path)}
>   world/{temporary dir; created and used to store full paths
>  and all files needed within the structure}
> 
> /
> ...
> 
> My current lrp "package" setup was to have the following:
> 
> iproute2-/
>   lrp/ {created}
> ...
> 
> Under lrp/ there is a Makefile which contains all of the targets to make packages, 
>etc.
> There is also a directory like world/ above which contains all paths and a Makefile
> in each directory that needs to have a binary in it.
> 
> After this lrp/ directory is correctly configured, then the entire directory is
> "wrapped up" into a *.diff file and saved with the unmodified source archive.  
>Examples
> of this can be found in the Oxygen/LEAF Resource CDROM.
> 
> Perhaps what I will do is to use this patch as a regular patch in the CVS ports tree
> and add the patch to the source code, then use it to create packages at will.

I've been considering using whatever structure I settle on as my
development environment.  I have cvs setup on my own network and hope to
integrate leaf development into my other development projects.  However,
cvs doesn't lend itself to this end for several reasons:

[1] Each sandbox includes cvs directories under each directory in the
project.  So, rolling up the hierarchy directly into an LRP is
cumbersome.  cvs export only adds to the kludge.

[2] Since cvs does not retain group, mode nor ownership attributes, [1]
is further complicated and requires another kludge to correct directory
and files attributes.

[3] I still have not figured out how to force synchronization between
cvs revision numbers and project source revision numbers.

[4] All of this makes inclusion of /package/.lrp an
absolute must!

If anybody has overcome any of these obstacles, I'd appreciate
enlightenment . . .

-- 

Best Regards,

mds
mds resource
888.250.3987

Dare to fix things before they break . . .

Our capacity for understanding is inversely proportional to how much we
think we know.  The more I know, the more I know I don't know . . .


---
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?] Upcoming Conferences

[Mike Noyes]

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.

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

[Leaf-devel] [OT?] Upcoming Conferences

[David Douthitt]

[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 :-)



---
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] CVS structure ???

[David Douthitt]

On Wed, Jul 17, 2002 at 03:21:32PM -0500, Michael D. Schleif wrote:
> 
> Jeff Newmiller wrote:

> > CVS is designed to handle directories full of information... so a
> > directory tree of html documents is a natural thing to enter.
> > 
> > An idea...
> > 
> >   net-snmp/
> > README.txt
> > package/
> >   net-snmp.lrp
> > target/
> >   etc/
> > blahblah
> >   usr/
> > bin/
> >   snmpbinary
> >   ...
> > doc/
> >   index.html
> >   images/
> > image1.jpg
> >   ...
> > src/
> >   sourcefiles...
> 
> [ snip ]
> 
> I took a liking to this structure, which you can see here:
> 
> 
> 
> I appreciate *ALL* feedback on this infrastructure, before I get carried
> away with further additions to cvs.
> 
> What do you think?

My model has been the following:

archives/
  .tar.gz
  .bz2
  ...

iproute2/
  distinfo
  Makefile
  patches/
.diff
.diff
...
  work/ {temporary dir; created and used to compile within}
  binaries/ {temporary dir; created and stores binaries ONLY (no path)}
  world/{temporary dir; created and used to store full paths
 and all files needed within the structure}

/
...

My current lrp "package" setup was to have the following:

iproute2-/
  lrp/ {created}
...

Under lrp/ there is a Makefile which contains all of the targets to make packages, etc.
There is also a directory like world/ above which contains all paths and a Makefile
in each directory that needs to have a binary in it.

After this lrp/ directory is correctly configured, then the entire directory is
"wrapped up" into a *.diff file and saved with the unmodified source archive.  Examples
of this can be found in the Oxygen/LEAF Resource CDROM.

Perhaps what I will do is to use this patch as a regular patch in the CVS ports tree
and add the patch to the source code, then use it to create packages at will.



---
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] cvs-commits-list

[Mike Noyes]

Everyone,
Project members should subscribe to our leaf-cvs-commits list.

http://lists.sourceforge.net/lists/listinfo/leaf-cvs-commits

-- 
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] Perl help

[Erich Titl]

Hi Mike

in case noone noticed until now..
there was a glitch in the perl script anyway, see the following test

luna > perl casetest.pl   MakefilefoobarDDD
All filenames must be completely lowercase except Makefiles. (/)
All filenames must be completely lowercase except Makefiles. (/)

but of course taking it out removed it.

cheers

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] CVS structure ???

[Michael D. Schleif]

Jeff Newmiller wrote:
> 
> On Wed, 10 Jul 2002, Michael D. Schleif wrote:

[ snip ]

> > I am starting to realize that, perhaps, I should take a directory based
> > approach to helices' cvs tree.
> >
> > I have not settled on any particular structure.  However, I am wondering
> > about several things:

[ snip ]

> CVS is designed to handle directories full of information... so a
> directory tree of html documents is a natural thing to enter.
> 
> An idea...
> 
>   net-snmp/
> README.txt
> package/
>   net-snmp.lrp
> target/
>   etc/
> blahblah
>   usr/
> bin/
>   snmpbinary
>   ...
> doc/
>   index.html
>   images/
> image1.jpg
>   ...
> src/
>   sourcefiles...

[ snip ]

I took a liking to this structure, which you can see here:



I appreciate *ALL* feedback on this infrastructure, before I get carried
away with further additions to cvs.

What do you think?

-- 

Best Regards,

mds
mds resource
888.250.3987

Dare to fix things before they break . . .

Our capacity for understanding is inversely proportional to how much we
think we know.  The more I know, the more I know I don't know . . .


---
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] Current CVS Oxygen Tree

[Mike Noyes]

On Wed, 2002-07-17 at 13:00, Michael D. Schleif wrote:
> 
> Mike Noyes wrote:
> > 
> > On Wed, 2002-07-17 at 12:23, David Douthitt wrote:
> > > I've been looking at some things, and updated
> > > syslinux and e3 (in the CVS tree) to their apparent
> > > current versions.
> > >
> > > I've noticed that CVS can be a major pain, especially with
> > > renaming files, or deleting or moving directories.
> > 
> > David,
> > Agreed. CVS has no commands for moving files or directories. It also has
> > no command for removing directories from a repository.
> 
> Look here 

Michael,
Pruning doesn't remove directories from a repository. It removes them
from working copies.

-- 
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] Current CVS Oxygen Tree

[Michael D. Schleif]

Mike Noyes wrote:
> 
> On Wed, 2002-07-17 at 12:23, David Douthitt wrote:
> > I've been looking at some things, and updated
> > syslinux and e3 (in the CVS tree) to their apparent
> > current versions.
> >
> > I've noticed that CVS can be a major pain, especially with
> > renaming files, or deleting or moving directories.
> 
> David,
> Agreed. CVS has no commands for moving files or directories. It also has
> no command for removing directories from a repository.

Look here 

[ snip ]

-- 

Best Regards,

mds
mds resource
888.250.3987

Dare to fix things before they break . . .

Our capacity for understanding is inversely proportional to how much we
think we know.  The more I know, the more I know I don't know . . .


---
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] Current CVS Oxygen Tree

[Mike Noyes]

On Wed, 2002-07-17 at 12:23, David Douthitt wrote:
> I've been looking at some things, and updated
> syslinux and e3 (in the CVS tree) to their apparent
> current versions.
> 
> I've noticed that CVS can be a major pain, especially with
> renaming files, or deleting or moving directories.

David,
Agreed. CVS has no commands for moving files or directories. It also has
no command for removing directories from a repository. Subversion is in
development at this time. It addresses these problems and others.

Subversion
http://subversion.tigris.org/

You may want to consider using generic names where possible, and use the
commit message to indicate the version committed.

http://cvs.leaf-project.org/cgi-bin/viewcvs.cgi/leaf/devel/ddouthitt/base/e3/
Example:
cvs ci -m "New checksum for new archive and new version..." \
e3-2.33.tar.gz.md5

Becomes:
cvs ci -m "update e3 md5 to v2.33" e3.tar.gz.md5

This would allow updates without deleting files.

-- 
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] image extractor program

[Jeff Newmiller]

On Wed, 17 Jul 2002, George Georgalis wrote:

> Below is a little script to mount and extract an image in a way that will
> allow for editing and repackaging of the lrp modules.

This is neat.  I normally extract the contents of the package I am
interested in, since I navigate the actual router filesystem and read its
/var/lib/lrpkg/*.list files to find out which package I am interested in.
ssh is my friend. :)

> It uses tmp files but eventually creates (replaces) a directory called
> lrp-super, which contains a directory for each lrp module and the root
> filesystem per the package below it. (see the second find output below)
> 
> I plan to borrow some code from lrcfg to repackage and add some new code 
> to manage the other critical files and reconstruct the image.

Sounds useful.

> I wanted to post this now for comments.

[...]

> #!/bin/sh
> 
> [ -z $1 ] && echo 'Supply image file to mount and extract' && exit
> [ -z '`du $1 | grep 1688`' ] && echo 'Supply image file to mount and extract' && exit
> 
> s=`date +%s`
> mnt='lrp-mnt-'$s
> mkdir $mnt
> 
> super='lrp-super-'$s
> mkdir $super
> 
> mount -oloop $1 $mnt

# I think this should be:
mount -t msdos -oloop $1 $mnt

> 
> cd $super
> pkgs=`ls ../$mnt/*lrp | sed -e 's/^.*initrd.lrp//'`

# Not all packages on the disk get loaded:
pkgs=`grep PKGPATH ../$mnt/syslinux.cfg \
  | tr ' ' '\n' | grep LRP | sed -e 's/LRP=//' | tr ',' ' '`

> for pkg in $pkgs ; do
> name=`echo $pkg | sed -e 's/^.*\///' -e 's/.lrp$//'`
> mkdir $name

The philosophy of extracting all of them, yet keeping their contents
separate, seems odd.  Certainly this would share little in common with
lrpkg.

I can see wanting tools to manipulate specific packages.

I can see wanting to see how the packages all overlay each
other.

But this approach seems to confound these needs.  Perhaps a tool to grab
the files out of the image, another tool to manipulate the packages, and
another to do a unpack/merge would lead to more re-use?

I rarely use floppies once I have the system working, since the dust kills
them.  Thus, I normally back up the files that comprise my system rather
than images.

> cd $name
> tar xzf ../$pkg
> cd ../
> done
> cd ..
> rm -rf lrp-super
> mv $super lrp-super
> umount $mnt ; rm -rf $mnt
> exit 0

Cool script. :)

---
Jeff NewmillerThe .   .  Go Live...
DCN:<[EMAIL PROTECTED]>Basics: ##.#.   ##.#.  Live Go...
  Live:   OO#.. Dead: OO#..  Playing
Research Engineer (Solar/BatteriesO.O#.   #.O#.  with
/Software/Embedded Controllers)   .OO#.   .OO#.  rocks...2k
---




---
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] Current CVS Oxygen Tree

[David Douthitt]

I've been looking at some things, and updated
syslinux and e3 (in the CVS tree) to their apparent
current versions.

I've noticed that CVS can be a major pain, especially with
renaming files, or deleting or moving directories.

Anyway, there are a few updates to the ports-style
setup that need to be done yet:

* Handle multiple distribution files
* Make checksum file use a generic name
* Rename patches and other files to remove version numbers
* Work on a "make lrp" (or "make package")
* Work on some form of "make install"
* A "make world" would be nice - might already be there.



---
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] image extractor program

[David Douthitt]

On Wed, Jul 17, 2002 at 01:56:31PM -0400, George Georgalis wrote:

> Below is a little script to mount and extract an image in a way that will
> allow for editing and repackaging of the lrp modules.

Every script is a solution to a problem; I don't see the problem, but
anyway...

> #!/bin/sh
> 
> [ -z $1 ] && echo 'Supply image file to mount and extract' && exit
> [ -z '`du $1 | grep 1688`' ] && echo 'Supply image file to mount and extract' && exit

What if the image file is 1722?

> s=`date +%s`
> mnt='lrp-mnt-'$s
> mkdir $mnt
> 
> super='lrp-super-'$s
> mkdir $super
> 
> mount -oloop $1 $mnt
> 
> cd $super
> pkgs=`ls ../$mnt/*lrp | sed -e 's/^.*initrd.lrp//'`

How about:

pkgs=`ls ../$mnt/*lrp | grep -v initrd.lrp`

> for pkg in $pkgs ; do
> name=`echo $pkg | sed -e 's/^.*\///' -e 's/.lrp$//'`

How about:

name=`basename $pkg .lrp`

> mkdir $name
> cd $name
> tar xzf ../$pkg
> cd ../
> done
> cd ..
> rm -rf lrp-super
> mv $super lrp-super
> umount $mnt ; rm -rf $mnt
> exit 0

Sounds like it populates an image with packages, eh?



---
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: UML-LEAF filesystem

[Jacques Nilo]

Le Mardi 16 Juillet 2002 20:33, vous avez écrit :
Hi Vic
My UML doc is really  outdated. I'll try to uptade it over the WE.
Basically you have to create your Bering LEAF fs yourself.
The procedure is as follow:

1/ creates a 2M minix file on the same dir as your linux-uml kernel
dd if=/dev/zero of=bering_fs bs=512k count=4
mkfs.minix bering_fs

2/ Mount a Bering image and bering_fs
mount -o loop -t msdos Bering_1.0-rc3...   /mnt1
mount -o loop bering_fs /mnt2

3/ Copy the *.lrp files to bering_fs
cp /mnt1/*.lrp /mnt2
You need to have initrd.lrp in the same level dir as the uml-kernel & 
bering_fs
cp /mnt1/initrd.lrp .

4/ Umount mnt1 and mnt2

5/ Creates the startuml script :

[leaf@linux uml]$ cat startuml
#!/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,shorwall
[leaf@linux uml]$

Et voila !

./startuml should fire up your virtual router

Good luck
Jacques

> G'Day Jacques,
>
> Firstly, congratulations and thanks on the Bering-LEAF build!  It's just
> what I need for my setup at home, and I'll get straight into working on it
> when I get back home to Australia (I'm working in the US for a few weeks).
>
> For another project, I would like to experiment with LEAF under UML, and
> have downloaded one of the UML kernels from SourceForge.  However, I
> can't find the LEAF-UML filesystem (leaf_fs) you refer to in your HOWTO!
>
> I have downloaded the Debian/slink filesystem, but it does not seem very
> applicable to what I am trying to do...  Can you help me locate the
> leaf_fs filesystem?  Is there a process I can use to build one from a
> Bering floppy disk image?
>
> Thanks and regards,
> Vic Cross


---
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] pptpd.lrp with bering rc3

[Jacques Nilo]

Le Mercredi 17 Juillet 2002 15:15, Stefan a écrit :
Hi Stefan:
Thanks for this very precise description. I'll try to look at that before the 
end of the week.
Two complementary questions:
1/ Could you confirm that this setting was working OK with rc1
2/ Could you give me the command (from the client side I guess) which 
generates the error ?
The main difference introduced by rc3 is the grsecurity patch. An easy test 
would be to replace the linux kernel and module.lrp file from rc1 to rc3 and 
see if that fixes your pb.
Jacques
> salut jacques
>
> you need:
>
> - image from
> http://prdownloads.sourceforge.net/leaf/Bering_1.0-rc3_img_bering_1680.bin?
>d ownload
> - pptpd.lrp from
> http://leaf.sourceforge.net/devel/jnilo/bering/latest/packages/pptpd.lrp
> - patched pppd from
> http://leaf.sourceforge.net/devel/jnilo/bering/latest/packages/pppd/pppd-pp
>t p-reqmmpe.gz
> - slhc.o,ppp_generic.o,ppp_deflate.o,ppp_async.o,ppp_mppe from
> http://leaf.sourceforge.net/devel/jnilo/bering/latest/modules/drivers/net/
>
> 1. put all on the disk. and activate ppp.lrp and pptpd.lrp in syslinux.cfg
> 2. edit /etc/modules with slhc,ppp_generic,ppp_deflate,ppp_async.o,ppp_mppe
> (this order)
> 3. add to /etc/shorewall/rules 4 lines:
>
> ACCEPTnetfwtcp1723
> ACCEPTfwnettcp1723
> ACCEPTnetfw47-
> ACCEPTfwnet47-
> 4. add to /etc/shorewall/hosts
>
> locppp+:192.168.1.0/24
>
> 5. add to /etc/shorewall/policy
>
> locloc ACCEPT
>
> 6. create /etc/pptpd.conf:
>
> speed 115200
> option /etc/ppp/pptpd-options
> debug
> localip 192.168.1.254
> remoteip 192.168.1.240-250
>
> 7. create /etc/ppp/ppptp-options
>
> debug
> name servername
> domain my.domain.net
> +chap
> +chapms
> +chapms-v2
> mppe-40
> mppe-stateless
> ms-dns 192.168.1.254
> netmask 255.255.255.0
> proxyarp
> lock
>
> 8. backup all the involved modules and restart.
>
> à bientôt
> stefan
>
> > Hi Stefan:
> > Could you  describe the simplest possible setup working with rc1 and not
> > working with rc3 so that I can try to reproduce your pb and see what I
> > can
>
> do
>
> > fo you ? I have never tried ppptd myself but I can learn...
> > Jacques
> >
> > I have on my home network access to win98 or linux machines.
>
> ---
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
>
> ___
> Leaf-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/leaf-devel


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

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

Re: [Leaf-devel] Perl help

[Mike Noyes]

On Wed, 2002-07-17 at 10:57, Brad Fritz wrote:
> 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.

Brad,
Thanks for taking another look at the file. I committed the changes
again.

> What was the context of the broken pipe message?

It was a errant import to the top level in our repository, by a member
without write privileges there.

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

[Leaf-devel] Anubis one-way SSL and SMTP+TLS

[Mike Noyes]

Everyone,
A request for Anubis support was mentioned to me this morning. Has
anyone taken a look at it?
http://anubis.sourceforge.net/

It may allow SMTP+TLS support for internal mail clients that don't
support TLS encryption.

-- 
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] Perl help

[Brad Fritz]

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

[Leaf-devel] image extractor program

[George Georgalis]

Below is a little script to mount and extract an image in a way that will
allow for editing and repackaging of the lrp modules.

It uses tmp files but eventually creates (replaces) a directory called
lrp-super, which contains a directory for each lrp module and the root
filesystem per the package below it. (see the second find output below)

I plan to borrow some code from lrcfg to repackage and add some new code 
to manage the other critical files and reconstruct the image.

I wanted to post this now for comments. Here is an example of the
(extend image) command line usage and the nature of the result.

$ extimg ../orig/Bering_1.0-rc3_img_bering_1680.bin
$ find lrp-super/ -type d -maxdepth 2 | sort
lrp-super/
lrp-super/bridge
lrp-super/bridge/etc
lrp-super/bridge/usr
lrp-super/bridge/var
lrp-super/dhcpd
lrp-super/dhcpd/etc
lrp-super/dhcpd/usr
lrp-super/dhcpd/var
lrp-super/dnscache
lrp-super/dnscache/etc
lrp-super/dnscache/usr
lrp-super/dnscache/var
lrp-super/etc
lrp-super/etc/etc
lrp-super/etc/var
lrp-super/keyboard
lrp-super/keyboard/etc
lrp-super/keyboard/usr
lrp-super/keyboard/var
lrp-super/local
lrp-super/local/usr
lrp-super/local/var
lrp-super/log
lrp-super/log/var
lrp-super/modules
lrp-super/modules/etc
lrp-super/modules/lib
lrp-super/modules/var
lrp-super/ppp
lrp-super/ppp/etc
lrp-super/pppoe
lrp-super/pppoe/etc
lrp-super/pppoe/usr
lrp-super/pppoe/var
lrp-super/ppp/usr
lrp-super/ppp/var
lrp-super/pump
lrp-super/pump/etc
lrp-super/pump/sbin
lrp-super/pump/var
lrp-super/root
lrp-super/root/bin
lrp-super/root/initrd
lrp-super/root/lib
lrp-super/root/root
lrp-super/root/sbin
lrp-super/root/usr
lrp-super/root/var
lrp-super/shorwall
lrp-super/shorwall/etc
lrp-super/shorwall/sbin
lrp-super/shorwall/var
lrp-super/tc
lrp-super/tc/sbin
lrp-super/tc/var
lrp-super/weblet
lrp-super/weblet/etc
lrp-super/weblet/usr
lrp-super/weblet/var


#!/bin/sh

[ -z $1 ] && echo 'Supply image file to mount and extract' && exit
[ -z '`du $1 | grep 1688`' ] && echo 'Supply image file to mount and extract' && exit

s=`date +%s`
mnt='lrp-mnt-'$s
mkdir $mnt

super='lrp-super-'$s
mkdir $super

mount -oloop $1 $mnt

cd $super
pkgs=`ls ../$mnt/*lrp | sed -e 's/^.*initrd.lrp//'`
for pkg in $pkgs ; do
name=`echo $pkg | sed -e 's/^.*\///' -e 's/.lrp$//'`
mkdir $name
cd $name
tar xzf ../$pkg
cd ../
done
cd ..
rm -rf lrp-super
mv $super lrp-super
umount $mnt ; rm -rf $mnt
exit 0


// George

-- 
GEORGE GEORGALIS, System Admin/Architectcell: 347-451-8229 
Security Services, Web, Mail,mailto:[EMAIL PROTECTED] 
File, Print, DB and DNS Servers.   http://www.galis.org/george 



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

[Mike Noyes]

On Wed, 2002-07-17 at 08:34, Mike Noyes wrote:
> leaf/CVSROOT/enforce_naming rev 1.3
> http://cvs.leaf-project.org/cgi-bin/viewcvs.cgi/leaf/CVSROOT/

Everyone,
Our enforce_naming is now at rev 1.4, and lowercase name enforcement
should be disabled. Please let me know if you experience any problems. I
thank Michael and Brad for their help.

-- 
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] is Bering GNU?

[Jeff Newmiller]

On Wed, 17 Jul 2002, George Georgalis wrote:

> On Sat, Jul 13, 2002 at 08:47:58AM +0200, Etienne Charlier wrote:

[...]

> >3  You seem very upset by not being able to {use | install} bering on your
> > system and you feel better if you can put the responsability on someone
> >else.
> 
> I'm using Bering very differently than most users, isp verses home
> / small office.  My needs are very different, it would be good if
> modifications and sharing thereof were easier. This is what I'm working
> towards.

Bering uses the Debian networking scripts (ifupdown), which I do not think
are intended only for home/small office.  I also think Shorewall is a very
flexible tool. I could empathize more with your NIH point of view if you
were working with Dachstein, which is very optimized for small network
use.

The one area that LEAF has not been so good at has been redundant
connections.  The most robust approach I have seen so far involves scripts
customized to detect specific ping failures that invoke ifup and ifdown
and shorewall restart as appropriate.  What has been lacking are EGP
protocol support, I suspect because people doing EGP work haven't been
using Bering.  This is a bit of chicken and egg problem.  I don't know
details, but Zebra doesn't appear to be up to kernel 2.4 yet.

Regarding difficulty changing Bering: when you get used to the
load-from-scratch approach used in Bering, I think you should find that
its operation is very transparent if you are familiar with Linux and
SysV-style operation.  The RCDLINKS bit is a small stumbling block, and
the package format is unusual, but other than that it seems very similar
to my Debian workstation.

The CVS tree will be a valuable addition to the LEAF resources.  
Meanwhile, most of us have learned LEAF variants by poking around running
LEAF boxes rather than dissecting and building packages offline... so by
the time we do get around to the package structure it makes a little more
sense.  Building a box for remote installation your first time out is
pretty ambitious, particularly when you choose to start replacing major
functionality at the same time.

---
Jeff NewmillerThe .   .  Go Live...
DCN:<[EMAIL PROTECTED]>Basics: ##.#.   ##.#.  Live Go...
  Live:   OO#.. Dead: OO#..  Playing
Research Engineer (Solar/BatteriesO.O#.   #.O#.  with
/Software/Embedded Controllers)   .OO#.   .OO#.  rocks...2k
---



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

[Mike Noyes]

On Wed, 2002-07-17 at 09:58, Michael D. Schleif wrote:
> 
> Mike Noyes wrote:
> > 
> > On Wed, 2002-07-17 at 08:58, Michael D. Schleif wrote:
> > > Mike Noyes wrote:
> > > >
> > > > Anyone,
> > > > Will removing the following lines from enforce_naming leave the perl
> > > > script functional?
> > >
> > > Yes, absolutely yes; provided that either all of the lines are
> > > completely _removed_ or completely commented out.
> > 
> > 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.
> > 
> > Any enlightenment is appreciated.
> 
> Previously, you said that _cvs import_ somehow bypasses case checking,
> or this script.  Since all I did last night was _cvs import_, and
> because there is nothing in enforce_naming (no version in cvs) that
> would result in "broken pipe" errors, I believe the culprit is
> elsewhere.

Michael,
It seems to, but I don't think it should. Our commitinfo seems to
process our cvs_acls script but not enforce_naming on imports. I need to
find a reference to what commands activate commitinfo in which
circumstances.

> > > Also, remove the lone `next;' at end of for loop, since the for loop
> > > does that automatically, by design ;>
> > 
> > Is this true for older versions of perl too? The SF cvs server may not
> > have the newest perl release on it.
> 
> I've been Perl'ing since v4.0x days.  That is the design of a for loop. 
> That `next;' does not do anything bad except waste a couple cpu cycles .

Thanks for the info. I'll remove it also.

-- 
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] Perl help

[Mike Noyes]

On Wed, 2002-07-17 at 09:54, Brad Fritz wrote:
> 
> 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?

Brad,
Thanks for the proof. The broken pipe may have been a coincidence, but I
thought I should check before trying this again.

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


-- 
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] Perl help

[Michael D. Schleif]

Mike Noyes wrote:
> 
> On Wed, 2002-07-17 at 08:58, Michael D. Schleif wrote:
> > Mike Noyes wrote:
> > >
> > > Anyone,
> > > Will removing the following lines from enforce_naming leave the perl
> > > script functional?
> >
> > Yes, absolutely yes; provided that either all of the lines are
> > completely _removed_ or completely commented out.
> 
> 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.
> 
> Any enlightenment is appreciated.

Previously, you said that _cvs import_ somehow bypasses case checking,
or this script.  Since all I did last night was _cvs import_, and
because there is nothing in enforce_naming (no version in cvs) that
would result in "broken pipe" errors, I believe the culprit is
elsewhere.

> > >  # 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/
> >
> > Also, remove the lone `next;' at end of for loop, since the for loop
> > does that automatically, by design ;>
> 
> Is this true for older versions of perl too? The SF cvs server may not
> have the newest perl release on it.

I've been Perl'ing since v4.0x days.  That is the design of a for loop. 
That `next;' does not do anything bad except waste a couple cpu cycles .
. .

-- 

Best Regards,

mds
mds resource
888.250.3987

Dare to fix things before they break . . .

Our capacity for understanding is inversely proportional to how much we
think we know.  The more I know, the more I know I don't know . . .


---
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] CVS src tree structure

[Mike Noyes]

On Tue, 2002-07-16 at 14:41, David Douthitt wrote:
> On Mon, Jul 15, 2002 at 10:28:00AM -0700, Mike Noyes wrote:
> 
> > I think a system similar to "BSD Ports" or "Gentoo Portage" would be
> > great. David already has sample implementation available.
> > 
> > http://cvs.leaf-project.org/cgi-bin/viewcvs.cgi/leaf/devel/ddouthitt/base/
> 
> Now I've actually (with Mike's help) been able to properly
> update this to reflect the current state of my ports configuration.
> 
> Be aware that I must go over these again to refresh my memory and to
> update any thing that needs updating.
> 
> That directory "archive" isn't supposed to be there; I'm going
> to try and delete it...

David,
The "archives" directory was removed. Your tree should be correct now.
Let me know if you need any other assistance.

-- 
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] Perl help

[Brad Fritz]

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

Re: [Leaf-devel] is Bering GNU?

[George Georgalis]

On Sat, Jul 13, 2002 at 08:47:58AM +0200, Etienne Charlier wrote:

>0. It's quite amazing that such a great product has been developed
>and integrated by a few people during part time ( when do they sleep
>??? )

Yes it is a fantastic project. I only want the distribution presented in
a way that makes it possible for more people to modify or contribute to
the projects development.


>1. I'm not a leaf contributor. I just use the binaries ... and I like them
>You looked at the sourceforge.net but you missed the most usefull part
>of the site the mailing list archive ( a gold mine for the one who
> try to  use it )

Explaining how I arrived at my problems would be very difficult and time
consuming, because the issues come from a very heavily modified distro, I
don't expect people to take the time to understand all my changes. What
I would like to see is an environment where I can communicate all this in
a standard way so it's practical for others to think about what might be
wrong with my picture.

I did write an image extractor which I'll post shortly, this might help
with such communications.


>2  This list was the most polite and fair a ever seen ... till you came
>( maybe i'm a little bit too hard but I cannot express it more correctly )
>(remember the dns resolver thread ??? )

I apologies if I hurt anyone's feelings. If I understand your meaning,
I do try to be polite at all times, if there is one place I'm least
polite it's probably technical communications. Sometimes politeness can
be difficult in technical forum, I can work on this. I really appreciate
responses (public/private) that engage the issues; I'm not out to make
anyone feel bad and I see no benefit from that anyway. No promises, but
your feelings for me might improve. I hope so anyway.

>3  You seem very upset by not being able to {use | install} bering on your
> system and you feel better if you can put the responsability on someone
>else.

I'm using Bering very differently than most users, isp verses home
/ small office.  My needs are very different, it would be good if
modifications and sharing thereof were easier. This is what I'm working
towards.

// George

-- 
GEORGE GEORGALIS, System Admin/Architectcell: 347-451-8229 
Security Services, Web, Mail,mailto:[EMAIL PROTECTED] 
File, Print, DB and DNS Servers.   http://www.galis.org/george 



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

[Mike Noyes]

On Wed, 2002-07-17 at 08:58, Michael D. Schleif wrote:
> Mike Noyes wrote:
> > 
> > Anyone,
> > Will removing the following lines from enforce_naming leave the perl
> > script functional?
> 
> Yes, absolutely yes; provided that either all of the lines are
> completely _removed_ or completely commented out.

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.

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/
> 
> Also, remove the lone `next;' at end of for loop, since the for loop
> does that automatically, by design ;>

Is this true for older versions of perl too? The SF cvs server may not
have the newest perl release on it.

-- 
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] Perl help

[Michael D. Schleif]

Mike Noyes wrote:
> 
> Anyone,
> Will removing the following lines from enforce_naming leave the perl
> script functional?

Yes, absolutely yes; provided that either all of the lines are
completely _removed_ or completely commented out.

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

Also, remove the lone `next;' at end of for loop, since the for loop
does that automatically, by design ;>

-- 

Best Regards,

mds
mds resource
888.250.3987

Dare to fix things before they break . . .

Our capacity for understanding is inversely proportional to how much we
think we know.  The more I know, the more I know I don't know . . .


---
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] is Bering GNU?

[George Georgalis]

On Sat, Jul 13, 2002 at 08:45:12AM +0200, Jacques Nilo wrote:
>Le Samedi 13 Juillet 2002 07:55, George Georgalis a écrit :
>>  Is Bering GNU?
>>
>> I'm beginning to have my doubts. Where is /usr/src/linux/.config?  
>http://leaf.sourceforge.net/devel/jnilo/bering/rc3/
>http://leaf.sourceforge.net/devel/jnilo/bering/rc3/patches/

Excellent - I hadn't found this part of the tree before.

// George

-- 
GEORGE GEORGALIS, System Admin/Architectcell: 347-451-8229 
Security Services, Web, Mail,mailto:[EMAIL PROTECTED] 
File, Print, DB and DNS Servers.   http://www.galis.org/george 



---
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] Perl help

[Mike Noyes]

Anyone,
Will removing the following lines from enforce_naming leave the perl
script functional?

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

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

[Leaf-devel] Re: is Bering GNU?

[George Georgalis]

>George,
>David has a proposed solution for building our releases/branches from
>cvs. It's similar to the BSD ports system. Any feedback you have on
>David's proposed src build solution is welcome.
>
>http://cvs.leaf-project.org/cgi-bin/viewcvs.cgi/leaf/devel/ddouthitt/base/

This looks excellent!

// George

-- 
GEORGE GEORGALIS, System Admin/Architectcell: 347-451-8229 
Security Services, Web, Mail,mailto:[EMAIL PROTECTED] 
File, Print, DB and DNS Servers.   http://www.galis.org/george 



---
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] ppptd.lrp with bering rc3

[Stefan]

salut jacques

you need:

- image from
http://prdownloads.sourceforge.net/leaf/Bering_1.0-rc3_img_bering_1680.bin?d
ownload
- pptpd.lrp from
http://leaf.sourceforge.net/devel/jnilo/bering/latest/packages/pptpd.lrp
- patched pppd from
http://leaf.sourceforge.net/devel/jnilo/bering/latest/packages/pppd/pppd-ppt
p-reqmmpe.gz
- slhc.o,ppp_generic.o,ppp_deflate.o,ppp_async.o,ppp_mppe from
http://leaf.sourceforge.net/devel/jnilo/bering/latest/modules/drivers/net/

1. put all on the disk. and activate ppp.lrp and pptpd.lrp in syslinux.cfg
2. edit /etc/modules with slhc,ppp_generic,ppp_deflate,ppp_async.o,ppp_mppe
(this order)
3. add to /etc/shorewall/rules 4 lines:

ACCEPTnetfwtcp1723
ACCEPTfwnettcp1723
ACCEPTnetfw47-
ACCEPTfwnet47-
4. add to /etc/shorewall/hosts

locppp+:192.168.1.0/24

5. add to /etc/shorewall/policy

locloc ACCEPT

6. create /etc/pptpd.conf:

speed 115200
option /etc/ppp/pptpd-options
debug
localip 192.168.1.254
remoteip 192.168.1.240-250

7. create /etc/ppp/ppptp-options

debug
name servername
domain my.domain.net
+chap
+chapms
+chapms-v2
mppe-40
mppe-stateless
ms-dns 192.168.1.254
netmask 255.255.255.0
proxyarp
lock

8. backup all the involved modules and restart.

à bientôt
stefan

> Hi Stefan:
> Could you  describe the simplest possible setup working with rc1 and not
> working with rc3 so that I can try to reproduce your pb and see what I can
do
> fo you ? I have never tried ppptd myself but I can learn...
> Jacques
>
> I have on my home network access to win98 or linux machines.




---
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] CVS structure ???

[George Georgalis]

On Wed, Jul 10, 2002 at 01:01:27PM -0700, Jeff Newmiller wrote:
>On Wed, 10 Jul 2002, Michael D. Schleif wrote:

>CVS is designed to handle directories full of information... so a
>directory tree of html documents is a natural thing to enter.
>
>An idea...
>
>  net-snmp/
>README.txt
>package/
>  net-snmp.lrp
>target/
>  etc/
>blahblah
>  usr/
>bin/
>  snmpbinary
>  ...
>doc/
>  index.html
>  images/
>image1.jpg
>  ...
>src/
>  sourcefiles...
>
>Let CVS deal with versioning.

Yeah, I was thinking about http/ftp access. Looks good.

// George


-- 
GEORGE GEORGALIS, System Admin/Architectcell: 347-451-8229 
Security Services, Web, Mail,mailto:[EMAIL PROTECTED] 
File, Print, DB and DNS Servers.   http://www.galis.org/george 



---
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] CVS structure ???

[George Georgalis]

On Wed, Jul 10, 2002 at 02:19:58PM -0500, Michael D. Schleif wrote:

>[1] Should I have separate trees for different underlying versions of
>net-snmp?  For example, I committed net-snmp v4.2.4.  I am contemplating
>building and committing both v4.2.5 and the totally different
>distribution v5.x.  So, one line of thinking is like this:
>
>devel/helices/net-snmp/v4.2.4/netsnmp.lrp
>devel/helices/net-snmp/v4.2.4/netsnmpd.lrp

Looks good to me, would allow for recursive wget --no-parent or ncftp -R
and version management would be a simpler. A copy of the current as
devel/helices/net-snmp/current/netsnmpd.lrp
or a zero legnth file 
devel/helices/net-snmp/current-is-v5.0.2
are also helpful; get devel/helices/net-snmp/current-* | sed | ncftpget -R v5.0.2


> presents several
>TXT files that, once clicked on, present descriptive text regarding the
>LRP's that reside in versioned directories below this one.  Another
>example is Jacques Nilo's 
>wonderful page that links to installation and troubleshooting
>information.  How are we to do this under cvs?

I would put the txt files in the version directores for which they
belong.  At some point (maybe even by a cgi to select components) a
custom disk image might be generated, such a program would have no
trouble separating out .txt and .lrp files.

// George

-- 
GEORGE GEORGALIS, System Admin/Architectcell: 347-451-8229 
Security Services, Web, Mail,mailto:[EMAIL PROTECTED] 
File, Print, DB and DNS Servers.   http://www.galis.org/george 



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