[Leaf-cvs-commits] bin/packages/uclibc-0.9/20 hdsupp.lrp,1.4,1.5

2004-06-06 Thread Martin Hejl
Update of /cvsroot/leaf/bin/packages/uclibc-0.9/20
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv26288

Modified Files:
hdsupp.lrp 
Log Message:
Added mkswap binary


Index: hdsupp.lrp
===
RCS file: /cvsroot/leaf/bin/packages/uclibc-0.9/20/hdsupp.lrp,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
Binary files /tmp/cvsL6XXg8 and /tmp/cvsrYTl02 differ



---
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
___
Leaf-cvs-commits mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-cvs-commits


[Leaf-cvs-commits] src/bering-uclibc/apps/hdsupp buildtool.cfg,1.4,1.5

2004-06-06 Thread Martin Hejl
Update of /cvsroot/leaf/src/bering-uclibc/apps/hdsupp
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv26979/hdsupp

Modified Files:
buildtool.cfg 
Log Message:
Added mkswap to hsupp.lrp


Index: buildtool.cfg
===
RCS file: /cvsroot/leaf/src/bering-uclibc/apps/hdsupp/buildtool.cfg,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** buildtool.cfg   1 Jun 2004 17:33:46 -   1.4
--- buildtool.cfg   6 Jun 2004 06:48:22 -   1.5
***
*** 14,23 
hdsupp
  Version  = 1.0
! Revision = 4
  Help EOF
  HD support tools 
  Tools to be create a bootable partition from within Bering-uClibc. 
Currently includes: badblocks, e2label, fdisk, hdparm, mke2fs, mkfs.ext2, 
!   mkfs.ext3, mkfs.minix, mkfs.msdos, swapon, swapoff, syslinux, tune2fs
  LEAF package by __PACKAGER__, __BUILDDATE__
  
--- 14,23 
hdsupp
  Version  = 1.0
! Revision = 5
  Help EOF
  HD support tools 
  Tools to be create a bootable partition from within Bering-uClibc. 
Currently includes: badblocks, e2label, fdisk, hdparm, mke2fs, mkfs.ext2, 
!   mkfs.ext3, mkfs.minix, mkfs.msdos, mkswap, swapon, swapoff, syslinux, tune2fs
  LEAF package by __PACKAGER__, __BUILDDATE__
  
***
*** 102,106 
  Permissions = 755
/File
!  
File
  Source  = usr/sbin/mke2fs
--- 102,112 
  Permissions = 755
/File
!   File
! Source  = sbin/mkswap
! Filename= sbin/mkswap
! Type= binary
! Permissions = 755
!   /File
!   
File
  Source  = usr/sbin/mke2fs



---
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
___
Leaf-cvs-commits mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-cvs-commits


[Leaf-cvs-commits] src/bering-uclibc/apps/util-linux buildtool.mk,1.8,1.9

2004-06-06 Thread Martin Hejl
Update of /cvsroot/leaf/src/bering-uclibc/apps/util-linux
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv26979/util-linux

Modified Files:
buildtool.mk 
Log Message:
Added mkswap to hsupp.lrp


Index: buildtool.mk
===
RCS file: /cvsroot/leaf/src/bering-uclibc/apps/util-linux/buildtool.mk,v
retrieving revision 1.8
retrieving revision 1.9
diff -C2 -d -r1.8 -r1.9
*** buildtool.mk1 Jun 2004 17:34:12 -   1.8
--- buildtool.mk6 Jun 2004 06:48:23 -   1.9
***
*** 33,43 
-$(BT_STRIP) --strip-unneeded $(UTIL_LINUX_DIR)/mount/swapon
-$(BT_STRIP) --strip-unneeded $(UTIL_LINUX_DIR)/disk-utils/mkfs.minix
-cp $(UTIL_LINUX_DIR)/fdisk/fdisk $(UTIL_LINUX_TARGET_DIR)/
-cp $(UTIL_LINUX_DIR)/mount/swapon $(UTIL_LINUX_TARGET_DIR)/
!   -cp $(UTIL_LINUX_DIR)/disk-utils/mkfs.minix $(UTIL_LINUX_TARGET_DIR)/
mkdir -p $(BT_STAGING_DIR)/sbin
-cp $(UTIL_LINUX_DIR)/fdisk/fdisk $(BT_STAGING_DIR)/sbin/
-cp $(UTIL_LINUX_DIR)/mount/swapon $(BT_STAGING_DIR)/sbin/
-cp $(UTIL_LINUX_DIR)/disk-utils/mkfs.minix $(BT_STAGING_DIR)/sbin/
touch $(UTIL_LINUX_DIR)/.build

