aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEmilio López <turl@tuxfamily.org>2013-06-08 12:53:59 -0300
committerEmilio López <turl@tuxfamily.org>2013-06-08 12:56:11 -0300
commit7ac751f6ea3e71651bfe54083a5b9a93647f0331 (patch)
tree99a771d4cc9639bcf8d8048c61a891a8c62def20
parente672fdfefb0f2febfb0312257dd2fe2b09e2d81c (diff)
downloadbootable_recovery-7ac751f6ea3e71651bfe54083a5b9a93647f0331.zip
bootable_recovery-7ac751f6ea3e71651bfe54083a5b9a93647f0331.tar.gz
bootable_recovery-7ac751f6ea3e71651bfe54083a5b9a93647f0331.tar.bz2
recovery: use just the mount point instead of the full path
When resorting to using mount because a block device uses 'auto' filesystem, we should use the mount point and not the full path. This fixes an issue with nandroid to external sd on yuga. Change-Id: Idbff944ea6d5af9112644c2ed46e23ea0a33e5ee
-rw-r--r--roots.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/roots.c b/roots.c
index a42e355..44fa14a 100644
--- a/roots.c
+++ b/roots.c
@@ -298,7 +298,7 @@ int ensure_path_mounted_at_mount_point(const char* path, const char* mount_point
} else {
// let's try mounting with the mount binary and hope for the best.
char mount_cmd[PATH_MAX];
- sprintf(mount_cmd, "mount %s", path);
+ sprintf(mount_cmd, "mount %s", mount_point);
return __system(mount_cmd);
}