| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20060904170929.GA27986@dreamland.darkstar.lan>
Date: Mon, 4 Sep 2006 19:09:29 +0200
From: Luca <kronos.it@...il.com>
To: Paul Mackerras <paulus@...ba.org>
Cc: linux-kernel@...r.kernel.org, Alon Bar-Lev <alon.barlev@...il.com>
Subject: Re: [PATCH 00/26] Dynamic kernel command-line
(trimming CC list)
Paul Mackerras <paulus@...ba.org> ha scritto:
Alon Bar-Lev writes:
>
>> Current implementation stores a static command-line
>> buffer allocated to COMMAND_LINE_SIZE size. Most
>> architectures stores two copies of this buffer, one
>> for future reference and one for parameter parsing.
>
> Under what circumstances do we actually need a command line of more
> than 256 bytes?
>
> It seems to me that if 256 bytes isn't enough, we should take a deep
> breath, step back, and think about whether there might be a better way
> to pass whatever information it is that's using up so much of the
> command line.
Well, if you want to set a parameter of a builtin module you have to
use:
modulename.parameter=whatever
which can use a lot of space... I suppose that with an "everything
builtin" kernel and a few modules to tune you can get near the limit.
Luca
--
Home: http://kronoz.cjb.net
Il tempo speso
a coltivare sogni
non è sprecato.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists