According to editpadlite, the kernel line is 253 chars...
I will read the installation guide for a change.

Rick.

-----Original Message-----
From: Charles Steinkuehler [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 30, 2005 7:07 AM
To: Tibbs, Richard
Cc: Leaf-User (E-mail)
Subject: Re: [leaf-user] New Problem with UClibc syslinux

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tibbs, Richard wrote:

| Ah! Looks like leaf.cfg has changed from the Bering 1.2 days.
| My leaf.cfg with uclibc looks like below, but I will try one like
yours.
|
| Strange thing is the leaf.cfg packages load, while everything beyond
| local in syslinux LRP= (see below) does not.
| Thx. Rick
|
| LRP="$KCMD_LRP libc207"
| LRP="$LRP libssl"
| LRP="$LRP liblzo"
| LRP="$LRP openvpnz"

Looks like your syslinux.cfg kernel command line is longer than 256
characters (a kernel limit), so probably the stuff past local is getting
chopped off.  Run "cat /proc/cmdline" to see what got passed to the
kernel.

It's probably just your bad luck that the 256 character limit hit right
at
the end of local, making it harder to debug.  The length limit on the
kernel
commandline string is the reason for the leaf.cfg file.

- --
Charles Steinkuehler
[EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFDjZYALywbqEHdNFwRAh4jAJ4qGgTW9t/JwptF3jsRoWL2LOD5FwCeNAOD
UajrYPEog0Km92S3YODjisQ=
=5qO9
-----END PGP SIGNATURE-----


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/

Reply via email to