lkml.org 
[lkml]   [2000]   [Feb]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Linux's future: //posix/ipc, //root and so on ?
Date
From
> AC> Millions of apps rely on // working.
>
> Are you sure ? Why ? Till there no warning we can not check it.

Because everyone knows // is fine so everyone is really sloppy about
combining paths together.

> POSIX IPC implementation needed finename, visible from userspace. If you

POSIX IPC filespace doesnt have to be visible as the normal file
space if I remember correctly, thats a luxury add on that makes sense to do.

> construct such name. With //ipc //ipc/bla-bla-bla will be ALWAYS
> //ipc/bla-bla-bla -- no matter what and when. The same goes for //proc and

Which is a bug.

> AC> mounting /ipc can be handled in startup space quite easily.
> Then we'll end up with kludges like devpts handling in glibc :-((

Actually putting ipc under devfs or proc isnt too daft. However the only
case we need to deal with is 'where do I mount ipc if I mount it'. That is
policy so belongs in user space.

As it stands now if you forget to mount /proc odd things occur. It hasnt killed
anyone despite predictions that /proc being a real fs would cause doom gloom
and the end of the world made several years ago 8)

Alan


-
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/

\
 
 \ /
  Last update: 2005-03-22 13:56    [W:0.071 / U:0.448 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site