--- 33,46 
-$(BT_STRIP) --strip-unneeded $(UTIL_LINUX_DIR)/mount/swapon
-$(BT_STRIP) --strip-unneeded $(UTIL_LINUX_DIR)/disk-utils/mkfs.minix
+   -$(BT_STRIP) --strip-unneeded $(UTIL_LINUX_DIR)/disk-utils/mkswap
-cp $(UTIL_LINUX_DIR)/fdisk/fdisk $(UTIL_LINUX_TARGET_DIR)/
-cp $(UTIL_LINUX_DIR)/mount/swapon $(UTIL_LINUX_TARGET_DIR)/
!   -cp $(UTIL_LINUX_DIR)/disk-utils/mkfs.minix $(UTIL_LINUX_TARGET_DIR)/ 
!   -cp $(UTIL_LINUX_DIR)/disk-utils/mkswap $(UTIL_LINUX_TARGET_DIR)/ 
mkdir -p $(BT_STAGING_DIR)/sbin
-cp $(UTIL_LINUX_DIR)/fdisk/fdisk $(BT_STAGING_DIR)/sbin/
-cp $(UTIL_LINUX_DIR)/mount/swapon $(BT_STAGING_DIR)/sbin/
-cp $(UTIL_LINUX_DIR)/disk-utils/mkfs.minix $(BT_STAGING_DIR)/sbin/
+   -cp $(UTIL_LINUX_DIR)/disk-utils/mkswap $(BT_STAGING_DIR)/sbin/
touch $(UTIL_LINUX_DIR)/.build




---
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
___
Leaf-cvs-commits mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-cvs-commits


[Leaf-cvs-commits] bin/bering-uclibc/beta dhcpcd.lrp,NONE,1.1 iptables.lrp,NONE,1.1 ppp-filter.lrp,NONE,1.1 ppp.lrp,NONE,1.1 pppoatm.lrp,NONE,1.1 pppoe.lrp,NONE,1.1 initrd.lrp,1.1,1.2 initrd_ide_cd.lr

2004-06-06 Thread Eric Spakman
Update of /cvsroot/leaf/bin/bering-uclibc/beta
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv20721

Modified Files:
initrd.lrp initrd_ide_cd.lrp modules.lrp modules_ipv6.lrp 
root.lrp 
Added Files:
dhcpcd.lrp iptables.lrp ppp-filter.lrp ppp.lrp pppoatm.lrp 
pppoe.lrp 
Log Message:
Bering-uClibc-2.2 beta 3

Index: root.lrp
===
RCS file: /cvsroot/leaf/bin/bering-uclibc/beta/root.lrp,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
Binary files /tmp/cvs0sePE5 and /tmp/cvsVLMvkG differ

--- NEW FILE: pppoe.lrp ---
(This appears to be a binary file; contents omitted.)

--- NEW FILE: dhcpcd.lrp ---
(This appears to be a binary file; contents omitted.)

--- NEW FILE: ppp.lrp ---
(This appears to be a binary file; contents omitted.)

Index: modules.lrp
===
RCS file: /cvsroot/leaf/bin/bering-uclibc/beta/modules.lrp,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
Binary files /tmp/cvsK4gvIc and /tmp/cvsq3LYtN differ

Index: modules_ipv6.lrp
===
RCS file: /cvsroot/leaf/bin/bering-uclibc/beta/modules_ipv6.lrp,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
Binary files /tmp/cvsBqwOhj and /tmp/cvsSGeH7T differ

