linux-kernel - Re: [PATCH][RFC] Create a top-level "Space-critical features" menu.

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070508085654.GG4226@stusta.de>
Date:	Tue, 8 May 2007 10:56:54 +0200
From:	Adrian Bunk <bunk@...sta.de>
To:	"Robert P. J. Day" <rpjday@...dspring.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH][RFC] Create a top-level "Space-critical features" menu.

On Tue, May 08, 2007 at 04:06:30AM -0400, Robert P. J. Day wrote:
> 
>   i've always hated that lower-level menu under "General setup":
> 
> Configure standard kernel features (for small systems)  --->
> 
> which buries the choice of de-selecting features to save space one
> level down without really explaining what it's all about.  so i just
> shifted all of that up to the top under what i think is a more
> meaningful name.
> 
>   this patch is also why i asked earlier why top-level menu entries
> have no "help" text -- because, in this case, it would be useful for
> someone looking at the config screen to see that choice and be able to
> ask, "hey, i wonder what *that's* all about", and get help along the
> lines of:
> 
>   "these features are normally selected but, if you're strapped for
> space, such as with embedded systems, you might consider turning some
> of them off.  if space isn't an issue, you might as well just leave
> them as they are."  (or something like that.)
>...

I'm against it:

I don't have numbers, but I'd expect the vast majority of people 
building kernels to be people with low kernel knowledge building for an 
i386/x86_64 system.

OTOH, people developing embedded systems are most likely more familiar 
with kernel internals.

Kernel size doesn't matter that much for average desktop or server 
systems, and most things for possible space savings behind hidden behind 
EMBEDDED are things where you _really_ have to know what you are doing 
when playing with these options.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
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/