The distibution has been made with the chmod, but without the chown command
in its /bin directory.
chown is in /usr/sbin/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send
On Tue, Feb 12, 2008 at 08:49:22AM -0800, deepcore wrote:
chown is in /usr/sbin/
ok. I get that, and i found it
I can, however not execute it.
whenever i go to the usr/sbin and type chown i get
chown: Command not found.
That is most likely because it is not in your path.
It you had
deepcore wrote:
chown is in /usr/sbin/
ok. I get that, and i found it
I can, however not execute it.
whenever i go to the usr/sbin and type chown i get
chown: Command not found.
i find this pretty strange as ls -l shows:
-r-xr-xr-x 1 root wheel 6688 Jan 12 2007 chown
shouldn't
At 10:49 AM 2/12/2008, deepcore wrote:
chown is in /usr/sbin/
ok. I get that, and i found it
I can, however not execute it.
whenever i go to the usr/sbin and type chown i get
chown: Command not found.
i find this pretty strange as ls -l shows:
-r-xr-xr-x 1 root wheel 6688 Jan 12 2007
chown is in /usr/sbin/
ok. I get that, and i found it
I can, however not execute it.
whenever i go to the usr/sbin and type chown i get
chown: Command not found.
i find this pretty strange as ls -l shows:
-r-xr-xr-x 1 root wheel 6688 Jan 12 2007 chown
shouldn't this mean that the file
.
When i installed it ages ago i did, however not have the insight to see
which users should own which directories, and i need to change that now.
The distibution has been made with the chmod, but without the chown command
in its /bin directory.
Does anyone know where to get this nifty util
On Mon, 22 Mar 2004, Gerald S. Stoller wrote:
This gives the system owner the flexibility to leave
it this way, or to restrict this ability to root as it is now by
seting chown's permissions to 500 , it is already owned by root.
The chown command merely uses the chown system call
In freeBSD 4.3 4.7 ( others), the chown command only works
for root , for other users the command responds (if one actually tries
to change the ownership) chown: file name: Operation not permitted
where file name is the first file name in the argument-list. This
command does work