--- NEW FILE: ppp-filter.lrp ---
(This appears to be a binary file; contents omitted.)

Index: initrd_ide_cd.lrp
===
RCS file: /cvsroot/leaf/bin/bering-uclibc/beta/initrd_ide_cd.lrp,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
Binary files /tmp/cvsbJBLJm and /tmp/cvsxCMZFX differ

--- NEW FILE: iptables.lrp ---
(This appears to be a binary file; contents omitted.)

Index: initrd.lrp
===
RCS file: /cvsroot/leaf/bin/bering-uclibc/beta/initrd.lrp,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
Binary files /tmp/cvsmgE2Hy and /tmp/cvsbIirJ9 differ

--- NEW FILE: pppoatm.lrp ---
(This appears to be a binary file; contents omitted.)



---
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
___
Leaf-cvs-commits mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-cvs-commits


[Leaf-cvs-commits] doc/guide/user-bering-uclibc bucu-ppp.xml,1.13,1.14

2004-06-06 Thread KP Kirchd�rfer
Update of /cvsroot/leaf/doc/guide/user-bering-uclibc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv9582

Modified Files:
bucu-ppp.xml 
Log Message:
minor corrections


Index: bucu-ppp.xml
===
RCS file: /cvsroot/leaf/doc/guide/user-bering-uclibc/bucu-ppp.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -C2 -d -r1.13 -r1.14
*** bucu-ppp.xml4 May 2004 20:03:17 -   1.13
--- bucu-ppp.xml6 Jun 2004 22:25:06 -   1.14
***
*** 25,29 
  
  revhistory
- 
revision
  revnumber0.4/revnumber
--- 25,28 
***
*** 78,87 
  the configuration of this dial-up modem router. Your external interface
  (to the internet) will be ppp0, your internal interface (to your internal
! network) is supposed to be done through an ethernet network card
! (eth0)./para
  
! paraThe ulink
! url=http://en.tldp.org/HOWTO/PPP-HOWTO/index.html;PPP-Howto/ulink is a
! useful reference for this section./para
  
  paraComments on this section should be addressed to its maintainer: Eric
--- 77,84 
  the configuration of this dial-up modem router. Your external interface
  (to the internet) will be ppp0, your internal interface (to your internal
! network) is supposed to be done through an ethernet network card (eth0)./para
  
! paraThe ulink 
url=http://en.tldp.org/HOWTO/PPP-HOWTO/index.html;PPP-Howto/ulink
! is a useful reference for this section./para
  
  paraComments on this section should be addressed to its maintainer: Eric
***
*** 103,111 
  
  paraBoot a Bering-uClibc floppy image. Once the LEAF menu appears get
! access to the linux shell by (q)uitting the menu. Edit the 
filenamelrpkg.cfg/filename 
! (pre Bering-uClibc-2.2.0) or filenameleaf.cfg/filename (Bering-uClibc-2.2.0 
onwards) 
! file and replace the dhcpcd entry by ppp in the list of packages to be loaded at 
boot. 
! Check the Bering ulink 
url=http://leaf.sourceforge.net/doc/guide/buci-install.html;installation 
guide/ulink 
! to learn how to do that./para
/section
  
--- 100,110 
  
  paraBoot a Bering-uClibc floppy image. Once the LEAF menu appears get
! access to the linux shell by (q)uitting the menu. Edit the
! filenamelrpkg.cfg/filename (pre Bering-uClibc-2.2.0) or
! filenameleaf.cfg/filename (Bering-uClibc-2.2.0 onwards) file and
! replace the dhcpcd entry by ppp in the list of packages to be loaded at
! boot. Check the Bering-uClibc ulink
! url=http://leaf.sourceforge.net/doc/guide/buci-lrpkg.html;Installation
! Guide/ulink to learn how to do that./para
/section
  
***
*** 120,126 
  
  paraTo configure your modules, go to the LEAF Packages configuration
! menu and choose modules. Enter 1) to edit the
! filename/etc/modules/filename file and enter the following
! information:/para
  
  screen
