Re: Configure mangles hex values

m, Marcelo Tosatti wrote: > Hi Nick, > > Curiosity: What was the reason for stripping the leading 0x? > > On Mon, Jan 24, 2005 at 02:41:56PM -0800, Nick Pollitt wrote: > > Sorry about previous message. > > > > The hex function in scripts/Configure strips the leading

Re: Configure mangles hex values

Sorry about previous message. The hex function in scripts/Configure strips the leading 0x from hex values. The 0x needs to be there in autoconf.h, and stripping it out causes the following problematic scenario: If I start with a hex value in my config file like this: CONFIG_LOWMEM_SIZE=0x4

Configure mangles hex values

[PATCH] Process pinning

This patch applies cleanly to 2.4.3-ac3. Changes to array.c expose cpus_allowed in proc/pid/stat. PR_GET_RUNON and PR_SET_RUNON were done by Ingo and Dimitris. Added MUSTRUN_PID and RUNANY_PID. Also attached is runon and it's manpage. Nick diff -X /home/npollitt/dontdiff -Nur 243-ac3/l

Re: New Guy!!

s list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ -- Nick Pollitt phone: 650.933.7406 MTS - Design fax: 65

Proc fs limit workaround?

I have a machine with many partitions, and /proc/partitions, being limited to 4K output, doesn't display all the information I need. My first question/request is has anyone else already written a patch to get around the 4K limit? And second, why is the 4K limit there in the first place? Thank