XPost: comp.os.linux.misc, comp.os.linux.development.apps, comp.unix.programmer   
   From: rweikusat@talktalk.net   
      
   Lew Pitcher  writes:   
      
   [...]   
      
   > Well, I can answer my own question, now. But the answer   
   > leads to more questions.   
   >   
   > The reason I get "Operation not permitted" on the   
   > container /proc mount on my "production" system is that   
   > I also run an nfs server on my "production" system (and   
   > do not run one on my development system), and is nfs   
   > server maintains two mountpoints within the /proc   
   > filesystem.   
   >   
   > Apparently, the attempt to mount /proc within my container   
   > was blocked by the existance of these two mount points   
   > (/proc/fs/nfs and /proc/fs/nfsd), as when I shut down my   
   > rpc and nfs servers, and umounted these two mounts, I could   
   > successfully run my demo container.   
   >   
   > /Now/ the question is: how do I get my container /proc mount   
   > to ignore or bypass these two nfsd mounts?   
      
   Instead of doing a bind mount of a proc filesystem already mounted   
   somewhere, you could mount a new instance of it. The command for this   
   would be   
      
   mount -t proc proc    
      
   You'll generally also want to mount sysfs, BTW.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)