--- 119,124 
  
  paraTo configure your modules, go to the LEAF Packages configuration
! menu and choose modules. Enter 1) to edit the filename/etc/modules/filename
! file and enter the following information:/para
  
  screen
***
*** 135,144 
  ppp_deflate
  
! # Masquerading 'helper' modules
  ip_conntrack_ftp
  ip_conntrack_irc
  ip_nat_ftp
! ip_nat_irc
! /screen
  
  important
--- 133,141 
  ppp_deflate
  
! # Masquerading #39;helper#39; modules
  ip_conntrack_ftp
  ip_conntrack_irc
  ip_nat_ftp
! ip_nat_irc/screen
  
  important
***
*** 173,178 
q) quit

! Selection:
! /screen
  
  paraEntry 1) allows you to adjust the parameter of your ppp connection
--- 170,174 
q) quit

! Selection:/screen
  
  paraEntry 1) allows you to adjust the parameter of your ppp connection
***
*** 203,218 
  defaultroute# ppp becomes default route to the internet
  noipdefault
! lock# don't let other processes besides PPP use the device
! connect /usr/sbin/chat -v -f /etc/chatscripts/provider
! /screen
  
  paraIf you plan to dial into a Windows RAS server or a server that uses
  PAP or CHAP authentication, you need to add a line to this file. Just
! above the connect command, on a line of its own, add:/para
  
  screen
  name your_ISP_login
! connect /usr/sbin/chat -v -f /etc/chatscripts/provider
! /screen
  
  paraYou need this because ppp has to masquerade the firewall as you when
--- 199,212 
  defaultroute# ppp becomes default route to the internet
  noipdefault
! lock# don#39;t let other processes besides PPP use the device
! connect #34;/usr/sbin/chat -v -f /etc/chatscripts/provider#34;/screen
  
  paraIf you plan to 

[Leaf-cvs-commits] doc/guide/user-bering-uclibc bucu-pppoe.xml,1.8,1.9

2004-06-06 Thread KP Kirchd�rfer
Update of /cvsroot/leaf/doc/guide/user-bering-uclibc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv12452

Modified Files:
bucu-pppoe.xml 
Log Message:
minor corrections


Index: bucu-pppoe.xml
===
RCS file: /cvsroot/leaf/doc/guide/user-bering-uclibc/bucu-pppoe.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -C2 -d -r1.8 -r1.9
*** bucu-pppoe.xml  9 May 2004 14:19:30 -   1.8
--- bucu-pppoe.xml  6 Jun 2004 22:37:23 -   1.9
***
*** 90,129 
  titleStep 1: declare the ppp and pppoe packages/title
  
! paraThose two packages are provided on the standard Bering floppy disk,
! but are not activated by default./para
  
! paraBoot a Bering floppy image. Once the LEAF menu appears get access to
! the linux shell by (q)uitting the menu. Edit the filenamelrpkg.cfg/filename
! (pre Bering-uClibc-2.2.0) or filenameleaf.cfg/filename (Bering-uClibc-2.2.0 
onwards)
! file and REPLACE the dhcpcd entry by ppp,pppoe in the list of packages to
! be loaded at boot. Check the Bering-uClibc ulink
! url=http://leaf.sourceforge.net/doc/guide/buci-install.html;installation
! guide/ulink to learn how to do that./para
  
!   section
! titleStep 2: declare the ppp and pppoe modules/title
  
! paraIn order to have a PPPoE connection working, you need to have ppp
! and pppoe support enabled through the appropriate kernel modules. You also
! need to declare the driver(s) module(s) of your network card(s). In the
! following example, we assume that both ethernet interfaces are provided
! through a standard ne 2000 PCI card./para
  
! paraAll the modules which are necessary for a PPPoE connection are
! provided on the standard Bering floppy. You just need to #34;declare#34;
! them since they are not loaded by default. As far as your network cards
! are concerned, the most popular driver modules are provided in
! filename/lib/modules/filename but you might need to download the one
! corresponding to your own hardware from the Bering-uClibc modules ulink
! 
url=http://cvs.sourceforge.net/viewcvs.py/leaf/bin/bering-uclibc/packages/;download
! area/ulink. Refer to the Bering-uClibc ulink
! url=http://leaf.sourceforge.net/doc/guide/buci-install.html;installation
! guide/ulink to learn how to do that./para
  
