Same from me, better late than never ... and have a good new year.

Hi,

One more question here...


Since default file permission is 666, how can I make the file to have rwx permission?

Well, if you mean:

rwx------ then just 'chmod 700 file'.

666 = rw-rw-rw-

If you mean you want all the permission bits turned on, then:

chmod 777 file will give you rwxrwxrwx.

Each 3 position permission 'field', rwx, is represented by just one of the digits in 666.

If you mean you want to set umask such that a newly created file is defaulted to rwx------, then.. uh... I'd have to look into that. But, I don't think you want to have that as a default.

Hi,

Sorry for not indicating clearly my query.

What I'm mean is that since the default file permission is 666, and umask is 022. Even if I change umask to 000, permission set for creating new file is still 666. In that case, how can I make the file to be executable once a new file is created? having permission 7?

Well, that's just something you have to figure out on a case by case basis depending on who you want to be allowed to execute the file. You have to come up with whatever it takes to get the x bit set for owner, group, or others.

There are some other options, using u g and o, for setting the permissions, but I haven't gotten around to looking into those yet.

Go back and look at that link to that Introduction to Linux.

You coud aslo cut and paste in here the ls -l output for your file and then the rwxrwxrwx combination you want and we can work from there maybe.

7 is not the execute bit, 7 is the "all" bit. You don't need the "all" bit to execute, you only need execute:
chmod 100

When dealing with permissions you want to set the lowest amount possible to attain your goal. Giving 7 permissions on every file just to execute it is a failure on one's security precautions.

Permissions are there for a reason

As for how your umask of 022 is setting 666 permissions, that's likely happening somewhere else on the system. Look at your /etc/profile and each users bash_profile and bashrc to see if you find any umask=111 (chmod 666). If you are placing these files into a fat32 partition, you will need to look at the umask of the mounting partition. This is more likely your problem(case) than elsewhere. Setting a noexec on a non-linux partition is a security measure again. If you are not the admin of the box, then speak with the administrator to see if they have done something to set a no-exec bit on all files on a given partition/set of files (/etc/profile /etc/fstab and bashrc/bash_profile are a few places to check).

HTH

Cool