From: Mail@JoesLife.org
On Sat, 7 Jan 2023 07:06:37 -0000 (UTC), Jasen Betts wrote:
> On 2023-01-07, Lew Pitcher wrote:
>> On Sat, 07 Jan 2023 01:27:28 +0000, Lew Pitcher wrote:
>
>>> I try to
>>> mount("proc","proc","proc",MS_REC,NULL)
>>> /but/ ONLY ON THIS ONE SYSTEM.
>
>> 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?
>
> What's the difference between mount() and /bin/mount
I'm going to try *again* to reply (having trouble):
Because I write bash code, your question looks to me like you are asking
for the difference between a shell function called mount and the mount
executable at /bin/mount.
For example you could write a function definition, source it, and then
use it to perform the real (or modified) /bin/mount. Here is such a
function defintion with no modification:
mount() {
local device
local point
device="$1"
point="$2"
/bin/mount $device $point
return
}
Notice the "mount()" syntax in the function definition. That is what
prompted me to respond as I did.
-Joe
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
