[EMAIL PROTECTED] wrote:
OHHHHH! Then chmod involves an already decompressed file. I wasn't aware of that but I believe it. I knew scanmodem.gz. was a zipped file, but I did not know it had to be uzipped before chmod, whatever it's function, could act upon it. Thanks I will definitely try that.Well, you were trying to run chmod on scanmodem, but the file scanmodem is not the same as scanmodem.gz. So chmod failed. When you uncompress the file using gunzip, it changes the name of the file as part of the process. It normaly restores the origional name of the file. Thus <file>.gz becomes <file>, <file>.tgz becomes <file>.tar, and so on. (While you could have run "chmod +x scanmodem.gz" and it would have worked, it doesn't realy make sence to make a compressed file executable.)
chmode changes the "mode" of the file. While Windows uses the extension of a file to determine if it is executable, Linux uses the mode of the file. And because Linux is designed to be multi-user, you actualy have 3 levels of "mode". You have the mode for the "owner" of the file, the mode for the "group" of the file, and the mode for everyone else. This allows you do do things like have a file that can only be run by the "owner", can be written and read by the "owner", users in the same group as the file, and can be read by everyone.
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
