How do I manually mount a linux file system read/write as a normal user?
This may seem like a stupid question, but with most Linux stuff, it seems to me that a lot of trivial things are not documented.
Anyway, I want to simply mount an ext4 file-system onto a normal mount point in Ubuntu (/media/whereever), as read-writable for the current logged-in user, i.e. me.
I don't want to add anything into /etc/fstab, I just want to do it now, manually. I need super-user privileges to mount a device, but then only root can read-write that mount. I've tried various of the mount options, added it into fstab, but with no luck.
linux permissions mount
add a comment |
This may seem like a stupid question, but with most Linux stuff, it seems to me that a lot of trivial things are not documented.
Anyway, I want to simply mount an ext4 file-system onto a normal mount point in Ubuntu (/media/whereever), as read-writable for the current logged-in user, i.e. me.
I don't want to add anything into /etc/fstab, I just want to do it now, manually. I need super-user privileges to mount a device, but then only root can read-write that mount. I've tried various of the mount options, added it into fstab, but with no luck.
linux permissions mount
Is there a reason why you don't want to mount it somewhere within your home directory?
– Robert S Ciaccio
Oct 6 '10 at 19:14
add a comment |
This may seem like a stupid question, but with most Linux stuff, it seems to me that a lot of trivial things are not documented.
Anyway, I want to simply mount an ext4 file-system onto a normal mount point in Ubuntu (/media/whereever), as read-writable for the current logged-in user, i.e. me.
I don't want to add anything into /etc/fstab, I just want to do it now, manually. I need super-user privileges to mount a device, but then only root can read-write that mount. I've tried various of the mount options, added it into fstab, but with no luck.
linux permissions mount
This may seem like a stupid question, but with most Linux stuff, it seems to me that a lot of trivial things are not documented.
Anyway, I want to simply mount an ext4 file-system onto a normal mount point in Ubuntu (/media/whereever), as read-writable for the current logged-in user, i.e. me.
I don't want to add anything into /etc/fstab, I just want to do it now, manually. I need super-user privileges to mount a device, but then only root can read-write that mount. I've tried various of the mount options, added it into fstab, but with no luck.
linux permissions mount
linux permissions mount
edited Oct 6 '10 at 19:04
ricbax
4,56632539
4,56632539
asked Oct 6 '10 at 18:53
nicodemus13nicodemus13
208127
208127
Is there a reason why you don't want to mount it somewhere within your home directory?
– Robert S Ciaccio
Oct 6 '10 at 19:14
add a comment |
Is there a reason why you don't want to mount it somewhere within your home directory?
– Robert S Ciaccio
Oct 6 '10 at 19:14
Is there a reason why you don't want to mount it somewhere within your home directory?
– Robert S Ciaccio
Oct 6 '10 at 19:14
Is there a reason why you don't want to mount it somewhere within your home directory?
– Robert S Ciaccio
Oct 6 '10 at 19:14
add a comment |
5 Answers
5
active
oldest
votes
On an ext4 filesystem (like ext2, ext3, and most other unix-originating filesystems), the effective file permissions don't depend on who mounted the filesystem or on mount options, only on the metadata stored within the filesystem.
With Ubuntu, mounting should happen automatically when you insert the disk, or you should be able to click on an icon to mount. You can also install pmount
to mount filesystems as an ordinary user from the command line.
If you have a removable filesystem that uses different user IDs from your system, you can use bindfs
(in the Ubuntu package of the same name) to provide a view of any filesystem with different ownership or permissions. The removable filesystem must be mounted already, e.g. on /media/disk9
; then, if you want to appear as the owner of all files, you can run
mkdir ~/disk9
sudo bindfs -u $(id -u) -g $(id -g) /media/disk9 ~/disk9
Thanks! This worked for me with ext3. Note that I had to first mount the ext3 filesystem into some mount directory, then mount that directory with bindfs into the final directory.
– Ilari Kajaste
Jun 9 '11 at 12:19
add a comment |
When you mount the ext4 file system, it uses the permissions that are embedded in that file system. If you wish to override these, then use the following:
1. Find the UID of the user you want to mount as: id <username>
and look for UID=<userid>(<username>) GID=<groupid>(<groupname>)
2. sudo mount -o nosuid,uid=<userid>,gid=<groupid> /dev/whatever /media/wherever
This will mount the filesystem and mark the specified user as the owner of all files, and the specified group as the group for all files. nosuid
is a security measure that prevents the user from bringing in suid programs and using them to gain root access to the system (i.e, a suid version of bash on the filesystem). Adding the noexec
option will provide additional security, but will prevent the user from executing files on the filesystem.
Note: If you're just trying to interact with the file system yourself, you should either fix the permissions on the device, or interact with it as root if it's just a temporary thing (i.e., recovering a broken install).
If this is for mounting a USB or other removable external drive, you should check out the pmount
system which can automate the process for you, or at least make it considerably easier (i.e., pmount <device>
should create the folders for you, mount it as your user, and allow you to unmount it as your user)
1
Any idea whether this should work with EXT3 as well? I getEXT3-fs: Unrecognized mount option "uid=1000" or missing value
in dmesg when I try it with ext3.
– Ilari Kajaste
Jun 9 '11 at 11:25
@Ilari: It won't work with ext3, nor with ext4 for that matter. Most Linux drivers for unix filesystems don't have UID and GID mapping options.
– Gilles
Jun 9 '11 at 12:31
-1 Doesn't work.
– Ilari Kajaste
Jun 10 '11 at 6:16
add a comment |
You can use:
mount -o user /dev/devicename
and user
option in your fstab.
add a comment |
If you're not in the mood to hand-edit your /etc/fstab file, I'd suggest trying out PySDM to define the rules for mounting your ext4 file system on a regular basis. It can be installed by installing the "pysdm" package in Synaptic, or by searching the Ubuntu Software Center for "pysdm".
Once installed, it is available under the System --> Administration --> Storage Device Manager..
add a comment |
Just realised after reading last comment at http://ubuntuforums.org/showthread.php?t=2142284 that all one has to do is a sudo chown -Rvf <user>:<group> <mountpoint>
This is all that is required ...
2
This is a destructive operation. If you do it before mounting, it won't make any difference to file ownership on the mounted drive; if you do it after mounting then it will overwrite all of the permissions. If the drive contains a Linux installation, changing permissions like this will make it unbootable after you unmount it.
– Warbo
Apr 12 '18 at 9:14
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f196653%2fhow-do-i-manually-mount-a-linux-file-system-read-write-as-a-normal-user%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
On an ext4 filesystem (like ext2, ext3, and most other unix-originating filesystems), the effective file permissions don't depend on who mounted the filesystem or on mount options, only on the metadata stored within the filesystem.
With Ubuntu, mounting should happen automatically when you insert the disk, or you should be able to click on an icon to mount. You can also install pmount
to mount filesystems as an ordinary user from the command line.
If you have a removable filesystem that uses different user IDs from your system, you can use bindfs
(in the Ubuntu package of the same name) to provide a view of any filesystem with different ownership or permissions. The removable filesystem must be mounted already, e.g. on /media/disk9
; then, if you want to appear as the owner of all files, you can run
mkdir ~/disk9
sudo bindfs -u $(id -u) -g $(id -g) /media/disk9 ~/disk9
Thanks! This worked for me with ext3. Note that I had to first mount the ext3 filesystem into some mount directory, then mount that directory with bindfs into the final directory.
– Ilari Kajaste
Jun 9 '11 at 12:19
add a comment |
On an ext4 filesystem (like ext2, ext3, and most other unix-originating filesystems), the effective file permissions don't depend on who mounted the filesystem or on mount options, only on the metadata stored within the filesystem.
With Ubuntu, mounting should happen automatically when you insert the disk, or you should be able to click on an icon to mount. You can also install pmount
to mount filesystems as an ordinary user from the command line.
If you have a removable filesystem that uses different user IDs from your system, you can use bindfs
(in the Ubuntu package of the same name) to provide a view of any filesystem with different ownership or permissions. The removable filesystem must be mounted already, e.g. on /media/disk9
; then, if you want to appear as the owner of all files, you can run
mkdir ~/disk9
sudo bindfs -u $(id -u) -g $(id -g) /media/disk9 ~/disk9
Thanks! This worked for me with ext3. Note that I had to first mount the ext3 filesystem into some mount directory, then mount that directory with bindfs into the final directory.
– Ilari Kajaste
Jun 9 '11 at 12:19
add a comment |
On an ext4 filesystem (like ext2, ext3, and most other unix-originating filesystems), the effective file permissions don't depend on who mounted the filesystem or on mount options, only on the metadata stored within the filesystem.
With Ubuntu, mounting should happen automatically when you insert the disk, or you should be able to click on an icon to mount. You can also install pmount
to mount filesystems as an ordinary user from the command line.
If you have a removable filesystem that uses different user IDs from your system, you can use bindfs
(in the Ubuntu package of the same name) to provide a view of any filesystem with different ownership or permissions. The removable filesystem must be mounted already, e.g. on /media/disk9
; then, if you want to appear as the owner of all files, you can run
mkdir ~/disk9
sudo bindfs -u $(id -u) -g $(id -g) /media/disk9 ~/disk9
On an ext4 filesystem (like ext2, ext3, and most other unix-originating filesystems), the effective file permissions don't depend on who mounted the filesystem or on mount options, only on the metadata stored within the filesystem.
With Ubuntu, mounting should happen automatically when you insert the disk, or you should be able to click on an icon to mount. You can also install pmount
to mount filesystems as an ordinary user from the command line.
If you have a removable filesystem that uses different user IDs from your system, you can use bindfs
(in the Ubuntu package of the same name) to provide a view of any filesystem with different ownership or permissions. The removable filesystem must be mounted already, e.g. on /media/disk9
; then, if you want to appear as the owner of all files, you can run
mkdir ~/disk9
sudo bindfs -u $(id -u) -g $(id -g) /media/disk9 ~/disk9
edited Jan 3 at 9:07
Jérôme
1289
1289
answered Oct 6 '10 at 19:53
GillesGilles
52.6k14114161
52.6k14114161
Thanks! This worked for me with ext3. Note that I had to first mount the ext3 filesystem into some mount directory, then mount that directory with bindfs into the final directory.
– Ilari Kajaste
Jun 9 '11 at 12:19
add a comment |
Thanks! This worked for me with ext3. Note that I had to first mount the ext3 filesystem into some mount directory, then mount that directory with bindfs into the final directory.
– Ilari Kajaste
Jun 9 '11 at 12:19
Thanks! This worked for me with ext3. Note that I had to first mount the ext3 filesystem into some mount directory, then mount that directory with bindfs into the final directory.
– Ilari Kajaste
Jun 9 '11 at 12:19
Thanks! This worked for me with ext3. Note that I had to first mount the ext3 filesystem into some mount directory, then mount that directory with bindfs into the final directory.
– Ilari Kajaste
Jun 9 '11 at 12:19
add a comment |
When you mount the ext4 file system, it uses the permissions that are embedded in that file system. If you wish to override these, then use the following:
1. Find the UID of the user you want to mount as: id <username>
and look for UID=<userid>(<username>) GID=<groupid>(<groupname>)
2. sudo mount -o nosuid,uid=<userid>,gid=<groupid> /dev/whatever /media/wherever
This will mount the filesystem and mark the specified user as the owner of all files, and the specified group as the group for all files. nosuid
is a security measure that prevents the user from bringing in suid programs and using them to gain root access to the system (i.e, a suid version of bash on the filesystem). Adding the noexec
option will provide additional security, but will prevent the user from executing files on the filesystem.
Note: If you're just trying to interact with the file system yourself, you should either fix the permissions on the device, or interact with it as root if it's just a temporary thing (i.e., recovering a broken install).
If this is for mounting a USB or other removable external drive, you should check out the pmount
system which can automate the process for you, or at least make it considerably easier (i.e., pmount <device>
should create the folders for you, mount it as your user, and allow you to unmount it as your user)
1
Any idea whether this should work with EXT3 as well? I getEXT3-fs: Unrecognized mount option "uid=1000" or missing value
in dmesg when I try it with ext3.
– Ilari Kajaste
Jun 9 '11 at 11:25
@Ilari: It won't work with ext3, nor with ext4 for that matter. Most Linux drivers for unix filesystems don't have UID and GID mapping options.
– Gilles
Jun 9 '11 at 12:31
-1 Doesn't work.
– Ilari Kajaste
Jun 10 '11 at 6:16
add a comment |
When you mount the ext4 file system, it uses the permissions that are embedded in that file system. If you wish to override these, then use the following:
1. Find the UID of the user you want to mount as: id <username>
and look for UID=<userid>(<username>) GID=<groupid>(<groupname>)
2. sudo mount -o nosuid,uid=<userid>,gid=<groupid> /dev/whatever /media/wherever
This will mount the filesystem and mark the specified user as the owner of all files, and the specified group as the group for all files. nosuid
is a security measure that prevents the user from bringing in suid programs and using them to gain root access to the system (i.e, a suid version of bash on the filesystem). Adding the noexec
option will provide additional security, but will prevent the user from executing files on the filesystem.
Note: If you're just trying to interact with the file system yourself, you should either fix the permissions on the device, or interact with it as root if it's just a temporary thing (i.e., recovering a broken install).
If this is for mounting a USB or other removable external drive, you should check out the pmount
system which can automate the process for you, or at least make it considerably easier (i.e., pmount <device>
should create the folders for you, mount it as your user, and allow you to unmount it as your user)
1
Any idea whether this should work with EXT3 as well? I getEXT3-fs: Unrecognized mount option "uid=1000" or missing value
in dmesg when I try it with ext3.
– Ilari Kajaste
Jun 9 '11 at 11:25
@Ilari: It won't work with ext3, nor with ext4 for that matter. Most Linux drivers for unix filesystems don't have UID and GID mapping options.
– Gilles
Jun 9 '11 at 12:31
-1 Doesn't work.
– Ilari Kajaste
Jun 10 '11 at 6:16
add a comment |
When you mount the ext4 file system, it uses the permissions that are embedded in that file system. If you wish to override these, then use the following:
1. Find the UID of the user you want to mount as: id <username>
and look for UID=<userid>(<username>) GID=<groupid>(<groupname>)
2. sudo mount -o nosuid,uid=<userid>,gid=<groupid> /dev/whatever /media/wherever
This will mount the filesystem and mark the specified user as the owner of all files, and the specified group as the group for all files. nosuid
is a security measure that prevents the user from bringing in suid programs and using them to gain root access to the system (i.e, a suid version of bash on the filesystem). Adding the noexec
option will provide additional security, but will prevent the user from executing files on the filesystem.
Note: If you're just trying to interact with the file system yourself, you should either fix the permissions on the device, or interact with it as root if it's just a temporary thing (i.e., recovering a broken install).
If this is for mounting a USB or other removable external drive, you should check out the pmount
system which can automate the process for you, or at least make it considerably easier (i.e., pmount <device>
should create the folders for you, mount it as your user, and allow you to unmount it as your user)
When you mount the ext4 file system, it uses the permissions that are embedded in that file system. If you wish to override these, then use the following:
1. Find the UID of the user you want to mount as: id <username>
and look for UID=<userid>(<username>) GID=<groupid>(<groupname>)
2. sudo mount -o nosuid,uid=<userid>,gid=<groupid> /dev/whatever /media/wherever
This will mount the filesystem and mark the specified user as the owner of all files, and the specified group as the group for all files. nosuid
is a security measure that prevents the user from bringing in suid programs and using them to gain root access to the system (i.e, a suid version of bash on the filesystem). Adding the noexec
option will provide additional security, but will prevent the user from executing files on the filesystem.
Note: If you're just trying to interact with the file system yourself, you should either fix the permissions on the device, or interact with it as root if it's just a temporary thing (i.e., recovering a broken install).
If this is for mounting a USB or other removable external drive, you should check out the pmount
system which can automate the process for you, or at least make it considerably easier (i.e., pmount <device>
should create the folders for you, mount it as your user, and allow you to unmount it as your user)
answered Oct 6 '10 at 19:44
Darth AndroidDarth Android
34.1k476100
34.1k476100
1
Any idea whether this should work with EXT3 as well? I getEXT3-fs: Unrecognized mount option "uid=1000" or missing value
in dmesg when I try it with ext3.
– Ilari Kajaste
Jun 9 '11 at 11:25
@Ilari: It won't work with ext3, nor with ext4 for that matter. Most Linux drivers for unix filesystems don't have UID and GID mapping options.
– Gilles
Jun 9 '11 at 12:31
-1 Doesn't work.
– Ilari Kajaste
Jun 10 '11 at 6:16
add a comment |
1
Any idea whether this should work with EXT3 as well? I getEXT3-fs: Unrecognized mount option "uid=1000" or missing value
in dmesg when I try it with ext3.
– Ilari Kajaste
Jun 9 '11 at 11:25
@Ilari: It won't work with ext3, nor with ext4 for that matter. Most Linux drivers for unix filesystems don't have UID and GID mapping options.
– Gilles
Jun 9 '11 at 12:31
-1 Doesn't work.
– Ilari Kajaste
Jun 10 '11 at 6:16
1
1
Any idea whether this should work with EXT3 as well? I get
EXT3-fs: Unrecognized mount option "uid=1000" or missing value
in dmesg when I try it with ext3.– Ilari Kajaste
Jun 9 '11 at 11:25
Any idea whether this should work with EXT3 as well? I get
EXT3-fs: Unrecognized mount option "uid=1000" or missing value
in dmesg when I try it with ext3.– Ilari Kajaste
Jun 9 '11 at 11:25
@Ilari: It won't work with ext3, nor with ext4 for that matter. Most Linux drivers for unix filesystems don't have UID and GID mapping options.
– Gilles
Jun 9 '11 at 12:31
@Ilari: It won't work with ext3, nor with ext4 for that matter. Most Linux drivers for unix filesystems don't have UID and GID mapping options.
– Gilles
Jun 9 '11 at 12:31
-1 Doesn't work.
– Ilari Kajaste
Jun 10 '11 at 6:16
-1 Doesn't work.
– Ilari Kajaste
Jun 10 '11 at 6:16
add a comment |
You can use:
mount -o user /dev/devicename
and user
option in your fstab.
add a comment |
You can use:
mount -o user /dev/devicename
and user
option in your fstab.
add a comment |
You can use:
mount -o user /dev/devicename
and user
option in your fstab.
You can use:
mount -o user /dev/devicename
and user
option in your fstab.
edited Oct 4 '12 at 17:19
AruAkise
1,4121917
1,4121917
answered Sep 10 '12 at 3:50
Andrey RegentovAndrey Regentov
82611015
82611015
add a comment |
add a comment |
If you're not in the mood to hand-edit your /etc/fstab file, I'd suggest trying out PySDM to define the rules for mounting your ext4 file system on a regular basis. It can be installed by installing the "pysdm" package in Synaptic, or by searching the Ubuntu Software Center for "pysdm".
Once installed, it is available under the System --> Administration --> Storage Device Manager..
add a comment |
If you're not in the mood to hand-edit your /etc/fstab file, I'd suggest trying out PySDM to define the rules for mounting your ext4 file system on a regular basis. It can be installed by installing the "pysdm" package in Synaptic, or by searching the Ubuntu Software Center for "pysdm".
Once installed, it is available under the System --> Administration --> Storage Device Manager..
add a comment |
If you're not in the mood to hand-edit your /etc/fstab file, I'd suggest trying out PySDM to define the rules for mounting your ext4 file system on a regular basis. It can be installed by installing the "pysdm" package in Synaptic, or by searching the Ubuntu Software Center for "pysdm".
Once installed, it is available under the System --> Administration --> Storage Device Manager..
If you're not in the mood to hand-edit your /etc/fstab file, I'd suggest trying out PySDM to define the rules for mounting your ext4 file system on a regular basis. It can be installed by installing the "pysdm" package in Synaptic, or by searching the Ubuntu Software Center for "pysdm".
Once installed, it is available under the System --> Administration --> Storage Device Manager..
answered Oct 6 '10 at 20:06
ZootZoot
4301614
4301614
add a comment |
add a comment |
Just realised after reading last comment at http://ubuntuforums.org/showthread.php?t=2142284 that all one has to do is a sudo chown -Rvf <user>:<group> <mountpoint>
This is all that is required ...
2
This is a destructive operation. If you do it before mounting, it won't make any difference to file ownership on the mounted drive; if you do it after mounting then it will overwrite all of the permissions. If the drive contains a Linux installation, changing permissions like this will make it unbootable after you unmount it.
– Warbo
Apr 12 '18 at 9:14
add a comment |
Just realised after reading last comment at http://ubuntuforums.org/showthread.php?t=2142284 that all one has to do is a sudo chown -Rvf <user>:<group> <mountpoint>
This is all that is required ...
2
This is a destructive operation. If you do it before mounting, it won't make any difference to file ownership on the mounted drive; if you do it after mounting then it will overwrite all of the permissions. If the drive contains a Linux installation, changing permissions like this will make it unbootable after you unmount it.
– Warbo
Apr 12 '18 at 9:14
add a comment |
Just realised after reading last comment at http://ubuntuforums.org/showthread.php?t=2142284 that all one has to do is a sudo chown -Rvf <user>:<group> <mountpoint>
This is all that is required ...
Just realised after reading last comment at http://ubuntuforums.org/showthread.php?t=2142284 that all one has to do is a sudo chown -Rvf <user>:<group> <mountpoint>
This is all that is required ...
answered Nov 14 '14 at 18:07
SACHIN GARGSACHIN GARG
111
111
2
This is a destructive operation. If you do it before mounting, it won't make any difference to file ownership on the mounted drive; if you do it after mounting then it will overwrite all of the permissions. If the drive contains a Linux installation, changing permissions like this will make it unbootable after you unmount it.
– Warbo
Apr 12 '18 at 9:14
add a comment |
2
This is a destructive operation. If you do it before mounting, it won't make any difference to file ownership on the mounted drive; if you do it after mounting then it will overwrite all of the permissions. If the drive contains a Linux installation, changing permissions like this will make it unbootable after you unmount it.
– Warbo
Apr 12 '18 at 9:14
2
2
This is a destructive operation. If you do it before mounting, it won't make any difference to file ownership on the mounted drive; if you do it after mounting then it will overwrite all of the permissions. If the drive contains a Linux installation, changing permissions like this will make it unbootable after you unmount it.
– Warbo
Apr 12 '18 at 9:14
This is a destructive operation. If you do it before mounting, it won't make any difference to file ownership on the mounted drive; if you do it after mounting then it will overwrite all of the permissions. If the drive contains a Linux installation, changing permissions like this will make it unbootable after you unmount it.
– Warbo
Apr 12 '18 at 9:14
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f196653%2fhow-do-i-manually-mount-a-linux-file-system-read-write-as-a-normal-user%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Is there a reason why you don't want to mount it somewhere within your home directory?
– Robert S Ciaccio
Oct 6 '10 at 19:14