! paraTo declare your modules, go to the LEAF Packages configuration menu
! and choose modules. Enter 1) to edit the filename/etc/modules/filename
! file and enter the following information:/para
  
! screen
  # 8390 based ethernet cards
  8390
--- 90,131 
  titleStep 1: declare the ppp and pppoe packages/title
  
! paraThose two packages are provided on the standard Bering-uClibc floppy
! disk, but are not activated by default./para
  
! paraBoot a Bering-uClibc floppy image. Once the LEAF menu appears get
! access to the linux shell by (q)uitting the menu. Edit the
! filenamelrpkg.cfg/filename (pre Bering-uClibc-2.2.0) or
! filenameleaf.cfg/filename (Bering-uClibc-2.2.0 onwards) file and
! REPLACE the dhcpcd entry by ppp,pppoe in the list of packages to be loaded
! at boot. Check the Bering-uClibc ulink
! url=http://leaf.sourceforge.net/doc/guide/buci-install.html;Installation
! Guide/ulink to learn how to do that./para
  
! section
!   titleStep 2: declare the ppp and pppoe modules/title
  
!   paraIn order to have a PPPoE connection working, you need to have ppp
!   and pppoe support enabled through the appropriate kernel modules. You
!   also need to declare the driver(s) module(s) of your network card(s). In
!   the following example, we assume that both ethernet interfaces are
!   provided through a standard ne 2000 PCI card./para
  
!   paraAll the modules which are necessary for a PPPoE connection are
!   provided on the standard Bering-uClibc floppy. You just need to
!   #34;declare#34; them since they are not loaded by default. As far as
!   your network cards are concerned, the most popular driver modules are
!   provided in filename/lib/modules/filename but you might need to
!   download the one corresponding to your own hardware from the
!   Bering-uClibc modules ulink
!   
url=http://cvs.sourceforge.net/viewcvs.py/leaf/bin/bering-uclibc/packages/;download
!   area/ulink. Refer to the Bering-uClibc ulink
!   url=http://leaf.sourceforge.net/doc/guide/buci-lrpkg.html;Installation
!   Guide/ulink to learn how to do that./para
  
!   paraTo declare your modules, go to the LEAF Packages configuration
!   menu and choose modules. Enter 1) to edit the filename/etc/modules/filename
!   file and enter the following information:/para
  
!   screen
  # 8390 based ethernet cards
  8390
***
*** 145,185 
  /screen
  
! important
!   paraThe 

[Leaf-cvs-commits] doc/guide/user-bering-uclibc bucu-pppoe.xml,1.9,1.10

2004-06-06 Thread KP Kirchd�rfer
Update of /cvsroot/leaf/doc/guide/user-bering-uclibc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv16466

Modified Files:
bucu-pppoe.xml 
Log Message:
spelling corrections


Index: bucu-pppoe.xml
===
RCS file: /cvsroot/leaf/doc/guide/user-bering-uclibc/bucu-pppoe.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -C2 -d -r1.9 -r1.10
*** bucu-pppoe.xml  6 Jun 2004 22:37:23 -   1.9
--- bucu-pppoe.xml  6 Jun 2004 22:53:03 -   1.10
***
*** 88,92 
  
section
! titleStep 1: declare the ppp and pppoe packages/title
  
  paraThose two packages are provided on the standard Bering-uClibc floppy
--- 88,92 
  
section
! titleStep 1: Declare the ppp and pppoe packages/title
  
  paraThose two packages are provided on the standard Bering-uClibc floppy
***
*** 103,107 
  
  section
!   titleStep 2: declare the ppp and pppoe modules/title
  
paraIn order to have a PPPoE connection working, you need to have ppp
--- 103,107 
  
  section
!   titleStep 2: Declare the ppp and pppoe modules/title
  
