Date: Tue, 4 Dec 2001 01:44:08 -0800 From: "Crist J . Clark" <cjc@FreeBSD.ORG> To: Anthony Atkielski <anthony@freebie.atkielski.com> Cc: George Reid <greid@FreeBSD.ORG>, FreeBSD Questions <freebsd-questions@FreeBSD.ORG> Subject: Re: Modifying only certain bits with chmod Message-ID: <20011204014408.D37981@blossom.cjclark.org> In-Reply-To: <009101c17c12$649fe2e0$0a00000a@atkielski.com>; from anthony@freebie.atkielski.com on Mon, Dec 03, 2001 at 04:50:24PM %2B0100 References: <007a01c17c08$fd7f1030$0a00000a@atkielski.com> <20011203144722.A19484@FreeBSD.org> <009101c17c12$649fe2e0$0a00000a@atkielski.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 03, 2001 at 04:50:24PM +0100, Anthony Atkielski wrote:
> I ended up modifying the command, which was easier (for me) than memorizing the
> symbolic syntax. Now I can type
>
> chmod 600:500 file
>
> to turn on the the r bit and turn off the x bit for the owner while leaving
> everything else alone. I find it easier to relate the bits in octal to the
> positions of the permission as output from ls than to try to remember letters
> and parameters.
>
> It's great to have source!
>
> So ... what's the safest way to make this my system-wide command without
> interfering with the standard chmod source and stuff? I guess I could just copy
> the modified binary over to bin, no? What do most people do when they develop
> their own local custom versions of a command?
Switching CVS instead of CVSup will allow you to keep changes in your
source repository that are kept when you update code. But this might
be a heavyweight solution for just one program.
--
Crist J. Clark | cjclark@alum.mit.edu
| cjclark@jhu.edu
http://people.freebsd.org/~cjc/ | cjc@freebsd.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011204014408.D37981>