Skip to content

Permission issue when mounting on a computer with different UIDs #6

Closed
boyska opened this Issue Jul 10, 2011 · 15 comments

2 participants

@boyska
Dyne.org member
boyska commented Jul 10, 2011

This is because of permission on ext3. Re-mapping dinamically everything seems to be difficult AND unpractical; there is no mounting option to force everything to be owned by user X.

Simplest solution could be just using a user-less filestystem, like... FAT32

@jaromil
Dyne.org member
jaromil commented Oct 27, 2011

related to #45

last discussion on mailinglist set forward the option to make FAT a default filesystem

downsides: tomb will be slower and less reliable, filenames can get scrambled

@boyska
Dyne.org member
boyska commented Oct 27, 2011

Another solution could be just using

chown user $mountpoint -T

when mounting the tomb. It could be a post-hook, but an option is maybe more appropriate. I'm not really sure on what to do.

EDIT: it was

chown user $mountpoint -R
@jaromil
Dyne.org member
@boyska
Dyne.org member
boyska commented Oct 28, 2011

oops, it was -R sorry for the typo

@jaromil
Dyne.org member
@boyska
Dyne.org member
boyska commented Oct 28, 2011

maybe it should be done in background.

No, it should not be automatically done. Because you may like to use a tomb on a single machine where the owner is not always the user who is mounting it. For example, a crazy man could use a tomb for /tmp or who knows what.

also worth looking inside the chown command if it does i/o on every file even is the permission > is already set...

I suppose it does a stat and, if necessary, it changes it. Otherwise, the -c option of chown could not work.

@jaromil
Dyne.org member
@boyska
Dyne.org member
boyska commented Oct 30, 2011

and most importantly, are you giving up on VFAT? :) if yes, thanks! :D

No way! :P
Well, I'm trying to make tomb versatile. I'd like to add a --fs= to tomb, so that I could create my tombs with vfat. Often, it's just good that way.
But sometimes you can't/don't want, while like to make data moving easy. I want to address ALL that situations, because I need it ;)

@jaromil
Dyne.org member
@boyska
Dyne.org member
boyska commented Oct 31, 2011

however i think the default should stay currently used ext3

of course it should

@boyska
Dyne.org member
boyska commented Nov 12, 2011

btw, I've said "it could be a post-hook". I was wrong, it couldn't, because it needs sudo.

I propose a "permission-hook", so that tomb will automatically chown the tomb IF that file is present.

@jaromil
Dyne.org member
@boyska
Dyne.org member
@boyska
Dyne.org member
boyska commented Sep 1, 2012

957e820 seems to fix this. @jaromil can you confirm?

@jaromil
Dyne.org member
jaromil commented Feb 16, 2013

yes indeed, it was coded with this discussion in mind. thanks for your argumenting :^)

@jaromil jaromil closed this Feb 16, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.