我想编写“批处理文件”（shell脚本）的Ubuntu类似物。但是我不知道如何使用命令来使脚本可以运行。我也不知道在哪里使用它。chmod +x filename

简而言之：

chmod +x在文件上（您的脚本）仅意味着您将使其可执行。右键单击脚本，然后选择属性 -> 权限 -> 允许以程序形式执行文件，使您得到与终端命令完全相同的结果。

如果要在其上更改权限的文件位于systems目录中，则可能需要为root，例如：（注意，在使用sudo命令时）

sudo chmod +x /usr/share/testfolder/aFile 

同样不清楚的是，您到底想在这里存档。请编辑您的问题，并提供有关实际问题的更多详细信息！

您还可以参考此问题以获取更多信息：chmod u + x'与'chmod + x

在长：

键入man chmod在终端窗口（Ctrl+ Alt+ T），你会得到以下的输出：

名称： chmod-更改文件模式位

概要

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.

SETUID和SETGID位

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]))+'.

首先，您的脚本必须声明要使用的解释器。您可以在文件的第一行中执行此操作。如果是Shell脚本，则应为#!/bin/sh或#!/bin/bash。

所以这是一个写您的用户名的脚本：echo-whoami.sh

#!/bin/sh echo $(whoami)

要使其可执行，请使用chmod +x echo-whoami.sh。然后，您可以使用运行它./echo-whoami.sh。

一个批处理文件和shell脚本有两个方面有效好心的Linux下的相同。但是，术语“ 脚本”的使用频率更高。

最简单的Shell脚本文件仅包含您在命令行上键入的命令（即Bash命令解释器）。从理论上讲，您甚至可以用您喜欢的任何语言替换解释器（并提供翻译器）。更明确地说，建议您从第一行开始

#!/bin/sh （如果您不希望最大程度地使用旧版系统进行移植）

要么

#!/bin/bash （如果您想要一些额外的功能，那么您今天可能不在乎）

在此行之后，输入命令，每行一个。除此问题的范围外，还有很多其他构造，请参见man bash或http://www.tldp.org/LDP/Bash-Beginners-Guide/Bash-Beginners-Guide.pdf（面向初学者）或http：// www .tldp.org / LDP / abs / abs-guide.pdf（更多高级问题）。

要实际运行脚本，有两个要求：首先，解释器进程需要读取文件，其次，它检查文件是否标记为可执行文件。为了方便起见，能够编写脚本也很有用（因此您可以进行更改或需要进行修复）。

进一步假设您希望团队成员和其他人也能够运行（并查看）您的脚本，但是您不希望他们操纵该脚本，

• 执行所有权限（默认为a+x或），+xa
• 读取所有内容的权限（a+r或+r，a也是默认值），
• 只为您写权限（u=w）

通常是文件权限的合理值。您可以键入串联的单个动作，并用逗号分隔。

尽管这种“动作语言”非常令人着迷（请注意，+和=运算符的不同，这取决于更改权限之前设置的权限而导致不同的结果），但是键入它们很繁琐。

由于所有操作都会创建内部应用的位掩码，因此您也可以直接键入位掩码（man chmod有关详细信息，请参见）。

对于shellscript chmod 755，myscript.sh在至少95％的情况下最有意义。