From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] User can mount/umount but not write to top the new drive
Date: Tue, 10 Apr 2012 12:18:38 +0100 [thread overview]
Message-ID: <ABC8FA89-A41E-4390-90E8-855769F85A3D@stellar.eclipse.co.uk> (raw)
In-Reply-To: <CAK2H+eddgVMBoVUFR0V8QA79y9eE_3hMcQDdAW-UwhyOY+mEdQ@mail.gmail.com>
On 9 April 2012, at 20:59, Mark Knecht wrote:
> …
> In the past I've gotten around this by having root mount the drive
> and then change ownership to mark:users once it's mounted. Linux
> remembers I've done that once and no longer requires me to do anything
> else as root.
>
> Is that truly required or is there a way to give the user access to
> the top of the new mount point without roots' involvement?
I recall having exactly this problem years ago, and having had it explained to me here on this list.
I'm sure that if you *once* chmod / chown as root, then the permissions will be remembered correctly forever after. If you unmount and remount the drive, reboot the computer or whatever, the user will be able to write to the drive.
Do double & triple check this because, although I'm certainly fallible, I feel certain of this.
If I'm mistaken I guess you could do something involving udev mounting rules.
Note that if you use the same USB drive on different computers (or dual-boot different distros) then you have to be aware of user name vs. user ID number.
Stroller.
next prev parent reply other threads:[~2012-04-10 11:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 19:59 [gentoo-user] User can mount/umount but not write to top the new drive Mark Knecht
2012-04-09 20:38 ` Canek Peláez Valdés
2012-04-09 21:22 ` Mark Knecht
2012-04-09 20:48 ` Neil Bothwick
2012-04-09 21:23 ` Mark Knecht
2012-04-09 21:39 ` Neil Bothwick
2012-04-09 21:42 ` Canek Peláez Valdés
2012-04-09 21:58 ` Mark Knecht
2012-04-09 22:45 ` Michael Mol
2012-04-10 11:18 ` Stroller [this message]
2012-04-10 11:55 ` Alan McKinnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ABC8FA89-A41E-4390-90E8-855769F85A3D@stellar.eclipse.co.uk \
--to=stroller@stellar.eclipse.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox