linux-kernel - 2.6.18-rc: EMBEDDED menu is split up

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>] [day] [month] [year] [list]

Message-ID: <200609110014_MC3-1-CAD2-A49D@compuserve.com>
Date:	Mon, 11 Sep 2006 00:12:52 -0400
From:	Chuck Ebbert <76306.1226@...puserve.com>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Cc:	Sam Ravnborg <sam@...nborg.org>, Andrew Morton <akpm@...l.org>
Subject: 2.6.18-rc: EMBEDDED menu is split up

In menuconfig, I enabled CONFIG_EMBEDDED in the "general setup" menu
and all of the submenu items starting with "enable futex support" appeared
in the main menu instead of the submenu:

         [*] Configure standard kernel features (for small systems)  --->                
         [*] Enable futex support (NEW)                                                  
         [*] Enable eventpoll support (NEW)                                              
         [*] Use full shmem filesystem (NEW)                                      
         [*] Use full SLAB allocator (NEW)                                          
         [*] Enable VM event counters for /proc/vmstat (NEW)                      

Two more items also appear, but they're _above_ the submenu prompt:

         [*] Sysctl support (NEW)                                                        

         [*] Enable 16-bit UID system calls (NEW)                                        

Should these be moved into the submenu?

-- 
Chuck

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