[SOLVED] Problem about noexec option in /etc/fstab
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi all,
I set the noexec option in the /etc/fstab and then mount the nfs directory. I copied an rpm package from dvd to nfs server shared folder. Then I executed the rpm package from cilent. But it did work!
Who can explain that strange phenomenon?
Thanks in advance!
The executable was on the client, not the NTFS server. The rpm command is on the client box, not the server so you are not running an executable on the server.
Hi ,
I made you understood. I used executable command on the client but not server.
you failed to understand the point, the package itself isn't an executable, RPM was used on the client and is stored on the client, all you did was point RPM to USE the package the package itself did nothing and did NOT execute as the RPM executable on the client did all the work. If the RPM executable was on the server and you tried executing that, then that is what would not work, but that's not what you are doing. Your using RPM on a client machine where executables are allowed.
you failed to understand the point, the package itself isn't an executable, RPM was used on the client and is stored on the client, all you did was point RPM to USE the package the package itself did nothing and did NOT execute as the RPM executable on the client did all the work. If the RPM executable was on the server and you tried executing that, then that is what would not work, but that's not what you are doing. Your using RPM on a client machine where executables are allowed.
Hi,
But the rpm package was in the nfs shared directory!(meant on the server). And I mounted the shared directory and then execute the rpm package...
Let me try...
A file called filename.rpm is a data file not an application. Just like windows associations when you click on a file.xls your not executing file.xls but actually excel file.xls. The same is true when you click on a filename.rpm. The actual application that starts when you click on the rpm file is running on your local computer not the share.
Hi michaelk,
What you meant was that the rpm package was not a binary file? If it was, then why I could execute it with noexec option? Thanks for your help!
Not all binary files are executable. Here is another example, a windows word document is a binary file. When you click on it the actual program that starts and runs is word not the file.doc. Once again, its not the rpm file that is running.
FYI an RPM is a collection of files not all binary.
Hi Michaelk,
I understood your meaning that the rpm package was managed by rpm. When you wanted to install the rpm package, actually you ran rpm but not rpm binary package. Was I right? So with noexec options, it would not take effect.
Then I had another question. How can I verify the noexec option which did work? In other words, how could I make the experiment succsessful?
Thanks for your help!
I tried a script made by bash language with noexec option when the shared directory was mounted. But I could exectue the script with right permission (x access).
So I really got confused.
Who could help me
how did you start the script? did you start the script, did you try to call on the script directly or did you use the sh command? Also can you confirm the filesystem has actually been remounted since you made the change to fstab or the machine rebooted.
Last edited by r3sistance; 09-12-2009 at 05:45 AM.
how did you start the script? did you start the script, did you try to call on the script directly or did you use the sh command? Also can you confirm the filesystem has actually been remounted since you made the change to fstab or the machine rebooted.
I did run the script by sh command. But it really could work! Also I used mount command to check the mount status which was noexec.
So strange...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.