neulab/tldr huggingface dataset:
<zsh-announce-subscribe@zsh.org> <zsh-users-subscribe@zsh.org> <zsh-workers-subscribe@zsh.org> <zsh-announce-unsubscribe@zsh.org> <zsh-users-unsubscribe@zsh.org> <zsh-workers-unsubscribe@zsh.org>
YOU ONLY NEED TO JOIN ONE OF THE MAILING LISTS AS THEY ARE NESTED.  All submissions to zsh-announce are automatically forwarded to zsh-users. All submissions to zsh-users are automatically forwarded to zsh-workers.
If you have problems subscribing/unsubscribing to any of the mailing lists, send mail to <listmaster@zsh.org>.  The mailing lists are maintained by Karsten Thygesen <karthy@kom.auc.dk>.
The mailing lists are archived; the archives can be accessed via the administrative addresses listed above.  There is also a hypertext archive, maintained by Geoff Wing <gcw@zsh.org>, available at https://www.zsh.org/mla/.
Zsh has a list of Frequently Asked Questions (FAQ), maintained by Peter Stephenson <pws@zsh.org>.  It is regularly posted to the newsgroup comp.unix.shell and the zsh-announce mailing list.  The latest version can be found at any of the Zsh FTP sites, or at http://www.zsh.org/FAQ/. The contact address for FAQ-related matters is <faqmaster@zsh.org>.
Zsh has a web page which is located at https://www.zsh.org/.  This is maintained by Karsten Thygesen <karthy@zsh.org>, of SunSITE Denmark.  The contact address for web-related matters is <webmaster@zsh.org>.
A userguide is currently in preparation.  It is intended to complement the manual, with explanations and hints on issues where the manual can be cabbalistic, hierographic, or downright mystifying (for example, the word `hierographic' does not exist).  It can be viewed in its current state at http://zsh.sourceforge.net/Guide/.  At the time of writing, chapters dealing with startup files and their contents and the new completion system were essentially complete.
The following flags are interpreted by the shell when invoked to determine where the shell will read commands from:
-c     Take the first argument as a command to execute, rather than reading commands from a script or standard input.  If any further arguments are given, the first one is assigned to $0, rather than being used as a positional parameter.
-i     Force shell to be interactive.  It is still possible to specify a script to execute.
-s     Force shell to read commands from the standard input.  If the -s flag is not present and an argument is given, the first argument is taken to be the pathname of a script to execute.
If there are any remaining arguments after option processing, and neither of the options -c or -s was supplied, the first argument is taken as the file name of a script containing shell commands to be executed.  If the option PATH_SCRIPT is set, and the file name does not contain a directory path (i.e. there is no `/' in the name), first the current directory and then the command path given by the variable PATH are searched for the script.  If the option is not set or the file name contains a `/' it is used directly.
After the first one or two arguments have been appropriated as described above, the remaining arguments are assigned to the positional parameters.
For further options, which are common to invocation and the set builtin, see zshoptions(1).
The long option `--emulate' followed (in a separate word) by an emulation mode may be passed to the shell.  The emulation modes are those described for the emulate builtin, see zshbuiltins(1).  The `--emulate' option must precede any other options (which might otherwise be overridden), but following options are honoured, so may be used to modify the requested emulation mode.  Note that certain extra steps are taken to ensure a smooth emulation when this option is used compared with the emulate command within the shell: for example, variables that conflict with POSIX usage such as path are not defined within the shell.
Options may be specified by name using the -o option.  -o acts like a single-letter option, but takes a following string as the option name. For example,
zsh -x -o shwordsplit scr
runs the script scr, setting the XTRACE option by the corresponding letter `-x' and the SH_WORD_SPLIT option by name.  Options may be turned off by name by using +o instead of -o.  -o can be stacked up with preceding single-letter options, so for example `-xo shwordsplit' or `-xoshwordsplit' is equivalent to `-x -o shwordsplit'.
Options may also be specified by name in GNU long option style, `--option-name'.  When this is done, `-' characters in the option name are permitted: they are translated into `_', and thus ignored.  So, for example, `zsh --sh-word-split' invokes zsh with the SH_WORD_SPLIT option turned on.  Like other option syntaxes, options can be turned off by replacing the initial `-' with a `+'; thus `+-sh-word-split' is equivalent to `--no-sh-word-split'.  Unlike other option syntaxes, GNU-style long options cannot be stacked with any other options, so for example `-x-shwordsplit' is an error, rather than being treated like `-x --shwordsplit'.
The special GNU-style option `--version' is handled; it sends to standard output the shell's version information, then exits successfully. `--help' is also handled; it sends to standard output a list of options that can be used when invoking the shell, then exits successfully.
Option processing may be finished, allowing following arguments that start with `-' or `+' to be treated as normal arguments, in two ways. Firstly, a lone `-' (or `+') as an argument by itself ends option processing.  Secondly, a special option `--' (or `+-'), which may be specified on its own (which is the standard POSIX usage) or may be stacked with preceding options (so `-x-' is equivalent to `-x --'). Options are not permitted to be stacked after `--' (so `-x-f' is an error), but note the GNU-style option form discussed above, where `--shwordsplit' is permitted and does not end option processing.
Except when the sh/ksh emulation single-letter options are in effect, the option `-b' (or `+b') ends option processing.  `-b' is like `--', except that further single-letter options can be stacked after the `-b' and will take effect as normal.
Zsh tries to emulate sh or ksh when it is invoked as sh or ksh respectively; more precisely, it looks at the first letter of the name by which it was invoked, excluding any initial `r' (assumed to stand for `restricted'), and if that is `b', `s' or `k' it will emulate sh or ksh. Furthermore, if invoked as su (which happens on certain systems when the shell is executed by the su command), the shell will try to find an alternative name from the SHELL environment variable and perform emulation based on that.
In sh and ksh compatibility modes the following parameters are not special and not initialized by the shell: ARGC, argv, cdpath, fignore, fpath, HISTCHARS, mailpath, MANPATH, manpath, path, prompt, PROMPT, PROMPT2, PROMPT3, PROMPT4, psvar, status, watch.
The usual zsh startup/shutdown scripts are not executed.  Login shells source /etc/profile followed by $HOME/.profile.  If the ENV environment variable is set on invocation, $ENV is sourced after the profile scripts. The value of ENV is subjected to parameter expansion, command substitution, and arithmetic expansion before being interpreted as a pathname.  Note that the PRIVILEGED option also affects the execution of startup files.
The following options are set if the shell is invoked as sh or ksh: NO_BAD_PATTERN, NO_BANG_HIST, NO_BG_NICE, NO_EQUALS, NO_FUNCTION_ARGZERO, GLOB_SUBST, NO_GLOBAL_EXPORT, NO_HUP, INTERACTIVE_COMMENTS, KSH_ARRAYS, NO_MULTIOS, NO_NOMATCH, NO_NOTIFY, POSIX_BUILTINS, NO_PROMPT_PERCENT, RM_STAR_SILENT, SH_FILE_EXPANSION, SH_GLOB, SH_OPTION_LETTERS, SH_WORD_SPLIT.  Additionally the BSD_ECHO and IGNORE_BRACES options are set if zsh is invoked as sh.  Also, the KSH_OPTION_PRINT, LOCAL_OPTIONS, PROMPT_BANG, PROMPT_SUBST and SINGLE_LINE_ZLE options are set if zsh is invoked as ksh.
When the basename of the command used to invoke zsh starts with the letter `r' or the `-r' command line option is supplied at invocation, the shell becomes restricted.  Emulation mode is determined after stripping the letter `r' from the invocation name.  The following are disabled in restricted mode:
•      changing directories with the cd builtin
•      changing or unsetting the EGID, EUID, GID, HISTFILE, HISTSIZE, IFS, LD_AOUT_LIBRARY_PATH, LD_AOUT_PRELOAD, LD_LIBRARY_PATH, LD_PRELOAD, MODULE_PATH, module_path, PATH, path, SHELL, UID and USERNAME parameters
•      specifying command names containing /
•      specifying command pathnames using hash
•      redirecting output to files
•      using the exec builtin command to replace the shell with another command
•      using jobs -Z to overwrite the shell process' argument and environment space
•      using the ARGV0 parameter to override argv[0] for external commands
•      turning off restricted mode with set +r or unsetopt RESTRICTED
These restrictions are enforced after processing the startup files.  The startup files should set up PATH to point to a directory of commands which can be safely invoked in the restricted environment.  They may also add further restrictions by disabling selected builtins.
Restricted mode can also be activated any time by setting the RESTRICTED option.  This immediately enables all the restrictions described above even if the shell still has not processed all startup files.
A shell Restricted Mode is an outdated way to restrict what users may do: modern systems have better, safer and more reliable ways to confine user actions, such as chroot jails, containers and zones.
A restricted shell is very difficult to implement safely.  The feature may be removed in a future version of zsh.
It is important to realise that the restrictions only apply to the shell, not to the commands it runs (except for some shell builtins).  While a restricted shell can only run the restricted list of commands accessible via the predefined `PATH' variable, it does not prevent those commands from running any other command.
As an example, if `env' is among the list of allowed commands, then it allows the user to run any command as `env' is not a shell builtin command and can run arbitrary executables.
So when implementing a restricted shell framework it is important to be fully aware of what actions each of the allowed commands or features (which may be regarded as modules) can perform.
Many commands can have their behaviour affected by environment variables. Except for the few listed above, zsh does not restrict the setting of environment variables.
If a `perl', `python', `bash', or other general purpose interpreted script it treated as a restricted command, the user can work around the restriction by setting specially crafted `PERL5LIB', `PYTHONPATH', `BASHENV' (etc.) environment variables. On GNU systems, any command can be made to run arbitrary code when performing character set conversion (including zsh itself) by setting a `GCONV_PATH' environment variable. Those are only a few examples.
Bear in mind that, contrary to some other shells, `readonly' is not a security feature in zsh as it can be undone and so cannot be used to mitigate the above.
A restricted shell only works if the allowed commands are few and carefully written so as not to grant more access to users than intended. It is also important to restrict what zsh module the user may load as some of them, such as `zsh/system', `zsh/mapfile' and `zsh/files', allow bypassing most of the restrictions.
STARTUP/SHUTDOWN FILES Commands are first read from /etc/zshenv; this cannot be overridden. Subsequent behaviour is modified by the RCS and GLOBAL_RCS options; the former affects all startup files, while the second only affects global startup files (those shown here with an path starting with a /).  If one of the options is unset at any point, any subsequent startup file(s) of the corresponding type will not be read.  It is also possible for a file in $ZDOTDIR to re-enable GLOBAL_RCS. Both RCS and GLOBAL_RCS are set by default.
Commands are then read from $ZDOTDIR/.zshenv.  If the shell is a login shell, commands are read from /etc/zprofile and then $ZDOTDIR/.zprofile. Then, if the shell is interactive, commands are read from /etc/zshrc and then $ZDOTDIR/.zshrc.  Finally, if the shell is a login shell, /etc/zlogin and $ZDOTDIR/.zlogin are read.
When a login shell exits, the files $ZDOTDIR/.zlogout and then /etc/zlogout are read.  This happens with either an explicit exit via the exit or logout commands, or an implicit exit by reading end-of-file from the terminal.  However, if the shell terminates due to exec'ing another process, the logout files are not read.  These are also affected by the RCS and GLOBAL_RCS options.  Note also that the RCS option affects the saving of history files, i.e. if RCS is unset when the shell exits, no history file will be saved.
If ZDOTDIR is unset, HOME is used instead.  Files listed above as being in /etc may be in another directory, depending on the installation.
As /etc/zshenv is run for all instances of zsh, it is important that it be kept as small as possible.  In particular, it is a good idea to put code that does not need to be run for every single shell behind a test of the form `if [[ -o rcs ]]; then ...' so that it will not be executed when zsh is invoked with the `-f' option.
Any of these files may be pre-compiled with the zcompile builtin command (see zshbuiltins(1)).  If a compiled file exists (named for the original file plus the .zwc extension) and it is newer than the original file, the compiled file will be used instead.
$ZDOTDIR/.zshenv $ZDOTDIR/.zprofile $ZDOTDIR/.zshrc $ZDOTDIR/.zlogin $ZDOTDIR/.zlogout ${TMPPREFIX}*   (default is /tmp/zsh*) /etc/zshenv /etc/zprofile /etc/zshrc /etc/zlogin /etc/zlogout    (installation-specific - /etc is the default)
sh(1), csh(1), tcsh(1), rc(1), bash(1), ksh(1), zshall(1), zshbuiltins(1), zshcalsys(1), zshcompwid(1), zshcompsys(1), zshcompctl(1), zshcontrib(1), zshexpn(1), zshmisc(1), zshmodules(1), zshoptions(1), zshparam(1), zshroadmap(1), zshtcpsys(1), zshzftpsys(1), zshzle(1)
IEEE Standard for information Technology - Portable Operating System Interface (POSIX) - Part 2: Shell and Utilities, IEEE Inc, 1993, ISBN 1-55937-255-9.
ARC(1L)                          LOCAL COMMANDS                          ARC(1L)
arc - pc archive utility
arc a|m|u|f|d|x|e|r|p|l|v|t|c [ biswnoq ] [ gpassword ] archive [ filename ...]
Arc is a general archive and file compression utility, used to maintain a compressed archive of files.  An archive is a single file that combines many files, reducing storage space and allowing multiple files to be handled as one.  Arc uses one of several compression methods for each file within the archive, based on whichever method yields the smallest result.
Execute arc with no arguments for fairly verbose, usable instructions.
a  add files to archive.  Copies the indicated files to the archive.
m  move files to archive.  Same as 'a' switch except that the files are deleted from the directory as they are moved to the archive.
u  update files in archive.  This switch will replace archived files when the named file is newer than the archived copy.  New files will be added automatically.
f  freshen files in archive.  Same as 'u' except that new files will not be added.
d  delete files in archive.  The named files are removed from the archive.
x,e extract files from archive.  The named files are extracted from the archive and created in the current directory in an uncompressed state.
r  run one file with arguments from archive.  Any program may be executed directly from the archive.  The parameters given after the program name are passed to the program without modification.
p  copy files from archive to standard output.  Useful with I/O redirection. A form-feed is appended after each file, to ease use with printers.
l  list files in archive.  Limited information listing of files contained in an archive.  Displays the filename, original length, and date last modified.  If the 'n' option (see below) is used, only the filename is displayed.
v  verbose listing of files in archive.  Complete information listing of files contained in an archive.  Displays the filename, original length, storage method, storage factor (% savings), compressed size, date, time, and CRC.
t  test archive integrity.  Computes CRC values for each member of the archive and compares against the previously saved value.
c  convert entry to new packing method.  Convert files stored with older methods to newer methods that are more efficient. Also useful for files previously archived with the 's' option.
b  retain backup copy of archive.  Keep the original archive file and rename to .BAK.  This switch may be used with the following commands: a, m, u, f, d, c.
i  suppress image mode.  This switch causes files to be treated as text files, and will translate their end-of-line sequence. (Unix's '\n' vs. '\r\n' used on many other systems.)  The default is to perform no translation when compressing or extracting files.  This option makes dealing with text files much nicer, though the 'tr' command can also be used. ('\r' in makefiles and C source code is such a nuisance...)
s  suppress compression.  This forces new files to be saved using Method 2 (no compression).  This switch may be used with the following commands:  a, m, u, f, c.
w  suppress warning messages.  This switch will keep warning messages from being displayed which is the default.  Most warnings concern the deletion or existence of files with the same name.
n  suppress notes and comments.  This switch will keep useful notes from being displayed which is the default.  Most notes indicate what stage of compression is being run (analyze, compaction, storage).
o  overwrite existing files when extracting.  This switch will make existing files silently get overwritten, instead of asking for confirmation, which is the default.
q  force Squash compression method.  This switch causes the Squash compression method to be used, instead of Crunch, which is the default.
g  encrypt/decrypt archive entry.  This is used to encode files so that others may not read them.  BE CAREFUL!  This must be the last parameter in the switches because everything following is part of the password.
Arc Version 2 differs from version 1 in that archive entries are automatically compressed when they are added to the archive, making a separate compression step unecessary.  The nature of the compression is indicated by the header version number placed in each archive entry, as follows: 1 = Old style, no compression 2 = New style, no compression 3 = Compression of repeated characters only 4 = Compression of repeated characters plus Huffman SQueezing 5 = Lempel-Zev packing of repeated strings (old style) 6 = Lempel-Zev packing of repeated strings (new style) 7 = Lempel-Zev Williams packing with improved hash function 8 = Dynamic Lempel-Zev packing with adaptive reset 9 = Squashing
Type 5, Lempel-Zev packing, was added as of version 4.0
Type 6 is Lempel-Zev packing where runs of repeated characters have been collapsed, and was added as of version 4.1
Type 7 is a variation of Lempel-Zev using a different hash function which yields speed improvements of 20-25%, and was added as of version 4.6
Type 8 is a different implementation of Lempel-Zev, using a variable code size and an adaptive block reset, and was added as of version 5.0
Type 9 is another variation of Lempel-Zev, using a larger hash table. This method was developed by Phil Katz, and is not supported by the "official" ARC programs.
Arc will look for environment variables named ARCTEMP or TMPDIR, which, if present, indicates the pathname where temporary files should be created. This is typically the location of a RAMdisk on a microcomputer, "/tmp/" or left unset.
See the included documentation file for more details.
Arc has been in use in the CP/M and MSDOS world for many years.  Thom Henderson developed the original version, but it is important to note that arc is based on the file compression theories developed by Huffman, Welch, Knott, Knuth, and many other scientists. This implementation is based on version 5.21 of the MSDOS program.
Arc behaves just like the PC version of the program; all functions of the "usage" display are working.  Full compatibility with PC ARC files is maintained, the price for which is that arc doesn't like long filenames, and can only archive files with names of up to 12 characters.  It will *sometimes* do The Right Thing with them, but I suggest you put long- winded filenames in a "shar" before arcing them.
There shouldn't be any problems, (hah!) but if you find any, please send them to me at:
hyc@hanauma.jpl.nasa.gov
Original MSDOS program by Thom Henderson COPYRIGHT(C) 1985-87 by System Enhancement Associates; ALL RIGHTS RESERVED
Original Lempel-Zev code derived from compress 4.0.  Modified to support Squashing by Dan Lanciani (ddl@harvard.edu) Ported from MSDOS by Howard Chu, with help from John Gilmore (hoptoad!gnu), James Turner (daisy!turner) and others.
dillo(1)                          USER COMMANDS                         dillo(1)
dillo - web browser
dillo [OPTION]...  [--] [URL|FILE]...
Dillo is a lightweight graphical web browser that aims to be secure.  It handles HTTP internally, and FILE, FTP, and DATA URIs are handled through a plugin system (dpi). In addition, INSECURE HTTPS support can be enabled. Both FTP and Dillo's download manager use the wget(1) downloader.
Dillo displays HTML, text, PNG, JPEG, and GIF files.  It handles cookies, HTTP authentication (basic and digest), proxying (basic), and some CSS.
Framesets are displayed as links to frames, and there is currently no support for javascript or video.
In order to use the hyphenation feature, pattern files from CTAN need to be installed to /usr/lib/dillo/hyphenation/.  This can be done with the script dillo-install-hyphenation.  Call it with ISO-639-1 language codes as arguments, or without arguments to get more help.
-f, --fullwindow Start in full window mode: hide address bar, navigation buttons, menu, and status bar.
-g, -geometry GEO Set initial window position where GEO is WxH[{+-}X{+-}Y].
-h, --help Display this help text and exit.
-l, --local Don't load images or stylesheets, or follow redirections, for these FILEs or URLs. This is intended for use with HTML email.
-v, --version Display version info and exit.
-x, --xid XID Open first Dillo window in an existing window whose window ID is XID.
1      Internal error.
2      Error in command line arguments.
HOME (or HOMEDRIVE and HOMEPATH on Cygwin) User's home directory.
http_proxy URL of proxy to send HTTP traffic through.
dpid   Dillo plugin daemon
dpidc  Control program for dpid.
~/.dillo/bm.txt User bookmarks
~/.dillo/certs/ Saved certificates for HTTPS.
~/.dillo/cookies.txt Stored cookies
~/.dillo/cookiesrc Cookie settings
~/.dillo/dillorc Configuration file.
~/.dillo/domainrc Rules for cross-domain requests.
~/.dillo/dpid_comm_keys Keys used in dpi daemon communication.
~/.dillo/dpidrc Contains name of directory containing dpis, and associates dpi files with protocols.
~/.dillo/keysrc Keybindings.
~/.dillo/style.css User style sheet.
/usr/lib/dillo/hyphenation/ Hyphenation pattern files.
wget(1)
Dillo website: http://www.dillo.org
IN2CSV(1)                            csvkit                            IN2CSV(1)
in2csv - in2csv Documentation
Converts various tabular data formats into CSV.
Converting fixed width requires that you provide a schema file with the “-s” option. The schema file should have the following format:
column,start,length name,0,30 birthday,30,10 age,40,3
The header line is required though the columns may be in any order:
usage: in2csv [-h] [-d DELIMITER] [-t] [-q QUOTECHAR] [-u {0,1,2,3}] [-b] [-p ESCAPECHAR] [-z FIELD_SIZE_LIMIT] [-e ENCODING] [-L LOCALE] [-S] [--blanks] [--date-format DATE_FORMAT] [--datetime-format DATETIME_FORMAT] [-H] [-K SKIP_LINES] [-v] [-l] [--zero] [-V] [-f FILETYPE] [-s SCHEMA] [-k KEY] [-n] [--sheet SHEET] [--write-sheets WRITE_SHEETS] [--encoding-xls ENCODING_XLS] [-y SNIFF_LIMIT] [-I] [FILE]
Convert common, but less awesome, tabular data formats to CSV.
optional arguments: -h, --help            show this help message and exit -f FILETYPE, --format FILETYPE The format of the input file. If not specified will be inferred from the file type. Supported formats: csv, dbf, fixed, geojson, json, ndjson, xls, xlsx. -s SCHEMA, --schema SCHEMA Specify a CSV-formatted schema file for converting fixed-width files. See documentation for details. -k KEY, --key KEY     Specify a top-level key to use look within for a list of objects to be converted when processing JSON. -n, --names           Display sheet names from the input Excel file. --sheet SHEET         The name of the Excel sheet to operate on. --write-sheets WRITE_SHEETS The names of the Excel sheets to write to files, or "-" to write all sheets. -y SNIFF_LIMIT, --snifflimit SNIFF_LIMIT Limit CSV dialect sniffing to the specified number of bytes. Specify "0" to disable sniffing entirely. -I, --no-inference    Disable type inference (and --locale, --date-format, --datetime-format) when parsing CSV input.
Some command-line flags only pertain to specific input formats.
NOTE: The “ndjson” format refers to “newline delimited JSON”, as used by many streaming APIs.
NOTE: If an XLS looks identical to an XLSX when viewed in Excel, they may not be identical as CSV. For example, XLSX has an integer type, but XLS doesn’t. Numbers that look like integers from an XLS will have decimals in CSV, but those from an XLSX won’t.
NOTE: To convert from HTML, consider messytables.
Convert the 2000 census geo headers file from fixed-width to CSV and from latin-1 encoding to utf8:
in2csv -e iso-8859-1 -f fixed -s examples/realdata/census_2000/census2000_geo_schema.csv examples/realdata/census_2000/usgeo_excerpt.upl
NOTE: A library of fixed-width schemas is maintained in the ffs project:
https://github.com/wireservice/ffs
Convert an Excel .xls file:
in2csv examples/test.xls
Standardize the formatting of a CSV file (quoting, line endings, etc.):
in2csv examples/realdata/FY09_EDU_Recipients_by_State.csv
Fetch csvkit’s open issues from the GitHub API, convert the JSON response into a CSV and write it to a file:
curl https://api.github.com/repos/wireservice/csvkit/issues?state=open | in2csv -f json -v
Convert a DBase DBF file to an equivalent CSV:
in2csv examples/testdbf.dbf
This tool names unnamed headers. To avoid that behavior, run:
in2csv --no-header-row examples/test.xlsx | tail -n +2
RESIZE2FS(8)                 System Manager's Manual                RESIZE2FS(8)
resize2fs - ext2/ext3/ext4 file system resizer
resize2fs [ -fFpPMbs ] [ -d debug-flags ] [ -S RAID-stride ] [ -z undo_file ] device [ size ]
The resize2fs program will resize ext2, ext3, or ext4 file systems.  It can be used to enlarge or shrink an unmounted file system located on device.  If the file system is mounted, it can be used to expand the size of the mounted file system, assuming the kernel and the file system supports on-line resizing.  (Modern Linux 2.6 kernels will support on- line resize for file systems mounted using ext3 and ext4; ext3 file systems will require the use of file systems with the resize_inode feature enabled.)
The size parameter specifies the requested new size of the file system. If no units are specified, the units of the size parameter shall be the file system blocksize of the file system.  Optionally, the size parameter may be suffixed by one of the following units designators: 'K', 'M', 'G', 'T' (either upper-case or lower-case) or 's' for power-of-two kilobytes, megabytes, gigabytes, terabytes or 512 byte sectors respectively. The size of the file system may never be larger than the size of the partition.  If size parameter is not specified, it will default to the size of the partition.
The resize2fs program does not manipulate the size of partitions.  If you wish to enlarge a file system, you must make sure you can expand the size of the underlying partition first.  This can be done using fdisk(8) by deleting the partition and recreating it with a larger size or using lvextend(8), if you're using the logical volume manager lvm(8).  When recreating the partition, make sure you create it with the same starting disk cylinder as before!  Otherwise, the resize operation will certainly not work, and you may lose your entire file system.  After running fdisk(8), run resize2fs to resize the ext2 file system to use all of the space in the newly enlarged partition.
If you wish to shrink an ext2 partition, first use resize2fs to shrink the size of file system.  Then you may use fdisk(8) to shrink the size of the partition.  When shrinking the size of the partition, make sure you do not make it smaller than the new size of the ext2 file system!
The -b and -s options enable and disable the 64bit feature, respectively. The resize2fs program will, of course, take care of resizing the block group descriptors and moving other data blocks out of the way, as needed. It is not possible to resize the file system concurrent with changing the 64bit status.
-b     Turns on the 64bit feature, resizes the group descriptors as necessary, and moves other metadata out of the way.
-d debug-flags Turns on various resize2fs debugging features, if they have been compiled into the binary.  debug-flags should be computed by adding the numbers of the desired features from the following list: 2    - Debug block relocations 4    - Debug inode relocations 8    - Debug moving the inode table 16   - Print timing information 32   - Debug minimum file system size (-M) calculation
-f     Forces resize2fs to proceed with the file system resize operation, overriding some safety checks which resize2fs normally enforces.
-F     Flush the file system device's buffer caches before beginning. Only really useful for doing resize2fs time trials.
-M     Shrink the file system to minimize its size as much as possible, given the files stored in the file system.
-p     Print out percentage completion bars for each resize2fs phase during an offline (non-trivial) resize operation, so that the user can keep track of what the program is doing.  (For very fast resize operations, no progress bars may be displayed.)
-P     Print an estimate of the number of file system blocks in the file system if it is shrunk using resize2fs's -M option and then exit.
-s     Turns off the 64bit feature and frees blocks that are no longer in use.
-S RAID-stride The resize2fs program will heuristically determine the RAID stride that was specified when the file system was created.  This option allows the user to explicitly specify a RAID stride setting to be used by resize2fs instead.
-z undo_file Before overwriting a file system block, write the old contents of the block to an undo file.  This undo file can be used with e2undo(8) to restore the old contents of the file system should something go wrong.  If the empty string is passed as the undo_file argument, the undo file will be written to a file named resize2fs-device.e2undo in the directory specified via the E2FSPROGS_UNDO_DIR environment variable.
The minimum size of the file system as estimated by resize2fs may be incorrect, especially for file systems with 1k and 2k blocksizes.
resize2fs was written by Theodore Ts'o <tytso@mit.edu>.
Resize2fs is Copyright 1998 by Theodore Ts'o and PowerQuest, Inc.  All rights reserved.  As of April, 2000 Resize2fs may be redistributed under the terms of the GPL.
fdisk(8), e2fsck(8), mke2fs(8), lvm(8), lvextend(8)
DUNE(1)                            Dune Manual                           DUNE(1)
dune - composable build system for OCaml
dune build [--watch] dune runtest [--watch] dune exec NAME dune utop [DIR] dune install dune init project NAME [PATH] [--libs=l1,l2 --ppx=p1,p2 --inline-tests]
Dune is a build system designed for OCaml projects only. It focuses on providing the user with a consistent experience and takes care of most of the low-level details of OCaml compilation. All you have to do is provide a description of your project and Dune will do the rest.
The scheme it implements is inspired from the one used inside Jane Street and adapted to the open source world. It has matured over a long time and is used daily by hundreds of developers, which means that it is highly tested and productive.
build Build the given targets, or all installable targets if none are given.
cache Manage the shared artifacts cache
clean Clean the project.
compute Compute internal function.
describe Describe the workspace.
exec Execute a command in a similar environment as if installation was performed.
external-lib-deps Print out external libraries needed to build the given targets.
format-dune-file Format dune files
help Additional Dune help
init Initialize dune components
installed-libraries Print out libraries installed on the system.
ocaml-merlin Start a merlin configuration server
printenv Print the environment of a directory
promote Promote files from the last run
rules Dump internal rules.
runtest Run tests.
subst Substitute watermarks in source files.
top Print a list of toplevel directives for including directories and loading cma files.
upgrade Upgrade jbuilder projects to dune
utop Load library in utop
test An alias for runtest.
--build-info Show build information.
-f, --force Force actions associated to aliases to be re-executed even if their dependencies haven't changed.
--help[=FMT] (default=auto) Show this help in format FMT. The value FMT must be one of `auto', `pager', `groff' or `plain'. With `auto', the format is `pager` or `plain' whenever the TERM env var is `dumb' or undefined.
--sandbox=VAL (absent DUNE_SANDBOX env) Sandboxing mode to use by default. Some actions require a certain sandboxing mode, so they will ignore this setting. The allowed values are: none, symlink, copy.
-w, --watch Instead of terminating build after completion, wait continuously for file changes.
These options are common to all commands.
--always-show-command-line Always show the full command lines of programs executed by dune
--auto-promote Automatically promote files. This is similar to running dune promote after the build.
--build-dir=FILE (absent DUNE_BUILD_DIR env) Specified build directory. _build if unspecified
--cache=VAL (absent DUNE_CACHE env) Activate binary cache (either `disabled' or `enabled'). Default is `disabled'.
--cache-check-probability=VAL (absent=0. or DUNE_CACHE_CHECK_PROBABILITY env) Probability cached rules are rerun to check for reproducibility
--cache-duplication=VAL (absent DUNE_CACHE_DUPLICATION env) Binary cache duplication mode
--cache-transport=VAL (absent DUNE_CACHE_TRANSPORT env) Binary cache protocol
--config-file=FILE Load this configuration file instead of the default one.
--debug-artifact-substitution Print debugging info about artifact substitution
--debug-backtraces Always print exception backtraces.
--debug-dependency-path In case of error, print the dependency path from the targets on the command line to the rule that failed.
--debug-findlib Debug the findlib sub-system.
--default-target=TARGET (absent=@@default) Set the default target that when none is specified to dune build.
--diff-command=VAL Shell command to use to diff files. Use - to disable printing the diff.
--disable-promotion (absent DUNE_DISABLE_PROMOTION env) Disable all promotion rules
--display=MODE Control the display mode of Dune. See dune-config(5) for more details.
--ignore-promoted-rules Ignore rules with (mode promote), except ones with (only ...). The variable %{ignoring_promoted_rules} in dune files reflects whether this option was passed or not.
--instrument-with=BACKENDS (absent DUNE_INSTRUMENT_WITH env) "Enable instrumentation by BACKENDS. BACKENDS is a comma-separated list of library names, each one of which must declare an instrumentation backend.
-j JOBS Run no more than JOBS commands simultaneously.
--no-buffer Do not buffer the output of commands executed by dune. By default dune buffers the output of subcommands, in order to prevent interleaving when multiple commands are executed in parallel. However, this can be an issue when debugging long running tests. With --no-buffer, commands have direct access to the terminal. Note that as a result their output won't be captured in the log file. You should use this option in conjunction with -j 1, to avoid interleaving. Additionally you should use --verbose as well, to make sure that commands are printed before they are being executed.
--no-config Do not load the configuration file
--no-print-directory Suppress "Entering directory" messages
--only-packages=PACKAGES Ignore stanzas referring to a package that is not in PACKAGES. PACKAGES is a comma-separated list of package names. Note that this has the same effect as deleting the relevant stanzas from dune files. It is mostly meant for releases. During development, it is likely that what you want instead is to build a particular <package>.install target.
-p PACKAGES, --for-release-of-packages=PACKAGES (required) Shorthand for --release --only-packages PACKAGE. You must use this option in your <package>.opam files, in order to build only what's necessary when your project contains multiple packages as well as getting reproducible builds.
--profile=VAL (absent DUNE_PROFILE env) Select the build profile, for instance dev or release. The default is dev.
--promote-install-files[=VAL] (default=true) Promote the generated <package>.install files to the source tree
--release Put dune into a reproducible release mode. This is in fact a shorthand for --root . --ignore-promoted-rules --no-config --profile release --always-show-command-line --promote-install-files --default-target @install. You should use this option for release builds. For instance, you must use this option in your <package>.opam files. Except if you already use -p, as -p implies this option.
--root=DIR Use this directory as workspace root instead of guessing it. Note that this option doesn't change the interpretation of targets given on the command line. It is only intended for scripts.
--store-orig-source-dir (absent DUNE_STORE_ORIG_SOURCE_DIR env) Store original source location in dune-package metadata
--terminal-persistence=MODE Changes how the log of build results are displayed to the console between rebuilds while in --watch mode. Supported modes: preserve, clear-on-rebuild.
--trace-file=FILE Output trace data in catapult format (compatible with chrome://tracing)
--verbose Same as --display verbose
--workspace=FILE (absent DUNE_WORKSPACE env) Use this specific workspace file instead of looking it up.
-x VAL Cross-compile using this toolchain.
Use `dune COMMAND --help' for help on a single command.
These environment variables affect the execution of dune:
DUNE_BUILD_DIR Specified build directory. _build if unspecified
DUNE_CACHE Activate binary cache (either `disabled' or `enabled'). Default is `disabled'.
DUNE_CACHE_CHECK_PROBABILITY Probability cached rules are rerun to check for reproducibility
DUNE_CACHE_DUPLICATION Binary cache duplication mode
DUNE_CACHE_TRANSPORT Binary cache protocol
DUNE_DISABLE_PROMOTION Disable all promotion rules
DUNE_INSTRUMENT_WITH "Enable instrumentation by BACKENDS. BACKENDS is a comma-separated list of library names, each one of which must declare an instrumentation backend.
DUNE_PROFILE Build profile. dev if unspecified or release if -p is set.
DUNE_SANDBOX Sandboxing mode to use by default. (see --sandbox)
DUNE_STORE_ORIG_SOURCE_DIR Store original source location in dune-package metadata
DUNE_WORKSPACE Use this specific workspace file instead of looking it up.
Check bug reports at https://github.com/ocaml/dune/issues
1.  Initialise a new project named `foo':
dune init project foo
2.  Build all targets in the current source tree:
dune build
3.  Run the executable named `bar':
dune exec bar
4.  Run all tests in the current source tree:
dune runtest
5.  Install all components defined in the project:
dune install
6.  Remove all build artefacts:
dune clean
TS(1)                                OpenSSL                               TS(1)
openssl-ts, ts - Time Stamping Authority tool (client/server)
openssl ts -query [-rand file...]  [-writerand file] [-config configfile] [-data file_to_hash] [-digest digest_bytes] [-digest] [-tspolicy object_id] [-no_nonce] [-cert] [-in request.tsq] [-out request.tsq] [-text]
openssl ts -reply [-config configfile] [-section tsa_section] [-queryfile request.tsq] [-passin password_src] [-signer tsa_cert.pem] [-inkey file_or_id] [-digest] [-chain certs_file.pem] [-tspolicy object_id] [-in response.tsr] [-token_in] [-out response.tsr] [-token_out] [-text] [-engine id]
openssl ts -verify [-data file_to_hash] [-digest digest_bytes] [-queryfile request.tsq] [-in response.tsr] [-token_in] [-CApath trusted_cert_path] [-CAfile trusted_certs.pem] [-untrusted cert_file.pem] [verify options]
verify options: [-attime timestamp] [-check_ss_sig] [-crl_check] [-crl_check_all] [-explicit_policy] [-extended_crl] [-ignore_critical] [-inhibit_any] [-inhibit_map] [-issuer_checks] [-no_alt_chains] [-no_check_time] [-partial_chain] [-policy arg] [-policy_check] [-policy_print] [-purpose purpose] [-suiteB_128] [-suiteB_128_only] [-suiteB_192] [-trusted_first] [-use_deltas] [-auth_level num] [-verify_depth num] [-verify_email email] [-verify_hostname hostname] [-verify_ip ip] [-verify_name name] [-x509_strict]
The ts command is a basic Time Stamping Authority (TSA) client and server application as specified in RFC 3161 (Time-Stamp Protocol, TSP). A TSA can be part of a PKI deployment and its role is to provide long term proof of the existence of a certain datum before a particular time. Here is a brief description of the protocol:
1.  The TSA client computes a one-way hash value for a data file and sends the hash to the TSA.
2.  The TSA attaches the current date and time to the received hash value, signs them and sends the timestamp token back to the client. By creating this token the TSA certifies the existence of the original data file at the time of response generation.
3.  The TSA client receives the timestamp token and verifies the signature on it. It also checks if the token contains the same hash value that it had sent to the TSA.
There is one DER encoded protocol data unit defined for transporting a timestamp request to the TSA and one for sending the timestamp response back to the client. The ts command has three main functions: creating a timestamp request based on a data file, creating a timestamp response based on a request, verifying if a response corresponds to a particular request or a data file.
There is no support for sending the requests/responses automatically over HTTP or TCP yet as suggested in RFC 3161. The users must send the requests either by ftp or e-mail.
Time Stamp Request generation The -query switch can be used for creating and printing a timestamp request with the following options:
-config configfile The configuration file to use.  Optional; for a description of the default value, see "COMMAND SUMMARY" in openssl(1).
-data file_to_hash The data file for which the timestamp request needs to be created. stdin is the default if neither the -data nor the -digest parameter is specified. (Optional)
-digest digest_bytes It is possible to specify the message imprint explicitly without the data file. The imprint must be specified in a hexadecimal format, two characters per byte, the bytes optionally separated by colons (e.g. 1A:F6:01:... or 1AF601...). The number of bytes must match the message digest algorithm in use. (Optional)
-digest The message digest to apply to the data file.  Any digest supported by the OpenSSL dgst command can be used.  The default is SHA-1. (Optional)
-tspolicy object_id The policy that the client expects the TSA to use for creating the timestamp token. Either the dotted OID notation or OID names defined in the config file can be used. If no policy is requested the TSA will use its own default policy. (Optional)
-no_nonce No nonce is specified in the request if this option is given. Otherwise a 64 bit long pseudo-random none is included in the request. It is recommended to use nonce to protect against replay- attacks. (Optional)
-cert The TSA is expected to include its signing certificate in the response. (Optional)
-in request.tsq This option specifies a previously created timestamp request in DER format that will be printed into the output file. Useful when you need to examine the content of a request in human-readable format. (Optional)
-out request.tsq Name of the output file to which the request will be written. Default is stdout. (Optional)
-text If this option is specified the output is human-readable text format instead of DER. (Optional)
Time Stamp Response generation A timestamp response (TimeStampResp) consists of a response status and the timestamp token itself (ContentInfo), if the token generation was successful. The -reply command is for creating a timestamp response or timestamp token based on a request and printing the response/token in human-readable format. If -token_out is not specified the output is always a timestamp response (TimeStampResp), otherwise it is a timestamp token (ContentInfo).
-config configfile The configuration file to use.  Optional; for a description of the default value, see "COMMAND SUMMARY" in openssl(1).  See CONFIGURATION FILE OPTIONS for configurable variables.
-section tsa_section The name of the config file section containing the settings for the response generation. If not specified the default TSA section is used, see CONFIGURATION FILE OPTIONS for details. (Optional)
-queryfile request.tsq The name of the file containing a DER encoded timestamp request. (Optional)
-passin password_src Specifies the password source for the private key of the TSA. See "Pass Phrase Options" in openssl(1). (Optional)
-signer tsa_cert.pem The signer certificate of the TSA in PEM format. The TSA signing certificate must have exactly one extended key usage assigned to it: timeStamping. The extended key usage must also be critical, otherwise the certificate is going to be refused. Overrides the signer_cert variable of the config file. (Optional)
-inkey file_or_id The signer private key of the TSA in PEM format. Overrides the signer_key config file option. (Optional) If no engine is used, the argument is taken as a file; if an engine is specified, the argument is given to the engine as a key identifier.
-digest Signing digest to use. Overrides the signer_digest config file option. (Mandatory unless specified in the config file)
-chain certs_file.pem The collection of certificates in PEM format that will all be included in the response in addition to the signer certificate if the -cert option was used for the request. This file is supposed to contain the certificate chain for the signer certificate from its issuer upwards. The -reply command does not build a certificate chain automatically. (Optional)
-tspolicy object_id The default policy to use for the response unless the client explicitly requires a particular TSA policy. The OID can be specified either in dotted notation or with its name. Overrides the default_policy config file option. (Optional)
-in response.tsr Specifies a previously created timestamp response or timestamp token (if -token_in is also specified) in DER format that will be written to the output file. This option does not require a request, it is useful e.g. when you need to examine the content of a response or token or you want to extract the timestamp token from a response. If the input is a token and the output is a timestamp response a default 'granted' status info is added to the token. (Optional)
-token_in This flag can be used together with the -in option and indicates that the input is a DER encoded timestamp token (ContentInfo) instead of a timestamp response (TimeStampResp). (Optional)
-out response.tsr The response is written to this file. The format and content of the file depends on other options (see -text, -token_out). The default is stdout. (Optional)
-token_out The output is a timestamp token (ContentInfo) instead of timestamp response (TimeStampResp). (Optional)
-engine id Specifying an engine (by its unique id string) will cause ts to attempt to obtain a functional reference to the specified engine, thus initialising it if needed. The engine will then be set as the default for all available algorithms. Default is builtin. (Optional)
Time Stamp Response verification The -verify command is for verifying if a timestamp response or timestamp token is valid and matches a particular timestamp request or data file. The -verify command does not use the configuration file.