paraIn order to have a PPPoE connection working, you need to have ppp
***
*** 158,162 
  
  section
!   titleStep 3: configure ppp/title
  
paraIn the normal situation, you won#39;t have to do anything here,
--- 158,162 
  
  section
!   titleStep 3: Configure ppp/title
  
paraIn the normal situation, you won#39;t have to do anything here,
***
*** 251,255 
  
  section
!   titleStep 5: configure your interfaces file/title
  
paraTrough the LEAF configuration menu type 1 to access to the network
--- 251,255 
  
  section
!   titleStep 5: Configure your interfaces file/title
  
paraTrough the LEAF configuration menu type 1 to access to the network
***
*** 300,304 
  
  section
!   titleStep 6: configure Shorewall/title
  
paraThrough the LEAF packages configuration menu, choose shorwall and
--- 300,304 
  
  section
!   titleStep 6: Configure Shorewall/title
  
paraThrough the LEAF packages configuration menu, choose shorwall and
***
*** 351,355 
  
  section
!   titleStep 7: reboot.../title
  
paraYour modem connection should be established automatically. Type
--- 351,355 
  
  section
!   titleStep 7: Reboot.../title
  
paraYour modem connection should be established automatically. Type



---
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
___
Leaf-cvs-commits mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-cvs-commits


[Leaf-cvs-commits] doc/guide/user-bering-uclibc bucu-freenet6.xml,1.2,1.3

2004-06-06 Thread KP Kirchd�rfer
Update of /cvsroot/leaf/doc/guide/user-bering-uclibc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv19225

Modified Files:
bucu-freenet6.xml 
Log Message:
changes for 2.2


Index: bucu-freenet6.xml
===
RCS file: /cvsroot/leaf/doc/guide/user-bering-uclibc/bucu-freenet6.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** bucu-freenet6.xml   31 Mar 2004 21:52:37 -  1.2
--- bucu-freenet6.xml   6 Jun 2004 23:04:55 -   1.3
***
*** 55,75 
  
section id=freenet6-2
! titleInstalling the freenet6.lrp package/title
  
  paraDownload the ulink
  
url=http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/leaf/bin/packages/uclibc-0.9/20/freenet6.lrp?rev=HEAD#38;content-type=application/octet-stream;freenet6.lrp/ulink
! package. Copy the package to your LEAF diskette. Edit your
! filenamelrpkg.cfg/filename file to add applicationfreenet6/application
! to the list of your packages./para
! 
! paraYour filenamelrpkg.cfg/filename file could look like:/para
! 
! 
screenroot,etc,local,modules,pump,ezipupd,keyboard,shorwall,dnscache,weblet,freenet6/screen
  
! paraReboot./para
/section
  
section
! titleObtain an (authenticated) tunnel or a whole subnet /title
  
  paraIf you just need an ipv6 address for LEAF router, you don#39;t have
--- 55,76 
  
section id=freenet6-2
! titleDeclare the freenet6.lrp package/title
  
  paraDownload the ulink
  
url=http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/leaf/bin/packages/uclibc-0.9/20/freenet6.lrp?rev=HEAD#38;content-type=application/octet-stream;freenet6.lrp/ulink
! package and copy the package to your Bering-uClibc diskette. /para
  
! paraBoot a Bering-uClibc floppy image. Once the LEAF menu appears get
! access to the linux shell by (q)uitting the menu. Edit the
! filenamelrpkg.cfg/filename (pre Bering-uClibc-2.2.0) or
! filenameleaf.cfg/filename (Bering-uClibc-2.2.0 onwards) file and add
! filenamefreenet6.lrp/filename in the list of packages to be loaded at
! boot. Check the Bering-uClibc ulink
! url=http://leaf.sourceforge.net/doc/guide/buci-install.html;Installation
! Guide/ulink to learn how to do that./para
/section
  
section
! titleObtain an (authenticated) tunnel or a whole subnet/title
  
  paraIf you just need an ipv6 address for LEAF router, you don#39;t have



---
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
___
Leaf-cvs-commits mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-cvs-commits