neulab/tldr huggingface dataset:
-o, --oldfile FILE ... Old file mode. Convert file FILE and overwrite output to it. The program defaults to run in this mode. Wildcard names may be used.
In old file (in-place) mode the converted file gets the same owner, group, and read/write permissions as the original file. Also when the file is converted by another user who has write permissions on the file (e.g. user root).  The conversion will be aborted when it is not possible to preserve the original values.  Change of owner could mean that the original owner is not able to read the file any more. Change of group could be a security risk, the file could be made readable for persons for whom it is not intended.  Preservation of owner, group, and read/write permissions is only supported on Unix.
To check if dos2unix has support for preserving the user and group ownership of files type "dos2unix -V".
Conversion is always done via a temporary file. When an error occurs halfway the conversion, the temporary file is deleted and the original file stays intact. When the conversion is successful, the original file is replaced with the temporary file. You may have write permission on the original file, but no permission to put the same user and/or group ownership properties on the temporary file as the original file has. This means you are not able to preserve the user and/or group ownership of the original file. In this case you can use option "--allow-chown" to continue with the conversion:
dos2unix --allow-chown foo.txt
Another option is to use new file mode:
dos2unix -n foo.txt foo.txt
The advantage of the "--allow-chown" option is that you can use wildcards, and the ownership properties will be preserved when possible.
-q, --quiet Quiet mode. Suppress all warnings and messages. The return value is zero.  Except when wrong command-line options are used.
-r, --remove-bom Remove Byte Order Mark (BOM). Do not write a BOM in the output file. This is the default behavior when converting to Unix line breaks. See also option "-b".
-s, --safe Skip binary files (default).
The skipping of binary files is done to avoid accidental mistakes. Be aware that the detection of binary files is not 100% foolproof. Input files are scanned for binary symbols which are typically not found in text files. It is possible that a binary file contains only normal text characters. Such a binary file will mistakenly be seen as a text file.
-u, --keep-utf16 Keep the original UTF-16 encoding of the input file. The output file will be written in the same UTF-16 encoding, little or big endian, as the input file.  This prevents transformation to UTF-8. An UTF-16 BOM will be written accordingly. This option can be disabled with the "-ascii" option.
-ul, --assume-utf16le Assume that the input file format is UTF-16LE.
When there is a Byte Order Mark in the input file the BOM has priority over this option.
When you made a wrong assumption (the input file was not in UTF-16LE format) and the conversion succeeded, you will get an UTF-8 output file with wrong text.  You can undo the wrong conversion with iconv(1) by converting the UTF-8 output file back to UTF-16LE. This will bring back the original file.
The assumption of UTF-16LE works as a conversion mode. By switching to the default ascii mode the UTF-16LE assumption is turned off.
-ub, --assume-utf16be Assume that the input file format is UTF-16BE.
This option works the same as option "-ul".
-v, --verbose Display verbose messages. Extra information is displayed about Byte Order Marks and the amount of converted line breaks.
-F, --follow-symlink Follow symbolic links and convert the targets.
-R, --replace-symlink Replace symbolic links with converted files (original target files remain unchanged).
-S, --skip-symlink Keep symbolic links and targets unchanged (default).
In normal mode line breaks are converted from DOS to Unix and vice versa. Mac line breaks are not converted.
In Mac mode line breaks are converted from Mac to Unix and vice versa. DOS line breaks are not changed.
To run in Mac mode use the command-line option "-c mac" or use the commands "mac2unix" or "unix2mac".
ascii In mode "ascii" only line breaks are converted. This is the default conversion mode.
Although the name of this mode is ASCII, which is a 7 bit standard, the actual mode is 8 bit. Use always this mode when converting Unicode UTF-8 files.
7bit In this mode all 8 bit non-ASCII characters (with values from 128 to 255) are converted to a 7 bit space.
iso Characters are converted between a DOS character set (code page) and ISO character set ISO-8859-1 (Latin-1) on Unix. DOS characters without ISO-8859-1 equivalent, for which conversion is not possible, are converted to a dot. The same counts for ISO-8859-1 characters without DOS counterpart.
When only option "-iso" is used dos2unix will try to determine the active code page. When this is not possible dos2unix will use default code page CP437, which is mainly used in the USA.  To force a specific code page use options "-437" (US), "-850" (Western European), "-860" (Portuguese), "-863" (French Canadian), or "-865" (Nordic).  Windows code page CP1252 (Western European) is also supported with option "-1252". For other code pages use dos2unix in combination with iconv(1).  Iconv can convert between a long list of character encodings.
Never use ISO conversion on Unicode text files. It will corrupt UTF-8 encoded files.
Convert from DOS default code page to Unix Latin-1:
dos2unix -iso -n in.txt out.txt
Convert from DOS CP850 to Unix Latin-1:
dos2unix -850 -n in.txt out.txt
Convert from Windows CP1252 to Unix Latin-1:
dos2unix -1252 -n in.txt out.txt
Convert from Windows CP1252 to Unix UTF-8 (Unicode):
iconv -f CP1252 -t UTF-8 in.txt | dos2unix > out.txt
Convert from Unix Latin-1 to DOS default code page:
unix2dos -iso -n in.txt out.txt
Convert from Unix Latin-1 to DOS CP850:
unix2dos -850 -n in.txt out.txt
Convert from Unix Latin-1 to Windows CP1252:
unix2dos -1252 -n in.txt out.txt
Convert from Unix UTF-8 (Unicode) to Windows CP1252:
unix2dos < in.txt | iconv -f UTF-8 -t CP1252 > out.txt
See also <http://czyborra.com/charsets/codepages.html> and <http://czyborra.com/charsets/iso8859.html>.
Encodings There exist different Unicode encodings. On Unix and Linux Unicode files are typically encoded in UTF-8 encoding. On Windows Unicode text files can be encoded in UTF-8, UTF-16, or UTF-16 big endian, but are mostly encoded in UTF-16 format.
Conversion Unicode text files can have DOS, Unix or Mac line breaks, like regular text files.
All versions of dos2unix and unix2dos can convert UTF-8 encoded files, because UTF-8 was designed for backward compatibility with ASCII.
Dos2unix and unix2dos with Unicode UTF-16 support, can read little and big endian UTF-16 encoded text files. To see if dos2unix was built with UTF-16 support type "dos2unix -V".
On Unix/Linux UTF-16 encoded files are converted to the locale character encoding. Use the locale(1) command to find out what the locale character encoding is. When conversion is not possible a conversion error will occur and the file will be skipped.
On Windows UTF-16 files are by default converted to UTF-8. UTF-8 formatted text files are well supported on both Windows and Unix/Linux.
UTF-16 and UTF-8 encoding are fully compatible, there will no text be lost in the conversion. When an UTF-16 to UTF-8 conversion error occurs, for instance when the UTF-16 input file contains an error, the file will be skipped.
When option "-u" is used, the output file will be written in the same UTF-16 encoding as the input file. Option "-u" prevents conversion to UTF-8.
Dos2unix and unix2dos have no option to convert UTF-8 files to UTF-16.
ISO and 7-bit mode conversion do not work on UTF-16 files.
Byte Order Mark On Windows Unicode text files typically have a Byte Order Mark (BOM), because many Windows programs (including Notepad) add BOMs by default. See also <http://en.wikipedia.org/wiki/Byte_order_mark>.
On Unix Unicode files typically don't have a BOM. It is assumed that text files are encoded in the locale character encoding.
Dos2unix can only detect if a file is in UTF-16 format if the file has a BOM.  When an UTF-16 file doesn't have a BOM, dos2unix will see the file as a binary file.
Use option "-ul" or "-ub" to convert an UTF-16 file without BOM.
Dos2unix writes by default no BOM in the output file. With option "-b" Dos2unix writes a BOM when the input file has a BOM.
Unix2dos writes by default a BOM in the output file when the input file has a BOM. Use option "-r" to remove the BOM.
Dos2unix and unix2dos write always a BOM when option "-m" is used.
Unicode file names on Windows Dos2unix has optional support for reading and writing Unicode file names in the Windows Command Prompt. That means that dos2unix can open files that have characters in the name that are not part of the default system ANSI code page.  To see if dos2unix for Windows was built with Unicode file name support type "dos2unix -V".
There are some issues with displaying Unicode file names in a Windows console.  See option "-D", "--display-enc". The file names may be displayed wrongly in the console, but the files will be written with the correct name.
Unicode examples Convert from Windows UTF-16 (with BOM) to Unix UTF-8:
dos2unix -n in.txt out.txt
Convert from Windows UTF-16LE (without BOM) to Unix UTF-8:
dos2unix -ul -n in.txt out.txt
Convert from Unix UTF-8 to Windows UTF-8 with BOM:
unix2dos -m -n in.txt out.txt
Convert from Unix UTF-8 to Windows UTF-16:
unix2dos < in.txt | iconv -f UTF-8 -t UTF-16 > out.txt
GB18030 GB18030 is a Chinese government standard. A mandatory subset of the GB18030 standard is officially required for all software products sold in China. See also <http://en.wikipedia.org/wiki/GB_18030>.
GB18030 is fully compatible with Unicode, and can be considered an unicode transformation format. Like UTF-8, GB18030 is compatible with ASCII. GB18030 is also compatible with Windows code page 936, also known as GBK.
On Unix/Linux UTF-16 files are converted to GB18030 when the locale encoding is set to GB18030. Note that this will only work if the locale is supported by the system. Use command "locale -a" to get the list of supported locales.
On Windows you need to use option "-gb" to convert UTF-16 files to GB18030.
GB18030 encoded files can have a Byte Order Mark, like Unicode files.
Read input from 'stdin' and write output to 'stdout':
dos2unix < a.txt cat a.txt | dos2unix
Convert and replace a.txt. Convert and replace b.txt:
dos2unix a.txt b.txt dos2unix -o a.txt b.txt
Convert and replace a.txt in ascii conversion mode:
dos2unix a.txt
Convert and replace a.txt in ascii conversion mode, convert and replace b.txt in 7bit conversion mode:
dos2unix a.txt -c 7bit b.txt dos2unix -c ascii a.txt -c 7bit b.txt dos2unix -ascii a.txt -7 b.txt
Convert a.txt from Mac to Unix format:
dos2unix -c mac a.txt mac2unix a.txt
Convert a.txt from Unix to Mac format:
unix2dos -c mac a.txt unix2mac a.txt
Convert and replace a.txt while keeping original date stamp:
dos2unix -k a.txt dos2unix -k -o a.txt
Convert a.txt and write to e.txt:
dos2unix -n a.txt e.txt
Convert a.txt and write to e.txt, keep date stamp of e.txt same as a.txt:
dos2unix -k -n a.txt e.txt
Convert and replace a.txt, convert b.txt and write to e.txt:
dos2unix a.txt -n b.txt e.txt dos2unix -o a.txt -n b.txt e.txt
Convert c.txt and write to e.txt, convert and replace a.txt, convert and replace b.txt, convert d.txt and write to f.txt:
dos2unix -n c.txt e.txt -o a.txt b.txt -n d.txt f.txt
In a Unix shell the find(1) and xargs(1) commands can be used to run dos2unix recursively over all text files in a directory tree. For instance to convert all .txt files in the directory tree under the current directory type:
find . -name '*.txt' -print0 |xargs -0 dos2unix
The find(1) option "-print0" and corresponding xargs(1) option "-0" are needed when there are files with spaces or quotes in the name. Otherwise these options can be omitted. Another option is to use find(1) with the "-exec" option:
find . -name '*.txt' -exec dos2unix {} \;
In a Windows Command Prompt the following command can be used:
for /R %G in (*.txt) do dos2unix "%G"
PowerShell users can use the following command in Windows PowerShell:
get-childitem -path . -filter '*.txt' -recurse | foreach-object {dos2unix $_.Fullname}
LANG The primary language is selected with the environment variable LANG. The LANG variable consists out of several parts. The first part is in small letters the language code. The second is optional and is the country code in capital letters, preceded with an underscore. There is also an optional third part: character encoding, preceded with a dot. A few examples for POSIX standard type shells:
export LANG=nl               Dutch export LANG=nl_NL            Dutch, The Netherlands export LANG=nl_BE            Dutch, Belgium export LANG=es_ES            Spanish, Spain export LANG=es_MX            Spanish, Mexico export LANG=en_US.iso88591   English, USA, Latin-1 encoding export LANG=en_GB.UTF-8      English, UK, UTF-8 encoding
For a complete list of language and country codes see the gettext manual: <http://www.gnu.org/software/gettext/manual/html_node/Usual-Language-Codes.html>
On Unix systems you can use the command locale(1) to get locale specific information.
LANGUAGE With the LANGUAGE environment variable you can specify a priority list of languages, separated by colons. Dos2unix gives preference to LANGUAGE over LANG.  For instance, first Dutch and then German: "LANGUAGE=nl:de". You have to first enable localization, by setting LANG (or LC_ALL) to a value other than "C", before you can use a language priority list through the LANGUAGE variable. See also the gettext manual: <http://www.gnu.org/software/gettext/manual/html_node/The-LANGUAGE-variable.html>
If you select a language which is not available you will get the standard English messages.
DOS2UNIX_LOCALEDIR With the environment variable DOS2UNIX_LOCALEDIR the LOCALEDIR set during compilation can be overruled. LOCALEDIR is used to find the language files. The GNU default value is "/usr/local/share/locale". Option --version will display the LOCALEDIR that is used.
Example (POSIX shell):
export DOS2UNIX_LOCALEDIR=$HOME/share/locale
On success, zero is returned.  When a system error occurs the last system error will be returned. For other errors 1 is returned.
The return value is always zero in quiet mode, except when wrong command- line options are used.
<http://en.wikipedia.org/wiki/Text_file>
<http://en.wikipedia.org/wiki/Carriage_return>
<http://en.wikipedia.org/wiki/Newline>
<http://en.wikipedia.org/wiki/Unicode>
Benjamin Lin - <blin@socs.uts.edu.au>, Bernd Johannes Wuebben (mac2unix mode) - <wuebben@kde.org>, Christian Wurll (add extra newline) - <wurll@ira.uka.de>, Erwin Waterlander - <waterlan@xs4all.nl> (maintainer)
Project page: <http://waterlan.home.xs4all.nl/dos2unix.html>
SourceForge page: <http://sourceforge.net/projects/dos2unix/>
file(1) find(1) iconv(1) locale(1) xargs(1)
DF(1)                             User Commands                            DF(1)
df - report file system space usage
df [OPTION]... [FILE]...
This manual page documents the GNU version of df.  df displays the amount of space available on the file system containing each file name argument. If no file name is given, the space available on all currently mounted file systems is shown.  Space is shown in 1K blocks by default, unless the environment variable POSIXLY_CORRECT is set, in which case 512-byte blocks are used.
If an argument is the absolute file name of a device node containing a mounted file system, df shows the space available on that file system rather than on the file system containing the device node.  This version of df cannot show the space available on unmounted file systems, because on most kinds of systems doing so requires very nonportable intimate knowledge of file system structures.
Show information about the file system on which each FILE resides, or all file systems by default.
-a, --all include pseudo, duplicate, inaccessible file systems
-h, --human-readable print sizes in powers of 1024 (e.g., 1023M)
-H, --si print sizes in powers of 1000 (e.g., 1.1G)
-i, --inodes list inode information instead of block usage
-l, --local limit listing to local file systems
--no-sync do not invoke sync before getting usage info (default)
--output[=FIELD_LIST] use the output format defined by FIELD_LIST, or print all fields if FIELD_LIST is omitted.
-P, --portability use the POSIX output format
--sync invoke sync before getting usage info
--total elide all entries insignificant to available space, and produce a grand total
-t, --type=TYPE limit listing to file systems of type TYPE
-T, --print-type print file system type
-x, --exclude-type=TYPE limit listing to file systems not of type TYPE
-v     (ignored)
Display values are in units of the first available SIZE from --block-size, and the DF_BLOCK_SIZE, BLOCK_SIZE and BLOCKSIZE environment variables.  Otherwise, units default to 1024 bytes (or 512 if POSIXLY_CORRECT is set).
FIELD_LIST is a comma-separated list of columns to be included.  Valid field names are: 'source', 'fstype', 'itotal', 'iused', 'iavail', 'ipcent', 'size', 'used', 'avail', 'pcent', 'file' and 'target' (see info page).
Written by Torbjorn Granlund, David MacKenzie, and Paul Eggert.
Full documentation <https://www.gnu.org/software/coreutils/df> or available locally via: info '(coreutils) df invocation'
gh-pr - Manage pull requests
gh pr <command> [flags]
Work with GitHub pull requests
$ gh pr checkout 353 $ gh pr create --fill $ gh pr view --web
gh(1), gh-pr-checkout(1), gh-pr-checks(1), gh-pr-close(1), gh-pr- comment(1), gh-pr-create(1), gh-pr-diff(1), gh-pr-edit(1), gh-pr-list(1), gh-pr-merge(1), gh-pr-ready(1), gh-pr-reopen(1), gh-pr-review(1), gh-pr- status(1), gh-pr-view(1)
SCC(4)                    BSD Kernel Interfaces Manual                    SCC(4)
scc — driver for Serial Communications Controllers (SCC) devices
device scc device uart
The scc device driver provides support for various classes of SCCs.  It is an umbrella driver that delegates control of each independent communication channel to subordinate drivers.  These subordinate drivers, like uart(4), take care of the details of the communication itself.
The scc driver supports the following classes of SCCs:
•   SAB82532: Siemens SAB 82532 based serial communications controllers. •   Z8530: Zilog 8530 based serial communications controllers.
puc(4), uart(4)
The scc device driver first appeared in FreeBSD 7.0.
The scc driver and this manual page were written by Marcel Moolenaar <marcel@xcllnt.net>.
lxc(7)                                                                    lxc(7)
lxc - linux containers
The container technology is actively being pushed into the mainstream Linux kernel. It provides resource management through control groups and resource isolation via namespaces.
lxc, aims to use these new functionalities to provide a userspace container object which provides full resource isolation and resource control for an applications or a full system.
lxc is small enough to easily manage a container with simple command lines and complete enough to be used for other purposes.
The kernel version >= 3.10 shipped with the distros, will work with lxc, this one will have less functionalities but enough to be interesting.
lxc relies on a set of functionalities provided by the kernel. The helper script lxc-checkconfig will give you information about your kernel configuration, required, and missing features.
A container is an object isolating some resources of the host, for the application or system running in it.
The application / system will be launched inside a container specified by a configuration that is either initially created or passed as a parameter of the commands.
How to run an application in a container
Before running an application, you should know what are the resources you want to isolate. The default configuration is to isolate PIDs, the sysv IPC and mount points. If you want to run a simple shell inside a container, a basic configuration is needed, especially if you want to share the rootfs. If you want to run an application like sshd, you should provide a new network stack and a new hostname. If you want to avoid conflicts with some files eg.  /var/run/httpd.pid, you should remount /var/run with an empty directory. If you want to avoid the conflicts in all the cases, you can specify a rootfs for the container. The rootfs can be a directory tree, previously bind mounted with the initial rootfs, so you can still use your distro but with your own /etc and /home
Here is an example of directory tree for sshd:
[root@lxc sshd]$ tree -d rootfs
rootfs |-- bin |-- dev |   |-- pts |   `-- shm |       `-- network |-- etc |   `-- ssh |-- lib |-- proc |-- root |-- sbin |-- sys |-- usr `-- var |-- empty |   `-- sshd |-- lib |   `-- empty |       `-- sshd `-- run `-- sshd
and the mount points file associated with it:
[root@lxc sshd]$ cat fstab
/lib /home/root/sshd/rootfs/lib none ro,bind 0 0 /bin /home/root/sshd/rootfs/bin none ro,bind 0 0 /usr /home/root/sshd/rootfs/usr none ro,bind 0 0 /sbin /home/root/sshd/rootfs/sbin none ro,bind 0 0
How to run a system in a container
Running a system inside a container is paradoxically easier than running an application. Why? Because you don't have to care about the resources to be isolated, everything needs to be isolated, the other resources are specified as being isolated but without configuration because the container will set them up. eg. the ipv4 address will be setup by the system container init scripts. Here is an example of the mount points file:
[root@lxc debian]$ cat fstab
/dev /home/root/debian/rootfs/dev none bind 0 0 /dev/pts /home/root/debian/rootfs/dev/pts  none bind 0 0
CONTAINER LIFE CYCLE When the container is created, it contains the configuration information. When a process is launched, the container will be starting and running. When the last process running inside the container exits, the container is stopped.
In case of failure when the container is initialized, it will pass through the aborting state.
--------- | STOPPED |<--------------- ---------                 | |                     | start                   | |                     | V                     | ----------                | | STARTING |--error-       | ----------         |      | |              |      | V              V      | ---------    ----------   | | RUNNING |  | ABORTING |  | ---------    ----------   | |              |      | no process          |      | |              |      | V              |      | ----------         |      | | STOPPING |<-------       | ----------                | |                     | ---------------------
CONFIGURATION The container is configured through a configuration file, the format of the configuration file is described in lxc.conf(5)
CREATING / DESTROYING CONTAINERS A persistent container object can be created via the lxc-create command. It takes a container name as parameter and optional configuration file and template. The name is used by the different commands to refer to this container. The lxc-destroy command will destroy the container object.
lxc-create -n foo lxc-destroy -n foo
VOLATILE CONTAINER It is not mandatory to create a container object before starting it.  The container can be directly started with a configuration file as parameter.
STARTING / STOPPING CONTAINER When the container has been created, it is ready to run an application / system. This is the purpose of the lxc-execute and lxc-start commands. If the container was not created before starting the application, the container will use the configuration file passed as parameter to the command, and if there is no such parameter either, then it will use a default isolation. If the application ended, the container will be stopped, but if needed the lxc-stop command can be used to stop the container.
Running an application inside a container is not exactly the same thing as running a system. For this reason, there are two different commands to run an application into a container:
lxc-execute -n foo [-f config] /bin/bash lxc-start -n foo [-f config] [/bin/bash]
The lxc-execute command will run the specified command into a container via an intermediate process, lxc-init.  This lxc-init after launching the specified command, will wait for its end and all other reparented processes. (to support daemons in the container). In other words, in the container, lxc-init has PID 1 and the first process of the application has PID 2.
The lxc-start command will directly run the specified command in the container. The PID of the first process is 1. If no command is specified lxc-start will run the command defined in lxc.init.cmd or if not set, /sbin/init .
To summarize, lxc-execute is for running an application and lxc-start is better suited for running a system.
If the application is no longer responding, is inaccessible or is not able to finish by itself, a wild lxc-stop command will kill all the processes in the container without pity.
lxc-stop -n foo -k
CONNECT TO AN AVAILABLE TTY If the container is configured with ttys, it is possible to access it through them. It is up to the container to provide a set of available ttys to be used by the following command. When the tty is lost, it is possible to reconnect to it without login again.
lxc-console -n foo -t 3
FREEZE / UNFREEZE CONTAINER Sometime, it is useful to stop all the processes belonging to a container, eg. for job scheduling. The commands:
lxc-freeze -n foo
will put all the processes in an uninteruptible state and
lxc-unfreeze -n foo
will resume them.
This feature is enabled if the freezer cgroup v1 controller is enabled in the kernel.
GETTING INFORMATION ABOUT CONTAINER When there are a lot of containers, it is hard to follow what has been created or destroyed, what is running or what are the PIDs running in a specific container. For this reason, the following commands may be useful:
lxc-ls -f lxc-info -n foo
lxc-ls lists containers.
lxc-info gives information for a specific container.
Here is an example on how the combination of these commands allows one to list all the containers and retrieve their state.
for i in $(lxc-ls -1); do lxc-info -n $i done
MONITORING CONTAINER It is sometime useful to track the states of a container, for example to monitor it or just to wait for a specific state in a script.
lxc-monitor command will monitor one or several containers. The parameter of this command accepts a regular expression for example:
lxc-monitor -n "foo|bar"
will monitor the states of containers named 'foo' and 'bar', and:
lxc-monitor -n ".*"
will monitor all the containers.
For a container 'foo' starting, doing some work and exiting, the output will be in the form:
'foo' changed state to [STARTING] 'foo' changed state to [RUNNING] 'foo' changed state to [STOPPING] 'foo' changed state to [STOPPED]
lxc-wait command will wait for a specific state change and exit. This is useful for scripting to synchronize the launch of a container or the end. The parameter is an ORed combination of different states. The following example shows how to wait for a container if it successfully started as a daemon.
# launch lxc-wait in background lxc-wait -n foo -s STOPPED & LXC_WAIT_PID=$!
# this command goes in background lxc-execute -n foo mydaemon &
# block until the lxc-wait exits # and lxc-wait exits when the container # is STOPPED wait $LXC_WAIT_PID echo "'foo' is finished"
CGROUP SETTINGS FOR CONTAINERS The container is tied with the control groups, when a container is started a control group is created and associated with it. The control group properties can be read and modified when the container is running by using the lxc-cgroup command.
lxc-cgroup command is used to set or get a control group subsystem which is associated with a container. The subsystem name is handled by the user, the command won't do any syntax checking on the subsystem name, if the subsystem name does not exists, the command will fail.
lxc-cgroup -n foo cpuset.cpus
will display the content of this subsystem.
lxc-cgroup -n foo cpu.shares 512
will set the subsystem to the specified value.
lxc(7), lxc-create(1), lxc-copy(1), lxc-destroy(1), lxc-start(1), lxc- stop(1), lxc-execute(1), lxc-console(1), lxc-monitor(1), lxc-wait(1), lxc-cgroup(1), lxc-ls(1), lxc-info(1), lxc-freeze(1), lxc-unfreeze(1), lxc-attach(1), lxc.conf(5)
Daniel Lezcano <daniel.lezcano@free.fr>
Christian Brauner <christian.brauner@ubuntu.com>
Serge Hallyn <serge@hallyn.com>
StÃ©phane Graber <stgraber@ubuntu.com>
SNMPWALK(1)                         Net-SNMP                         SNMPWALK(1)
snmpwalk - retrieve a subtree of management values using SNMP GETNEXT requests
snmpwalk [APPLICATION OPTIONS] [COMMON OPTIONS] AGENT [OID]
snmpwalk is an SNMP application that uses SNMP GETNEXT requests to query a network entity for a tree of information.
An object identifier (OID) may be given on the command line.  This OID specifies which portion of the object identifier space will be searched using GETNEXT requests.  All variables in the subtree below the given OID are queried and their values presented to the user.  Each variable name is given in the format specified in variables(5).
If no OID argument is present, snmpwalk will search the subtree rooted at SNMPv2-SMI::mib-2 (including any MIB object values from other MIB modules, that are defined as lying within this subtree).  If the network entity has an error processing the request packet, an error packet will be returned and a message will be shown, helping to pinpoint why the request was malformed.
If the tree search causes attempts to search beyond the end of the MIB, the message "End of MIB" will be displayed.
-Cc     Do not check whether the returned OIDs are increasing.  Some agents (LaserJets are an example) return OIDs out of order, but can complete the walk anyway.  Other agents return OIDs that are out of order and can cause snmpwalk to loop indefinitely.  By default, snmpwalk tries to detect this behavior and warns you when it hits an agent acting illegally.  Use -Cc to turn off this check.
-CE {OID} End the walk at the specified OID, rather than a simple subtree. This can be used to walk a partial subtree, selected columns of a table, or even two or more tables within a single command.
-Ci     Include the given OID in the search range.  Normally snmpwalk uses GETNEXT requests starting with the OID you specified and returns all results in the MIB subtree rooted at that OID. Sometimes, you may wish to include the OID specified on the command line in the printed results if it is a valid OID in the tree itself.  This option lets you do this explicitly.
-CI     In fact, the given OID will be retrieved automatically if the main subtree walk returns no useable values.  This allows a walk of a single instance to behave as generally expected, and return the specified instance value.  This option turns off this final GET request, so a walk of a single instance will return nothing.
-Cp     Upon completion of the walk, print the number of variables found.
-Ct     Upon completion of the walk, print the total wall-clock time it took to collect the data (in seconds).  Note that the timer is started just before the beginning of the data request series and stopped just after it finishes.  Most importantly, this means that it does not include snmp library initialization, shutdown, argument processing, and any other overhead.
In addition to these options, snmpwalk takes the common options described in the snmpcmd(1) manual page.
Note that snmpwalk REQUIRES  an argument specifying the agent to query and at most one OID argument, as described there.  The command:
snmpwalk -Os -c public -v 1 zeus system
will retrieve all of the variables under system:
sysDescr.0 = STRING: "SunOS zeus.net.cmu.edu 4.1.3_U1 1 sun4m" sysObjectID.0 = OID: enterprises.hp.nm.hpsystem.10.1.1 sysUpTime.0 = Timeticks: (155274552) 17 days, 23:19:05 sysContact.0 = STRING: "" sysName.0 = STRING: "zeus.net.cmu.edu" sysLocation.0 = STRING: "" sysServices.0 = INTEGER: 72 (plus the contents of the sysORTable).
snmpwalk -Os -c public -v 1 -CE sysORTable zeus system
will retrieve the scalar values, but omit the sysORTable.
snmpcmd(1), snmpbulkwalk(1), variables(5).
GIT-SHOW-INDEX(1)                  Git Manual                  GIT-SHOW-INDEX(1)
git-show-index - Show packed archive index
git show-index [--object-format=<hash-algorithm>]
Read the .idx file for a Git packfile (created with git-pack-objects(1) or git-index-pack(1)) from the standard input, and dump its contents. The output consists of one object per line, with each line containing two or three space-separated columns:
•   the first column is the offset in bytes of the object within the corresponding packfile
•   the second column is the object id of the object
•   if the index version is 2 or higher, the third column contains the CRC32 of the object data
The objects are output in the order in which they are found in the index file, which should be (in a correctly constructed file) sorted by object id.
Note that you can get more information on a packfile by calling git- verify-pack(1). However, as this command considers only the index file itself, it’s both faster and more flexible.
--object-format=<hash-algorithm> Specify the given object format (hash algorithm) for the index file. The valid values are sha1 and (if enabled) sha256. The default is the algorithm for the current repository (set by extensions.objectFormat), or sha1 if no value is set or outside a repository..
HYDRA(1)                     General Commands Manual                    HYDRA(1)
hydra - a very fast network logon cracker which supports many different services
hydra [[[-l LOGIN|-L FILE] [-p PASS|-P FILE|-x OPT -y]] | [-C FILE]] [-e nsr] [-u] [-f|-F] [-M FILE] [-o FILE] [-b FORMAT] [-t TASKS] [-T TASKS] [-w TIME] [-W TIME] [-m OPTIONS] [-s PORT] [-c TIME] [-S] [-O] [-4|6] [-I] [-vV] [-d] server service [OPTIONS]
Hydra is a parallelized login cracker which supports numerous protocols to attack. New modules are easy to add, beside that, it is flexible and very fast.
This tool gives researchers and security consultants the possibility to show how easy it would be to gain unauthorized access from remote to a system.
Currently this tool supports: adam6500 afp asterisk cisco cisco-enable cvs firebird ftp ftps http[s]-{head|get|post} http[s]-{get|post}-form http-proxy http- proxy-urlenum icq imap[s] irc ldap2[s] ldap3[-{cram|digest}md5][s] mssql mysql(v4) mysql5 ncp nntp oracle oracle-listener oracle-sid pcanywhere pcnfs pop3[s] postgres rdp radmin2 redis rexec rlogin rpcap rsh rtsp s7-300 sapr3 sip smb smtp[s] smtp-enum snmp socks5 ssh sshkey svn teamspeak telnet[s] vmauthd vnc xmpp
For most protocols SSL is supported (e.g. https-get, ftp-ssl, etc.).  If not all necessary libraries are found during compile time, your available services will be less.  Type "hydra" to see what is available.
Options target a target to attack, can be an IPv4 address, IPv6 address or DNS name.
service a service to attack, see the list of protocols available
OPTIONAL SERVICE PARAMETER Some modules have optional or mandatory options. type "hydra -U <servicename>" to get help on on the options of a service.
-R     restore a previously aborted session. Requires a hydra.restore file was written. Options are restored, but can be changed by setting them after -R on the command line
-S     connect via SSL
-O     use old SSL v2 and v3
-s PORT if the service is on a different default port, define it here
-l LOGIN or -L FILE login with LOGIN name, or load several logins from FILE
-p PASS or -P FILE try password PASS, or load several passwords from FILE
-x min:max:charset generate passwords from min to max length. charset can contain 1 for numbers, a for lowcase and A for upcase characters. Any other character is added is put to the list. Example: 1:2:a1%. The generated passwords will be of length 1 to 2 and contain lowcase letters, numbers and/or percent signs and dots.
-y     disable use of symbols in -x bruteforce, see above
-e nsr additional checks, "n" for null password, "s" try login as pass, "r" try the reverse login as pass
-C FILE colon separated "login:pass" format, instead of -L/-P options
-u     by default Hydra checks all passwords for one login and then tries the next login. This option loops around the passwords, so the first password is tried on all logins, then the next password.
-f     exit after the first found login/password pair (per host if -M)
-F     exit after the first found login/password pair for any host (for usage with -M)
-M FILE server list for parallel attacks, one entry per line
-o FILE write found login/password pairs to FILE instead of stdout
-b FORMAT specify the format for the -o FILE: text(default), json, jsonv1
-t TASKS run TASKS number of connects in parallel (default: 16)
-m OPTIONS module specific options. See hydra -U <module> what options are available.
-w TIME defines the max wait time in seconds for responses (default: 32)
-W TIME defines a wait time between each connection a task performs. This usually only makes sense if a low task number is used, .e.g -t 1
-c TIME the wait time in seconds per login attempt over all threads (-t 1 is recommended) This usually only makes sense if a low task number is used, .e.g -t 1
-4 / -6 prefer IPv4 (default) or IPv6 addresses
-v / -V verbose mode / show login+pass combination for each attempt
-d     debug mode
-I     ignore an existing restore file (don't wait 10 seconds)
xhydra(1), pw-inspector(1). The programs are documented fully by van Hauser <vh@thc.org>
hydra was written by van Hauser / THC <vh@thc.org> Find new versions or report bugs at https://github.com/vanhauser-thc/thc-hydra
This manual page was written by Daniel Echeverry <epsilon77@gmail.com>, for the Debian project (and may be used by others).
QJOYPAD(1)                   General Commands Manual                  QJOYPAD(1)
qjoypad - Program for mapping gamepad/joystick events to mouse/keyboard events
qjoypad [--device "/device/path"] [--notray] ["layout name"]
Program for mapping gamepad/joystick events to mouse/keyboard events
--device Look for joystick devices in "path". This should be something like "/dev/input" if your game devices are in /dev/input/js0, /dev/input/js1, etc.
--notray Do not use a system tray icon. This is useful for window managers that don't support this feature.
--update Force a running instance of QJoyPad to update its list of devices and layouts.
"layout name" Load the given layout in an already running instance of QJoyPad, or start QJoyPad using the given layout.
GIT-CHERRY-PICK(1)                 Git Manual                 GIT-CHERRY-PICK(1)
git-cherry-pick - Apply the changes introduced by some existing commits
git cherry-pick [--edit] [-n] [-m parent-number] [-s] [-x] [--ff] [-S[<keyid>]] <commit>... git cherry-pick (--continue | --skip | --abort | --quit)
Given one or more existing commits, apply the change each one introduces, recording a new commit for each. This requires your working tree to be clean (no modifications from the HEAD commit).
When it is not obvious how to apply a change, the following happens:
1. The current branch and HEAD pointer stay at the last commit successfully made.
2. The CHERRY_PICK_HEAD ref is set to point at the commit that introduced the change that is difficult to apply.
3. Paths in which the change applied cleanly are updated both in the index file and in your working tree.
4. For conflicting paths, the index file records up to three versions, as described in the "TRUE MERGE" section of git-merge(1). The working tree files will include a description of the conflict bracketed by the usual conflict markers <<<<<<< and >>>>>>>.
5. No other modifications are made.
See git-merge(1) for some hints on resolving such conflicts.
<commit>... Commits to cherry-pick. For a more complete list of ways to spell commits, see gitrevisions(7). Sets of commits can be passed but no traversal is done by default, as if the --no-walk option was specified, see git-rev-list(1). Note that specifying a range will feed all <commit>... arguments to a single revision walk (see a later example that uses maint master..next).
-e, --edit With this option, git cherry-pick will let you edit the commit message prior to committing.
-x When recording the commit, append a line that says "(cherry picked from commit ...)" to the original commit message in order to indicate which commit this change was cherry-picked from. This is done only for cherry picks without conflicts. Do not use this option if you are cherry-picking from your private branch because the information is useless to the recipient. If on the other hand you are cherry-picking between two publicly visible branches (e.g. backporting a fix to a maintenance branch for an older release from a development branch), adding this information can be useful.
-r It used to be that the command defaulted to do -x described above, and -r was to disable it. Now the default is not to do -x so this option is a no-op.
-m parent-number, --mainline parent-number Usually you cannot cherry-pick a merge because you do not know which side of the merge should be considered the mainline. This option specifies the parent number (starting from 1) of the mainline and allows cherry-pick to replay the change relative to the specified parent.
-n, --no-commit Usually the command automatically creates a sequence of commits. This flag applies the changes necessary to cherry-pick each named commit to your working tree and the index, without making any commit. In addition, when this option is used, your index does not have to match the HEAD commit. The cherry-pick is done against the beginning state of your index.
This is useful when cherry-picking more than one commits' effect to your index in a row.
--ff If the current HEAD is the same as the parent of the cherry-pickâ€™ed commit, then a fast forward to this commit will be performed.
--allow-empty By default, cherry-picking an empty commit will fail, indicating that an explicit invocation of git commit --allow-empty is required. This option overrides that behavior, allowing empty commits to be preserved automatically in a cherry-pick. Note that when "--ff" is in effect, empty commits that meet the "fast-forward" requirement will be kept even without this option. Note also, that use of this option only keeps commits that were initially empty (i.e. the commit recorded the same tree as its parent). Commits which are made empty due to a previous commit are dropped. To force the inclusion of those commits use --keep-redundant-commits.
--allow-empty-message By default, cherry-picking a commit with an empty message will fail. This option overrides that behavior, allowing commits with empty messages to be cherry picked.
--keep-redundant-commits If a commit being cherry picked duplicates a commit already in the current history, it will become empty. By default these redundant commits cause cherry-pick to stop so the user can examine the commit. This option overrides that behavior and creates an empty commit object. Implies --allow-empty.
git cherry-pick master Apply the change introduced by the commit at the tip of the master branch and create a new commit with this change.
git cherry-pick ..master, git cherry-pick ^HEAD master Apply the changes introduced by all commits that are ancestors of master but not of HEAD to produce new commits.
git cherry-pick maint next ^master, git cherry-pick maint master..next Apply the changes introduced by all commits that are ancestors of maint or next, but not master or any of its ancestors. Note that the latter does not mean maint and everything between master and next; specifically, maint will not be used if it is included in master.
git cherry-pick master~4 master~2 Apply the changes introduced by the fifth and third last commits pointed to by master and create 2 new commits with these changes.
git cherry-pick -n master~1 next Apply to the working tree and the index the changes introduced by the second last commit pointed to by master and by the last commit pointed to by next, but do not create any commit with these changes.
git cherry-pick --ff ..next If history is linear and HEAD is an ancestor of next, update the working tree and advance the HEAD pointer to match next. Otherwise, apply the changes introduced by those commits that are in next but not HEAD to the current branch, creating a new commit for each new change.
git rev-list --reverse master -- README | git cherry-pick -n --stdin Apply the changes introduced by all commits on the master branch that touched README to the working tree and index, so the result can be inspected and made into a single new commit if suitable.
The following sequence attempts to backport a patch, bails out because the code the patch applies to has changed too much, and then tries again, this time exercising more care about matching up context lines.
$ git cherry-pick topic^             (1) $ git diff                           (2) $ git reset --merge ORIG_HEAD        (3) $ git cherry-pick -Xpatience topic^  (4)
1. apply the change that would be shown by git show topic^. In this example, the patch does not apply cleanly, so information about the conflict is written to the index and working tree and no new commit results. 2. summarize changes to be reconciled 3. cancel the cherry-pick. In other words, return to the pre-cherry-pick state, preserving any local modifications you had in the working tree. 4. try to apply the change introduced by topic^ again, spending extra time to avoid mistakes based on incorrectly matching context lines.
git-revert(1)
pdftotext(1)                 General Commands Manual                pdftotext(1)
pdftotext - Portable Document Format (PDF) to text converter (version 3.03)
pdftotext [options] [PDF-file [text-file]]
Pdftotext converts Portable Document Format (PDF) files to plain text.
Pdftotext reads the PDF file, PDF-file, and writes a text file, text- file.  If text-file is not specified, pdftotext converts file.pdf to file.txt.  If text-file is ´-', the text is sent to stdout.  If PDF-file is ´-', it reads the PDF file from stdin.
-r number Specifies the resolution, in DPI.  The default is 72 DPI.
-x number Specifies the x-coordinate of the crop area top left corner
-y number Specifies the y-coordinate of the crop area top left corner
-W number Specifies the width of crop area in pixels (default is 0)
-H number Specifies the height of crop area in pixels (default is 0)
-layout Maintain (as best as possible) the original physical layout of the text.  The default is to ´undo' physical layout (columns, hyphenation, etc.) and output the text in reading order.
-fixed number Assume fixed-pitch (or tabular) text, with the specified character width (in points).  This forces physical layout mode.
-raw   Keep the text in content stream order.  This is a hack which often "undoes" column formatting, etc.  Use of raw mode is no longer recommended.
-nodiag Discard diagonal text (i.e., text that is not close to one of the 0, 90, 180, or 270 degree axes). This is useful for skipping watermarks drawn on body text.
-htmlmeta Generate a simple HTML file, including the meta information.  This simply wraps the text in <pre> and </pre> and prepends the meta headers.
-bbox  Generate an XHTML file containing bounding box information for each word in the file.
-bbox-layout Generate an XHTML file containing bounding box information for each block, line, and word in the file.
-cropbox Use the crop box rather than the media box with -bbox and -bbox- layout.
-enc encoding-name Sets the encoding to use for text output. This defaults to "UTF-8".
-listenc Lists the available encodings
-eol unix | dos | mac Sets the end-of-line convention to use for text output.
-nopgbrk Don't insert page breaks (form feed characters) between pages.
Some PDF files contain fonts whose encodings have been mangled beyond recognition.  There is no way (short of OCR) to extract text from these files.
The Xpdf tools use the following exit codes:
The pdftotext software and documentation are copyright 1996-2011 Glyph & Cog, LLC.
pdfdetach(1), pdffonts(1), pdfimages(1), pdfinfo(1), pdftocairo(1), pdftohtml(1), pdftoppm(1), pdftops(1), pdfseparate(1), pdfsig(1), pdfunite(1)
Nautilus(1)                  General Commands Manual                 Nautilus(1)
nautilus - a file manager for GNOME
nautilus [options] URIs...
nautilus is a file manager, designed for the GNOME 3 desktop.
-c, --check Perform a quick set of self-check tests.
--version Show the version of the program.
-w, --new-window Always open a new window for browsing specified URIs.
-q, --quit Quit Nautilus.
-s, --select Select specified URI in parent folder.
-h, --help Show a summary of options.