ecryptfs-mount-private mounts the private/home directory, but the pwd is still the unmounted directory
Bug #332331 reported by
Dustin Kirkland
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ecryptfs-utils (Ubuntu) |
Fix Released
|
Medium
|
Dustin Kirkland |
Bug Description
Binary package hint: ecryptfs-utils
In the situation where you are in your $HOME or ~/Private, and this directory is unmounted, you can run:
$ ecryptfs-
Assuming this mount succeeds, you are good to go. However, you are still in your unmounted home/private directory.
To solve this, you need to cd to this directory again. This should definitely be fixed by a one-liner in ecryptfs-
:-Dustin
Related branches
Changed in ecryptfs-utils: | |
assignee: | nobody → kirkland |
importance: | Undecided → Medium |
milestone: | none → jaunty-alpha-5 |
status: | New → In Progress |
Changed in ecryptfs-utils: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
Actually, this is impossible to "solve" within shell: www.faqs. org/faqs/ unix-faq/ faq/part2/ section- 8.html
* http://
A given shell script can't actually affect the working directory of the calling shell.
Thus, we're going to have to solve this with an informative info message. Check if the current directory matches that of the directory just mounted. If so, tell the user to run:
$ cd $PWD
:-Dustin