2011-01-19 23:00:46 |
RK |
bug |
|
|
added bug |
2011-01-19 23:03:10 |
RK |
attachment added |
|
patch https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/705178/+attachment/1799965/+files/mountall-705178.patch |
|
2011-01-19 23:10:07 |
RK |
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,noexec,nodev,auto 0 0
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 unkown -
it does not understand the special syntax. |
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,noexec,nodev,auto 0 0
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.
|
|
2011-01-19 23:10:32 |
RK |
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,noexec,nodev,auto 0 0
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.
|
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,noexec,nodev,auto 0 0
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.
|
|
2011-01-19 23:10:48 |
RK |
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,noexec,nodev,auto 0 0
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.
|
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,noexec,nodev,auto 0 0
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.
|
|
2011-01-20 17:38:38 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Review Team |
2011-01-20 17:38:40 |
Brian Murray |
tags |
|
patch |
|
2012-03-13 21:18:35 |
Launchpad Janitor |
mountall (Ubuntu): status |
New |
Confirmed |
|
2012-05-20 03:44:05 |
Steve Langasek |
mountall (Ubuntu): status |
Confirmed |
Triaged |
|
2012-05-20 03:44:07 |
Steve Langasek |
mountall (Ubuntu): importance |
Undecided |
Medium |
|