Skip to contentSkip to conversation

remove CONFIG_UID16

DISCUSSION Bodo Eggert 3 participants 4 messages Dec 17, 2005 – Dec 21, 2005 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 4 lines · Adrian Bunk

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.

Signature · 2 lines
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.
#2 lore raw
Quoted 8 lines · Bodo Eggert
Quoted 4 lines · Adrian Bunk

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?

Lee

#3 lore raw
Quoted 10 lines
Quoted 7 lines
Quoted 5 lines

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:

Quoted 8 lines

(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

Signature · 2 lines
| Alphagate Systems, http://alphagate.hopto.org/
| jengelh's site, http://jengelh.hopto.org/
#4 lore raw
Quoted 16 lines · Jan Engelhardt
Quoted 16 lines
Quoted 6 lines
Quoted 4 lines

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. *

Quoted 5 lines
Quoted 1 line

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?

I don't think this is a productive line of reasoning, even if we could not identify one such app. We should not break user visible APIs without a compelling reason.

Lee