Prev: disable sudoers "notty" option on a per directive basis
Next: cat for binary file
From: Aragorn on 9 Feb 2010 02:47
On Tuesday 09 February 2010 08:16 in comp.os.linux.misc, somebody
identifying as Phred Phungus wrote...

>> On Mon, 08 Feb 2010 17:24:14 -0700, Phred Phungus wrote:
>>
>>> I've now tripped on another instance of being denied permission:
>>>
>>> dan(a)dan-desktop:/usr/bin$ ls -l >text1.txt bash: text1.txt:
>>> Permission denied

Unprivileged users do not have write access to anything under "/usr",
except for "/usr/tmp", because that's normally a symlink to "/var/tmp",
and the latter is world-writable, with the sticky bit set.

>>> dan(a)dan-desktop:/usr/bin$ ls -l text1.txt ls: cannot access
>>> text1.txt: No such file or directory dan(a)dan-desktop:/usr/bin$
>>>
>>> How can a non-existent file deny me permission?

It didn't. Please do some reading on UNIX ownerships and permissions.

--
*Aragorn*
(registered GNU/Linux user #223157)
From: Chris F.A. Johnson on 9 Feb 2010 03:23
On 2010-02-09, Phred Phungus wrote:
....
> [x-posting]
>
> I heard from c.l.p.misc that this group exists. My first question for
> the group goes to the AssClown percentage: how many jerks do you have
> in here like Dan C?

None; we use killfiles.

You should do the same instead of spreading his pre-adolescent
drivel that we wouldn't see if you didn't repeat it.

--
Chris F.A. Johnson, author | <http://cfajohnson.com>
Shell Scripting Recipes: | My code in this post, if any,
A Problem-Solution Approach | is released under the
2005, Apress | GNU General Public Licence
 | 
Pages: 1
Prev: disable sudoers "notty" option on a per directive basis
Next: cat for binary file