Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I want to set the permissions of Launcher and its subdirectories such that only I, or someone in my group, can manipulate them. (I know how to do this.)
As an operator, I need to be able to execute launch.sh, and to copy executables from the Bin subdirectory to a local directory for execution. How do I accomplish this while still keeping Launcher and its subdirectories locked down?
I am trying to think the problem out, and basically what I want is for the operator to be able to run a script that he cannot read/modify. This script has the permission necessary to execute lauch.sh, perform the copies (, and set file permission so that operator can use those files). Is this possible?
FYI: Currently this software is setup so that operator is the owner, but Iíd really like to separate the developer from the operator (as an operator should never be tinkering with the source code or scripts).
1. if you really mean a script (eg bash, Perl etc) then it must be readable to be executed; ie must have at least r-x somewhere.
You would have to compile a binary (eg using C) to avoid the r perm and have it run only with x perms.
a) you could go with rwxrwxr-x owned by you:you, but that of course means anyone can read/run.
b) You could go with rwxr-x--- owned by you:somegrp & add operator to somegroup, but only you would be able to edit it.