Do you have a period (.) at the end of your lrp line?
Perhaps as a temporary workaround until we figure this out, insert a bogus
package at the end (ie. bogus.lrp!)
- Bob Coffman
---
This SF.Net email sponsored by: Free pre-built ASP.NET
Make sure you type ENTER at the end, so that lrpkg.cfg has 2 lines.
-Original Message-
From: Robert Coffman - Info From Data Corporation
[mailto:[EMAIL PROTECTED]
Sent: quarta-feira, 13 de Agosto de 2003 18:21
To: [EMAIL PROTECTED]
Subject: RE: [leaf-user] Last package won't load
Jeremy
At 01:36 13.08.2003 -0500, Jeremy A Tourville wrote:
Ok, I've followed the directions regarding creating a lrpkg.cfg file and
when the CD boots I get a *.lrp (nf!) error. I've tried to add a
carriage return at the end of the lrpkg.cfg file and still no luck. I've
tried switching the
Hi
At 19:04 13.08.2003, [EMAIL PROTECTED] wrote:
Erich,
Thank you for your reply. I have confirmed all packages that are listed
in my lrpkg.cfg are on the CD. Let me state again the LAST package listed
won't load properly. (makes no difference which one) That is the part
that confuses me.
Jeremy A Tourville wrote:
Ok, I've followed the directions regarding creating a lrpkg.cfg file and
when the CD boots I get a *.lrp (nf!) error. I've tried to add a
I just changed my (working) lrpkg.cfg file. I added *one*
whitespace after the last packagename. -
And it failed. Removing the
-
From: Jeremy A Tourville [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 12, 2003 11:36 PM
Subject: [leaf-user] Last package won't load (Bering v 1.2 on CD)
My isolinux.cfg is as follows:
display syslinux.dpy
timeout 0
default linux initrd=initrd.lrp init=/linuxrc rw root
Ok, I've followed the directions regarding creating a lrpkg.cfg file and
when the CD boots I get a *.lrp (nf!) error. I've tried to add a
carriage return at the end of the lrpkg.cfg file and still no luck. I've
tried switching the order the packages load in and it makes no
difference, the last
package won't load (Bering v 1.2 on CD)
Do you have a period (.) at the end of your lrp line?
Perhaps as a temporary workaround until we figure this out,
insert a bogus
package at the end (ie. bogus.lrp!)
- Bob Coffman
And make sure your lrpkg.cfg is using linux (not MS-DOS)
end-of-lines...the CR
