>> But that shouldn't be the only option - because it would be horrible >> to use. If I login on multiple terminals, I normally want to mount >> filesystems in /home/jamie/mnt on one terminal, and use them on another. > >And when you log in on several terminals you usually want same $PATH. >You don't do that by sharing VM between shell processes, do you?
I share Al's view, and would expand: You'd _like_ to be able to add something to your namespace once and have it show up in multiple process' namespaces, but you wouldn't expect it, because Unix has been horrible to use in that way forever. I am frequently frustrated when I decide to change my environment either by setting an environment variable or shell variable or alias, and I have to do it separately in every existing shell. And forget about the background jobs. But at least it's consistent. And there are other times when I exploit the fact that I can set something differently in different shells of the same user. We do have a few areas where a group of processes can share the same kernel state, but it's always based on common ancestry. It would take a major new concept to have a different kind of group of processes for namespace purposes, and then we probably wouldn't want to base it on uid, because uid means other things already. Why tie them together? -- Bryan Henderson IBM Almaden Research Center San Jose CA Filesystems - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
