public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roberto De Leo <deleo@unica.it>
To: linux-kernel@vger.kernel.org
Subject: limit to the length of args passed to kernel
Date: Sat, 05 Oct 2002 10:23:57 +0000	[thread overview]
Message-ID: <3D9EBDBD.4030402@unica.it> (raw)

Hi,
I recently found out the you can't pass too many args to the kernel 
through the LILO "append"
option. Actually I passed the args through the similar "append" option 
of the SysLinux package
(http://syslinux.zytor.com/) but on their ML I have been told it is 
equivalent to LILO's one and
that there is a 256 characters limit for passing args at boot time to 
the kernel.

My question is: is this really a kernel limit or I misunderstood? if it 
is a kernel limit,
is there any way to bypass it?

It would be very useful for a package I am developing: it is a micro 
linux distro (the initrd.gz
is ~4MB) containing basically only a kernel and what you need to play a 
movie through the FB.
The kernel (2.4.19) has been compiled with support for all possible FB 
drivers, but for several
reasons it would be nice to have two booting options: one containing the 
initialization for all
possible FB and one turning all of them off except the vesa FB.
Unfortunately though there are so many FB driverd that to turn them all 
off it takes much more
than 256 chars!

Any help would be greatly appreciated.
Please CC me any answer to deleo@unica.it, I'm not subscrribed to the ML.
Thanks,
 Roberto De Leo



             reply	other threads:[~2002-10-05  8:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-05 10:23 Roberto De Leo [this message]
2002-10-07  5:07 ` limit to the length of args passed to kernel Randy.Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D9EBDBD.4030402@unica.it \
    --to=deleo@unica.it \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox