> > It can't be as simple as putting "...LRP=/dev/hda1/lrpkg.cfg" in the
> > syslinux.cfg. Or can it?
>
> No, it's actually simpler :)
>
> If a file with the name "lrpkg.cfg" is found on your boot= device, the
> contents of that file replace the LRP= portion of the kernel command line.
>
Charles
> Thanks! I did look at the DCD image to see how it was done but in the ISO
> image, the syslinux.cfg file has the packages listed out and the lrpkg.cfg
> has that same information so I'm not clear on the syntax to make the
program
> look for the list of packages in the lrpkg.cfg file. That's the
What happens if your syslinux.cfg ends like this?:
boot=/dev/fd0,msdos PKGPATH=/dev/hda,msdos
And your lrpkg.cfg looks like this
etc,ramlog,local,modules,libz,sshd,weblet,modules,dnscache,xntp,psentry,
no need for the words LRP= in the file lrpkg.cfg - just a single line of comma
separated lis
nt: Sunday, March 31, 2002 6:37 PM
> To: Leaf-User@Lists. Sourceforge. Net
> Subject: Re: [Leaf-user] Breaking the 255 byte barrier
>
>
> How about using the file lrpkg.cfg according to the DCD format.
> Not a lot of
> difference between a CD and a flash other than R/W.
>
> lr
How about using the file lrpkg.cfg according to the DCD format. Not a lot of
difference between a CD and a flash other than R/W.
lrpkg.cfg has no limit. It is is just a text line containing everything from
syslinux.cfg after the LRP=
it could look like this
etc,local,modules,ramlog,dhcpd,lbiz,
Greetings!
I'm working on a project using the Dachstein v1.0.2 on a flash module.
Everything is working well except that I am up against the 255 character
limit for syslinux.cfg. As an immediate workaround, I just renamed several
of the packages with 1 character names (1.lrp, etc.) but that caus
