Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964845AbVLUWeR (ORCPT ); Wed, 21 Dec 2005 17:34:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964841AbVLUWeR (ORCPT ); Wed, 21 Dec 2005 17:34:17 -0500 Received: from linux01.gwdg.de ([134.76.13.21]:36518 "EHLO linux01.gwdg.de") by vger.kernel.org with ESMTP id S1751186AbVLUWeP (ORCPT ); Wed, 21 Dec 2005 17:34:15 -0500 Date: Wed, 21 Dec 2005 23:33:40 +0100 (MET) From: Jan Engelhardt To: Lee Revell cc: 7eggert@gmx.de, Adrian Bunk , linux-kernel@vger.kernel.org Subject: Re: remove CONFIG_UID16 In-Reply-To: <1134844168.11227.3.camel@mindpipe> Message-ID: References: <5kCbe-45z-7@gated-at.bofh.it> <1134844168.11227.3.camel@mindpipe> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 976 Lines: 34 >> > It seems noone noticed that CONFIG_UID16 was accidentially always >> > disabled in the latest -mm kernels. >> > >> > Is there any reason against removing it completely? >> >> Maybe embedded systems. > >The comments in the code say it's for backwards compatibility: > >(from include/linux/highuid.h) > > * > * CONFIG_UID16 is defined if the given architecture needs to > * support backwards compatibility for old system calls. > * > >This implies that removing it would break some applications, right? So what are the most recent apps that still use them, and for what kernel were they originally designed? Jan Engelhardt -- | Alphagate Systems, http://alphagate.hopto.org/ | jengelh's site, http://jengelh.hopto.org/ - 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/