Re: THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit
From: H. Peter Anvin (hpa_at_zytor.com)
Date: 08/31/05
- Previous message: Valdis.Kletnieks_at_vt.edu: "Re: [ANNOUNCE] DSFS Network Forensic File System for Linux Patches"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 31 Aug 2005 14:29:44 -0700 To: Alon Bar-Lev <alon.barlev@gmail.com>
Alon Bar-Lev wrote:
>
> Hello Peter,
>
> I am sorry that I am contacting you directly... Please refer me to
> correct contact if you are not the one.
>
> Lately, I've found that 256 bytes long kernel parameters are not enough
> for my configuration.
>
> I've found the place where the kernel defines the length, I've actually
> found it in two places... I cannot understand why...
>
> include/asm-i386/param.h: #define COMMAND_LINE_SIZE 256
> include/asm-i386/setup.h: #define COMMAND_LINE_SIZE 256
>
> Now... I've added an entry in the kernel configuration menu so that I
> can define these constants using menuconfig.
>
> I was quite happy...
>
> But then I've got into a discussion with grub's development team...
>
> From what I've read in the Documentation/i386/boot.txt I understood
> that if I use boot protocol 2.02+ there should be no reason for 256 byte
> limitation on the string pointed by the cmd_line_ptr, so I guessed they
> will deliver the command-line twice once for the old protocol truncated,
> and once for the new protocol not truncated.
>
> Grub and Lilo approach is to point the cmd_line_ptr to the old
> protocol's command line, thus truncating it to 256.
>
> I'm just wondering... Can the 256 limit be broken, without modifying the
> boot protocol?
>
> I think it can... But I need a formal answer so I can push it forward.
>
Yes, it can. Several people on the SYSLINUX mailing list have tried
this, and it works just fine. The current version of SYSLINUX has a
limit of 511 characters (because of memory management reasons inside
SYSLINUX) instead of 255 (plus null).
I think someone on the SYSLINUX mailing list already sent a patch to
akpm to make 512 the default; making it configurable would be a better
idea. Feel free to send your patch through me.
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Valdis.Kletnieks_at_vt.edu: "Re: [ANNOUNCE] DSFS Network Forensic File System for Linux Patches"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- PROBLEM: Dell Inspiron 1501 fails to boot in 2.6.21+
... My new laptop won't boot with kernel versions 2.6.21 or 2.6.22. ... I've also
included my kernel configuration and ver_linux output. ... Enabling unmasked SIMD FPU
exception support... ... usbcore: ... (Linux-Kernel) - 2.6.16-rtXYZ hangs at boot on quad Opteron
... Debian etch and used the 2.6.14-rt9 kernel. ... NULL ptr deref on boot
... HyperTransport Technology Configuration ... # ACPI Support ...
(Linux-Kernel) - Re: Oops in megaraid_mbox_dpc(), kernel 2.6.23.9-85.fc8.i686
... Controller name, FW version, RAID configuration, host system info, how ... Also
do you see the issue on other kernel ... # Process debugging support ...
# AX.25 network device drivers ... (Linux-Kernel) - Re: 2.6.16-rtXYZ hangs at boot on quad Opteron
... Debian etch and used the 2.6.14-rt9 kernel. ... NULL ptr deref on boot
... HyperTransport Technology Configuration ... # ACPI Support ...
(Linux-Kernel) - Re:SOLVVED vinum crashes the Box... WRONG POSTING
... vinum crashes the Box by using more then ten disks on ... > With this configuration
vinum crashes the Machine with this Message: ... > I'm going to enable the kernel debugger
now... ... >> while devfs rules works for those, but they vanish on reboot. ...
(freebsd-stable)