32-bit UID support

Eugene Crosser (crosser@average.org)
14 Jan 2000 08:58:55 +0300

Can Chris or someone please tell me what is the reason behind leaving
__kernel_uid_t == short on x86 architecture, and adding
__kernel_uid32_t? To me, it sounds more reasonable to rather make
__kernel_uid_t == int and add __kernel_uid16_t == short for binary
compatibility things.

As a result of current status of things, 32bit uid support does *not*
become visible to the userspace when you rebuild glibc with the new
kernel source. To make it take effect, you also need to modify glibc
source, and in a rather illogical way.

Am I missing something?

Eugene

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

 //linuxgfx.sourceforge.net

On Thu, 13 Jan 2000, Patrick Lerda wrote:

> <<chipsfb.c.bz2>>
> * v0.5
> *
>
> * Work and tested on i386 and powerpc architectures
> * More than one chip 65555 boards allowed.
> * A secondary board with bios is initialized.
> * Support specific 65555 io access, or vga legacy.
> * But, limited to 800x600x8.
>
>
> Patrick LERDA. (lerda@microprocess.com)
>
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/