neulab/tldr huggingface dataset:
PREFIX        Where to install this port (usually set to the same as LOCALBASE).
MASTER_SITES  Primary sites for distribution files if not found locally.
PATCH_SITES   Primary locations for distribution patch files if not found locally.
MASTER_SITE_FREEBSD If set, go to the master FreeBSD site for all files.
MASTER_SITE_OVERRIDE Try going to these sites for all files and patches, first.
MASTER_SITE_BACKUP Try going to these sites for all files and patches, last.
RANDOMIZE_MASTER_SITES Try the download locations in a random order.
MASTER_SORT   Sort the download locations according to user supplied pattern.  Example: .dk .sunet.se .se dk.php.net .no .de heanet.dl.sourceforge.net
MASTER_SITE_INDEX Where to get INDEX source built on FreeBSD cluster (for fetchindex target).  Defaults to https://www.FreeBSD.org/ports/.
FETCHINDEX    Command to get INDEX (for fetchindex target).  Defaults to “fetch -am”.
NOCLEANDEPENDS If defined, do not let clean recurse to dependencies.
FETCH_CMD     Command to use to fetch files.  Normally fetch(1).
FORCE_PKG_REGISTER If set, overwrite any existing package registration on the system.
INTERACTIVE   If defined, only operate on a port if it requires interaction.
BATCH         If defined, only operate on a port if it can be installed 100% automatically.
DISABLE_VULNERABILITIES If defined, disable check for security vulnerabilities using pkg-audit(8) when installing new ports.
NO_IGNORE     If defined, allow installation of ports marked as ⟨FORBIDDEN⟩.  The default behavior of the Ports framework is to abort when the installation of a forbidden port is attempted.  Of course, these ports may not work as expected, but if you really know what you are doing and are sure about installing a forbidden port, then NO_IGNORE lets you do it.
NO_CHECKSUM   If defined, skip verifying the port's checksum.
TRYBROKEN     If defined, attempt to build a port even if it is marked as ⟨BROKEN⟩.
PORT_DBDIR    Directory where the results of configuring OPTIONS are stored.  Defaults to /var/db/ports.  Each port where OPTIONS have been configured will have a uniquely named sub- directory, containing a single file options.
The following list provides a name and short description for many of the variables that are used when building ports.  More information on these and other related variables may be found in ${PORTSDIR}/Mk/* and the FreeBSD Porter's Handbook.
WITH_DEBUG         (bool) If set, debugging symbols are installed for ports binaries.
WITH_DEBUG_PORTS   A list of origins for which to set WITH_DEBUG.
WITH_CCACHE_BUILD  (bool) If set, enables the use of ccache(1) for building ports.
CCACHE_DIR         Which directory to use for the ccache(1) data.
/usr/ports                 The default ports directory. /usr/ports/Mk/bsd.port.mk  The big Kahuna.
Example 1: Building and Installing a Port
The following command builds and installs Emacs.
# cd /usr/ports/editors/emacs # make install
Example 2: Installing Dependencies with pkg(8)
The following example shows how to build and install a port without having to build its dependencies.  Instead, the dependencies are downloaded via pkg(8).
# make install-missing-packages # make install
It is especially useful, when the dependencies are costly in time and resources to build (like lang/rust).  The drawback is that pkg(8) offers only packages built with the default set of OPTIONS.
Example 3: Building a Non-Default Flavor of a Port
The following command builds a non-default flavor of a port.  (In this case devel/py-pip is going to be built with Python 3.7 support.)
# cd /usr/ports/devel/py-pip # env FLAVOR=py37 make build
Example 4: Setting Ports Options via make.conf(5)
The following lines present various ways of configuring ports options via make.conf(5) (as an alternative to, e.g., running “make config”):
# Enable NLS for all ports unless configured otherwise # using the options dialog. OPTIONS_SET=            NLS # Disable DOCS for all ports overriding the options set # via the options dialog. OPTIONS_UNSET_FORCE=    DOCS # Disable DOCS and EXAMPLES for the shells/zsh port. shells_zsh_UNSET=       DOCS EXAMPLES
These and other options-related variables are documented in /usr/ports/Mk/bsd.options.mk.
make(1), make.conf(5), development(7), pkg(7)
Additional developer documentation:
- portlint(1)
- /usr/ports/Mk/bsd.port.mk
Additional user documentation:
- pkg(8)
- Searchable index of all ports: https://www.FreeBSD.org/ports
The Ports Collection appeared in FreeBSD 1.0.  It has since spread to NetBSD and OpenBSD.
This manual page was originated by David O'Brien.
Ports documentation is split over four places — /usr/ports/Mk/bsd.port.mk, The Porter's Handbook, the “Packages and Ports” chapter of The FreeBSD Handbook, and this manual page.
GOCRYPTFS(1)                                                        GOCRYPTFS(1)
gocryptfs - create or mount an encrypted filesystem
Initialize new encrypted filesystem gocryptfs -init [OPTIONS] CIPHERDIR
Mount gocryptfs [OPTIONS] CIPHERDIR MOUNTPOINT [-o COMMA-SEPARATED-OPTIONS]
Unmount fusermount -u MOUNTPOINT
Change password gocryptfs -passwd [OPTIONS] CIPHERDIR
Check consistency gocryptfs -fsck [OPTIONS] CIPHERDIR
Show filesystem information gocryptfs -info [OPTIONS] CIPHERDIR
gocryptfs is an encrypted overlay filesystem written in Go.  Encrypted files are stored in CIPHERDIR, and a plain-text view can be presented by mounting the filesystem at MOUNTPOINT.
gocryptfs was inspired by encfs(1) and strives to fix its security issues while providing good performance.
Unless one of the following action flags is passed, the default action is to mount a filesystem (see SYNOPSIS).
-fsck Check CIPHERDIR for consistency.  If corruption is found, the exit code is 26.
-h, -help Print a short help text that shows the more-often used options.
-hh Long help text, shows all available options.
-info Pretty-print the contents of the config file in CIPHERDIR for human consumption, stripping out sensitive data.
$ gocryptfs -info my_cipherdir Creator:      gocryptfs v2.0-beta2 FeatureFlags: GCMIV128 HKDF DirIV EMENames LongNames Raw64 EncryptedKey: 64B ScryptObject: Salt=32B N=65536 R=8 P=1 KeyLen=32
-init Initialize encrypted directory.
-passwd Change the password.  Will ask for the old password, check if it is correct, and ask for a new one.
This can be used together with -masterkey if you forgot the password but know the master key.  Note that without the old password, gocryptfs cannot tell if the master key is correct and will overwrite the old one without mercy.  It will, however, create a backup copy of the old config file as gocryptfs.conf.bak.  Delete it after you have verified that you can access your files with the new password.
-speed Run crypto speed test.  Benchmark Go’s built-in GCM against OpenSSL (if available).  The library that will be selected on “-openssl=auto” (the default) is marked as such.
-version Print version and exit.  The output contains three fields separated by “;”.  Example: “gocryptfs v1.1.1-5-g75b776c; go-fuse 6b801d3; 2016-11-01 go1.7.3”.  Field 1 is the gocryptfs version, field 2 is the version of the go-fuse library, field 3 is the compile date and the Go version that was used.
Available options for -init are listed below.  Usually, you don’t need any.  Defaults are fine.
-aessiv Use the AES-SIV encryption mode.  This is slower than AES-GCM but is secure with deterministic nonces as used in “-reverse” mode.
Run gocryptfs -speed to find out if and how much slower.
-deterministic-names Disable file name randomisation and creation of gocryptfs.diriv files. This can prevent sync conflicts conflicts when synchronising files, but leaks information about identical file names across directories (“Identical names leak” in https://nuetzlich.net/gocryptfs/comparison/#file-names ).
The resulting gocryptfs.conf has “DirIV” missing from “FeatureFlags”.
-devrandom Obsolete and ignored on gocryptfs v2.2 and later.
See https://github.com/rfjakob/gocryptfs/commit/f3c777d5eaa682d878c638192311e52f9c204294 and https://github.com/rfjakob/gocryptfs/issues/596 for background info.
-hkdf Use HKDF to derive separate keys for content and name encryption from the master key.  Default true.
-plaintextnames Do not encrypt file names and symlink targets.
-raw64 Use unpadded base64 encoding for file names.  This gets rid of the trailing “\=\=”.  A filesystem created with this option can only be mounted using gocryptfs v1.2 and higher.  Default true.
-reverse Reverse mode shows a read-only encrypted view of a plaintext directory. Implies “-aessiv”.
-scryptn int scrypt cost parameter expressed as scryptn=log2(N).  Possible values are 10 to 28, representing N=2^10 to N=2^28.
Setting this to a lower value speeds up mounting and reduces its memory needs, but makes the password susceptible to brute-force attacks.  The default is 16.
-xchacha Use XChaCha20-Poly1305 file content encryption.  This should be much faster than AES-GCM on CPUs that lack AES acceleration.
Run gocryptfs -speed to find out if and how much faster.
Available options for mounting are listed below.  Usually, you don’t need any.  Defaults are fine.
-allow_other By default, the Linux kernel prevents any other user (even root) to access a mounted FUSE filesystem.  Settings this option allows access for other users, subject to file permission checking.  Only works if user_allow_other is set in /etc/fuse.conf.  This option is equivalent to “allow_other” plus “default_permissions” described in fuse(8).
-badname string When gocryptfs encounters a “bad” file name (cannot be decrypted or decrypts to garbage), a warning is logged and the file is hidden from the plaintext view.
With the -badname option, you can select “bad” file names that should still be shown in the plaintext view instead of hiding them.  Bad files will get GOCRYPTFS_BAD_NAME appended to their name.
Glob pattern.  Can be passed multiple times for multiple patterns.
Dropbox sync conflicts:
-badname '*conflicted copy*'
Syncthing sync conflicts:
-badname '*.sync-conflict*'
Show all invalid filenames:
-badname '*'
-ctlsock string Create a control socket at the specified location.  The socket can be used to decrypt and encrypt paths inside the filesystem.  When using this option, make sure that the directory you place the socket in is not world-accessible.  For example, /run/user/UID/my.socket would be suitable.
-dev, -nodev Enable (-dev) or disable (-nodev) device files in a gocryptfs mount (default: -nodev).  If both are specified, -nodev takes precedence.  You need root permissions to use -dev.
-e PATH, -exclude PATH Only for reverse mode: exclude relative plaintext path from the encrypted view, matching only from root of mounted filesystem.  Can be passed multiple times.
Example that excludes the directories “Music” and “Movies” from the root directory:
gocryptfs -reverse -exclude Music -exclude Movies /home/user /mnt/user.encrypted
See also -exclude-wildcard, -exclude-from and the EXCLUDING FILES section.
-ew GITIGNORE-PATTERN, -exclude-wildcard GITIGNORE-PATTERN Only for reverse mode: exclude paths from the encrypted view in gitignore(5) syntax, wildcards supported.  Pass multiple times for multiple patterns.
Example to exclude all .mp3 files in any directory:
gocryptfs -reverse -exclude-wildcard '*.mp3' /home/user /mnt/user.encrypted
Example to to exclude everything but the directory `important' in the root dir:
gocryptfs -reverse -exclude-wildcard '*' -exclude-wildcard '!/important' /home/user /mnt/user.encrypted
See also -exclude-from and the EXCLUDING FILES section.
-exclude-from FILE Only for reverse mode: reads gitignore patterns from a file.  Can be passed multiple times.  Example:
gocryptfs -reverse -exclude-from ~/crypt-exclusions /home/user /mnt/user.encrypted
See also -exclude, -exclude-wildcard and the EXCLUDING FILES section.
-exec, -noexec Enable (-exec) or disable (-noexec) executables in a gocryptfs mount (default: -exec).  If both are specified, -noexec takes precedence.
-fg, -f Stay in the foreground instead of forking away.  For compatibility, “-f” is also accepted, but “-fg” is preferred.
Unless -notifypid is also passed, the logs go to stdout and stderr instead of syslog.
-force_owner string If given a string of the form “uid:gid” (where both “uid” and “gid” are substituted with positive integers), presents all files as owned by the given uid and gid, regardless of their actual ownership.  Implies “allow_other”.
This is rarely desired behavior: One should usually run gocryptfs as the account which owns the backing-store files, which should usually be one and the same with the account intended to access the decrypted content. An example of a case where this may be useful is a situation where content is stored on a filesystem that doesn’t properly support UNIX ownership and permissions.
-forcedecode Obsolete and ignored on gocryptfs v2.2 and later.
See https://github.com/rfjakob/gocryptfs/commit/d023cd6c95fcbc6b5056ba1f425d2ac3df4abc5a for what it was and why it was dropped.
-fsname string Override the filesystem name (first column in df -T).  Can also be passed as “-o fsname=” and is equivalent to libfuse’s option of the same name. By default, CIPHERDIR is used.
-fusedebug Enable fuse library debug output.
-i duration, -idle duration Only for forward mode: automatically unmount the filesystem if it has been idle for the specified duration.  Durations can be specified like “500s” or “2h45m”.  0 (the default) means stay mounted indefinitely.
When a process has open files or its working directory in the mount, this will keep it not idle indefinitely.
-kernel_cache Enable the kernel_cache option of the FUSE filesystem, see fuse(8) for details.
-ko Pass additional mount options to the kernel (comma-separated list).  FUSE filesystems are mounted with “nodev,nosuid” by default.  If gocryptfs runs as root, you can enable device files by passing the opposite mount option, “dev”, and if you want to enable suid-binaries, pass “suid”. “ro” (equivalent to passing the “-ro” option) and “noexec” may also be interesting.  For a complete list see the section FILESYSTEM-INDEPENDENT MOUNT OPTIONS in mount(8).  On MacOS, “local”, “noapplexattr”, “noappledouble” may be interesting.
Note that unlike “-o”, “-ko” is a regular option and must be passed BEFORE the directories.  Example:
gocryptfs -ko noexec /tmp/foo /tmp/bar
-longnames Store names longer than 176 bytes in extra files (default true) This flag is useful when recovering old gocryptfs filesystems using “-masterkey”. It is ignored (stays at the default) otherwise.
-nodev See -dev, -nodev.
-noexec See -exec, -noexec.
-nofail Having the nofail option in /etc/fstab instructs systemd to continue booting normally even if the mount fails (see man systemd.fstab).
The option is ignored by gocryptfs itself and has no effect outside /etc/fstab.
-nonempty Allow mounting over non-empty directories.  FUSE by default disallows this to prevent accidental shadowing of files.
-noprealloc Disable preallocation before writing.  By default, gocryptfs preallocates the space the next write will take using fallocate(2) in mode FALLOC_FL_KEEP_SIZE.  The preallocation makes sure it cannot run out of space in the middle of the write, which would cause the last 4kB block to be corrupt and unreadable.
On ext4, preallocation is fast and does not cause a noticeable performance hit.  Unfortunately, on Btrfs, preallocation is very slow, especially on rotational HDDs.  The “-noprealloc” option gives users the choice to trade robustness against out-of-space errors for a massive speedup.
For benchmarks and more details of the issue see https://github.com/rfjakob/gocryptfs/issues/63 .
-nosuid See -suid, -nosuid.
-nosyslog Diagnostic messages are normally redirected to syslog once gocryptfs daemonizes.  This option disables the redirection and messages will continue be printed to stdout and stderr.
-notifypid int Send USR1 to the specified process after successful mount.  This is used internally for daemonization.
-one-file-system Don’t cross filesystem boundaries (like rsync’s --one-file-system). Mountpoints will appear as empty directories.
Only applicable to reverse mode.
Limitation: Mounted single files (yes this is possible) are NOT hidden.
-rw, -ro Mount the filesystem read-write (-rw, default) or read-only (-ro).  If both are specified, -ro takes precedence.
-reverse See the -reverse section in INIT FLAGS.  You need to specify the -reverse option both at -init and at mount.
-serialize_reads The kernel usually submits multiple concurrent reads to service userspace requests and kernel readahead.  gocryptfs serves them concurrently and in arbitrary order.  On backing storage that performs poorly for concurrent or out-of-order reads (like Amazon Cloud Drive), this behavior can cause very slow read speeds.
The -serialize_reads option does two things: (1) reads will be submitted one-by-one (no concurrency) and (2) gocryptfs tries to order the reads by file offset order.
The ordering requires gocryptfs to wait a certain time before submitting a read.  The serialization introduces extra locking.  These factors will limit throughput to below 70MB/s.
For more details visit https://github.com/rfjakob/gocryptfs/issues/92 .
-sharedstorage Enable work-arounds so gocryptfs works better when the backing storage directory is concurrently accessed by multiple gocryptfs instances.
At the moment, it does two things:
1. Disable stat() caching so changes to the backing storage show up immediately.
2. Disable hard link tracking, as the inode numbers on the backing storage are not stable when files are deleted and re-created behind our back.  This would otherwise produce strange “file does not exist” and other errors.
When “-sharedstorage” is active, performance is reduced and hard links cannot be created.
Even with this flag set, you may hit occasional problems.  Running gocryptfs on shared storage does not receive as much testing as the usual (exclusive) use-case.  Please test your workload in advance and report any problems you may hit.
More info: https://github.com/rfjakob/gocryptfs/issues/156
-suid, -nosuid Enable (-suid) or disable (-nosuid) suid and sgid executables in a gocryptfs mount (default: -nosuid).  If both are specified, -nosuid takes precedence.  You need root permissions to use -suid.
-zerokey Use all-zero dummy master key.  This options is only intended for automated testing as it does not provide any security.
Options that apply to more than one action are listed below.  Each options lists where it is applicable.  Again, usually you don’t need any.
-config string Use specified config file instead of CIPHERDIR/gocryptfs.conf.
Applies to: all actions that use a config file: mount, -fsck, -passwd, -info, -init.
-cpuprofile string Write cpu profile to specified file.
Applies to: all actions.
-d, -debug Enable debug output.
-extpass CMD [-extpass ARG1 ...] Use an external program (like ssh-askpass) for the password prompt.  The program should return the password on stdout, a trailing newline is stripped by gocryptfs.  If you just want to read from a password file, see -passfile.
When -extpass is specified once, the string argument will be split on spaces.  For example, -extpass "md5sum my password.txt" will be executed as "md5sum" "my" "password.txt", which is NOT what you want.
Specify -extpass twice or more to use the string arguments as-is.  For example, you DO want to call md5sum like this: -extpass "md5sum" -extpass "my password.txt".
If you want to prevent splitting on spaces but don’t want to pass arguments to your program, use "--", which is accepted by most programs: -extpass "my program" -extpass "--"
Applies to: all actions that ask for a password.
-fido2 DEVICE_PATH Use a FIDO2 token to initialize and unlock the filesystem.  Use “fido2-token -L” to obtain the FIDO2 token device path.
-masterkey string Use a explicit master key specified on the command line or, if the special value “stdin” is used, read the masterkey from stdin, instead of reading the config file and asking for the decryption password.
Note that the command line, and with it the master key, is visible to anybody on the machine who can execute “ps -auxwww”.  Use “-masterkey=stdin” to avoid that risk.
The masterkey option is meant as a recovery option for emergencies, such as if you have forgotten the password or lost the config file.
Even if a config file exists, it will not be used.  All non-standard settings have to be passed on the command line: -aessiv when you mount a filesystem that was created using reverse mode, or -plaintextnames for a filesystem that was created with that option.
-masterkey=6f717d8b-6b5f8e8a-fd0aa206-778ec093-62c5669b-abd229cd-241e00cd-b4d6713d -masterkey=stdin
-memprofile string Write memory profile to the specified file.  This is useful when debugging memory usage of gocryptfs.
-o COMMA-SEPARATED-OPTIONS For compatibility with mount(1), options are also accepted as “-o COMMA- SEPARATED-OPTIONS” at the end of the command line.  For example, “-o q,zerokey” is equivalent to passing “-q -zerokey”.
Note that you can only use options that are understood by gocryptfs with “-o”.  If you want to pass special flags to the kernel, you should use “-ko” (kernel option).  This is different in libfuse-based filesystems, that automatically pass any “-o” options they do not understand along to the kernel.
gocryptfs /tmp/foo /tmp/bar -o q,zerokey
-openssl bool/“auto” Use OpenSSL instead of built-in Go crypto (default “auto”).  Using built- in crypto is 4x slower unless your CPU has AES instructions and you are using Go 1.6+.  In mode “auto”, gocrypts chooses the faster option.
-passfile FILE [-passfile FILE2 ...] Read password from the specified plain text file.  The file should contain exactly one line (do not use binary files!).  A warning will be printed if there is more than one line, and only the first line will be used.  A single trailing newline is allowed and does not cause a warning.
Pass this option multiple times to read the first line from multiple files.  They are concatenated for the effective password.
echo hello > hello.txt echo word > world.txt gocryptfs -passfile hello.txt -passfile world.txt
The effective password will be “helloworld”.
-q, -quiet Quiet - silence informational messages.
-trace string Write execution trace to file.  View the trace using “go tool trace FILE”.
-wpanic When encountering a warning, panic and exit immediately.  This is useful in regression testing.
-- Stop option parsing.  Helpful when CIPHERDIR may start with a dash “-”.
In reverse mode, it is possible to exclude files from the encrypted view, using the -exclude, -exclude-wildcard and -exclude-from options.
-exclude matches complete paths, so -exclude file.txt only excludes a file named file.txt in the root of the mounted filesystem; files named file.txt in subdirectories are still visible.  Wildcards are NOT supported.  This option is kept for compatibility with the behavior up to version 1.6.x.  New users should use -exclude-wildcard instead.
-exclude-wildcard uses gitignore syntax and matches files anywhere, so -exclude-wildcard file.txt excludes files named file.txt in any directory.  If you want to match complete paths, you can prefix the filename with a /: -exclude-wildcard /file.txt excludes only file.txt in the root of the mounted filesystem.
If there are many exclusions, you can use -exclude-from to read gitignore patterns from a file.  As with -exclude-wildcard, use a leading / to match complete paths.
The rules for exclusion are that of gitignore (https://git- scm.com/docs/gitignore#_pattern_format).  In short:
1. A blank line matches no files, so it can serve as a separator for readability.
2. A line starting with # serves as a comment.  Put a backslash (\) in front of the first hash for patterns that begin with a hash.
3. Trailing spaces are ignored unless they are quoted with backslash (\).
4. An optional prefix ! negates the pattern; any matching file excluded by a previous pattern will become included again.  It is not possible to re-include a file if a parent directory of that file is excluded. Put a backslash (\) in front of the first ! for patterns that begin with a literal !, for example, \!important!.txt.
5. If the pattern ends with a slash, it is removed for the purpose of the following description, but it would only find a match with a directory.  In other words, foo/ will match a directory foo and paths underneath it, but will not match a regular file or a symbolic link foo.
6. If the pattern does not contain a slash /, it is treated as a shell glob pattern and checked for a match against the pathname relative to the root of the mounted filesystem.
7. Otherwise, the pattern is treated as a shell glob suitable for consumption by fnmatch(3) with the FNM_PATHNAME flag: wildcards in the pattern will not match a / in the pathname.  For example, Documentation/*.html matches Documentation/git.html but not Documentation/ppc/ppc.html or tools/perf/Documentation/perf.html.
8. A leading slash matches the beginning of the pathname.  For example, /*.c matches cat-file.c but not mozilla-sha1/sha1.c.
9. Two consecutive asterisks (**) in patterns matched against full pathname may have special meaning:
i. A leading ** followed by a slash means match in all directories. For example, **/foo matches file or directory foo anywhere, the same as pattern foo.  **/foo/bar matches file or directory bar anywhere that is directly under directory foo.
ii. A trailing /** matches everything inside.  For example, abc/** matches all files inside directory abc, with infinite depth.
iii. A slash followed by two consecutive asterisks then a slash matches zero or more directories.  For example, a/**/b matches a/b, a/x/b, a/x/y/b and so on.
iv. Other consecutive asterisks are considered invalid.
Init Create an encrypted filesystem in directory “mydir.crypt”, mount it on “mydir”:
mkdir mydir.crypt mydir gocryptfs -init mydir.crypt gocryptfs mydir.crypt mydir
Mount Mount an encrypted view of joe’s home directory using reverse mode:
mkdir /home/joe.crypt gocryptfs -init -reverse /home/joe gocryptfs -reverse /home/joe /home/joe.crypt
fstab Adding this line to /etc/fstab will mount /tmp/cipher to /tmp/plain on boot, using the password in /tmp/passfile.  Use sudo mount -av to test the line without having to reboot.  Adjust the gocryptfs path acc.  to the output of the command which gocryptfs.  Do use the nofail option to prevent an unbootable system if the gocryptfs mount fails (see the -nofail option for details).
/tmp/cipher /tmp/plain fuse./usr/local/bin/gocryptfs nofail,allow_other,passfile=/tmp/password 0 0
0: success 6: CIPHERDIR is not an empty directory (on “-init”) 10: MOUNTPOINT is not an empty directory 12: password incorrect 22: password is empty (on “-init”) 23: could not read gocryptfs.conf 24: could not write gocryptfs.conf (on “-init” or “-password”) 26: fsck found errors other: please check the error message
See also: https://github.com/rfjakob/gocryptfs/blob/master/internal/exitcodes/exitcodes.go
mount(2) fuse(8) fallocate(2) encfs(1) gitignore(5)
github.com/rfjakob.
docker-ps - List containers
docker ps [OPTIONS]
Alias for docker container ls.
-f, --filter=      Filter output based on conditions provided
--format=""      Pretty-print containers using a Go template
-h, --help[=false]      help for ps
-n, --last=-1      Show n last created containers (includes all states)
-l, --latest[=false]      Show the latest created container (includes all states)
--no-trunc[=false]      Don't truncate output
-q, --quiet[=false]      Only display container IDs
-s, --size[=false]      Display total file sizes
CSVSORT(1)                           csvkit                           CSVSORT(1)
csvsort - csvsort Documentation
Sort CSV files. Like the Unix “sort” command, but for tabular data:
usage: csvsort [-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] [-n] [-c COLUMNS] [-r] [-y SNIFF_LIMIT] [-I] [FILE]
Sort CSV files. Like the Unix "sort" command, but for tabular data.
optional arguments: -h, --help            show this help message and exit -n, --names           Display column names and indices from the input CSV and exit. -c COLUMNS, --columns COLUMNS A comma separated list of column indices, names or ranges to sort by, e.g. "1,id,3-5". Defaults to all columns. -r, --reverse         Sort in descending order. -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 when parsing the input.
NOTE: If your file is large, try sort -t, file.csv instead.
Sort the veteran’s education benefits table by the “TOTAL” column:
csvsort -c 9 examples/realdata/FY09_EDU_Recipients_by_State.csv
View the five states with the most individuals claiming veteran’s education benefits:
csvcut -c 1,9 examples/realdata/FY09_EDU_Recipients_by_State.csv | csvsort -r -c 2 | head -n 5
STDBUF(1)                         User Commands                        STDBUF(1)
stdbuf - Run COMMAND, with modified buffering operations for its standard streams.
stdbuf OPTION... COMMAND
Run COMMAND, with modified buffering operations for its standard streams.
-i, --input=MODE adjust standard input stream buffering
-o, --output=MODE adjust standard output stream buffering
-e, --error=MODE adjust standard error stream buffering
If MODE is 'L' the corresponding stream will be line buffered.  This option is invalid with standard input.
If MODE is '0' the corresponding stream will be unbuffered.
Otherwise MODE is a number which may be followed by one of the following: KB 1000, K 1024, MB 1000*1000, M 1024*1024, and so on for G, T, P, E, Z, Y.  Binary prefixes can be used, too: KiB=K, MiB=M, and so on.  In this case the corresponding stream will be fully buffered with the buffer size set to MODE bytes.
NOTE: If COMMAND adjusts the buffering of its standard streams ('tee' does for example) then that will override corresponding changes by 'stdbuf'.  Also some filters (like 'dd' and 'cat' etc.) don't use streams for I/O, and are thus unaffected by 'stdbuf' settings.
tail -f access.log | stdbuf -oL cut -d ' ' -f1 | uniq This will immediately display unique entries from access.log
On GLIBC platforms, specifying a buffer size, i.e., using fully buffered mode will result in undefined operation.
Full documentation <https://www.gnu.org/software/coreutils/stdbuf> or available locally via: info '(coreutils) stdbuf invocation'
PARQUET-TOOLS(1)                  parquet-tools                 PARQUET-TOOLS(1)
parquet-tools - Java based command line tool that aid in the inspection of Parquet files.
parquet-tools
--debug Disable color output even if supported.
-h,--help Show this help string
--no-color Disable color output even if supported.
usage: parquet-tools cat [OPTIONS...] [INPUT...]
usage: parquet-tools head [OPTIONS...] [INPUT...]
usage: parquet-tools schema [OPTIONS...] [INPUT...]
usage: parquet-tools meta [OPTIONS...] [INPUT...]
usage: parquet-tools dump [OPTIONS...] [INPUT...]
parquet-tools cat [option...] <input>
Where <input> is the parquet file to print to stdout.
parquet-tools head [option...] <input>
-n,--records <arg> The number of records to show (default: 5)
parquet-tools schema [option...] <input>
where <input> is the parquet file containing the schema to show.
-d,--detailed <arg> Show detailed information about the schema.
parquet-tools meta [option...] <input>
where <input> is the parquet file to print to stdout.
parquet-tools dump [option...] <input>
-c,--column <arg> Dump only the given column, can be specified more than once.
-d,--disable-data Do not dump column data.
-m,--disable-meta Do not dump row group and page metadata.
BANNER(6)                       BSD Games Manual                       BANNER(6)
banner â€” print large banner on printer
banner [-d] [-t] [-w width] message ...
Banner prints a large, high quality banner on the standard output.  If the message is omitted, it prompts for and reads one line of its standard input.
The output should be printed on paper of the appropriate width, with no breaks between the pages.
-d      Enable debug.
-t      Enable trace.
-w width Change the output from a width of 132 to width, suitable for a narrow terminal.
Several ASCII characters are not defined, notably <, >, [, ], \, ^, _, {, }, |, and ~.  Also, the characters ", ', and & are funny looking (but in a useful way.)
The -w option is implemented by skipping some rows and columns.  The smaller it gets, the grainier the output.  Sometimes it runs letters together.
Mark Horton
CAT(1P)                     POSIX Programmer's Manual                    CAT(1P)
cat — concatenate and print files
cat [-u] [file...]
The cat utility shall read files in sequence and shall write their contents to the standard output in the same sequence.
The cat utility shall conform to the Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines.
-u        Write bytes from the input file to the standard output without delay as each is read.
file      A pathname of an input file. If no file operands are specified, the standard input shall be used. If a file is '-', the cat utility shall read from the standard input at that point in the sequence. The cat utility shall not close and reopen standard input when it is referenced in this way, but shall accept multiple occurrences of '-' as a file operand.
The following environment variables shall affect the execution of cat:
The standard output shall contain the sequence of bytes read from the input files. Nothing else shall be written to the standard output.  If the standard output is a regular file, and is the same file as any of the input file operands, the implementation may treat this as an error.
The -u option has value in prototyping non-blocking reads from FIFOs. The intent is to support the following sequence:
mkfifo foo cat -u foo > /dev/tty13 & cat -u > foo
It is unspecified whether standard output is or is not buffered in the default case. This is sometimes of interest when standard output is associated with a terminal, since buffering may delay the output. The presence of the -u option guarantees that unbuffered I/O is available. It is implementation-defined whether the cat utility buffers output if the -u option is not specified. Traditionally, the -u option is implemented using the equivalent of the setvbuf() function defined in the System Interfaces volume of POSIX.1‐2017.
cat myfile
writes the contents of the file myfile to standard output.
cat doc1 doc2 > doc.all
concatenates the files doc1 and doc2 and writes the result to doc.all.
Because of the shell language mechanism used to perform output redirection, a command such as this:
cat doc doc.end > doc
causes the original data in doc to be lost before cat even begins execution. This is true whether the cat command fails with an error or silently succeeds (the specification allows both behaviors). In order to append the contents of doc.end without losing the original contents of doc, this command should be used instead:
cat doc.end >> doc
cat start - middle - end > file
when standard input is a terminal, gets two arbitrary pieces of input from the terminal with a single invocation of cat.  Note, however, that if standard input is a regular file, this would be equivalent to the command:
cat start - middle /dev/null end > file
because the entire contents of the file would be consumed by cat the first time '-' was used as a file operand and an end-of-file condition would be detected immediately when '-' was referenced the second time.
Historical versions of the cat utility include the -e, -t, and -v, options which permit the ends of lines, <tab> characters, and invisible characters, respectively, to be rendered visible in the output. The standard developers omitted these options because they provide too fine a degree of control over what is made visible, and similar output can be obtained using a command such as:
sed -n l pathname
The latter also has the advantage that its output is unambiguous, whereas the output of historical cat -etv is not.
The -s option was omitted because it corresponds to different functions in BSD and System V-based systems. The BSD -s option to squeeze blank lines can be accomplished by the shell script shown in the following example:
sed -n ' # Write non-empty lines. /./   { p d } # Write a single empty line, then look for more empty lines. /^$/  p # Get next line, discard the held <newline> (empty line), # and look for more empty lines. :Empty /^$/  { N s/.// b Empty } # Write the non-empty line before going back to search # for the first in a set of empty lines. p '
The System V -s option to silence error messages can be accomplished by redirecting the standard error. Note that the BSD documentation for cat uses the term ``blank line'' to mean the same as the POSIX ``empty line'': a line consisting only of a <newline>.
The BSD -n option was omitted because similar functionality can be obtained from the -n option of the pr utility.
The System Interfaces volume of POSIX.1‐2017, setvbuf()
NPM-NAME(1)                       User Commands                      NPM-NAME(1)
npm-name - check whether a package or organization name is available on npm
npm-name name [...]
npm-name chalk ✖ chalk is unavailable npm-name abc123 ⚠ abc123 is squatted npm-name unicorn-cake ✔ unicorn-cake is available npm-name @ava ✖ @ava is unavailable npm-name @abc123 ✔ @abc123 is available npm-name @sindresorhus/is unicorn-cake ✖ @sindresorhus/is is unavailable ✔ unicorn-cake is available
Exits with code 0 when all names are available or 2 when any names are taken.
lsusb(8)                       Linux USB Utilities                      lsusb(8)
lsusb - list USB devices
lsusb [ options ]
lsusb is a utility for displaying information about USB buses in the system and the devices connected to them.
-v, --verbose Tells lsusb to be verbose and display detailed information about the devices shown.  This includes configuration descriptors for the device's current speed.  Class descriptors will be shown, when available, for USB device classes including hub, audio, HID, communications, and chipcard.
-s [[bus]:][devnum] Show only devices in specified bus and/or devnum.  Both ID's are given in decimal and may be omitted.
-d [vendor]:[product] Show only devices with the specified vendor and product ID.  Both ID's are given in hexadecimal.
-D device Do not scan the /dev/bus/usb directory, instead display only information about the device whose device file is given.  The device file should be something like /dev/bus/usb/001/001.  This option displays detailed information like the v option; you must be root to do this.
-t     Tells lsusb to dump the physical USB device hierarchy as a tree. This overrides the v option.
-V, --version Print  version information on standard output, then exit successfully.
If the specified device is not found, a non-zero exit code is returned.
/var/lib/usbutils/usb.ids A list of all known USB ID's (vendors, products, classes, subclasses and protocols).
lspci(8), usbview(8).
Thomas Sailer, <sailer@ife.ee.ethz.ch>.
COMPLETE(3)                 Library Functions Manual                 COMPLETE(3)
complete, freecompletion - file name completion
#include <u.h> #include <libc.h> #include <complete.h>
typedef struct CompletionCompletion; struct Completion{ uchar advance; uchar complete; char *string; int nmatch; int nfile; char **filename; };
Completion* complete(char *dir, char *s);
void freecompletion(Completion *c);
The complete function implements file name completion.  Given a directory dir and a string s, it returns an analysis of the file names in that directory that begin with the string s.  The fields nmatch and nfile will be set to the number of files that match the prefix and filename will be filled in with their names.  If the file named is a directory, a slash character will be appended to it.
If no files match the string, nmatch will be zero, but complete will return the full set of files in the directory, with nfile set to their number.
The flag advance reports whether the string s can be extended without changing the set of files that match.  If true, string will be set to the extension; that is, the value of string may be appended to s by the caller to extend the embryonic file name unambiguously.
The flag complete reports whether the extended file name uniquely identifies a file.  If true, string will be suffixed with a blank, or a slash and a blank, depending on whether the resulting file name identifies a plain file or a directory.
The freecompletion function frees a Completion structure and its contents.
In and file name completion is triggered by a control-F character or an Insert character.
/src/libcomplete
The complete function returns a null pointer and sets errstr if the directory is unreadable or there is some other error.
The behavior of file name completion should be controlled by the plumber.
GIT-BROWSE(1)                      Git Extras                      GIT-BROWSE(1)
git-browse -
git-browse [remote_name]
Opens the current git repository website in your default web browser.
<remote_name>
The name of the remote you wish to browse to. Defaults to the first remote if not specified.
$ git browse
$ git browse upstream
Written by Mark Pitman <https://github.com/mapitman>
EVAL(1P)                    POSIX Programmer's Manual                   EVAL(1P)
eval â€” construct command by concatenating arguments
eval [argument...]
The eval utility shall construct a command by concatenating arguments together, separating each with a <space> character.  The constructed command shall be read and executed by the shell.
If there are no arguments, or only null arguments, eval shall return a zero exit status; otherwise, it shall return the exit status of the command defined by the string of concatenated arguments separated by <space> characters, or a non-zero exit status if the concatenation could not be parsed as a command and the shell is interactive (and therefore did not abort).
Since eval is not required to recognize the "--" end of options delimiter, in cases where the argument(s) to eval might begin with '-' it is recommended that the first argument is prefixed by a string that will not alter the commands to be executed, such as a <space> character:
eval " $commands"
eval " $(some_command)"
foo=10 x=foo y='$'$x echo $y $foo eval y='$'$x echo $y 10
This standard allows, but does not require, eval to recognize "--". Although this means applications cannot use "--" to protect against options supported as an extension (or errors reported for unsupported options), the nature of the eval utility is such that other means can be used to provide this protection (see APPLICATION USAGE above).
babel(1)                     User's Reference Manual                    babel(1)
babel, obabel â€” a converter for chemistry and molecular modeling data files
babel [-H help-options] babel [OPTIONS] [-i input-type] infile [-o output-type] outfile
obabel [-H help-options] obabel [OPTIONS] [-i input-type | -: "SMILES-string"] infile [-o output-type] -O outfile
babel is a cross-platform program designed to interconvert between many file formats used in molecular modeling and computational chemistry and related areas.
obabel and babel are slightly different. The first is closer to the normal Unix convention for commandline programs and more flexible when the user needs to specify parameter values on options. With babel this only works when the option is the last on the line; with obabel no such restriction applies. It further has a shortcut for entering SMILES strings, which can be used in place of an input file.
Open Babel is also a complete programmers toolkit for developing chemistry software. For more information, se the Open Babel web pages <http://openbabel.org/>.
If only input and output files are given, Open Babel will guess the file type from the filename extension.
-: "SMILES-string" Enter SMILES string and use it in place of an input file. The SMILES string should be enclosed in quotation marks. More than one can be used, and a molecule title can be included if enclosed in quotes.
-a options Format-specific input options. See -H format-ID for options allowed by a particular format
--addtotitle Append text to the current molecule title
--addformula Append the molecular formula after the current molecule title
-b    Convert dative bonds: e.g., [N+]([O-])=O to N(=O)=O
-c    Center atomic coordinates at (0,0,0)
-C    Combine molecules in first file with others having the same name
-e    Continue after errors
-d    Delete Hydrogens
---errorlevel 2 Filter the level of errors and warnings displayed: 1 = critical errors only 2 = include warnings too (default) 3 = include informational messages too 4 = include "audit log" messages of changes to data 5 = include debugging messages too
-f #  For multiple entry input, start import with molecule # as the first entry
-F    Output the available fingerprint types
-h    Add hydrogens
-H    Output usage information
-H format-ID Output formatting information and options for format specified
-Hall Output formatting information and options for all formats
-i<format-ID> Specifies input format, see below for the available formats
--join Join all input molecules into a single output molecule entry
-k    Translate computational chemistry modeling keywords (e.g., GAMESS and Gaussian)
-m    Produce multiple output files, to allow: -   Splitting one input file - put each molecule into consecutively numbered output files -   Batch conversion - convert each of multiple input files into a specified output format
-l #  For multiple entry input, stop import with molecule # as the last entry
-o format-ID Specifies output format, see below for the available formats
-O outfile Specify the output file. This option applies to obabel only.
-p    Add Hydrogens appropriate for pH (use transforms in phmodel.txt)
--property Add or replace a property (e.g., in an MDL SD file)
-s SMARTS Convert only molecules matching the SMARTS pattern specified
--separate Separate disconnected fragments into individual molecular records
-t    All input files describe a single molecule
--title title Add or replace molecular title
-x options Format-specific output options. See -H format-ID for options allowed by a particular format
-v SMARTS Convert only molecules NOT matching SMARTS pattern specified
-V    Output version number and exit
-z    Compress the output with gzip
Individual file formats may have additional formatting options.
Input format options are preceded by 'a', e.g. -as
Output format options are preceded by 'x', e.g. -xn
For further specific information and options, use -H<format-type> e.g., -Hcml
Standard conversion: babel -ixyz ethanol.xyz -opdb ethanol.pdb Conversion from a SMI file in STDIN to a Mol2 file written to STDOUT: babel -ismi -omol2 Split a multi-molecule file into new1.smi, new2.smi, etc.: babel infile.mol new.smi -m
obenergy(1), obfit(1), obgrep(1), obminimize(1), obprop(1), obrotate(1), obrotamer(1).  The web pages for Open Babel can be found at: <http://openbabel.org/>
A cast of many, including the currrent maintainers Geoff Hutchison, Chris Morley, Michael Banck, and innumerable others who have contributed fixes and additions.  For more contributors to Open Babel, see <http://openbabel.org/wiki/THANKS>
Copyright (C) 1998-2001 by OpenEye Scientific Software, Inc. Some portions Copyright (C) 2001-2007 by Geoffrey R. Hutchison
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation version 2 of the License.
GPG-ZIP(1)                    GNU Privacy Guard 2.1                   GPG-ZIP(1)
gpg-zip - Encrypt or sign files into an archive
gpg-zip [options] filename1 [ filename2, ... ] directory1 [ directory2, ... ]
gpg-zip encrypts or signs files into an archive.  It is an gpg-ized tar using the same format as used by PGP's PGP Zip.
gpg-zip understands these options:
--encrypt
-e     Encrypt data.  This option may be combined with --symmetric (for output that may be decrypted via a secret key or a passphrase).
--decrypt
-d     Decrypt data.
--symmetric
-c     Encrypt with a symmetric cipher using a passphrase.  The default symmetric cipher used is CAST5, but may be chosen with the --cipher-algo option to gpg.
--sign
-s     Make a signature.  See gpg.
--recipient user
-r user Encrypt for user id user. See gpg.
--local-user user
-u user Use user as the key to sign with.  See gpg.
--list-archive List the contents of the specified archive.
--output file
-o file Write output to specified file file.