संक्षेप में:
chmod +xएक फ़ाइल (आपकी स्क्रिप्ट) पर केवल इसका मतलब है, कि आप इसे निष्पादन योग्य बना देंगे। अपनी स्क्रिप्ट पर राइट क्लिक करें और गुण -> अनुमतियाँ -> प्रोग्राम के रूप में फ़ाइल निष्पादित करने की अनुमति दें , आपको टर्मिनल में कमांड के समान सटीक परिणाम के साथ छोड़ देता है।
यदि आप जिस फ़ाइल को अनुमतियों को बदलना चाहते हैं वह सिस्टम निर्देशिका के भीतर स्थित है, तो आपको इसकी आवश्यकता हो सकती है root, जैसे: ( sudoकमांड का उपयोग करते समय सावधान रहें )
sudo chmod +x /usr/share/testfolder/aFile
इसके अलावा यह स्पष्ट नहीं है, कि वास्तव में आप यहां क्या संग्रह करना चाहते हैं। कृपया अपने प्रश्न को संपादित करें और वास्तविक समस्या पर कुछ और विवरण दें!
अधिक जानकारी के लिए आप इस प्रश्न का भी उल्लेख कर सकते हैं: chmod u + x 'बनाम' chmod + x
लंबे समय में:
man chmodएक टर्मिनल विंडो में टाइप करें ( Ctrl+ Alt+ T) और आपको निम्न आउटपुट मिलेगा:
NAME: chmod - फ़ाइल मोड बिट्स बदलें
SYNOPSIS
chmod [OPTION]... MODE[,MODE]... FILE...
chmod [OPTION]... OCTAL-MODE FILE...
chmod [OPTION]... --reference=RFILE FILE...
विवरण
This manual page documents the GNU version of chmod. chmod changes the
file mode bits of each given file according to mode, which can be either
a symbolic representation of changes to make, or an octal number repre‐
senting the bit pattern for the new mode bits.
The format of a symbolic mode is [ugoa...][[+-=][perms...]...], where
perms is either zero or more letters from the set rwxXst, or a single
letter from the set ugo. Multiple symbolic modes can be given, sepa‐
rated by commas.
A combination of the letters ugoa controls which users' access to the
file will be changed: the user who owns it (u), other users in the
file's group (g), other users not in the file's group (o), or all users
(a). If none of these are given, the effect is as if a were given, but
bits that are set in the umask are not affected.
The operator + causes the selected file mode bits to be added to the
existing file mode bits of each file; - causes them to be removed; and =
causes them to be added and causes unmentioned bits to be removed except
that a directory's unmentioned set user and group ID bits are not
affected.
The letters rwxXst select file mode bits for the affected users: read
(r), write (w), execute (or search for directories) (x), execute/search
only if the file is a directory or already has execute permission for
some user (X), set user or group ID on execution (s), restricted dele‐
tion flag or sticky bit (t). Instead of one or more of these letters,
you can specify exactly one of the letters ugo: the permissions granted
to the user who owns the file (u), the permissions granted to other
users who are members of the file's group (g), and the permissions
granted to users that are in neither of the two preceding categories
(o).
A numeric mode is from one to four octal digits (0-7), derived by adding
up the bits with values 4, 2, and 1. Omitted digits are assumed to be
leading zeros. The first digit selects the set user ID (4) and set
group ID (2) and restricted deletion or sticky (1) attributes. The sec‐
ond digit selects permissions for the user who owns the file: read (4),
write (2), and execute (1); the third selects permissions for other
users in the file's group, with the same values; and the fourth for
other users not in the file's group, with the same values.
chmod never changes the permissions of symbolic links; the chmod system
call cannot change their permissions. This is not a problem since the
permissions of symbolic links are never used. However, for each sym‐
bolic link listed on the command line, chmod changes the permissions of
the pointed-to file. In contrast, chmod ignores symbolic links encoun‐
tered during recursive directory traversals.
सेट और सेट बिट्स
chmod clears the set-group-ID bit of a regular file if the file's group
ID does not match the user's effective group ID or one of the user's
supplementary group IDs, unless the user has appropriate privileges.
Additional restrictions may cause the set-user-ID and set-group-ID bits
of MODE or RFILE to be ignored. This behavior depends on the policy and
functionality of the underlying chmod system call. When in doubt, check
the underlying system behavior.
विकल्प
Change the mode of each FILE to MODE.
-c, --changes
like verbose but report only when a change is made
--no-preserve-root
do not treat `/' specially (the default)
--preserve-root
fail to operate recursively on `/'
-f, --silent, --quiet
suppress most error messages
-v, --verbose
output a diagnostic for every file processed
--reference=RFILE
use RFILE's mode instead of MODE values
-R, --recursive
change files and directories recursively
--help display this help and exit
--version
output version information and exit
Each MODE is of the form `[ugoa]*([-+=]([rwxXst]*|[ugo]))+'.