Skip to contentSkip to conversation

Yet another design for /proc. Or actually /kernel.

DISCUSSION Remco Post 4 participants 4 messages Nov 8, 2001 – Nov 12, 2001 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]

Remco Post

author
#1 lore raw
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines

Here's my go at a new design for /proc. I designed it from a userland point of view and tried not to drown myself into details.

Did you have to change the subject line. It makes it harder to kill >file when people keep doing that

Quoted 7 lines

You really consider this discussion to be unimportant? Granted, the lack of organization in /proc is not a bug, but keeping the kernel organized is part of maintenence. Like cleaning my room-- it's not a showstopper if it is messy, but it is nicer and easier to work in when neat.

Will Knop
[email protected]

Hi,

the discussion is irrelevant. Despite what everybody thinks, Linus thinks /proc must be not binary, so it will stay that way for those of us who run Linus kernels...

I can inmagine people like Alan ignoring this discussion after such a statement, the outcome of the discussion is irrelevant for the kernel development.

Signature · 10 lines
Met vriendelijke groeten,

Remco Post

SARA - Stichting Academisch Rekencentrum Amsterdam
High Performance Computing  Tel. +31 20 592 8008    Fax. +31 20 668 3167

"I really didn't foresee the Internet. But then, neither did the computer
industry. Not that that tells us very much of course - the computer industry
didn't even foresee that the century was going to end." -- Douglas Adams
#2 lore raw
Quoted 3 lines

the discussion is irrelevant. Despite what everybody thinks, Linus thinks /proc must be not binary, so it will stay that way for those of us who run Linus kernels...

Linus has been "wrong" before. It will require good code and numbers backing that codes "goodness" before Linus will begin to listen. Yes, a new procfs format will break a great deal of userland toys, so the changes had better be worth it and sufficient to never, EVER require a complete overhaul in the future.

Quoted 3 lines

I can inmagine people like Alan ignoring this discussion after such a statement, the outcome of the discussion is irrelevant for the kernel development.

I think Alan is already ignoring the entire discussion.

--Ricky

#3 lore raw
Quoted 9 lines · Ricky Beam
Quoted 3 lines

the discussion is irrelevant. Despite what everybody thinks, Linus thinks /proc must be not binary, so it will stay that way for those of us who run Linus kernels...

Linus has been "wrong" before. It will require good code and numbers backing that codes "goodness" before Linus will begin to listen. Yes, a new procfs format will break a great deal of userland toys, so the changes had better be worth it and sufficient to never, EVER require a complete overhaul in the future.

/proc for process info is a given (many Unices have it, it is nice at least for compatibility).

/proc for random other garbage should go away. To get at some value you can get via specialized calls by read(2) also is just kernel bloat.

Signature · 4 lines
Dr. Horst H. von Brand                Usuario #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513
#4 lore raw
Quoted 12 lines · Horst von Brand
Quoted 9 lines · Ricky Beam
Quoted 3 lines

the discussion is irrelevant. Despite what everybody thinks, Linus thinks /proc must be not binary, so it will stay that way for those of us who run Linus kernels...

Linus has been "wrong" before. It will require good code and numbers backing that codes "goodness" before Linus will begin to listen. Yes, a new procfs format will break a great deal of userland toys, so the changes had better be worth it and sufficient to never, EVER require a complete overhaul in the future.

Quoted 5 lines

/proc for process info is a given (many Unices have it, it is nice at least for compatibility).

/proc for random other garbage should go away. To get at some value you can get via specialized calls by read(2) also is just kernel bloat.

My absolute favourite is the following in arch/i386/kernel/irq.c!!!!

Disease symptoms like this are distributed all over the kernel code.

========================================================================
static struct proc_dir_entry * root_irq_dir;
static struct proc_dir_entry * irq_dir [NR_IRQS];

#define HEX_DIGITS 8

static unsigned int parse_hex_value (const char *buffer,
unsigned long count, unsigned long *ret)

{
	unsigned char hexnum [HEX_DIGITS];
	unsigned long value;
	int i;