Gentoo Archives: gentoo-user

From: meino.cramer@×××.de
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Weird (?) permission problem...
Date: Wed, 15 Dec 2010 15:22:12
Message-Id: 20101215152032.GD5525@solfire
In Reply to: Re: [gentoo-user] Weird (?) permission problem... by "J. Roeleveld"
1 J. Roeleveld <joost@××××××××.org> [10-12-15 16:00]:
2 > On Wednesday 15 December 2010 15:41:25 meino.cramer@×××.de wrote:
3 > > Neil Bothwick <neil@××××××××××.uk> [10-12-15 15:40]:
4 > > > On Wed, 15 Dec 2010 15:13:31 +0100, meino.cramer@×××.de wrote:
5 > > > > And this happens to any mountpoint I mount that device on regardless
6 > > > > of its perm settings before the mount
7 > > >
8 > > > With nothing mounted on it, the mount point's permission are those of the
9 > > > directory. As soon as you mount something on it, the mount point has the
10 > > > ownership and permissions of the root of the filesystem that you just
11 > > > mounted there. In the same way that the contents of the filesystem
12 > > > appear at the mount point, so does the metadata, so change the
13 > > > permissions after mounting.
14 > >
15 > > ...unfortunately (as root)
16 > >
17 > > cd /tmp
18 > > chmod 1777 .
19 > >
20 > > does not help...
21 >
22 > I don't think you can change the permissions like that.
23 > Try:
24 > cd /
25 > chmod 1777 /tmp
26 >
27 > To remove the "s"-bits, try the following:
28 > cd /
29 > chmod u-s /tmp
30 > chmod g-s /tmp
31 >
32 > This, however, needs to be done while the "/tmp" filesystem is mounted.
33 > Otherwise you are only changing the mount-point (directory) not the actual
34 > filesystem.
35 >
36 > --
37 > Joost
38 >
39
40 interesting...
41 Until now, I thought '.' is equal to the directory I am in.
42
43 Ok, times is changing, me too, but as it seems not fast enough ;)
44
45 Thanks a lot... thats fix it!
46
47 Best regards,
48 mcc

Replies

Subject Author
Re: [gentoo-user] Weird (?) permission problem... "J. Roeleveld" <joost@××××××××.org>
Re: [gentoo-user] Weird (?) permission problem... Alan McKinnon <alan.mckinnon@×××××.com>