ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 00:0c:29:11:f9:cf txqueuelen 1000 (Ethernet)
RX packets 237 bytes 14220 (13.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 3581 bytes 306588 (299.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3581 bytes 306588 (299.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:54:00:b5:cb:83 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
[root@localhost ~]# ifup ens33
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/3)
---------------------------
ls:
DESCRIPTION
List information about the FILEs (the current directory by default). Sort
entries alphabetically if none of -cftuvSUX nor --sort is specified.
Mandatory arguments to long options are mandatory for short options too.
-a, --all
do not ignore entries starting with .
-F, --classify
append indicator (one of */=>@|) to entries
-R, --recursive
list subdirectories recursively
-l use a long listing format
-s, --size
print the allocated size of each file, in blocks
-i, --inode
print the index number of each file
--------------------
touch:
DESCRIPTION
Update the access and modification times of each FILE to the current time.
A FILE argument that does not exist is created empty, unless -c or -h is sup‐
plied.
A FILE argument string of - is handled specially and causes touch to change the
times of the file associated with standard output.
Mandatory arguments to long options are mandatory for short options too.
-t STAMP
use [[CC]YY]MMDDhhmm[.ss] instead of current time
-a change only the access time
-m change only the modification time
---------------
cp:
NAME
cp - copy files and directories
SYNOPSIS
cp [OPTION]... [-T] SOURCE DEST
cp [OPTION]... SOURCE... DIRECTORY
cp [OPTION]... -t DIRECTORY SOURCE...
DESCRIPTION
Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY.
Mandatory arguments to long options are mandatory for short options too.
-p same as --preserve=mode,ownership,timestamps
--preserve[=ATTR_LIST]
preserve the specified attributes (default: mode,ownership,timestamps),
if possible additional attributes: context, links, xattr, all
-R, -r, --recursive
copy directories recursively
-f, --force
if an existing destination file cannot be opened, remove it and try again
(this option is ignored when the -n option is also used)
-n, --no-clobber
do not overwrite an existing file (overrides a previous -i option)
-i, --interactive
prompt before overwrite (overrides a previous -n option)
-l, --link
hard link files instead of copying
-s, --symbolic-link
make symbolic links instead of copying
-------------------------
MV(1) User Commands MV(1)
NAME
mv - move (rename) files
SYNOPSIS
mv [OPTION]... [-T] SOURCE DEST
mv [OPTION]... SOURCE... DIRECTORY
mv [OPTION]... -t DIRECTORY SOURCE...
DESCRIPTION
Rename SOURCE to DEST, or move SOURCE(s) to DIRECTORY.
Mandatory arguments to long options are mandatory for short options too.
---------------
RM(1) User Commands RM(1)
NAME
rm - remove files or directories
SYNOPSIS
rm [OPTION]... FILE...
-i prompt before every removal
DESCRIPTION
This manual page documents the GNU version of rm. rm removes each specified
file. By default, it does not remove directories.
If the -I or --interactive=once option is given, and there are more than three
files or the -r, -R, or --recursive are given, then rm prompts the user for
whether to proceed with the entire operation. If the response is not affirma‐
tive, the entire command is aborted.
Otherwise, if a file is unwritable, standard input is a terminal, and the -f or
--force option is not given, or the -i or --interactive=always option is given,
rm prompts the user for whether to remove the file. If the response is not
affirmative, the file is skipped.
-r, -R, --recursive
remove directories and their contents recursively
-f, --force
ignore nonexistent files and arguments, never prompt
--------------------
RMDIR(1) User Commands RMDIR(1)
NAME
rmdir - remove empty directories
SYNOPSIS
rmdir [OPTION]... DIRECTORY...
DESCRIPTION
Remove the DIRECTORY(ies), if they are empty.
--ignore-fail-on-non-empty
ignore each failure that is solely because a directory
is non-empty
-----------------
STAT(1) User Commands STAT(1)
NAME
stat - display file or file system status
SYNOPSIS
stat [OPTION]... FILE...
DESCRIPTION
Display file or file system status.
Mandatory arguments to long options are mandatory for short options too.
---------------------
file:
NAME
file - determine file type
tests, performed in this order: filesystem tests, magic tests, and language
tests. The first test that succeeds causes the file type to be printed.
The type printed will usually contain one of the words text (the file contains
only printing characters and a few common control characters and is probably safe
to read on an ASCII terminal), executable (the file contains the result of com-
piling a program in a form understandable to some UNIX kernel or another), or
data meaning anything else (data is usually ‘binary’ or non-printable). Excep-
tions are well-known file formats (core files, tar archives) that are known to
contain binary data. When modifying magic files or the program itself, make sure
to preserve these keywords. Users depend on knowing that all the readable files
in a directory have the word ‘text’ printed. Don’t do as Berkeley did and change
‘shell commands text’ to ‘shell script’.
The filesystem tests are based on examining the return from a stat(2) system
call. The program checks to see if the file is empty, or if it’s some sort of
special file. Any known file types appropriate to the system you are running on
(sockets, symbolic links, or named pipes (FIFOs) on those systems that implement
them) are intuited if they are defined in the system header file
The magic tests are used to check for files with data in particular fixed for-
mats. The canonical example of this is a binary executable (compiled program)
a.out file, whose format is defined in #include <a.out.h>
and possibly #include <exec.h>
in the standard include directory. These files have a ‘magic number’ stored in a
particular place near the beginning of the file that tells the UNIX operating
system that the file is a binary executable, and which of several types thereof.
The concept of a ‘magic’ has been applied by extension to data files. Any file
with some invariant identifier at a small fixed offset into the file can usually
be described in this way. The information identifying these files is read from
the compiled magic file /usr/share/misc/magic.mgc, or the files in the directory
/usr/share/misc/magic if the compiled file does not exist. In addition, if
$HOME/.magic.mgc or $HOME/.magic exists, it will be used in preference to the
system magic files. If /etc/magic exists, it will be used together with other
magic files.
If a file does not match any of the entries in the magic file, it is examined to
see if it seems to be a text file. ASCII, ISO-8859-x, non-ISO 8-bit extended-
ASCII character sets (such as those used on Macintosh and IBM PC systems),
UTF-8-encoded Unicode, UTF-16-encoded Unicode, and EBCDIC character sets can be
distinguished by the different ranges and sequences of bytes that constitute
printable text in each set. If a file passes any of these tests, its character
set is reported. ASCII, ISO-8859-x, UTF-8, and extended-ASCII files are identi-
fied as ‘text’ because they will be mostly readable on nearly any terminal;
UTF-16 and EBCDIC are only ‘character data’ because, while they contain text, it
is text that will require translation before it can be read. In addition, file
will attempt to determine other characteristics of text-type files. If the lines
of a file are terminated by CR, CRLF, or NEL, instead of the Unix-standard LF,
this will be reported. Files that contain embedded escape sequences or over-
striking will also be identified.
Once file has determined the character set used in a text-type file, it will
attempt to determine in what language the file is written. The language tests
look for particular strings (cf. #include <names.h>
) that can appear anywhere in the first few blocks of a file. For example, the
keyword .br indicates that the file is most likely a troff(1) input file, just as
the keyword struct indicates a C program. These tests are less reliable than the
previous two groups, so they are performed last. The language test routines also
test for some miscellany (such as tar(1) archives).
Any file that cannot be identified as having been written in any of the character
sets listed above is simply said to be ‘data’.
-----------------
cat:
-n, --number
number all output lines
-s, --squeeze-blank
suppress repeated empty output lines
-t equivalent to -vT
-T, --show-tabs
display TAB characters as ^I
-b, --number-nonblank
number nonempty output lines
------------------
tail:
-f, --follow[={name|descriptor}]
output appended data as the file grows; -f, --follow, and --fol-
low=descriptor are equivalent
-F same as --follow=name --retry
-n, --lines=K
output the last K lines, instead of the last 10; or use -n +K to output
lines starting with the Kth
-c, --bytes=K
output the last K bytes; alternatively, use -c +K to output bytes start-
ing with the Kth of each file
--------------------
ps:
DESCRIPTION
ps displays information about a selection of the active processes. If you want
a repetitive update of the selection and the displayed information, use top(1)
instead.
This version of ps accepts several kinds of options:
1 UNIX options, which may be grouped and must be preceded by a dash.
2 BSD options, which may be grouped and must not be used with a dash.
3 GNU long options, which are preceded by two dashes.
Options of different types may be freely mixed, but conflicts can appear. There
are some synonymous options, which are functionally identical, due to the many
standards and ps implementations that this ps is compatible with.
-A Select all processes. Identical to -e.
-N Select all processes except those that fulfill the specified
conditions. (negates the selection) Identical to --deselect.
-a Select all processes except both session leaders (see
getsid(2)) and processes not associated with a terminal.
-d Select all processes except session leaders.
-C cmdlist Select by command name.
This selects the processes whose executable name is given in
cmdlist.
-G grplist Select by real group ID (RGID) or name.
This selects the processes whose real group name or ID is in
the grplist list. The real group ID identifies the group of the
user who created the process, see getgid(2).
-e Select all processes. Identical to -A.
-U userlist select by real user ID (RUID) or name.
It selects the processes whose real user name or ID is in the
userlist list. The real user ID identifies the user who created
the process, see getuid(2).
-g grplist Select by session OR by effective group name.
Selection by session is specified by many standards, but
selection by effective group is the logical behavior that
several other operating systems use. This ps will select by
session when the list is completely numeric (as sessions are).
Group ID numbers will work only when some group names are also
specified. See the -s and --group options.
-f does full-format listing. This option can be combined with many
other UNIX-style options to add additional columns. It also
causes the command arguments to be printed. When used with -L,
the NLWP (number of threads) and LWP (thread ID) columns will
be added. See the c option, the format keyword args, and the
format keyword comm.
-l long format. The -y option is often useful with this.
-H show process hierarchy (forest)
--forest ASCII art process tree
------------------------