pam_namespaces and --make-shared vs mountall
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mountall (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Binary package hint: mountall
I'm using pam_namespaces in my PAM configuration (mainly to have /tmp and /var/tmp mapped into my encrypted $HOME, so that private temp files do not end up on the not yet encrypted root partition). However, having different namespaces means that udisks will run in a different namespace than my user, so it will mount removable drives (like DVD) in the other namespace than mine - resulting in e.g. the file manager being unable to open the newly mounted (but yet unreachable) directory. To solve this, I created another /media mount point on /tmp and was planning to call mount --make-shared on it, to make these mounts show through. Googling a little, I found that
none /media tmpfs defaults,
none /media none make-shared 0 0
should solve my issue - which mount -a confirms to be correct. However, mountall has two issues: it will ignore all lines except the last for the same mount point, and it will do nothing with fstype = none, since such a file system is indeed unknown - it does not understand the special syntax.
tags: | added: patch |
Changed in mountall (Ubuntu): | |
status: | Confirmed → Triaged |
importance: | Undecided → Medium |
The attached patch fixes both issues (the duplicate mount point issue also reported in bug #503003 and
making it "understand" make-*). (Actually, it relies on mount to know which --make-* options are valid.)