I am running a two floppy set and I have three files needed to cover both floppies:
Disk 1
pkgpath.cfg /dev/fd0u1440,/dev/fd1u1440
syslinux.cfg display syslinux.dpy timeout 0 default linux append=load_ramdisk=1 initrd=root.lrp initrd_archive=minix ramdisk_size=16384 root=/dev/ram0 boot=/dev/fd0u1440,msdos PKGPATH= LRP=
lrpkg.cfg etc,ramlog,local,modules,ppp,dhcpd,dnscache,ifconfig,pppoe,weblet,sshd,oiden td,libz,psentry,jbuster
Pkgpath.cfg file contains your drive info and floppy size syslinux.cfg file contains the path to load your programs lrpkg.cfg file contains the programs to load to get around the 255 character limit of syslinux.cfg
I have my programs split out between the two floppies, the lights bounce back and forth during loading.
Message: 4 Date: Fri, 05 Sep 2003 14:42:48 -0700 From: Arnold Wiegert <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: [leaf-user] Dachstein & lrpkg.cfg - BOOT_IMAGE=linux (nf!)
I have specified a second floppy in syslinux.cfg and it is recognized and does not seem to cause any error messages. I can mount this second floppy and edit files on it.
When I try to use the lrpkg.cfg file to extend the command line length, as described in various messages on this list and other documentation, to load more packages from the second floppy.
My boot floppy contains a file with a list of the modules taken from syslinux.cfg, again, as described in the above messages.
But, as soon as I remove all LRP=.... from syslinux.cfg, I get the following message during boot-up:
LINUXRC: Installing - BOOT_IMAGE=linux(nf!) - finished ... and then the system asks for a new Run Level and waits - only power cycle will let me carry on.
BTW, my version is Dachstein 4.0.1
I have used the firewall for some time without any problems - so now a got a bit bolder and was trying to add some more features, but :-( ..... no joy at all.
Any help would be most appreciated.
The features you're trying to use should be in Dachstein (which Bering is based on), as I added them to allow easy support for booting from a CD-ROM and keeping config information on a seperate media (typically a floppy or HDD).
I'm not sure what's going wrong. I'd first suggest trying to use the PKGPATH= setting in syslinux.cfg rather than the pkgpath.cfg file, if at all possible. This could help isolate the problem.
It would also be helpful to see *ALL* of the text spit out by linuxrc (or as much as you can write down), particularly the portions where it's mounting media.
-- Charles Steinkuehler [EMAIL PROTECTED]
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
