[sllug-members]: change ownership

[Remo Mattei]

Agree.

Good luck

Remo


On 3/25/10 09:06 , "Jarom Hatch" <jshatch at azza.com> wrote:

> Jack,
> 
> For the sake of sanity, if it still isn't working for you after the
> suggestions posted here (since many of them seem to conflict, I've been
> following this for a while now), feel free to contact me off-list and
> I'll be happy to assist you one-on-one or via remote access to get the
> problem solved and the machine working the way you desire.
> 
> Too many cooks in the kitchen ...
> 
> Thanks
> 
> Jarom
> 
> On 03/25/2010 09:01 AM, jfriend31 at comcast.net wrote:
>> thank you
>> jack
>> 
>> 
>> 
>> ----- Original Message -----
>> From: "Matthew Hatch" <matthew at azza.com>
>> To: sllug-members at sllug.org
>> Sent: Thursday, March 25, 2010 8:44:45 AM GMT -07:00 US/Canada Mountain
>> Subject: Re: [sllug-members]: change ownership
>> 
>> I wouldn't set /mnt to anything besides root:root.  Do an 'ls -l' of /
>> and check that the permissions and owners for /mnt match this:
>> 
>> drwxr-xr-x   2 root root   4096 2009-10-23 18:47 mnt
>> 
>> ^----  Those permissions only allow root to write to the /mnt directory
>> but will allow everyone else read-only access to enter it.  Then, if
>> /mnt/jacks has the same permissions (755) but is owned by jack:jack, you
>> can write to that directory.
>> 
>> Run this:
>> 
>> sudo chown root:root /mnt
>> sudo chmod 755 /mnt
>> 
>> If you still can't get to '/mnt/jacks', run this:
>> 
>> sudo chown jack:jack /mnt/jacks
>> sudo chmod 755 /mnt/jacks
>> 
>> ...though if you already did what jarom said, this should be unnecessary.
>> 
>> --
>> Matthew Hatch
>> 
>> On 03/25/2010 08:38 AM, Shawn Thompson wrote:
>>> [sudo|su -c] chown jack:jack -R /mnt
>>> That *should* fix the issue although you may have to repermission after
>>> remount but not 100% on that.
>>> 
>>> On Thu, Mar 25, 2010 at 8:16 AM, Remo Mattei <remo at italy1.com
>>> <mailto:remo at italy1.com>> wrote:
>>> 
>>>     What is the line on fstab?
>>> 
>>>     Inviato da iPhone
>>> 
>>>     Il giorno Mar 25, 2010, alle ore 7:09, jfriend31 at comcast.net
>>>     <mailto:jfriend31 at comcast.net> ha scritto:
>>> 
>>>         here is the result:
>>> 
>>> 
>>>         jack at jack-desktop:~$ sudo chmod a+x /mnt/jacks
>>>         [sudo] password for jack:
>>>         jack at jack-desktop:~$ cd /mnt
>>>         bash: cd: /mnt: Permission denied
>>> 
>>>         jack at jack-desktop:~$ cd
>>>         jack at jack-desktop:~$ cd /mnt/jacks
>>>         bash: cd: /mnt/jacks: Permission denied
>>>         jack at jack-desktop:~$
>>> 
>>> 
>>>         jack
>>> 
>>> 
>>>         ----- Original Message -----
>>>         From: "Jarom Hatch" <jshatch at azza.com <mailto:jshatch at azza.com>>
>>>         To: "Salt Lake Linux Users Group Discussions"
>>>         <sllug-members at sllug.org <mailto:sllug-members at sllug.org>>
>>>         Sent: Thursday, March 25, 2010 7:03:47 AM GMT -07:00 US/Canada
>>>         Mountain
>>>         Subject: Re: [sllug-members]: change ownership
>>> 
>>>             drw-rw-rw- 3 jack jack 4096 2010-03-22 19:49 jacks
>>> 
>>> 
>>>         You do not have the 'x' bit set on the directory.  For regular
>>>         files,
>>>         the x bit is the execute bit, but for directories it allows the
>>>         user to
>>>         enter.  If it isn't set, nobody but root will be able to get in, no
>>>         matter who the owner is.
>>> 
>>>         Run "chmod a+x /mnt/jacks" to set it properly.
>>> 
>>>         Thanks
>>> 
>>>         Jarom
>>> 
>>>         
>>> ______________________________________________________________________
>>>         See http://www.sllug.org/ for latest SLLUG news, information, links.
>>>         Join SLLUG and other UT LUG members on irc.FreeNode.net
>>>         <http://irc.FreeNode.net> channel #Utah
>>>         sllug-members at sllug.org <mailto:sllug-members at sllug.org>
>>>         http://www.sllug.org/cgi-bin/mailman/listinfo/sllug-members
>>>         
>>> ______________________________________________________________________
>>>         See http://www.sllug.org/ for latest SLLUG news, information, links.
>>>         Join SLLUG and other UT LUG members on irc.FreeNode.net
>>>         <http://irc.FreeNode.net> channel #Utah
>>>         sllug-members at sllug.org <mailto:sllug-members at sllug.org>
>>>         http://www.sllug.org/cgi-bin/mailman/listinfo/sllug-members
>>> 
>>>         
>>> 
>>>     ______________________________________________________________________
>>>     See http://www.sllug.org/ for latest SLLUG news, information, links.
>>>     Join SLLUG and other UT LUG members on irc.FreeNode.net
>>>     <http://irc.FreeNode.net> channel #Utah
>>>     sllug-members at sllug.org <mailto:sllug-members at sllug.org>
>>>     http://www.sllug.org/cgi-bin/mailman/listinfo/sllug-members
>>> 
>>> 
>>> 
>>> 
>>> ______________________________________________________________________
>>> See http://www.sllug.org/ for latest SLLUG news, information, links.
>>> Join SLLUG and other UT LUG members on irc.FreeNode.net channel #Utah
>>> sllug-members at sllug.org
>>> http://www.sllug.org/cgi-bin/mailman/listinfo/sllug-members
>> 
>> 
>> ______________________________________________________________________
>> See http://www.sllug.org/ for latest SLLUG news, information, links.
>> Join SLLUG and other UT LUG members on irc.FreeNode.net channel #Utah
>> sllug-members at sllug.org
>> http://www.sllug.org/cgi-bin/mailman/listinfo/sllug-members
>> ______________________________________________________________________
>> See http://www.sllug.org/ for latest SLLUG news, information, links.
>> Join SLLUG and other UT LUG members on irc.FreeNode.net channel #Utah
>> sllug-members at sllug.org
>> http://www.sllug.org/cgi-bin/mailman/listinfo/sllug-members
> 
> ______________________________________________________________________
> See http://www.sllug.org/ for latest SLLUG news, information, links.
> Join SLLUG and other UT LUG members on irc.FreeNode.net channel #Utah
> sllug-members at sllug.org
> http://www.sllug.org/cgi-bin/mailman/listinfo/sllug-members
> 
> !DSPAM:4bab7c98136741221455225!
>