Update of /cvsroot/leaf/doc/guide/install-bering-uclibc-v3
In directory sc8-pr-cvs6.sourceforge.net:/tmp/cvs-serv1845
Modified Files:
buci-apkg3.xml buci-dnsmasq3.xml buci-downmod3.xml
buci-ide3.xml buci-keybd3.xml buci-network3.xml buci-ppp3.xml
buci-pppoa3.xml buci-pppoatm3.xml buci-pppoe3.xml
buci-usbhdd3.xml
Log Message:
more document changes for Bering-uClibc 3.x
Index: buci-pppoatm3.xml
===================================================================
RCS file: /cvsroot/leaf/doc/guide/install-bering-uclibc-v3/buci-pppoatm3.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** buci-pppoatm3.xml 16 Nov 2006 18:08:49 -0000 1.1
--- buci-pppoatm3.xml 26 Nov 2006 20:18:34 -0000 1.2
***************
*** 97,112 ****
<para>In order to be able to get connected through PPPoA you will the
! pppoatm.lrp and libatm.lrp packages together with ppp.lrp.</para>
<para>Boot your Bering-uClibc floppy image. Once the LEAF menu appears get
access to the linux shell by (q)uitting the menu. Edit the
! <filename>lrpkg.cfg</filename> (pre Bering-uClibc-2.2.0) or
! <filename>leaf.cfg</filename> (Bering-uClibc-2.2.0 onwards) file and
! REPLACE the dhcpcd entry by pppoatm and libatm in the list of packages to
! be loaded at boot. Check the Bering-uClibc <ulink
url="http://leaf.sourceforge.net/doc/guide/buci-lrpkg3.html";>Installation
Guide</ulink> to learn how to do that.</para>
! <para>The pppoatm.lrp and libatm.lrp packages are available <ulink
url="http://leaf.cvs.sourceforge.net/leaf/bin/packages/uclibc-0.9/28/";>here</ulink>.</para>
</section>
--- 97,111 ----
<para>In order to be able to get connected through PPPoA you will the
! pppoatm.lrp package together with ppp.lrp.</para>
<para>Boot your Bering-uClibc floppy image. Once the LEAF menu appears get
access to the linux shell by (q)uitting the menu. Edit the
! <filename>leaf.cfg</filename> file and REPLACE the dhcpcd entry by pppoatm
! in the list of packages to be loaded at boot. Check the Bering-uClibc
! <ulink
url="http://leaf.sourceforge.net/doc/guide/buci-lrpkg3.html";>Installation
Guide</ulink> to learn how to do that.</para>
! <para>The pppoatm.lrp packages is available <ulink
url="http://leaf.cvs.sourceforge.net/leaf/bin/packages/uclibc-0.9/28/";>here</ulink>.</para>
</section>
***************
*** 319,324 ****
<para>To save the changes, start lrcfg. The added modules will be saved to
moddb with the command "<command>m</command>) Backup modules". The
! configuration changes are saved with "<command>s</command>) Save config".
! </para>
</section>
--- 318,323 ----
<para>To save the changes, start lrcfg. The added modules will be saved to
moddb with the command "<command>m</command>) Backup modules". The
! configuration changes are saved with "<command>s</command>) Save
! config".</para>
</section>
Index: buci-network3.xml
===================================================================
RCS file: /cvsroot/leaf/doc/guide/install-bering-uclibc-v3/buci-network3.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** buci-network3.xml 16 Nov 2006 18:08:49 -0000 1.1
--- buci-network3.xml 26 Nov 2006 20:18:34 -0000 1.2
***************
*** 8,12 ****
<important>
<para>If you want to permanently change any of the following parameters,
! do not forget to backup etc.lrp !</para>
</important>
--- 8,12 ----
<important>
<para>If you want to permanently change any of the following parameters,
! do not forget to save your configuration!</para>
</important>
***************
*** 19,30 ****
1) interfaces file (/etc/network/interfaces)
! 2) network options file (/etc/network/options)
! 3) hosts IP addresses (/etc/hosts)
! 4) hostname (/etc/hostname)
! 5) resolv.conf (/etc/resolv.conf)
! 6) super server daemon configuration (/etc/inetd.conf)
! 7) hosts.allow (/etc/hosts.allow)
! 8) hosts.deny (/etc/hosts.deny)
! 9) networks (/etc/networks)
q) quit
--- 19,29 ----
1) interfaces file (/etc/network/interfaces)
! 2) hosts IP addresses (/etc/hosts)
! 3) hostname (/etc/hostname)
! 4) resolv.conf (/etc/resolv.conf)
! 5) super server daemon configuration (/etc/inetd.conf)
! 6) hosts.allow (/etc/hosts.allow)
! 7) hosts.deny (/etc/hosts.deny)
! 8) networks (/etc/networks)
q) quit
***************
*** 66,90 ****
<section>
- <title>network options file
- (<filename>/etc/network/options</filename>)</title>
-
- <para>Default variables in this file are the following:</para>
-
- <para><programlisting>ip_forward=no
- ipv6_forward=no
- spoofprotect=yes
- syncookies=no</programlisting></para>
-
- <para>These are default variables generally acceptable. The ip_forward
- variable is set back to yes by Shorewall - so if you do not use Shorewall
- and want to enable ip forwarding you will have to set this variable to
- yes.</para>
-
- <para>The ipv6_forward variable is set back to yes by 6wall - so if you do
- not use 6wall and want to enable ipv6 forwarding you will have to set this
- variable to yes.</para>
- </section>
-
- <section>
<title>hosts IP addresses (<filename>/etc/hosts</filename>)</title>
--- 65,68 ----
***************
*** 230,232 ****
--- 208,240 ----
<screen>localnet 127.0.0.0</screen>
</section>
+
+ <section>
+ <title>system variables (/etc/sysctl.conf), in System Configuration
+ menu</title>
+
+ <para>Default variables in this file are the following:</para>
+
+ <para><programlisting># ip_forward
+ #net.ipv4.ip_forward=1
+ #
+ # ipv6_forward
+ #net.ipv6.conf.all.forwarding=1
+ #
+ # spoofprotect
+ net.ipv4.conf.default.rp_filter=1
+ net.ipv4.conf.all.rp_filter=1
+ #
+ # syncookies
+ #net.ipv4.tcp_syncookies=1
+ </programlisting></para>
+
+ <para>These are default variables generally acceptable. The ip_forward
+ variable is set back to true by Shorewall - so if you do not use Shorewall
+ and want to enable ip forwarding you will have to uncomment this
+ variable.</para>
+
+ <para>The ipv6_forward variable is set back to true by 6wall - so if you
+ do not use 6wall and want to enable ipv6 forwarding you will have to
+ uncomment this variable.</para>
+ </section>
</chapter>
\ No newline at end of file
Index: buci-apkg3.xml
===================================================================
RCS file: /cvsroot/leaf/doc/guide/install-bering-uclibc-v3/buci-apkg3.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** buci-apkg3.xml 16 Nov 2006 18:48:19 -0000 1.1
--- buci-apkg3.xml 26 Nov 2006 20:18:34 -0000 1.2
***************
*** 131,135 ****
<para><command>s</command> - will save all changed configuration files
! and directories to <filename>configdb.lrp</filename>.</para>
<para><command>m</command> -backs up the modules directory
--- 131,140 ----
<para><command>s</command> - will save all changed configuration files
! and directories to <filename>configdb.lrp</filename>.<note>
! <para>Config changes from packages removed from leaf.cfg will be
! removed from the configdb after a reboot and a save. If you want to
! preserve config changes of those uninstalled packages for later
! reference, you should make a backup of the configdb.</para>
! </note></para>
<para><command>m</command> -backs up the modules directory
Index: buci-keybd3.xml
===================================================================
RCS file: /cvsroot/leaf/doc/guide/install-bering-uclibc-v3/buci-keybd3.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** buci-keybd3.xml 16 Nov 2006 18:08:49 -0000 1.1
--- buci-keybd3.xml 26 Nov 2006 20:18:34 -0000 1.2
***************
*** 19,23 ****
q) quit</screen>
! <para>Type 1 to get access to the <filename>/etc/init.d/keyboard</filename>
script where you will have to replace the KEYMAP variable (default="us.map")
by the appropriate keyboard setting.</para>
--- 19,23 ----
q) quit</screen>
! <para>Type 1 to get access to the <filename>/etc/default/keyboard</filename>
script where you will have to replace the KEYMAP variable (default="us.map")
by the appropriate keyboard setting.</para>
***************
*** 42,55 ****
/etc/init.d/keyboard start</screen>
- <para>You can then remove the keymaps you do not need once you are happy
- with your choice. It will strip the keyboard.lrp package to 1k. From the
- LEAF console simply run:</para>
-
- <screen>
- /etc/init.d/keyboard remove</screen>
-
<important>
! <para>To save your modification(s) do not forget to backup
! <filename>keyboard.lrp</filename>!</para>
</important>
</chapter>
\ No newline at end of file
--- 42,48 ----
/etc/init.d/keyboard start</screen>
<important>
! <para>To save your modification(s) do not forget to save the
! configuration!</para>
</important>
</chapter>
\ No newline at end of file
Index: buci-ppp3.xml
===================================================================
RCS file: /cvsroot/leaf/doc/guide/install-bering-uclibc-v3/buci-ppp3.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** buci-ppp3.xml 16 Nov 2006 18:08:49 -0000 1.1
--- buci-ppp3.xml 26 Nov 2006 20:18:34 -0000 1.2
***************
*** 94,99 ****
filter version, the package needs to be renamed to ppp.lrp.</para>
! <para>The ppp source is version 2.4.2 and supports ipv6, mschapv2, mppe
! and optional pppoe or pppoatm with plugins</para>
</section>
--- 94,99 ----
filter version, the package needs to be renamed to ppp.lrp.</para>
! <para>The ppp source is version 2.4.4 and supports ipv6, mschapv2, mppe
! and optional pppoe, pppoatm or pppol2p with plugins</para>
</section>
***************
*** 103,110 ****
<para>Boot a Bering-uClibc floppy image. Once the LEAF menu appears get
access to the linux shell by (q)uitting the menu. Edit the
! <filename>lrpkg.cfg</filename> (pre Bering-uClibc-2.2.0) or
! <filename>leaf.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>
--- 103,108 ----
<para>Boot a Bering-uClibc floppy image. Once the LEAF menu appears get
access to the linux shell by (q)uitting the menu. Edit the
! <filename>leaf.cfg</filename> 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>
***************
*** 385,393 ****
<para>ppp-filter.lrp needs to be renamed to ppp.lrp before use and uses
libpcap.lrp (which also needs to be loaded in
! <filename>lrpkg.cfg/leaf.cfg</filename>). The filter version can be used
! to specify a packet filter to be applied to data packets to determine
! which packets are to be regarded as link activity, and therefore reset the
! idle timer, or cause the link to be brought down in demand-dialing mode.
! The configuration (except for the filter-part) is done like the ppp
package.</para>
--- 383,391 ----
<para>ppp-filter.lrp needs to be renamed to ppp.lrp before use and uses
libpcap.lrp (which also needs to be loaded in
! <filename>leaf.cfg</filename>). The filter version can be used to specify
! a packet filter to be applied to data packets to determine which packets
! are to be regarded as link activity, and therefore reset the idle timer,
! or cause the link to be brought down in demand-dialing mode. The
! configuration (except for the filter-part) is done like the ppp
package.</para>
Index: buci-usbhdd3.xml
===================================================================
RCS file: /cvsroot/leaf/doc/guide/install-bering-uclibc-v3/buci-usbhdd3.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** buci-usbhdd3.xml 16 Nov 2006 18:08:50 -0000 1.1
--- buci-usbhdd3.xml 26 Nov 2006 20:18:34 -0000 1.2
***************
*** 101,112 ****
<para>Download the image using your favourite tool. Here we have used
<command>wget</command> to download from a mirror in Kent/England.
! Please select your closest mirror to save bandwith:</para>
<para><programlisting>
! #wget
http://osdn.dl.sourceforge.net/sourceforge/leaf/Bering-uClibc_2.4.2_usb_bering-uclibc.bin.img.gz
</programlisting></para>
<para>Then unzip the image:<programlisting>
! #gunzip Bering-uClibc_2.4.2_usb_bering-uclibc.bin.img.gz
</programlisting></para>
--- 101,113 ----
<para>Download the image using your favourite tool. Here we have used
<command>wget</command> to download from a mirror in Kent/England.
! Please select your closest mirror to save bandwith (replace
! <version> with the version number):</para>
<para><programlisting>
! #wget
http://osdn.dl.sourceforge.net/sourceforge/leaf/Bering-uClibc_<version>_usb_bering-uclibc.bin.img.gz
</programlisting></para>
<para>Then unzip the image:<programlisting>
! #gunzip Bering-uClibc_<version>_usb_bering-uclibc.bin.img.gz
</programlisting></para>
***************
*** 114,118 ****
<para><programlisting>
! #dd if=Bering-uClibc_2.4.2_usb_bering-uclibc.bin.img of=/dev/sdg
</programlisting></para>
--- 115,119 ----
<para><programlisting>
! #dd if=Bering-uClibc_<version>_usb_bering-uclibc.bin.img
of=/dev/sdg
</programlisting></para>
Index: buci-pppoa3.xml
===================================================================
RCS file: /cvsroot/leaf/doc/guide/install-bering-uclibc-v3/buci-pppoa3.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** buci-pppoa3.xml 16 Nov 2006 18:08:49 -0000 1.1
--- buci-pppoa3.xml 26 Nov 2006 20:18:34 -0000 1.2
***************
*** 119,125 ****
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 modules <ulink
url="http://leaf.cvs.sourceforge.net/leaf/bin/bering-uclibc/packages/";>CVS
! area</ulink>. Refer to the Bering <ulink
url="http://leaf.sourceforge.net/doc/guide/buci-install.html";>installation
guide</ulink> to learn how to do that.</para>
--- 119,125 ----
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://leaf.cvs.sourceforge.net/leaf/bin/bering-uclibc/packages/";>CVS
! 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>
Index: buci-dnsmasq3.xml
===================================================================
RCS file: /cvsroot/leaf/doc/guide/install-bering-uclibc-v3/buci-dnsmasq3.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** buci-dnsmasq3.xml 16 Nov 2006 18:08:49 -0000 1.1
--- buci-dnsmasq3.xml 26 Nov 2006 20:18:34 -0000 1.2
***************
*** 63,68 ****
carefully, to get most out this application.</para>
! <para>Beginning with Bering-uClibc 2.2 dnsmasq will replace dnscache on
! the base image. Additionally it adds features previously only available if
both dhcpd and tinydns were loaded.</para>
--- 63,68 ----
carefully, to get most out this application.</para>
! <para>Beginning with Bering-uClibc 2.2 dnsmasq replaced dnscache on the
! base image. Additionally it adds features previously only available if
both dhcpd and tinydns were loaded.</para>
***************
*** 72,90 ****
<section>
- <title>Load dnsmasq package</title>
-
- <para>If you are using Bering-uClibc 2.2 or higher, this step can be
- skipped.</para>
-
- <para>For older Bering-uClibc versions edit <filename>lrpkg.cfg</filename>
- and add <filename>dnsmasq</filename> to packages list:</para>
-
-
<screen>root,config,etc,local,modules,iptables,keyboard,shorwall,ulogd,dnsmasq
..."</screen>
-
- <para>And you can remove dnscache from <filename>lrpkg.cfg</filename>,
- because it's replaced by dnsmasq.</para>
- </section>
-
- <section>
<title>Configure dnsmasq dns forwarder</title>
--- 72,75 ----
Index: buci-downmod3.xml
===================================================================
RCS file: /cvsroot/leaf/doc/guide/install-bering-uclibc-v3/buci-downmod3.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** buci-downmod3.xml 16 Nov 2006 18:08:49 -0000 1.1
--- buci-downmod3.xml 26 Nov 2006 20:18:34 -0000 1.2
***************
*** 18,25 ****
url="http://leaf.sourceforge.net/doc/guide/bucu-ide.html";>"Using
Bering-uClibc with an IDE harddisk or CD-ROM drive"</ulink> section of
! the Bering-uClibc user's guide). These modules will be saved in the
! <filename>initrd.lrp</filename> package. Special versions of initrd.lrp
! provides support to boot from CD-ROM, USB or an IDE harddisk. If you
! build your own initrd.lrp, you will also need to edit
<filename>/boot/etc/modules</filename> in order to declare the sequence
of modules you want to load at this stage.</para>
--- 18,24 ----
url="http://leaf.sourceforge.net/doc/guide/bucu-ide.html";>"Using
Bering-uClibc with an IDE harddisk or CD-ROM drive"</ulink> section of
! the Bering-uClibc user's guide). Special versions of initrd.lrp provides
! support to boot from CD-ROM, USB or an IDE harddisk. If you build your
! own initrd.lrp, you will also need to edit
<filename>/boot/etc/modules</filename> in order to declare the sequence
of modules you want to load at this stage.</para>
Index: buci-pppoe3.xml
===================================================================
RCS file: /cvsroot/leaf/doc/guide/install-bering-uclibc-v3/buci-pppoe3.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** buci-pppoe3.xml 17 Nov 2006 14:40:26 -0000 1.2
--- buci-pppoe3.xml 26 Nov 2006 20:18:34 -0000 1.3
***************
*** 97,104 ****
<para>Boot a Bering-uClibc floppy image. Once the LEAF menu appears get
access to the linux shell by (q)uitting the menu. Edit the
! <filename>lrpkg.cfg</filename> (pre Bering-uClibc-2.2.0) or
! <filename>leaf.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>
--- 97,103 ----
<para>Boot a Bering-uClibc floppy image. Once the LEAF menu appears get
access to the linux shell by (q)uitting the menu. Edit the
! <filename>leaf.cfg</filename> 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>
Index: buci-ide3.xml
===================================================================
RCS file: /cvsroot/leaf/doc/guide/install-bering-uclibc-v3/buci-ide3.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** buci-ide3.xml 17 Nov 2006 14:40:23 -0000 1.2
--- buci-ide3.xml 26 Nov 2006 20:18:34 -0000 1.3
***************
*** 137,142 ****
the Bering-uClibc team provides an already enhanced
<filename>initrd.lrp</filename> with all modules needed to boot from an
! IDE harddisk or IDE CD-ROM drive for Bering-uClibc version 2.0 and
! above.</para>
<para>You can download the file <ulink
--- 137,141 ----
the Bering-uClibc team provides an already enhanced
<filename>initrd.lrp</filename> with all modules needed to boot from an
! IDE harddisk or IDE CD-ROM drive for Bering-uClibc.</para>
<para>You can download the file <ulink
***************
*** 189,206 ****
<section>
! <title>syslinux.cfg for Bering-uClibc 2.1 and earlier versions</title>
!
! <para>Edit <filename>syslinux.cfg</filename> and make shure the
! PKGPATH points to the CD-ROM device and floppy as well (that's the
! place where you store your configuration
settings).<programlisting>display syslinux.dpy
! timeout 0
! default linux initrd=initrd.lrp init=/linuxrc rw root=/dev/ram0
boot=/dev/fd0:msdos PKG
! PATH=/dev/cdrom:iso9660,/dev/fd0:msdos
LRP=root,etc,loca.....</programlisting></para>
!
! <para>Now you have a bootable floppy for your CD.</para>
! </section>
!
! <section>
! <title>syslinuxcfg for Bering-uClibc 2.2 and later versions</title>
<para>Edit <filename>syslinux.cfg</filename> and change the LEAFCFG
--- 188,192 ----
<section>
! <title>syslinuxcfg</title>
<para>Edit <filename>syslinux.cfg</filename> and change the LEAFCFG
***************
*** 238,244 ****
<para>Packages can be added or removed in a flexibel way by
! declaring/undeclaring them in <filename>lrpkg.cfg</filename>
! (Bering-uClibc <= 2.1) or <filename>leaf.cfg</filename>
! (Bering-uClibc >= 2.2) on a new formatted floppy.</para>
<para>Additionally your configuration settings for all packages can be
--- 224,229 ----
<para>Packages can be added or removed in a flexibel way by
! declaring/undeclaring them in <filename>leaf.cfg</filename> on a new
! formatted floppy.</para>
<para>Additionally your configuration settings for all packages can be
***************
*** 246,262 ****
<section>
! <title>Declaring packages for Bering-uClibc 2.1 and earlier
! versions</title>
!
! <para>To add or remove packages just edit
! <filename>lrpkg.cfg</filename> on a blank formatted floppy disk - all
! entries on one line. It looks like:</para>
!
!
<screen>root,etc,local,modules,pump,keyboard,shorwall,dnscache,webconf</screen>
! </section>
!
! <section>
! <title>Declaring packages for Bering-uClibc 2.2 and later
! versions</title>
<para>Edit <filename>leaf.cfg</filename> on a blank formatted floppy
--- 231,235 ----
<section>
! <title>Declaring packages</title>
<para>Edit <filename>leaf.cfg</filename> on a blank formatted floppy
***************
*** 279,287 ****
<section>
! <title>Backing up your configuration</title>
! <para>You can backup your configuration changes onto the floppy, you
! have declared
! <filename>leaf.cfg</filename>/<filename>lrpkg.cfg</filename>.</para>
</section>
</section>
--- 252,259 ----
<section>
! <title>Save your configuration</title>
! <para>You can save your configuration changes onto the floppy, you
! have declared <filename>leaf.cfg</filename></para>
</section>
</section>
***************
*** 343,394 ****
<para><screen>mount /dev/fd0u1680 /mnt</screen></para>
- <para>Once this is done, the steps for Bering-uClibc 2.1 and previous
- versions and Bering-uClibc 2.2 and later versions are different.</para>
-
<section>
! <title>Bering-uClibc 2.1 and earlier versions</title>
!
! <para>For Bering-uClibc 2.1 and earlier versions edit the
! <filename>syslinux.cfg</filename> file in /mnt and change the "boot" and
! "PKGPATH" entries to point to your harddisk. It will look like:</para>
!
! <screen>
! display syslinux.dpy
! timeout 0
! default linux initrd=initrd.lrp init=/linuxrc rw root=/dev/ram0
boot=/dev/hda1:msdos PKGPATH=/dev/hda1
! LRP=root,etc,loc</screen>
!
! <para>Once you have finished with your floppy preparation, copy all the
! files from it except <filename>ldlinux.sys</filename> (which is created
! by syslinux) to the IDE device that you prepared earlier. You should now
! be able to boot from the IDE device. Once again be careful not to copy
! <filename>ldlinux.sys</filename> from the floppy otherwise your disk
! won't be bootable and you will have to go over the installation of
! syslinux on your hard disk again.</para>
!
! <para>An alternative methode is to prepare and load the packages onto
! your disk with pxeinstall.tgz described in the next chapter. Besides
! it's pretty fast, once you've setup the environment, it is especially
! useful if your router has no floppy drive.</para>
! </section>
!
! <section>
! <title>Bering-uClibc 2.2 and later versions</title>
!
! <para>For Bering-uClibc 2.2 and later versions edit
! <filename>syslinux.cfg</filename> and change the LEAFCFG variable to
! point to your harddisk:</para>
! <para><screen>display syslinux.dpy
timeout 0
! default linux initrd=initrd.lrp init=/linuxrc rw root=/dev/ram0
LEAFCFG=/dev/hda1:msdos</screen></para>
<para>Edit <filename>leaf.cfg</filename> and add your packages to LRP
and change PKGPATH to point to your harddisk.</para>
! <para><screen>LRP="root config etc local modules iptables dnsmasq
keyboard shorwall ulogd libz mawk libssl libm ezipupd dropbear webconf ppp
pppoe libpcap"
PKGPATH=/dev/hda1:msdos
syst_size=8M
! log_size=2M</screen></para>
<para>If you have declared two partitions on your harddisk, and intend
--- 315,337 ----
<para><screen>mount /dev/fd0u1680 /mnt</screen></para>
<section>
! <para>Edit <filename>syslinux.cfg</filename> and change the LEAFCFG
! variable to point to your harddisk:</para>
! <para>
! <screen>display syslinux.dpy
timeout 0
! default linux initrd=initrd.lrp init=/linuxrc rw root=/dev/ram0
LEAFCFG=/dev/hda1:msdos</screen>
! </para>
<para>Edit <filename>leaf.cfg</filename> and add your packages to LRP
and change PKGPATH to point to your harddisk.</para>
! <para>
! <screen>LRP="root config etc local modules iptables dnsmasq keyboard
shorwall ulogd libz mawk libssl libm ezipupd dropbear webconf ppp pppoe libpcap"
PKGPATH=/dev/hda1:msdos
syst_size=8M
! log_size=2M</screen>
! </para>
<para>If you have declared two partitions on your harddisk, and intend
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
leaf-cvs-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-cvs-commits
