Gestionnaire de fichiers - Editer - /home/wwgoat/public_html/blog/README.tar
Arrière
etc/httpd/conf.d/README 0000644 00000000556 14720760232 0010502 0 ustar 00 This directory holds configuration files for the Apache HTTP Server; any files in this directory which have the ".conf" extension will be processed as httpd configuration files. The directory is used in addition to the directory /etc/httpd/conf.modules.d/, which contains configuration files necessary to load modules. Files are processed in alphabetical order. etc/pki/ca-trust/extracted/README 0000644 00000001060 14721003307 0012501 0 ustar 00 This directory /etc/pki/ca-trust/extracted/ contains CA certificate bundle files which are automatically created. If your application isn't able to load the PKCS#11 module p11-kit-trust.so, then you can use these files in your application to load a list of global root CA certificates. Please never manually edit the files stored in this directory, because your changes will be lost and the files automatically overwritten, each time the update-ca-trust command gets executed. Please refer to the update-ca-trust(8) manual page for additional information. usr/share/apache2/error/README 0000644 00000004333 14721004427 0011777 0 ustar 00 Multi Language Custom Error Documents ------------------------------------- The 'error' directory contains HTTP error messages in multiple languages. If the preferred language of a client is available it is selected automatically via the MultiViews feature. This feature is enabled by default via the Options, Language and ErrorDocument directives. You may configure the design and markup of the documents by modifying the HTML files in the directory 'error/include'. Supported Languages: +-----------------------+------------------------------------------+ | Language | Contributed by | +-----------------------+------------------------------------------+ | Brazilian (pt-br) | Ricardo Leite | | Chinese (zh-cn/zh-tw) | CodeingBoy & popcorner | | Czech (cs) | Marcel Kolaja | | Dutch (nl) | Peter Van Biesen | | English (en) | Lars Eilebrecht | | French (fr) | Cecile de Crecy | | German (de) | Lars Eilebrecht | | Italian (it) | Luigi Rosa | | Japanese (ja) | TAKAHASHI Makoto | | Korean (ko) | Jaeho Shin | | Norwegian Bokmål (nb) | Tom Fredrik Klaussen | | Polish (pl) | Tomasz Kepczynski | | Romanian (ro) | Andrei Besleaga | | Russian (ru) | Alexander Gaganashvili | | Serbian (sr) | Nikola Smolenski | | Spanish (es) | Karla Quintero | | Swedish (sv) | Thomas Sjögren | | Turkish (tr) | Emre Sokullu & Nilgün Belma Bugüner | | Irish (ga) | Noirin Shirley | +-----------------------+------------------------------------------+ (Please see http://httpd.apache.org/docs-project/ if you would like to contribute the pages in an additional language.) usr/share/doc/systemd/README 0000644 00000022445 14721013447 0011606 0 ustar 00 systemd System and Service Manager DETAILS: http://0pointer.de/blog/projects/systemd.html WEB SITE: http://www.freedesktop.org/wiki/Software/systemd GIT: git://anongit.freedesktop.org/systemd/systemd ssh://git.freedesktop.org/git/systemd/systemd GITWEB: http://cgit.freedesktop.org/systemd/systemd MAILING LIST: http://lists.freedesktop.org/mailman/listinfo/systemd-devel http://lists.freedesktop.org/mailman/listinfo/systemd-commits IRC: #systemd on irc.freenode.org BUG REPORTS: https://bugs.freedesktop.org/enter_bug.cgi?product=systemd AUTHOR: Lennart Poettering Kay Sievers ...and many others LICENSE: LGPLv2.1+ for all code - except sd-readahead.[ch] which is MIT - except src/shared/MurmurHash2.c which is Public Domain - except src/shared/siphash24.c which is CC0 Public Domain - except src/journal/lookup3.c which is Public Domain - except src/udev/* which is (currently still) GPLv2, GPLv2+ REQUIREMENTS: Linux kernel >= 3.7 Linux kernel >= 3.8 for Smack support Kernel Config Options: CONFIG_DEVTMPFS CONFIG_CGROUPS (it is OK to disable all controllers) CONFIG_INOTIFY_USER CONFIG_SIGNALFD CONFIG_TIMERFD CONFIG_EPOLL CONFIG_NET CONFIG_SYSFS CONFIG_PROC_FS CONFIG_FHANDLE (libudev, mount and bind mount handling) udev will fail to work with the legacy sysfs layout: CONFIG_SYSFS_DEPRECATED=n Legacy hotplug slows down the system and confuses udev: CONFIG_UEVENT_HELPER_PATH="" Userspace firmware loading is not supported and should be disabled in the kernel: CONFIG_FW_LOADER_USER_HELPER=n Some udev rules and virtualization detection relies on it: CONFIG_DMIID Support for some SCSI devices serial number retrieval, to create additional symlinks in /dev/disk/ and /dev/tape: CONFIG_BLK_DEV_BSG Required for PrivateNetwork and PrivateDevices in service units: CONFIG_NET_NS CONFIG_DEVPTS_MULTIPLE_INSTANCES Note that systemd-localed.service and other systemd units use PrivateNetwork and PrivateDevices so this is effectively required. Optional but strongly recommended: CONFIG_IPV6 CONFIG_AUTOFS4_FS CONFIG_TMPFS_XATTR CONFIG_{TMPFS,EXT4,XFS,BTRFS_FS,...}_POSIX_ACL CONFIG_SECCOMP Required for CPUShares in resource control unit settings CONFIG_CGROUP_SCHED CONFIG_FAIR_GROUP_SCHED Required for CPUQuota in resource control unit settings CONFIG_CFS_BANDWIDTH For systemd-bootchart, several proc debug interfaces are required: CONFIG_SCHEDSTATS CONFIG_SCHED_DEBUG For UEFI systems: CONFIG_EFIVAR_FS CONFIG_EFI_PARTITION Note that kernel auditing is broken when used with systemd's container code. When using systemd in conjunction with containers, please make sure to either turn off auditing at runtime using the kernel command line option "audit=0", or turn it off at kernel compile time using: CONFIG_AUDIT=n If systemd is compiled with libseccomp support on architectures which do not use socketcall() and where seccomp is supported (this effectively means x86-64 and ARM, but excludes 32-bit x86!), then nspawn will now install a work-around seccomp filter that makes containers boot even with audit being enabled. This works correctly only on kernels 3.14 and newer though. TL;DR: turn audit off, still. glibc >= 2.14 libcap libmount >= 2.20 (from util-linux) libseccomp >= 1.0.0 (optional) libblkid >= 2.20 (from util-linux) (optional) libkmod >= 15 (optional) PAM >= 1.1.2 (optional) libcryptsetup (optional) libaudit (optional) libacl (optional) libselinux (optional) liblzma (optional) liblz4 >= 119 (optional) libgcrypt (optional) libqrencode (optional) libmicrohttpd (optional) libpython (optional) libidn (optional) gobject-introspection > 1.40.0 (optional) elfutils >= 158 (optional) make, gcc, and similar tools During runtime, you need the following additional dependencies: util-linux >= v2.19 (requires fsck -l, agetty -s), v2.21 required for tests in test/ dbus >= 1.4.0 (strictly speaking optional, but recommended) dracut (optional) PolicyKit (optional) When building from git, you need the following additional dependencies: docbook-xsl xsltproc automake autoconf libtool intltool gperf gtkdocize (optional) python (optional) python-lxml (optional, but required to build the indices) sphinx (optional) When systemd-hostnamed is used, it is strongly recommended to install nss-myhostname to ensure that, in a world of dynamically changing hostnames, the hostname stays resolvable under all circumstances. In fact, systemd-hostnamed will warn if nss-myhostname is not installed. To build HTML documentation for python-systemd using sphinx, please first install systemd (using 'make install'), and then invoke sphinx-build with 'make sphinx-<target>', with <target> being 'html' or 'latexpdf'. If using DESTDIR for installation, pass the same DESTDIR to 'make sphinx-html' invocation. USERS AND GROUPS: Default udev rules use the following standard system group names, which need to be resolvable by getgrnam() at any time, even in the very early boot stages, where no other databases and network are available: audio, cdrom, dialout, disk, input, kmem, lp, tape, tty, video During runtime, the journal daemon requires the "systemd-journal" system group to exist. New journal files will be readable by this group (but not writable), which may be used to grant specific users read access. In addition, system groups "wheel" and "adm" will be given read-only access to journal files using systemd-tmpfiles.service. The journal gateway daemon requires the "systemd-journal-gateway" system user and group to exist. During execution this network facing service will drop privileges and assume this uid/gid for security reasons. Similarly, the NTP daemon requires the "systemd-timesync" system user and group to exist. Similarly, the network management daemon requires the "systemd-network" system user and group to exist. Similarly, the name resolution daemon requires the "systemd-resolve" system user and group to exist. NSS: systemd ships with three NSS modules: nss-myhostname resolves the local hostname to locally configured IP addresses, as well as "localhost" to 127.0.0.1/::1. nss-resolve enables DNS resolution via the systemd-resolved DNS/LLMNR caching stub resolver "systemd-resolved". nss-mymachines enables resolution of all local containers registered with machined to their respective IP addresses. To make use of these NSS modules, please add them to the "hosts: " line in /etc/nsswitch.conf. The "resolve" module should replace the glibc "dns" module in this file. The three modules should be used in the following order: hosts: files mymachines resolve myhostname WARNINGS: systemd will warn you during boot if /etc/mtab is not a symlink to /proc/mounts. Please ensure that /etc/mtab is a proper symlink. systemd will warn you during boot if /usr is on a different file system than /. While in systemd itself very little will break if /usr is on a separate partition, many of its dependencies very likely will break sooner or later in one form or another. For example, udev rules tend to refer to binaries in /usr, binaries that link to libraries in /usr or binaries that refer to data files in /usr. Since these breakages are not always directly visible, systemd will warn about this, since this kind of file system setup is not really supported anymore by the basic set of Linux OS components. systemd requires that the /run mount point exists. systemd also requires that /var/run is a a symlink to /run. For more information on this issue consult http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken To run systemd under valgrind, compile with VALGRIND defined (e.g. ./configure CPPFLAGS='... -DVALGRIND=1'). Otherwise, false positives will be triggered by code which violates some rules but is actually safe. ENGINEERING AND CONSULTING SERVICES: ENDOCODE <https://endocode.com/> offers professional engineering and consulting services for systemd. Please contact Chris Kühl <chris@endocode.com> for more information. usr/share/doc/perl-Net-LibIDN-0.12/README 0000644 00000007646 14721013455 0013226 0 ustar 00 Net/LibIDN version 0.12 ======================= This module provides Perl bindings for GNU Libidn by Simon Josefsson (http://www.gnu.org/software/libidn/) in way that was heavily inspired by PHP bindings for the same library done by Turbo Fredriksson (http://php-idn.bayour.com/). INSTALLATION To install this module type the following: perl Makefile.PL [--with-libidn=<LIBPATH> --with-libidn-inc=<INCPATH> --disable-tld] make make test make install Installing under Cygwin: Sergei Koladka reports that the first make line above needs to be replaced by make LD_RUN_PATH="/usr/lib" LDLOADLIBS="/usr/lib/libidn.a \/usr/lib/libiconv.dll.a" assuming that Libidn was compiled with --prefix=/usr. You also will need to remove the >>die "This module requires GNU Libidn..."<<-line and manually set $libidn either to 2 or 1 depending on whether you have/want to use TLD checking support. DEPENDENCIES This module requires these other modules and libraries: GNU Libidn >=0.5.0 Linux hint: If Makefile.PL says that it cannot find GNU Libidn, even though you compiled/installed it, consider adding the location of the Libidn .so files to /etc/ld.so.conf. Also, take a look at the --with-libidn and --with-libidn-inc options. COPYRIGHT AND LICENCE Perl Module Net::LibIDN Copyright 2003-2009, Thomas Jacob, Internet24.de All rights reserved This program is free software; you can redistribute it and/or modify it under the terms of either: a) the GNU General Public License as published by the Free Software Foundation; either version 1, or (at your option) any later version, or b) the "Artistic License" which comes with this Kit. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See either the GNU General Public License or the Artistic License for more details. You should have received a copy of the Artistic License with this Kit, in the file named "Artistic". If not, I'll be glad to provide one. You should also have received a copy of the GNU General Public License along with this program in the file named "Copying". If not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA or visit their web page on the internet at http://www.gnu.org/copyleft/gpl.html. For those of you that choose to use the GNU General Public License, my interpretation of the GNU General Public License is that no Perl script falls under the terms of the GPL unless you explicitly put said script under the terms of the GPL yourself. Furthermore, any object code linked with perl does not automatically fall under the terms of the GPL, provided such object code only adds definitions of subroutines and variables, and does not otherwise impair the resulting interpreter from executing any standard Perl script. I consider linking in C subroutines in this manner to be the moral equivalent of defining subroutines in the Perl language itself. You may sell such an object file as proprietary provided that you provide or offer to provide the Perl source, as specified by the GNU General Public License. (This is merely an alternate way of specifying input to the program.) You may also sell a binary produced by the dumping of a running Perl script that belongs to you, provided that you provide or offer to provide the Perl source as specified by the GPL. (The fact that a Perl interpreter and your code are in the same binary file is, in this case, a form of mere aggregation.) This is my interpretation of the GPL. If you still have concerns or difficulties understanding my intent, feel free to contact me. Of course, the Artistic License spells all this out for your protection, so you may prefer to use that. usr/share/doc/perl-HTML-Form-6.03/README 0000644 00000041232 14721013463 0013100 0 ustar 00 NAME HTML::Form - Class that represents an HTML form element SYNOPSIS use HTML::Form; $form = HTML::Form->parse($html, $base_uri); $form->value(query => "Perl"); use LWP::UserAgent; $ua = LWP::UserAgent->new; $response = $ua->request($form->click); DESCRIPTION Objects of the `HTML::Form' class represents a single HTML `<form> ... </form>' instance. A form consists of a sequence of inputs that usually have names, and which can take on various values. The state of a form can be tweaked and it can then be asked to provide `HTTP::Request' objects that can be passed to the request() method of `LWP::UserAgent'. The following methods are available: @forms = HTML::Form->parse( $html_document, $base_uri ) @forms = HTML::Form->parse( $html_document, base => $base_uri, %opt ) @forms = HTML::Form->parse( $response, %opt ) The parse() class method will parse an HTML document and build up `HTML::Form' objects for each <form> element found. If called in scalar context only returns the first <form>. Returns an empty list if there are no forms to be found. The required arguments is the HTML document to parse ($html_document) and the URI used to retrieve the document ($base_uri). The base URI is needed to resolve relative action URIs. The provided HTML document should be a Unicode string (or US-ASCII). By default HTML::Form assumes that the original document was UTF-8 encoded and thus encode forms that don't specify an explict *accept-charset* as UTF-8. The charset assumed can be overridden by providing the `charset' option to parse(). It's a good idea to be explict about this parameter as well, thus the recommended simplest invocation becomes: my @forms = HTML::Form->parse( Encode::decode($encoding, $html_document_bytes), base => $base_uri, charset => $encoding, ); If the document was retrieved with LWP then the response object provide methods to obtain a proper value for `base' and `charset': my $ua = LWP::UserAgent->new; my $response = $ua->get("http://www.example.com/form.html"); my @forms = HTML::Form->parse($response->decoded_content, base => $response->base, charset => $response->content_charset, ); In fact, the parse() method can parse from an `HTTP::Response' object directly, so the example above can be more conveniently written as: my $ua = LWP::UserAgent->new; my $response = $ua->get("http://www.example.com/form.html"); my @forms = HTML::Form->parse($response); Note that any object that implements a decoded_content(), base() and content_charset() method with similar behaviour as `HTTP::Response' will do. Additional options might be passed in to control how the parse method behaves. The following are all the options currently recognized: `base => $uri' This is the URI used to retrive the original document. This option is not optional ;-) `charset => $str' Specify what charset the original document was encoded in. This is used as the default for accept_charset. If not provided this defaults to "UTF-8". `verbose => $bool' Warn (print messages to STDERR) about any bad HTML form constructs found. You can trap these with $SIG{__WARN__}. `strict => $bool' Initialize any form objects with the given strict attribute. $method = $form->method $form->method( $new_method ) This method is gets/sets the *method* name used for the `HTTP::Request' generated. It is a string like "GET" or "POST". $action = $form->action $form->action( $new_action ) This method gets/sets the URI which we want to apply the request *method* to. $enctype = $form->enctype $form->enctype( $new_enctype ) This method gets/sets the encoding type for the form data. It is a string like "application/x-www-form-urlencoded" or "multipart/form-data". $accept = $form->accept_charset $form->accept_charset( $new_accept ) This method gets/sets the list of charset encodings that the server processing the form accepts. Current implementation supports only one-element lists. Default value is "UNKNOWN" which we interpret as a request to use document charset as specified by the 'charset' parameter of the parse() method. $value = $form->attr( $name ) $form->attr( $name, $new_value ) This method give access to the original HTML attributes of the <form> tag. The $name should always be passed in lower case. Example: @f = HTML::Form->parse( $html, $foo ); @f = grep $_->attr("id") eq "foo", @f; die "No form named 'foo' found" unless @f; $foo = shift @f; $bool = $form->strict $form->strict( $bool ) Gets/sets the strict attribute of a form. If the strict is turned on the methods that change values of the form will croak if you try to set illegal values or modify readonly fields. The default is not to be strict. @inputs = $form->inputs This method returns the list of inputs in the form. If called in scalar context it returns the number of inputs contained in the form. See INPUTS for what methods are available for the input objects returned. $input = $form->find_input( $selector ) $input = $form->find_input( $selector, $type ) $input = $form->find_input( $selector, $type, $index ) This method is used to locate specific inputs within the form. All inputs that match the arguments given are returned. In scalar context only the first is returned, or `undef' if none match. If $selector is specified, then the input's name, id, class attribute must match. A selector prefixed with '#' must match the id attribute of the input. A selector prefixed with '.' matches the class attribute. A selector prefixed with '^' or with no prefix matches the name attribute. If $type is specified, then the input must have the specified type. The following type names are used: "text", "password", "hidden", "textarea", "file", "image", "submit", "radio", "checkbox" and "option". The $index is the sequence number of the input matched where 1 is the first. If combined with $name and/or $type then it select the *n*th input with the given name and/or type. $value = $form->value( $selector ) $form->value( $selector, $new_value ) The value() method can be used to get/set the value of some input. If strict is enabled and no input has the indicated name, then this method will croak. If multiple inputs have the same name, only the first one will be affected. The call: $form->value('foo') is basically a short-hand for: $form->find_input('foo')->value; @names = $form->param @values = $form->param( $name ) $form->param( $name, $value, ... ) $form->param( $name, \@values ) Alternative interface to examining and setting the values of the form. If called without arguments then it returns the names of all the inputs in the form. The names will not repeat even if multiple inputs have the same name. In scalar context the number of different names is returned. If called with a single argument then it returns the value or values of inputs with the given name. If called in scalar context only the first value is returned. If no input exists with the given name, then `undef' is returned. If called with 2 or more arguments then it will set values of the named inputs. This form will croak if no inputs have the given name or if any of the values provided does not fit. Values can also be provided as a reference to an array. This form will allow unsetting all values with the given name as well. This interface resembles that of the param() function of the CGI module. $form->try_others( \&callback ) This method will iterate over all permutations of unvisited enumerated values (<select>, <radio>, <checkbox>) and invoke the callback for each. The callback is passed the $form as argument. The return value from the callback is ignored and the try_others() method itself does not return anything. $request = $form->make_request Will return an `HTTP::Request' object that reflects the current setting of the form. You might want to use the click() method instead. $request = $form->click $request = $form->click( $selector ) $request = $form->click( $x, $y ) $request = $form->click( $selector, $x, $y ) Will "click" on the first clickable input (which will be of type `submit' or `image'). The result of clicking is an `HTTP::Request' object that can then be passed to `LWP::UserAgent' if you want to obtain the server response. If a $selector is specified, we will click on the first clickable input matching the selector, and the method will croak if no matching clickable input is found. If $selector is *not* specified, then it is ok if the form contains no clickable inputs. In this case the click() method returns the same request as the make_request() method would do. See description of the find_input() method above for how the $selector is specified. If there are multiple clickable inputs with the same name, then there is no way to get the click() method of the `HTML::Form' to click on any but the first. If you need this you would have to locate the input with find_input() and invoke the click() method on the given input yourself. A click coordinate pair can also be provided, but this only makes a difference if you clicked on an image. The default coordinate is (1,1). The upper-left corner of the image is (0,0), but some badly coded CGI scripts are known to not recognize this. Therefore (1,1) was selected as a safer default. @kw = $form->form Returns the current setting as a sequence of key/value pairs. Note that keys might be repeated, which means that some values might be lost if the return values are assigned to a hash. In scalar context this method returns the number of key/value pairs generated. $form->dump Returns a textual representation of current state of the form. Mainly useful for debugging. If called in void context, then the dump is printed on STDERR. INPUTS An `HTML::Form' objects contains a sequence of *inputs*. References to the inputs can be obtained with the $form->inputs or $form->find_input methods. Note that there is *not* a one-to-one correspondence between input *objects* and <input> *elements* in the HTML document. An input object basically represents a name/value pair, so when multiple HTML elements contribute to the same name/value pair in the submitted form they are combined. The input elements that are mapped one-to-one are "text", "textarea", "password", "hidden", "file", "image", "submit" and "checkbox". For the "radio" and "option" inputs the story is not as simple: All <input type="radio"> elements with the same name will contribute to the same input radio object. The number of radio input objects will be the same as the number of distinct names used for the <input type="radio"> elements. For a <select> element without the `multiple' attribute there will be one input object of type of "option". For a <select multiple> element there will be one input object for each contained <option> element. Each one of these option objects will have the same name. The following methods are available for the *input* objects: $input->type Returns the type of this input. The type is one of the following strings: "text", "password", "hidden", "textarea", "file", "image", "submit", "radio", "checkbox" or "option". $name = $input->name $input->name( $new_name ) This method can be used to get/set the current name of the input. $input->id $input->class These methods can be used to get/set the current id or class attribute for the input. $input->selected( $selector ) Returns TRUE if the given selector matched the input. See the description of the find_input() method above for a description of the selector syntax. $value = $input->value $input->value( $new_value ) This method can be used to get/set the current value of an input. If strict is enabled and the input only can take an enumerated list of values, then it is an error to try to set it to something else and the method will croak if you try. You will also be able to set the value of read-only inputs, but a warning will be generated if running under `perl -w'. $input->possible_values Returns a list of all values that an input can take. For inputs that do not have discrete values, this returns an empty list. $input->other_possible_values Returns a list of all values not tried yet. $input->value_names For some inputs the values can have names that are different from the values themselves. The number of names returned by this method will match the number of values reported by $input->possible_values. When setting values using the value() method it is also possible to use the value names in place of the value itself. $bool = $input->readonly $input->readonly( $bool ) This method is used to get/set the value of the readonly attribute. You are allowed to modify the value of readonly inputs, but setting the value will generate some noise when warnings are enabled. Hidden fields always start out readonly. $bool = $input->disabled $input->disabled( $bool ) This method is used to get/set the value of the disabled attribute. Disabled inputs do not contribute any key/value pairs for the form value. $input->form_name_value Returns a (possible empty) list of key/value pairs that should be incorporated in the form value from this input. $input->check Some input types represent toggles that can be turned on/off. This includes "checkbox" and "option" inputs. Calling this method turns this input on without having to know the value name. If the input is already on, then nothing happens. This has the same effect as: $input->value($input->possible_values[1]); The input can be turned off with: $input->value(undef); $input->click($form, $x, $y) Some input types (currently "submit" buttons and "images") can be clicked to submit the form. The click() method returns the corresponding `HTTP::Request' object. If the input is of type `file', then it has these additional methods: $input->file This is just an alias for the value() method. It sets the filename to read data from. For security reasons this field will never be initialized from the parsing of a form. This prevents the server from triggering stealth uploads of arbitrary files from the client machine. $filename = $input->filename $input->filename( $new_filename ) This get/sets the filename reported to the server during file upload. This attribute defaults to the value reported by the file() method. $content = $input->content $input->content( $new_content ) This get/sets the file content provided to the server during file upload. This method can be used if you do not want the content to be read from an actual file. @headers = $input->headers input->headers($key => $value, .... ) This get/set additional header fields describing the file uploaded. This can for instance be used to set the `Content-Type' reported for the file. SEE ALSO LWP, LWP::UserAgent, HTML::Parser COPYRIGHT Copyright 1998-2008 Gisle Aas. This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. usr/share/doc/gmp-6.0.0/README 0000644 00000010223 14721013550 0011322 0 ustar 00 Copyright 1991, 1996, 1999, 2000, 2007 Free Software Foundation, Inc. This file is part of the GNU MP Library. The GNU MP Library is free software; you can redistribute it and/or modify it under the terms of either: * the GNU Lesser General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version. or * the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. or both in parallel, as here. The GNU MP Library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received copies of the GNU General Public License and the GNU Lesser General Public License along with the GNU MP Library. If not, see https://www.gnu.org/licenses/. THE GNU MP LIBRARY GNU MP is a library for arbitrary precision arithmetic, operating on signed integers, rational numbers, and floating point numbers. It has a rich set of functions, and the functions have a regular interface. GNU MP is designed to be as fast as possible, both for small operands and huge operands. The speed is achieved by using fullwords as the basic arithmetic type, by using fast algorithms, with carefully optimized assembly code for the most common inner loops for lots of CPUs, and by a general emphasis on speed (instead of simplicity or elegance). GNU MP is believed to be faster than any other similar library. Its advantage increases with operand sizes for certain operations, since GNU MP in many cases has asymptotically faster algorithms. GNU MP is free software and may be freely copied on the terms contained in the files COPYING* (see the manual for information on which license(s) applies to which components of GNU MP). OVERVIEW OF GNU MP There are five classes of functions in GNU MP. 1. Signed integer arithmetic functions (mpz). These functions are intended to be easy to use, with their regular interface. The associated type is `mpz_t'. 2. Rational arithmetic functions (mpq). For now, just a small set of functions necessary for basic rational arithmetics. The associated type is `mpq_t'. 3. Floating-point arithmetic functions (mpf). If the C type `double' doesn't give enough precision for your application, declare your variables as `mpf_t' instead, set the precision to any number desired, and call the functions in the mpf class for the arithmetic operations. 4. Positive-integer, hard-to-use, very low overhead functions are in the mpn class. No memory management is performed. The caller must ensure enough space is available for the results. The set of functions is not regular, nor is the calling interface. These functions accept input arguments in the form of pairs consisting of a pointer to the least significant word, and an integral size telling how many limbs (= words) the pointer points to. Almost all calculations, in the entire package, are made by calling these low-level functions. 5. Berkeley MP compatible functions. To use these functions, include the file "mp.h". You can test if you are using the GNU version by testing if the symbol __GNU_MP__ is defined. For more information on how to use GNU MP, please refer to the documentation. It is composed from the file doc/gmp.texi, and can be displayed on the screen or printed. How to do that, as well how to build the library, is described in the INSTALL file in this directory. REPORTING BUGS If you find a bug in the library, please make sure to tell us about it! You should first check the GNU MP web pages at https://gmplib.org/, under "Status of the current release". There will be patches for all known serious bugs there. Report bugs to gmp-bugs@gmplib.org. What information is needed in a useful bug report is described in the manual. The same address can be used for suggesting modifications and enhancements. ---------------- Local variables: mode: text fill-column: 78 End: usr/share/doc/unixODBC-2.3.1/README 0000644 00000002452 14721013644 0012163 0 ustar 00 +-------------------------------------------------------------+ | unixODBC | +-------------------------------------------------------------+ README --------------------------------------------------------------- Description: unixODBC is an Open Source ODBC sub-system and an ODBC SDK for Linux, Mac OSX, and UNIX. License: All libraries are LGPL. All programs are GPL. Parts: unixODBC includes the following; - Driver Manager - Installer Library and command line tool - Command Line Tools to help install a driver and work with SQL How To Start: Look for and read README files with extensions of interest. Then read the INSTALL file. You can also jump into the doc directory and browse information there. And do not forget the online stuff. Some documentation may be a bit out of date the vast majority of it should be ok. Config Files: The ODBC Installer Library is responsible for reading and writing the unixODBC config files. The savy can look at; _odbcinst_SystemINI.c _odbcinst_UserINI.c In anycase; you can override where unixODBC looks for its system config files by setting the ODBCSYSINI enviroment variable during the use of unixODBC. Resources: http://sourceforge.net/projects/unixodbc/ usr/share/doc/perl-File-Slurp-9999.19/README 0000644 00000002360 14721013741 0013700 0 ustar 00 File::Slurp.pm =========================== This module provides subroutines to read or write entire files with a simple call. It also has a subroutine for reading the list of filenames in a directory. In the extras/ directory you can read an article (slurp_article.pod) about file slurping and also run a benchmark (slurp_bench.pl) that compares many ways of slurping/spewing files. This benchmark was rewritten for .14 and is much better. This module was first written and owned by David Muir Sharnoff (MUIR on CPAN). I checked out his module and decided to write a new version which would be faster and with many more features. To that end, David graciously transfered the namespace to me. There have been some comments about the somewhat unusual version number. The problem was that David used a future date (2004.0904) in his version number, and the only way I could get CPAN to index my new module was to make it have a version number higher than the old one, so I chose the 9999 prefix and appended the real revision number to it. INSTALLATION To install this module type the following: perl Makefile.PL make make test make install COPYRIGHT AND LICENCE Copyright (C) 2010 Uri Guttman <uri@PerlHunter.com> Licensed the same as Perl. usr/share/doc/perl-File-ReadBackwards-1.05/README 0000644 00000002461 14721014123 0014775 0 ustar 00 File::ReadBackwards.pm This module reads a file backwards line by line. It is simple to use, memory efficient and fast. It supports both an object and a tied handle interface. It is intended for processing log and other similar text files which typically have their newest entries appended to them. By default files are assumed to be plain text and have a line ending appropriate to the OS. But you can set the input record separator string on a per file basis. PREREQUISITES There are no prerequisite modules. INSTALLATION Installation is done as with most Perl modules by running these commands: perl Makefile.PL make make test make install DOCUMENTATION Documentation is in the module file in pod form. It will be installed in the normal documentation directories on your system. An HTML version of the documentation is at: http://www.sysarch.com/perl/modules/File-ReadBackwards.html SUPPORT If you have any questions, bug reports or feedback, email it to uri@sysarch.com AVAILABILITY The latest version of File::ReadBackwards.pm will always be available in this directory: http://www.sysarch.com/perl/modules COPYRIGHT (C) 2000 Uri Guttman. All rights reserved. This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. usr/share/doc/sgpio-1.2.0.10/README 0000644 00000004075 14721014170 0012103 0 ustar 00 ========================================================================== Intel(R) SGPIO tool RELEASE NOTES ========================================================================== DATE: January 2007 TO: Validation Team SUBJECT: SGPIO captive backplane tool ========================================================================== A. PACKAGE CONTENTS ========================================================================== The following files are included in this release package: - sgpio.tar.gz (SGPIO tool package with the items below) - commands.h (header file that contains the option structure for getopt) - Makefile (tells make what to build and where to install it) - readme (this file) - sgpio.1 (the sgpio tool's man page) - sgpio.c (the sgpio tool source) - version.h (contains the tool and sgpio interface version) ========================================================================== B. INSTALLATION ========================================================================== 1) The complete release is contained in a tar gzipped file. It can be extracted in Linux. For example, Run: tar -xzf sgpio.tar.gz 2) Build the tool by running make: Run: make 3) Install and Execute Run: su (need to be root) Run: make install ========================================================================== C. NOTES ========================================================================== - This tool will only function with a 2.6.23 Kernel that has been patched for SGPIO support. - This tool has not been validated beyond normal funcationality. - This tool has only been tested on Fedora 7 and RHEL 5. ========================================================================== D. KNOWN ISSUES ========================================================================== - Tool will not control SGPIO on SATA port multipliers. usr/share/doc/audit-2.8.5/README 0000644 00000011557 14721014347 0011676 0 ustar 00 This is some background information about the Linux Auditing Framework. LICENSE ======= The audit daemon is released as GPL'd code. The audit daemon's libraries libaudit.* and libauparse.* are released under LGPL so that it may be linked with 3rd party software. BUILDING ======== See the README-install File. USAGE ===== See the man pages for audit, auditctl, audit.rules, ausearch, and aureport. DISCUSSION ========== Original lkml thread(s): http://marc.theaimsgroup.com/?t=107815888100001&r=1&w=2 http://marc.theaimsgroup.com/?t=107901570800002&r=1&w=2 There is a linux audit mail list where any question whether kernel design, setup and configuration, or usage can be discussed: http://www.redhat.com/mailman/listinfo/linux-audit DESIGN INFO (Very old) ===================== The main goals were to provide system call auditing with 1) as low overhead as possible, and 2) without duplicating functionality that is already provided by SELinux (and/or other security infrastructures). This framework will work "stand-alone", but is not designed to provide, e.g., CAPP functionality without another security component in place. There are two main parts, one that is always on (generic logging in audit.c) and one that you can disable at boot- or run-time (per-system-call auditing in auditsc.c). The patch includes changes to security/selinux/avc.c as an example of how system-call auditing can be integrated with other code that identifies auditable events. Logging: 1) Uses a netlink socket for communication with user-space. All messages are logged via the netlink socket if a user-space daemon is listening. If not, the messages are logged via printk to the syslog daemon (by default). 2) Messages can be dropped (optionally) based on message rate or memory use (this isn't fully integrated into the selinux/avc.c part of the patch: the avc.c code that currently does this can be eliminated). 3) When some part of the kernel generates part of an audit record, the partial record is sent immediately to user-space, AND the system call "auditable" flag is automatically set for that call -- thereby producing extra information at syscall exit (if syscall auditing is enabled). System-call auditing: 1) At task-creation time, an audit context is allocated and linked off the task structure. 2) At syscall entry time, if the audit context exists, information is filled in (syscall number, timestamp; but not arguments). 3) During the system call, calls to getname() and path_lookup() are intercepted. These routines are called when the kernel is actually looking up information that will be used to make the decision about whether the syscall will succeed or fail. An effort has been made to avoid copying the information that getname generates, since getname is already making a kernel-private copy of the information. [Note that storing copies of all syscall arguments requires complexity and overhead that arguably isn't needed. With this patch, for example, if chroot("foo") fails because you are not root, "foo" will not appear in the audit record because the kernel determined the syscall cannot proceed before it ever needed to look up "foo". This approach avoids storing user-supplied information that could be misleading or unreliable (e.g., due to a cooperative shared-memory attack) in favor of reporting information actually used by the kernel.] 4) At syscall exit time, if the "auditable" flag has been set (e.g., because SELinux generated an avc record; or some other part of the kernel detected an auditable event), the syscall-part of the audit record is generated, including file names and inode numbers (if available). Some of this information is currently complementary to the information that selinux/avc.c generates (e.g., file names and some inode numbers), but some is less complete (e.g., getname doesn't return a fully-qualified path, and this patch does not add the overhead of determining one). [Note that the complete audit record comes to userspace in pieces, which eliminates the need to store messages for arbitrarily long periods inside the kernel.] 5) At task-exit time, the audit context is destroyed. At steps 1, 2, and 4, simple filtering can be done (e.g., a database role uid might have syscall auditing disabled for performance reasons). The filtering is simple and could be made more complex. However, I tried to implement as much filtering as possible without adding significant overhead (e.g., d_path()). In general, the audit framework should rely on some other kernel component (e.g., SELinux) to make the majority of the decisions about what is and is not auditable. usr/share/doc/shadow-utils-4.6/README 0000644 00000007562 14721014573 0013052 0 ustar 00 Shadow SITES ============ Homepage http://pkg-shadow.alioth.debian.org/ FTP site ftp://pkg-shadow.alioth.debian.org/pub/pkg-shadow SVN repository anonymous read only access: svn://svn.debian.org/pkg-shadow/upstream SVN web interface http://svn.debian.org/wsvn/pkg-shadow/upstream or http://svn.debian.org/viewsvn/pkg-shadow/upstream Mailing lists for general discuss: pkg-shadow-devel@lists.alioth.debian.org commit list: pkg-shadow-commits@lists.alioth.debian.org Mailing lists subscription http://lists.alioth.debian.org/mailman/listinfo/pkg-shadow-devel http://lists.alioth.debian.org/mailman/listinfo/pkg-shadow-commits Mailing lists archives: http://lists.alioth.debian.org/pipermail/pkg-shadow-devel/ http://lists.alioth.debian.org/pipermail/pkg-shadow-commits/ S/Key support: Shadow can be built with S/Key support using the S/Key package from: http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libskey/ or http://gentoo.osuosl.org/distfiles/skey-1.1.5.tar.bz2 Authors and contributors ======================== Thanks to at least the following people for sending patches, bug reports and various comments. This list may be incomplete, I received a lot of mail... Adam Rudnicki <adam@v-lo.krakow.pl> Alan Curry <pacman@tardis.mars.net> Aleksa Sarai <cyphar@cyphar.com> Alexander O. Yuriev <alex@bach.cis.temple.edu> Algis Rudys <arudys@rice.edu> Andreas Jaeger <aj@arthur.rhein-neckar.de> Aniello Del Sorbo <anidel@edu-gw.dia.unisa.it> Anton Gluck <gluc@midway.uchicago.edu> Arkadiusz Miskiewicz <misiek@pld.org.pl> Ben Collins <bcollins@debian.org> Brian R. Gaeke <brg@dgate.org> Calle Karlsson <ckn@kash.se> Chip Rosenthal <chip@unicom.com> Chris Evans <lady0110@sable.ox.ac.uk> Cristian Gafton <gafton@sorosis.ro> Dan Walsh <dwalsh@redhat.com> Darcy Boese <possum@chardonnay.niagara.com> Dave Hagewood <admin@arrowweb.com> David A. Holland <dholland@hcs.harvard.edu> David Frey <David.Frey@lugs.ch> Ed Carp <ecarp@netcom.com> Floody <flood@evcom.net> Frank Denis <j@4u.net> George Kraft IV <gk4@us.ibm.com> Greg Mortensen <loki@world.std.com> Guido van Rooij Guy Maor <maor@debian.org> Hrvoje Dogan <hdogan@bjesomar.srce.hr> Jakub Hrozek <jhrozek@redhat.com> Janos Farkas <chexum@bankinf.banki.hu> Jay Soffian <jay@lw.net> Jesse Thilo <Jesse.Thilo@pobox.com> Joey Hess <joey@kite.ml.org> John Adelsberger <jja@umr.edu> Jonathan Hankins <jhankins@mailserv.homewood.k12.al.us> Jon Lewis <jlewis@lewis.org> Joshua Cowan <jcowan@hermit.reslife.okstate.edu> Judd Bourgeois <shagboy@bluesky.net> Juergen Heinzl <unicorn@noris.net> Juha Virtanen <jiivee@iki.fi> Julian Pidancet <julian.pidancet@gmail.com> Julianne Frances Haugh <jockgrrl@ix.netcom.com> Leonard N. Zubkoff <lnz@dandelion.com> Luca Berra <bluca@www.polimi.it> Lukáš Kuklínek <lkukline@redhat.com> Lutz Schwalowsky <schwalow@mineralogie.uni-hamburg.de> Marc Ewing <marc@redhat.com> Martin Bene <mb@sime.com> Martin Mares <mj@gts.cz> Michael Meskes <meskes@topsystem.de> Michael Talbot-Wilson <mike@calypso.bns.com.au> Mike Frysinger <vapier@gentoo.org> Mike Pakovic <mpakovic@users.southeast.net> Nicolas François <nicolas.francois@centraliens.net> Nikos Mavroyanopoulos <nmav@i-net.paiko.gr> Pavel Machek <pavel@bug.ucw.cz> Peter Vrabec <pvrabec@redhat.com> Phillip Street Rafał Maszkowski <rzm@icm.edu.pl> Rani Chouha <ranibey@smartec.com> Sami Kerola <kerolasa@rocketmail.com> Scott Garman <scott.a.garman@intel.com> Sebastian Rick Rijkers <srrijkers@gmail.com> Seraphim Mellos <mellos@ceid.upatras.gr> Shane Watts <shane@nexus.mlckew.edu.au> Steve M. Robbins <steve@nyongwa.montreal.qc.ca> Thorsten Kukuk <kukuk@suse.de> Tim Hockin <thockin@eagle.ais.net> Timo Karjalainen <timok@iki.fi> Ulisses Alonso Camaro <ulisses@pusa.eleinf.uv.es> Werner Fink <werner@suse.de> Maintainers =========== Tomasz Kłoczko <kloczek@pld.org.pl> (2000-2007) Nicolas François <nicolas.francois@centraliens.net> (2007-2014) Serge E. Hallyn <serge@hallyn.com> (2014-now) usr/share/doc/perl-Exporter-5.68/README 0000644 00000041346 14721015326 0013263 0 ustar 00 NAME Exporter - Implements default import method for modules SYNOPSIS In module YourModule.pm: package YourModule; require Exporter; @ISA = qw(Exporter); @EXPORT_OK = qw(munge frobnicate); # symbols to export on request or package YourModule; use Exporter 'import'; # gives you Exporter's import() method directly @EXPORT_OK = qw(munge frobnicate); # symbols to export on request In other files which wish to use "YourModule": use YourModule qw(frobnicate); # import listed symbols frobnicate ($left, $right) # calls YourModule::frobnicate Take a look at "Good Practices" for some variants you will like to use in modern Perl code. DESCRIPTION The Exporter module implements an "import" method which allows a module to export functions and variables to its users' namespaces. Many modules use Exporter rather than implementing their own "import" method because Exporter provides a highly flexible interface, with an implementation optimised for the common case. Perl automatically calls the "import" method when processing a "use" statement for a module. Modules and "use" are documented in perlfunc and perlmod. Understanding the concept of modules and how the "use" statement operates is important to understanding the Exporter. How to Export The arrays @EXPORT and @EXPORT_OK in a module hold lists of symbols that are going to be exported into the users name space by default, or which they can request to be exported, respectively. The symbols can represent functions, scalars, arrays, hashes, or typeglobs. The symbols must be given by full name with the exception that the ampersand in front of a function is optional, e.g. @EXPORT = qw(afunc $scalar @array); # afunc is a function @EXPORT_OK = qw(&bfunc %hash *typeglob); # explicit prefix on &bfunc If you are only exporting function names it is recommended to omit the ampersand, as the implementation is faster this way. Selecting What To Export Do not export method names! Do not export anything else by default without a good reason! Exports pollute the namespace of the module user. If you must export try to use @EXPORT_OK in preference to @EXPORT and avoid short or common symbol names to reduce the risk of name clashes. Generally anything not exported is still accessible from outside the module using the "YourModule::item_name" (or "$blessed_ref->method") syntax. By convention you can use a leading underscore on names to informally indicate that they are 'internal' and not for public use. (It is actually possible to get private functions by saying: my $subref = sub { ... }; $subref->(@args); # Call it as a function $obj->$subref(@args); # Use it as a method However if you use them for methods it is up to you to figure out how to make inheritance work.) As a general rule, if the module is trying to be object oriented then export nothing. If it's just a collection of functions then @EXPORT_OK anything but use @EXPORT with caution. For function and method names use barewords in preference to names prefixed with ampersands for the export lists. Other module design guidelines can be found in perlmod. How to Import In other files which wish to use your module there are three basic ways for them to load your module and import its symbols: "use YourModule;" This imports all the symbols from YourModule's @EXPORT into the namespace of the "use" statement. "use YourModule ();" This causes perl to load your module but does not import any symbols. "use YourModule qw(...);" This imports only the symbols listed by the caller into their namespace. All listed symbols must be in your @EXPORT or @EXPORT_OK, else an error occurs. The advanced export features of Exporter are accessed like this, but with list entries that are syntactically distinct from symbol names. Unless you want to use its advanced features, this is probably all you need to know to use Exporter. Advanced features Specialised Import Lists If any of the entries in an import list begins with !, : or / then the list is treated as a series of specifications which either add to or delete from the list of names to import. They are processed left to right. Specifications are in the form: [!]name This name only [!]:DEFAULT All names in @EXPORT [!]:tag All names in $EXPORT_TAGS{tag} anonymous list [!]/pattern/ All names in @EXPORT and @EXPORT_OK which match A leading ! indicates that matching names should be deleted from the list of names to import. If the first specification is a deletion it is treated as though preceded by :DEFAULT. If you just want to import extra names in addition to the default set you will still need to include :DEFAULT explicitly. e.g., Module.pm defines: @EXPORT = qw(A1 A2 A3 A4 A5); @EXPORT_OK = qw(B1 B2 B3 B4 B5); %EXPORT_TAGS = (T1 => [qw(A1 A2 B1 B2)], T2 => [qw(A1 A2 B3 B4)]); Note that you cannot use tags in @EXPORT or @EXPORT_OK. Names in EXPORT_TAGS must also appear in @EXPORT or @EXPORT_OK. An application using Module can say something like: use Module qw(:DEFAULT :T2 !B3 A3); Other examples include: use Socket qw(!/^[AP]F_/ !SOMAXCONN !SOL_SOCKET); use POSIX qw(:errno_h :termios_h !TCSADRAIN !/^EXIT/); Remember that most patterns (using //) will need to be anchored with a leading ^, e.g., "/^EXIT/" rather than "/EXIT/". You can say "BEGIN { $Exporter::Verbose=1 }" to see how the specifications are being processed and what is actually being imported into modules. Exporting without using Exporter's import method Exporter has a special method, 'export_to_level' which is used in situations where you can't directly call Exporter's import method. The export_to_level method looks like: MyPackage->export_to_level($where_to_export, $package, @what_to_export); where $where_to_export is an integer telling how far up the calling stack to export your symbols, and @what_to_export is an array telling what symbols *to* export (usually this is @_). The $package argument is currently unused. For example, suppose that you have a module, A, which already has an import function: package A; @ISA = qw(Exporter); @EXPORT_OK = qw ($b); sub import { $A::b = 1; # not a very useful import method } and you want to Export symbol $A::b back to the module that called package A. Since Exporter relies on the import method to work, via inheritance, as it stands Exporter::import() will never get called. Instead, say the following: package A; @ISA = qw(Exporter); @EXPORT_OK = qw ($b); sub import { $A::b = 1; A->export_to_level(1, @_); } This will export the symbols one level 'above' the current package - ie: to the program or module that used package A. Note: Be careful not to modify @_ at all before you call export_to_level - or people using your package will get very unexplained results! Exporting without inheriting from Exporter By including Exporter in your @ISA you inherit an Exporter's import() method but you also inherit several other helper methods which you probably don't want. To avoid this you can do package YourModule; use Exporter qw( import ); which will export Exporter's own import() method into YourModule. Everything will work as before but you won't need to include Exporter in @YourModule::ISA. Note: This feature was introduced in version 5.57 of Exporter, released with perl 5.8.3. Module Version Checking The Exporter module will convert an attempt to import a number from a module into a call to "$module_name->require_version($value)". This can be used to validate that the version of the module being used is greater than or equal to the required version. The Exporter module supplies a default "require_version" method which checks the value of $VERSION in the exporting module. Since the default "require_version" method treats the $VERSION number as a simple numeric value it will regard version 1.10 as lower than 1.9. For this reason it is strongly recommended that you use numbers with at least two decimal places, e.g., 1.09. Managing Unknown Symbols In some situations you may want to prevent certain symbols from being exported. Typically this applies to extensions which have functions or constants that may not exist on some systems. The names of any symbols that cannot be exported should be listed in the @EXPORT_FAIL array. If a module attempts to import any of these symbols the Exporter will give the module an opportunity to handle the situation before generating an error. The Exporter will call an export_fail method with a list of the failed symbols: @failed_symbols = $module_name->export_fail(@failed_symbols); If the "export_fail" method returns an empty list then no error is recorded and all the requested symbols are exported. If the returned list is not empty then an error is generated for each symbol and the export fails. The Exporter provides a default "export_fail" method which simply returns the list unchanged. Uses for the "export_fail" method include giving better error messages for some symbols and performing lazy architectural checks (put more symbols into @EXPORT_FAIL by default and then take them out if someone actually tries to use them and an expensive check shows that they are usable on that platform). Tag Handling Utility Functions Since the symbols listed within %EXPORT_TAGS must also appear in either @EXPORT or @EXPORT_OK, two utility functions are provided which allow you to easily add tagged sets of symbols to @EXPORT or @EXPORT_OK: %EXPORT_TAGS = (foo => [qw(aa bb cc)], bar => [qw(aa cc dd)]); Exporter::export_tags('foo'); # add aa, bb and cc to @EXPORT Exporter::export_ok_tags('bar'); # add aa, cc and dd to @EXPORT_OK Any names which are not tags are added to @EXPORT or @EXPORT_OK unchanged but will trigger a warning (with "-w") to avoid misspelt tags names being silently added to @EXPORT or @EXPORT_OK. Future versions may make this a fatal error. Generating combined tags If several symbol categories exist in %EXPORT_TAGS, it's usually useful to create the utility ":all" to simplify "use" statements. The simplest way to do this is: %EXPORT_TAGS = (foo => [qw(aa bb cc)], bar => [qw(aa cc dd)]); # add all the other ":class" tags to the ":all" class, # deleting duplicates { my %seen; push @{$EXPORT_TAGS{all}}, grep {!$seen{$_}++} @{$EXPORT_TAGS{$_}} foreach keys %EXPORT_TAGS; } CGI.pm creates an ":all" tag which contains some (but not really all) of its categories. That could be done with one small change: # add some of the other ":class" tags to the ":all" class, # deleting duplicates { my %seen; push @{$EXPORT_TAGS{all}}, grep {!$seen{$_}++} @{$EXPORT_TAGS{$_}} foreach qw/html2 html3 netscape form cgi internal/; } Note that the tag names in %EXPORT_TAGS don't have the leading ':'. "AUTOLOAD"ed Constants Many modules make use of "AUTOLOAD"ing for constant subroutines to avoid having to compile and waste memory on rarely used values (see perlsub for details on constant subroutines). Calls to such constant subroutines are not optimized away at compile time because they can't be checked at compile time for constancy. Even if a prototype is available at compile time, the body of the subroutine is not (it hasn't been "AUTOLOAD"ed yet). perl needs to examine both the "()" prototype and the body of a subroutine at compile time to detect that it can safely replace calls to that subroutine with the constant value. A workaround for this is to call the constants once in a "BEGIN" block: package My ; use Socket ; foo( SO_LINGER ); ## SO_LINGER NOT optimized away; called at runtime BEGIN { SO_LINGER } foo( SO_LINGER ); ## SO_LINGER optimized away at compile time. This forces the "AUTOLOAD" for "SO_LINGER" to take place before SO_LINGER is encountered later in "My" package. If you are writing a package that "AUTOLOAD"s, consider forcing an "AUTOLOAD" for any constants explicitly imported by other packages or which are usually used when your package is "use"d. Good Practices Declaring @EXPORT_OK and Friends When using "Exporter" with the standard "strict" and "warnings" pragmas, the "our" keyword is needed to declare the package variables @EXPORT_OK, @EXPORT, @ISA, etc. our @ISA = qw(Exporter); our @EXPORT_OK = qw(munge frobnicate); If backward compatibility for Perls under 5.6 is important, one must write instead a "use vars" statement. use vars qw(@ISA @EXPORT_OK); @ISA = qw(Exporter); @EXPORT_OK = qw(munge frobnicate); Playing Safe There are some caveats with the use of runtime statements like "require Exporter" and the assignment to package variables, which can very subtle for the unaware programmer. This may happen for instance with mutually recursive modules, which are affected by the time the relevant constructions are executed. The ideal (but a bit ugly) way to never have to think about that is to use "BEGIN" blocks. So the first part of the "SYNOPSIS" code could be rewritten as: package YourModule; use strict; use warnings; our (@ISA, @EXPORT_OK); BEGIN { require Exporter; @ISA = qw(Exporter); @EXPORT_OK = qw(munge frobnicate); # symbols to export on request } The "BEGIN" will assure that the loading of Exporter.pm and the assignments to @ISA and @EXPORT_OK happen immediately, leaving no room for something to get awry or just plain wrong. With respect to loading "Exporter" and inheriting, there are alternatives with the use of modules like "base" and "parent". use base qw( Exporter ); # or use parent qw( Exporter ); Any of these statements are nice replacements for "BEGIN { require Exporter; @ISA = qw(Exporter); }" with the same compile-time effect. The basic difference is that "base" code interacts with declared "fields" while "parent" is a streamlined version of the older "base" code to just establish the IS-A relationship. For more details, see the documentation and code of base and parent. Another thorough remedy to that runtime vs. compile-time trap is to use Exporter::Easy, which is a wrapper of Exporter that allows all boilerplate code at a single gulp in the use statement. use Exporter::Easy ( OK => [ qw(munge frobnicate) ], ); # @ISA setup is automatic # all assignments happen at compile time What not to Export You have been warned already in "Selecting What To Export" to not export: * method names (because you don't need to and that's likely to not do what you want), * anything by default (because you don't want to surprise your users... badly) * anything you don't need to (because less is more) There's one more item to add to this list. Do not export variable names. Just because "Exporter" lets you do that, it does not mean you should. @EXPORT_OK = qw( $svar @avar %hvar ); # DON'T! Exporting variables is not a good idea. They can change under the hood, provoking horrible effects at-a-distance, that are too hard to track and to fix. Trust me: they are not worth it. To provide the capability to set/get class-wide settings, it is best instead to provide accessors as subroutines or class methods instead. SEE ALSO "Exporter" is definitely not the only module with symbol exporter capabilities. At CPAN, you may find a bunch of them. Some are lighter. Some provide improved APIs and features. Peek the one that fits your needs. The following is a sample list of such modules. Exporter::Easy Exporter::Lite Exporter::Renaming Exporter::Tidy Sub::Exporter / Sub::Installer Perl6::Export / Perl6::Export::Attrs LICENSE This library is free software. You can redistribute it and/or modify it under the same terms as Perl itself. usr/share/doc/libpipeline-1.2.3/README 0000644 00000011220 14721015474 0013040 0 ustar 00 libpipeline, a pipeline manipulation library ============================================ libpipeline is a C library for setting up and running pipelines of processes, without needing to involve shell command-line parsing which is often error-prone and insecure. This alleviates programmers of the need to laboriously construct pipelines using lower-level primitives such as fork(2) and execve(2). Full programmers' documentation may be found using 'man libpipeline'. Installation ------------ If you need to install libpipeline starting from source code, then you will need these separate packages installed before configuring libpipeline in order to run its test suite: pkg-config (http://www.freedesktop.org/wiki/Software/pkg-config) check (http://check.sourceforge.net/) See the INSTALL file for general installation instructions. Building programs with libpipeline ---------------------------------- libpipeline supplies a pkg-config file which lists appropriate compiler and linker flags for building programs using it. The output of 'pkg-config --cflags libpipeline' should be passed to the compiler (typically CFLAGS) and the output of 'pkg-config --libs libpipeline' should be passed to the linker (typically LDFLAGS). If your program uses the GNU Autotools, then you can put this in configure.ac: PKG_CHECK_MODULES([libpipeline], [libpipeline]) ... and this in the appropriate Makefile.am (replacing 'program' with the Automake-canonicalised name for your program): AM_CFLAGS = $(libpipeline_CFLAGS) program_LDADD = $(libpipeline_LIBS) The details may vary for particular build systems, but this should be a reasonable start. When building with GCC, you should use at least the -Wformat option (included in -Wall) to ensure that the 'sentinel' function attribute is checked. This means that your program will produce a warning if it calls any of the several libpipeline functions that require a trailing NULL without passing that trailing NULL. Copyright and licensing ----------------------- Copyright (C) 1994 Markus Armbruster. Copyright (C) 1989, 1990, 1991, 1992, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 Free Software Foundation, Inc. Copyright (C) 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 Colin Watson. libpipeline 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; either version 3 of the License, or (at your option) any later version. libpipeline is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with libpipeline; if not, write to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. Note on GPL versions -------------------- (This note is informative, and if it conflicts with the terms of the licence then the licence is correct. See the full text of the licence in the COPYING file for precise details.) The core source code of libpipeline is licensed under GPL v2 or later. However, libpipeline incorporates parts of the Gnulib portability library, copyrighted by the Free Software Foundation and others, and much of Gnulib is distributed under GPL v3 or later. This means that libpipeline as a whole falls under the terms of the GPL v3 or later. Unless you take special pains to remove the GPL v3 portions, you must therefore follow the terms and conditions of the GPL v3 or later when distributing libpipeline itself, or distributing code linked against it. Note that this does not require that your own source code be licensed under the GPL v3, contrary to popular misunderstanding. However, you must be prepared to distribute your work as a whole under the terms of the GPL v3 or later, which requires that your licence be compatible with the GPL v3. See http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses if you need advice on compatibility. The GPL mainly restricts distribution ("conveying", in the specific language of GPL v3), and is careful not to restrict private use. Therefore, you may write programs for your own use that use libpipeline without needing to license them under GPL v3-compatible terms. If you distribute these programs to others, then you must take care to use compatible licensing. Credits ------- Thanks to Scott James Remnant for code review, Ian Jackson for an extensive design review, and Kees Cook and Matthias Klose for helpful conversations. -- Colin Watson <cjwatson@debian.org> usr/share/doc/jwhois-4.0/README 0000644 00000011064 14721015636 0011715 0 ustar 00 This is jwhois, an improved Whois client capable of selecting Whois server to query based on a flexible configuration file using either regular expressions or CIDR blocks. Please send bug reports, suggestions, improvements, rewrites and other material to bug-jwhois@gnu.org. 1. Configuration file 2. ./configure 2.1 Default Host 2.2 Cache Functionality 3. IPv6 support 4. What to do when things go wrong 5. Obtaining jwhois 6. What to do after you've gotten things to work 7. The history of jwhois 1. Configuration File ===================== In the example/ subdirectory in the distribution archive is an example configuration file for jwhois. This file should contain all of the known public Whois server records. Any changes to either host listed in that example configuration file should be reported to the maintainer so that the change can be included in future releases. The configuration file should reside in the /usr/local/etc directory, or the directory that you specified using the --sysconfdir switch to the configure script. 2. ./configure 2.1. Default Host ================= If jwhois can't find any configuration file, the queries will be directed to a default host. The default value is `whois.internic.net', but this can be changed by using the --enable-DEFAULTHOST switch to the configure script. 2.2. Cache Functionality ======================== This version of jwhois includes a functionality that can cache Whois responses. The cached information is stored in a local database which can be read and written to by jwhois. The default location for this file is /usr/local/var, but this can be changed by adding another directory with --localstatedir=<dir> when running the configure script. The location of the database can also be set in the configuration file. For this to work, jwhois has to be able to read and write to the cache file. If you're on a single-user machine, this can be done easily by creating a cache file and changing the owner of it to the user you're running as. If you have several users, you would normally allow a specific group to write to the cache file and setgid the jwhois binary to this group. If you don't know how to do this, you can ask someone in your area with more UNIX experience. Chances are, if you don't use jwhois actively, there is little point in configuring a cache since it would not be used very much anyway. 3. IPv6 Support =============== jwhois has support for IPv6 using the inet6-apps package from The Inner Net. The package is delivered with the libinet6.a library which consists of a number of functions required for IPv6, such as improved versions of getaddrinfo(). If your systems C library already has support for IPv6 in getaddrinfo(), you don't need the inet6-apps package. 4. What to do when things go wrong ================================== There is a command line switch called -v or --verbose. Use it. The output that it gives can give significant help with locating a potential problem with jwhois. When attempting to use the cache feature, the most common problem is that jwhois doesn't have permission to write the database files that it need. Use the verbose flag to see if this is indeed the problem. If you want to receive even more debugging output, you can specify multiple -v switches. If you specify more than one -v switch, debugging output is enabled. 5. Obtaining JWHOIS =================== JWHOIS can be obtained via anonymous FTP from ftp://ftp.gnu.org/gnu/jwhois/ 6. What to do after you've gotten things to work ================================================ If you use JWHOIS and find it useful, you could always send a message to us at help-jwhois@gnu.org to let us know. You don't have to do this, but we would appreciate the gesture :-) 7. The history of jwhois ======================== The first public version of jwhois (version 1.1) was released in April 1999. Since then, some ten public releases has been made, arriving at the jwhois as it exists today. Here is a brief outline of the development: 1.1 Written in Perl with a standalone caching proxy. 2.0 Rewrite in C. Standalone caching proxy dropped from distribution. 2.1 Better documentation. Support for whois servers on other ports than 43. 2.2 Support for CIDR blocks and IPv6. 2.3 Redirections, caches and i18n are introduced. 2.4 Maintanance release preparing for 3.0 3.0 Rwhois and http support. Rewriting of queries introduced. 3.1 Added "default" to configuration file. 3.2 Added advanced rewrite of queries. A more detailed list of changes can be found in the file NEWS. usr/share/doc/glib2-2.56.1/README 0000644 00000036132 14721015700 0011634 0 ustar 00 General Information =================== This is GLib version 2.56.1. GLib is the low-level core library that forms the basis for projects such as GTK+ and GNOME. It provides data structure handling for C, portability wrappers, and interfaces for such runtime functionality as an event loop, threads, dynamic loading, and an object system. The official download locations are: ftp://ftp.gtk.org/pub/glib http://download.gnome.org/sources/glib The official web site is: http://www.gtk.org/ Information about mailing lists can be found at http://www.gtk.org/mailing-lists.php To subscribe, send mail to gtk-list-request@gnome.org with the subject "subscribe". Installation ============ See the file 'INSTALL' How to report bugs ================== Bugs should be reported to the GNOME bug tracking system. (http://bugzilla.gnome.org, product glib.) You will need to create an account for yourself. In the bug report please include: * Information about your system. For instance: - What operating system and version - For Linux, what version of the C library And anything else you think is relevant. * How to reproduce the bug. If you can reproduce it with one of the test programs that are built in the tests/ subdirectory, that will be most convenient. Otherwise, please include a short test program that exhibits the behavior. As a last resort, you can also provide a pointer to a larger piece of software that can be downloaded. * If the bug was a crash, the exact text that was printed out when the crash occured. * Further information such as stack traces may be useful, but is not necessary. Patches ======= Patches should also be submitted to bugzilla.gnome.org. If the patch fixes an existing bug, add the patch as an attachment to that bug report. Otherwise, enter a new bug report that describes the patch, and attach the patch to that bug report. Patches should be in unified diff form. (The -up option to GNU diff.) Notes about GLib 2.48 ===================== * The system copy of PCRE is now used by default to implement GRegex. Configure with --with-pcre=internal if a system PCRE version is unavailable or undesired. Notes about GLib 2.46 ===================== * GTask no longer imposes a fixed limit on the number of tasks that can be run_in_thread() simultaneously, since doing this inevitably results in deadlocks in some use cases. Instead, it now has a base number of threads that can be used "for free", but will gradually add more threads to the pool if too much time passes without any tasks completing. The exact behavior may continue to change in the future, and it's possible that some future version of GLib may not do any rate-limiting at all. As a result, you should no longer assume that GTask will rate-limit tasks itself (or, by extension, that calls to certain async gio methods will automatically be rate-limited for you). If you have a very large number of tasks to run, and don't want them to all run at once, you should rate-limit them yourself. Notes about GLib 2.40 ===================== * g_test_run() no longer runs tests in exactly the order they are registered; instead, it groups them according to test suites (ie, path components) like the documentation always claimed it did. In some cases, this can result in a sub-optimal ordering of tests, relative to the old behavior. The fix is to change the test paths to properly group together the tests that should run together. (eg, if you want to run test_foo_simple(), test_bar_simple(), and test_foo_using_bar() in that order, they should have test paths like "/simple/foo", "/simple/bar", "/complex/foo-using-bar", not "/foo/simple", "/bar/simple", "/foo/using-bar" (which would result in test_foo_using_bar() running before test_bar_simple()). (The behavior actually changed in GLib 2.36, but it was not documented at the time, since we didn't realize it mattered.) Notes about GLib 2.36 ===================== * It is no longer necessary to call g_type_init(). If you are loading GLib as a dynamic module, you should be careful to avoid unloading it, then subsequently loading it again. This never really worked before, but it is now explicitly undefined behavior. Note that if g_type_init() was the only explicit use of a GObject API and you are using linker flags such as --no-add-needed, then you may have to artificially use some GObject call to keep the linker from optimizing away -lgobject. We recommend to use g_type_ensure (G_TYPE_OBJECT) for this purpose. * This release contains an incompatible change to the g_get_home_dir() function. Previously, this function would effectively ignore the HOME environment variable and always return the value from /etc/password. As of this version, the HOME variable is used if it is set and the value from /etc/passwd is only used as a fallback. * The 'flowinfo' and 'scope_id' fields of GInetSocketAddress (introduced in GLib 2.32) have been fixed to be in host byte order rather than network byte order. This is an incompatible change, but the previous behavior was clearly broken, so it seems unlikely that anyone was using it. Notes about GLib 2.34 ===================== * GIO now looks for thumbnails in XDG_CACHE_HOME, following a recent alignment of the thumbnail spec with the basedir spec. * The default values for GThreadPools max_unused_threads and max_idle_time settings have been changed to 2 and 15*1000, respectively. Notes about GLib 2.32 ===================== * It is no longer necessary to use g_thread_init() or to link against libgthread. libglib is now always thread-enabled. Custom thread system implementations are no longer supported (including errorcheck mutexes). * The thread and synchronisation APIs have been updated. GMutex and GCond can be statically allocated without explicit initialisation, as can new types GRWLock and GRecMutex. The GStatic_______ variants of these types have been deprecated. GPrivate can also be statically allocated and has a nicer API (deprecating GStaticPrivate). Finally, g_thread_create() has been replaced with a substantially simplified g_thread_new(). * The g_once_init_enter()/_leave() functions have been replaced with macros that allow for a pointer to any gsize-sized object, not just a gsize*. The assertions to ensure that a pointer to a correctly-sized object is being used will not work with generic pointers (ie: (void*) and (gpointer) casts) which would have worked with the old version. * It is now mandatory to include glib.h instead of individual headers. * The -uninstalled variants of the pkg-config files have been dropped. * For a long time, gobject-2.0.pc mistakenly declared a public dependency on gthread-2.0.pc (when the dependency should have been private). This means that programs got away with calling g_thread_init() without explicitly listing gthread-2.0.pc among their dependencies. gthread has now been removed as a gobject dependency, which will cause such programs to break. The fix for this problem is either to declare an explicit dependency on gthread-2.0.pc (if you care about compatibility with older GLib versions) or to stop calling g_thread_init(). * g_debug() output is no longer enabled by default. It can be enabled on a per-domain basis with the G_MESSAGES_DEBUG environment variable like G_MESSAGES_DEBUG=domain1,domain2 or G_MESSAGES_DEBUG=all Notes about GLib 2.30 ===================== * GObject includes a generic marshaller, g_cclosure_marshal_generic. To use it, simply specify NULL as the marshaller in g_signal_new(). The generic marshaller is implemented with libffi, and consequently GObject depends on libffi now. Notes about GLib 2.28 ===================== * The GApplication API has changed compared to the version that was included in the 2.25 development snapshots. Existing users will need adjustments. Notes about GLib 2.26 ===================== * Nothing noteworthy. Notes about GLib 2.24 ===================== * It is now allowed to call g_thread_init(NULL) multiple times, and to call glib functions before g_thread_init(NULL) is called (although the later is mainly a change in docs as this worked before too). See the GThread reference documentation for the details. * GObject now links to GThread and threads are enabled automatically when g_type_init() is called. * GObject no longer allows to call g_object_set() on construct-only properties while an object is being initialized. If this behavior is needed, setting a custom constructor that just chains up will re-enable this functionality. * GMappedFile on an empty file now returns NULL for the contents instead of returning an empty string. The documentation specifically states that code may not rely on nul-termination here so any breakage caused by this change is a bug in application code. Notes about GLib 2.22 ===================== * Repeated calls to g_simple_async_result_set_op_res_gpointer used to leak the data. This has been fixed to always call the provided destroy notify. Notes about GLib 2.20 ===================== * The functions for launching applications (e.g. g_app_info_launch() + friends) now passes a FUSE file:// URI if possible (requires gvfs with the FUSE daemon to be running and operational). With gvfs 2.26, FUSE file:// URIs will be mapped back to gio URIs in the GFile constructors. The intent of this change is to better integrate POSIX-only applications, see bug #528670 for the rationale. The only user-visible change is when an application needs to examine an URI passed to it (e.g. as a positional parameter). Instead of looking at the given URI, the application will now need to look at the result of g_file_get_uri() after having constructed a GFile object with the given URI. Notes about GLib 2.18 ===================== * The recommended way of using GLib has always been to only include the toplevel headers glib.h, glib-object.h and gio.h. GLib enforces this by generating an error when individual headers are directly included. To help with the transition, the enforcement is not turned on by default for GLib headers (it is turned on for GObject and GIO). To turn it on, define the preprocessor symbol G_DISABLE_SINGLE_INCLUDES. Notes about GLib 2.16 ===================== * GLib now includes GIO, which adds optional dependencies against libattr and libselinux for extended attribute and SELinux support. Use --disable-xattr and --disable-selinux to build without these. Notes about GLib 2.10 ===================== * The functions g_snprintf() and g_vsnprintf() have been removed from the gprintf.h header, since they are already declared in glib.h. This doesn't break documented use of gprintf.h, but people have been known to include gprintf.h without including glib.h. * The Unicode support has been updated to Unicode 4.1. This adds several new members to the GUnicodeBreakType enumeration. * The support for Solaris threads has been retired. Solaris has provided POSIX threads for long enough now to have them available on every Solaris platform. * 'make check' has been changed to validate translations by calling msgfmt with the -c option. As a result, it may fail on systems with older gettext implementations (GNU gettext < 0.14.1, or Solaris gettext). 'make check' will also fail on systems where the C compiler does not support ELF visibility attributes. * The GMemChunk API has been deprecated in favour of a new 'slice allocator'. See the g_slice documentation for more details. * A new type, GInitiallyUnowned, has been introduced, which is intended to serve as a common implementation of the 'floating reference' concept that is e.g. used by GtkObject. Note that changing the inheritance hierarchy of a type can cause problems for language bindings and other code which needs to work closely with the type system. Therefore, switching to GInitiallyUnowned should be done carefully. g_object_compat_control() has been added to GLib 2.8.5 to help with the transition. Notes about GLib 2.6.0 ====================== * GLib 2.6 introduces the concept of 'GLib filename encoding', which is the on-disk encoding on Unix, but UTF-8 on Windows. All GLib functions returning or accepting pathnames have been changed to expect filenames in this encoding, and the common POSIX functions dealing with pathnames have been wrapped. These wrappers are declared in the header <glib/gstdio.h> which must be included explicitly; it is not included through <glib.h>. On current (NT-based) Windows versions, where the on-disk file names are Unicode, these wrappers use the wide-character API in the C library. Thus applications can handle file names containing any Unicode characters through GLib's own API and its POSIX wrappers, not just file names restricted to characters in the system codepage. To keep binary compatibility with applications compiled against older versions of GLib, the Windows DLL still provides entry points with the old semantics using the old names, and applications compiled against GLib 2.6 will actually use new names for the functions. This is transparent to the programmer. When compiling against GLib 2.6, applications intended to be portable to Windows must take the UTF-8 file name encoding into consideration, and use the gstdio wrappers to access files whose names have been constructed from strings returned from GLib. * Likewise, g_get_user_name() and g_get_real_name() have been changed to return UTF-8 on Windows, while keeping the old semantics for applications compiled against older versions of GLib. * The GLib uses an '_' prefix to indicate private symbols that must not be used by applications. On some platforms, symbols beginning with prefixes such as _g will be exported from the library, on others not. In no case can applications use these private symbols. In addition to that, GLib+ 2.6 makes several symbols private which were not in any installed header files and were never intended to be exported. * To reduce code size and improve efficiency, GLib, when compiled with the GNU toolchain, has separate internal and external entry points for exported functions. The internal names, which begin with IA__, may be seen when debugging a GLib program. * On Windows, GLib no longer opens a console window when printing warning messages if stdout or stderr are invalid, as they are in "Windows subsystem" (GUI) applications. Simply redirect stdout or stderr if you need to see them. * The child watch functionality tends to reveal a bug in many thread implementations (in particular the older LinuxThreads implementation on Linux) where it's not possible to call waitpid() for a child created in a different thread. For this reason, for maximum portability, you should structure your code to fork all child processes that you want to wait for from the main thread. * A problem was recently discovered with g_signal_connect_object(); it doesn't actually disconnect the signal handler once the object being connected to dies, just disables it. See the API docs for the function for further details and the correct workaround that will continue to work with future versions of GLib. usr/share/doc/dhcp-common-4.2.5/README 0000644 00000072132 14721015751 0012764 0 ustar 00 Internet Systems Consortium DHCP Distribution Version 4.2.5 8 January 2013 README FILE You should read this file carefully before trying to install or use the ISC DHCP Distribution. TABLE OF CONTENTS 1 WHERE TO FIND DOCUMENTATION 2 RELEASE STATUS 3 BUILDING THE DHCP DISTRIBUTION 3.1 UNPACKING IT 3.2 CONFIGURING IT 3.2.1 DYNAMIC DNS UPDATES 3.2.2 LOCALLY DEFINED OPTIONS 3.3 BUILDING IT 4 INSTALLING THE DHCP DISTRIBUTION 5 USING THE DHCP DISTRIBUTION 5.1 FIREWALL RULES 5.2 LINUX 5.2.1 IF_TR.H NOT FOUND 5.2.2 SO_ATTACH_FILTER UNDECLARED 5.2.3 PROTOCOL NOT CONFIGURED 5.2.4 BROADCAST 5.2.6 IP BOOTP AGENT 5.2.7 MULTIPLE INTERFACES 5.3 SCO 5.4 HP-UX 5.5 ULTRIX 5.6 FreeBSD 5.7 NeXTSTEP 5.8 SOLARIS 5.8.1 Solaris 11 5.8.2 Solaris 11 and ATF 5.8.3 Other Solaris Items 5.9 AIX 5.10 MacOS X 6 SUPPORT 6.1 HOW TO REPORT BUGS WHERE TO FIND DOCUMENTATION Documentation for this software includes this README file, the RELNOTES file, and the manual pages, which are in the server, common, client and relay subdirectories. The README file (this file) includes late-breaking operational and system-specific information that you should read even if you don't want to read the manual pages, and that you should *certainly* read if you run into trouble. Internet standards relating to the DHCP protocol are listed in the References document that is available in html, txt and xml formats in doc/ subdirectory. You will have the best luck reading the manual pages if you build this software and then install it, although you can read them directly out of the distribution if you need to. DHCP server documentation is in the dhcpd man page. Information about the DHCP server lease database is in the dhcpd.leases man page. Server configuration documentation is in the dhcpd.conf man page as well as the dhcp-options man page. A sample DHCP server configuration is in the file server/dhcpd.conf.example. The source for the dhcpd, dhcpd.leases and dhcpd.conf man pages is in the server/ sub- directory in the distribution. The source for the dhcp-options.5 man page is in the common/ subdirectory. DHCP Client documentation is in the dhclient man page. DHCP client configuration documentation is in the dhclient.conf man page and the dhcp-options man page. The DHCP client configuration script is documented in the dhclient-script man page. The format of the DHCP client lease database is documented in the dhclient.leases man page. The source for all these man pages is in the client/ subdirectory in the distribution. In addition, the dhcp-options man page should be referred to for information about DHCP options. DHCP relay agent documentation is in the dhcrelay man page, the source for which is distributed in the relay/ subdirectory. To read installed manual pages, use the man command. Type "man page" where page is the name of the manual page. This will only work if you have installed the ISC DHCP distribution using the ``make install'' command (described later). If you want to read manual pages that aren't installed, you can type ``nroff -man page |more'' where page is the filename of the unformatted manual page. The filename of an unformatted manual page is the name of the manual page, followed by '.', followed by some number - 5 for documentation about files, and 8 for documentation about programs. For example, to read the dhcp-options man page, you would type ``nroff -man common/dhcp-options.5 |more'', assuming your current working directory is the top level directory of the ISC DHCP Distribution. Please note that the pathnames of files to which our manpages refer will not be correct for your operating system until after you iterate 'make install' (so if you're reading a manpage out of the source directory, it may not have up-to-date information). RELEASE STATUS This is ISC DHCP 4.2.5, a maintenance release containing patches. In this release, the DHCPv6 server should be fully functional on Linux, Solaris, or any BSD. The DHCPv6 client should be similarly functional except on Solaris. The DHCPv4 server, relay, and client, should be fully functional on Linux, Solaris, any BSD, HPUX, SCO, NextSTEP, and Irix. If you are running the DHCP distribution on a machine which is a firewall, or if there is a firewall between your DHCP server(s) and DHCP clients, please read the section on firewalls which appears later in this document. If you wish to run the DHCP Distribution on Linux, please see the Linux-specific notes later in this document. If you wish to run on an SCO release, please see the SCO-specific notes later in this document. You particularly need to read these notes if you intend to support Windows 95 clients. If you are running HP-UX or Ultrix, please read the notes for those operating systems below. If you are running NeXTSTEP, please see the notes on NeXTSTEP below. If you start dhcpd and get a message, "no free bpf", that means you need to configure the Berkeley Packet Filter into your operating system kernel. On NetBSD, FreeBSD and BSD/os, type ``man bpf'' for information. On Digital Unix, type ``man pfilt''. BUILDING THE DHCP DISTRIBUTION UNPACKING IT To build the DHCP Distribution, unpack the compressed tar file using the tar utility and the gzip command - type something like: gunzip dhcp-4.2.5.tar.gz tar xvf dhcp-4.2.5.tar CONFIGURING IT Now, cd to the dhcp-4.2.5 subdirectory that you've just created and configure the source tree by typing: ./configure If the configure utility can figure out what sort of system you're running on, it will create a custom Makefile for you for that system; otherwise, it will complain. If it can't figure out what system you are using, that system is not supported - you are on your own. Several options may be enabled or disabled via the configure command. You can get a list of these by typing: ./configure --help DYNAMIC DNS UPDATES A fully-featured implementation of dynamic DNS updates is included in this release. It uses libraries from BIND and, to avoid issues with different versions, includes the necessary BIND version. The appropriate BIND libraries will be compiled and installed in the bind subdirectory as part of the make step. In order to build the necessary libraries you will need to have "gmake" available on your build system. There is documentation for the DDNS support in the dhcpd.conf manual page - see the beginning of this document for information on finding manual pages. LOCALLY DEFINED OPTIONS In previous versions of the DHCP server there was a mechanism whereby options that were not known by the server could be configured using a name made up of the option code number and an identifier: "option-nnn" This is no longer supported, because it is not future- proof. Instead, if you want to use an option that the server doesn't know about, you must explicitly define it using the method described in the dhcp-options man page under the DEFINING NEW OPTIONS heading. BUILDING IT Once you've run configure, just type ``make'', and after a while you should have a dhcp server. If you get compile errors on one of the supported systems mentioned earlier, please let us know. If you get warnings, it's not likely to be a problem - the DHCP server compiles completely warning-free on as many architectures as we can manage, but there are a few for which this is difficult. If you get errors on a system not mentioned above, you will need to do some programming or debugging on your own to get the DHCP Distribution working. INSTALLING THE DHCP DISTRIBUTION Once you have successfully gotten the DHCP Distribution to build, you can install it by typing ``make install''. If you already have an old version of the DHCP Distribution installed, you may want to save it before typing ``make install''. USING THE DHCP DISTRIBUTION FIREWALL RULES If you are running the DHCP server or client on a computer that's also acting as a firewall, you must be sure to allow DHCP packets through the firewall. In particular, your firewall rules _must_ allow packets from IP address 0.0.0.0 to IP address 255.255.255.255 from UDP port 68 to UDP port 67 through. They must also allow packets from your local firewall's IP address and UDP port 67 through to any address your DHCP server might serve on UDP port 68. Finally, packets from relay agents on port 67 to the DHCP server on port 67, and vice versa, must be permitted. We have noticed that on some systems where we are using a packet filter, if you set up a firewall that blocks UDP port 67 and 68 entirely, packets sent through the packet filter will not be blocked. However, unicast packets will be blocked. This can result in strange behaviour, particularly on DHCP clients, where the initial packet exchange is broadcast, but renewals are unicast - the client will appear to be unable to renew until it starts broadcasting its renewals, and then suddenly it'll work. The fix is to fix the firewall rules as described above. PARTIAL SERVERS If you have a server that is connected to two networks, and you only want to provide DHCP service on one of those networks (e.g., you are using a cable modem and have set up a NAT router), if you don't write any subnet declaration for the network you aren't supporting, the DHCP server will ignore input on that network interface if it can. If it can't, it will refuse to run - some operating systems do not have the capability of supporting DHCP on machines with more than one interface, and ironically this is the case even if you don't want to provide DHCP service on one of those interfaces. LINUX There are three big LINUX issues: the all-ones broadcast address, Linux 2.1 ip_bootp_agent enabling, and operations with more than one network interface. There are also two potential compilation/runtime problems for Linux 2.1/2.2: the "SO_ATTACH_FILTER undeclared" problem and the "protocol not configured" problem. LINUX: PROTOCOL NOT CONFIGURED If you get the following message, it's because your kernel doesn't have the linux packetfilter or raw packet socket configured: Make sure CONFIG_PACKET (Packet socket) and CONFIG_FILTER (Socket Filtering) are enabled in your kernel configuration If this happens, you need to configure your Linux kernel to support Socket Filtering and the Packet socket, or to select a kernel provided by your Linux distribution that has these enabled (virtually all modern ones do by default). LINUX: BROADCAST If you are running a recent version of Linux, this won't be a problem, but on older versions of Linux (kernel versions prior to 2.2), there is a potential problem with the broadcast address being sent incorrectly. In order for dhcpd to work correctly with picky DHCP clients (e.g., Windows 95), it must be able to send packets with an IP destination address of 255.255.255.255. Unfortunately, Linux changes an IP destination of 255.255.255.255 into the local subnet broadcast address (here, that's 192.5.5.223). This isn't generally a problem on Linux 2.2 and later kernels, since we completely bypass the Linux IP stack, but on old versions of Linux 2.1 and all versions of Linux prior to 2.1, it is a problem - pickier DHCP clients connected to the same network as the ISC DHCP server or ISC relay agent will not see messages from the DHCP server. It *is* possible to run into trouble with this on Linux 2.2 and later if you are running a verson of the DHCP server that was compiled on a Linux 2.0 system, though. It is possible to work around this problem on some versions of Linux by creating a host route from your network interface address to 255.255.255.255. The command you need to use to do this on Linux varies from version to version. The easiest version is: route add -host 255.255.255.255 dev eth0 On some older Linux systems, you will get an error if you try to do this. On those systems, try adding the following entry to your /etc/hosts file: 255.255.255.255 all-ones Then, try: route add -host all-ones dev eth0 Another route that has worked for some users is: route add -net 255.255.255.0 dev eth0 If you are not using eth0 as your network interface, you should specify the network interface you *are* using in your route command. LINUX: IP BOOTP AGENT Some versions of the Linux 2.1 kernel apparently prevent dhcpd from working unless you enable it by doing the following: echo 1 >/proc/sys/net/ipv4/ip_bootp_agent LINUX: MULTIPLE INTERFACES Very old versions of the Linux kernel do not provide a networking API that allows dhcpd to operate correctly if the system has more than one broadcast network interface. However, Linux 2.0 kernels with version numbers greater than or equal to 2.0.31 add an API feature: the SO_BINDTODEVICE socket option. If SO_BINDTODEVICE is present, it is possible for dhcpd to operate on Linux with more than one network interface. In order to take advantage of this, you must be running a 2.0.31 or greater kernel, and you must have 2.0.31 or later system headers installed *before* you build the DHCP Distribution. We have heard reports that you must still add routes to 255.255.255.255 in order for the all-ones broadcast to work, even on 2.0.31 kernels. In fact, you now need to add a route for each interface. Hopefully the Linux kernel gurus will get this straight eventually. Linux 2.1 and later kernels do not use SO_BINDTODEVICE or require the broadcast address hack, but do support multiple interfaces, using the Linux Packet Filter. LINUX: OpenWrt DHCP 4.1 has been tested on OpenWrt 7.09 and 8.09. In keeping with standard practice, client/scripts now includes a dhclient-script file for OpenWrt. However, this is not sufficient by itself to run dhcp on OpenWrt; a full OpenWrt package for DHCP is available at ftp://ftp.isc.org/isc/dhcp/dhcp-4.1.0-openwrt.tar.gz LINUX: 802.1q VLAN INTERFACES If you're using 802.1q vlan interfaces on Linux, it is necessary to vconfig the subinterface(s) to rewrite the 802.1q information out of packets received by the dhcpd daemon via LPF: vconfig set_flag eth1.523 1 1 Note that this may affect the performance of your system, since the Linux kernel must rewrite packets received via this interface. For more information, consult the vconfig man pages. SCO ISC DHCP will now work correctly on newer versions of SCO out of the box (tested on OpenServer 5.05b, assumed to work on UnixWare 7). Older versions of SCO have the same problem as Linux (described earlier). The thing is, SCO *really* doesn't want to let you add a host route to the all-ones broadcast address. You can try the following: ifconfig net0 xxx.xxx.xxx.xxx netmask 0xNNNNNNNN broadcast 255.255.255.255 If this doesn't work, you can also try the following strange hack: ifconfig net0 alias 10.1.1.1 netmask 8.0.0.0 Apparently this works because of an interaction between SCO's support for network classes and the weird netmask. The 10.* network is just a dummy that can generally be assumed to be safe. Don't ask why this works. Just try it. If it works for you, great. HP-UX HP-UX has the same problem with the all-ones broadcast address that SCO and Linux have. One user reported that adding the following to /etc/rc.config.d/netconf helped (you may have to modify this to suit your local configuration): INTERFACE_NAME[0]=lan0 IP_ADDRESS[0]=1.1.1.1 SUBNET_MASK[0]=255.255.255.0 BROADCAST_ADDRESS[0]="255.255.255.255" LANCONFIG_ARGS[0]="ether" DHCP_ENABLE[0]=0 ULTRIX Now that we have Ultrix packet filter support, the DHCP Distribution on Ultrix should be pretty trouble-free. However, one thing you do need to be aware of is that it now requires that the pfilt device be configured into your kernel and present in /dev. If you type ``man packetfilter'', you will get some information on how to configure your kernel for the packet filter (if it isn't already) and how to make an entry for it in /dev. FreeBSD Versions of FreeBSD prior to 2.2 have a bug in BPF support in that the ethernet driver swaps the ethertype field in the ethernet header downstream from BPF, which corrupts the output packet. If you are running a version of FreeBSD prior to 2.2, and you find that dhcpd can't communicate with its clients, you should #define BROKEN_FREEBSD_BPF in site.h and recompile. Modern versions of FreeBSD include the ISC DHCP 3.0 client as part of the base system, and the full distribution (for the DHCP server and relay agent) is available from the Ports Collection in /usr/ports/net/isc-dhcp3, or as a package on FreeBSD installation CDROMs. NeXTSTEP The NeXTSTEP support uses the NeXTSTEP Berkeley Packet Filter extension, which is not included in the base NextStep system. You must install this extension in order to get dhcpd or dhclient to work. SOLARIS There are two known issues seen when compiling using the Sun compiler. The first is that older Sun compilers generate an error on some of our uses of the flexible array option. Newer versions only generate a warning, which can be safely ignored. If you run into this error ("type of struct member "buf" can not be derived from structure with flexible array member"), upgrade your tools to Oracle Solaris Studio (previously Sun Studio) 12 or something newer. The second is the interaction between the configure script and the makefiles for the Bind libraries. Currently we don't pass all environment variables between the DHCP configure and the Bind configure. If you attempt to specify the compiler you wish to use like this: CC=/opt/SUNWspro/bin/cc ./configure "make" may not build the Bind libraries with that compiler. In order to use the same compiler for Bind and DHCP we suggest the following commands: CC=/opt/SUNWspro/bin/cc ./configure CC=/opt/SUNWspro/bin/cc make Solaris 11 We have integrated a patch from Oracle to use sockets instead of DLPI on Solaris 11. This functionality was written for use with Solaris Studio 12.2 and requires the system/header package. By default this code is disabled in order to minimize disruptions for current users. In order to enable this code you will need to enable both USE_SOCKETS and USE_V4_PKTINFO as part of the configuration step. The command line would be something like: ./configure --enable-use-sockets --enable-ipv4-pktinfo Solaris 11 and ATF We have reports that ATF 0.15 and 0.16 do not build on Solaris 11. The following changes to the ATF source code appear to fix this issue: diff -ru atf-0.15/atf-c/tp_test.c atf-0.15-patched/atf-c/tp_test.c --- atf-0.15/atf-c/tp_test.c 2011-12-06 06:31:11.000000000 +0100 +++ atf-0.15-patched/atf-c/tp_test.c 2012-06-19 15:54:57.000000000 +0200 @@ -28,6 +28,7 @@ */ #include <string.h> +#include <stdio.h> #include <unistd.h> #include <atf-c.h> diff -ru atf-0.15/atf-run/requirements.cpp atf-0.15-patched/atf-run/requirements.cpp --- atf-0.15/atf-run/requirements.cpp 2012-01-13 20:44:25.000000000 +0100 +++ atf-0.15-patched/atf-run/requirements.cpp 2012-06-19 15:41:51.000000000 +0200 @@ -29,7 +29,7 @@ extern "C" { #include <sys/param.h> -#include <sys/sysctl.h> +//#include <sys/sysctl.h> } #include <cerrno> Other Solaris Items One problem which has been observed and is not fixed in this patchlevel has to do with using DLPI on Solaris machines. The symptom of this problem is that the DHCP server never receives any requests. This has been observed with Solaris 2.6 and Solaris 7 on Intel x86 systems, although it may occur with other systems as well. If you encounter this symptom, and you are running the DHCP server on a machine with a single broadcast network interface, you may wish to edit the includes/site.h file and uncomment the #define USE_SOCKETS line. Then type ``make clean; make''. As an alternative workaround, it has been reported that running 'snoop' will cause the dhcp server to start receiving packets. So the practice reported to us is to run snoop at dhcpd startup time, with arguments to cause it to receive one packet and exit. snoop -c 1 udp port 67 > /dev/null & The DHCP client on Solaris will only work with DLPI. If you run it and it just keeps saying it's sending DHCPREQUEST packets, but never gets a response, you may be having DLPI trouble as described above. If so, we have no solution to offer at this time, aside from the above workaround which should also work here. Also, because Solaris requires you to "plumb" an interface before it can be detected by the DHCP client, you must either specify the name(s) of the interface(s) you want to configure on the command line, or must plumb the interfaces prior to invoking the DHCP client. This can be done with ``ifconfig iface plumb'', where iface is the name of the interface (e.g., ``ifconfig hme0 plumb''). It should be noted that Solaris versions from 2.6 onward include a DHCP client that you can run with ``/sbin/ifconfig iface dhcp start'' rather than using the ISC DHCP client, including DHCPv6. Consequently, we don't believe there is a need for the client to run on Solaris, and have not engineered the needed DHCPv6 modifications for the dhclient-script. If you feel this is in error, or have a need, please contact us. AIX The AIX support uses the BSD socket API, which cannot differentiate on which network interface a broadcast packet was received; thus the DHCP server and relay will work only on a single interface. (They do work on multi-interface machines if configured to listen on only one of the interfaces.) We have reports of Windows XP clients having difficutly retrieving addresses from a server running on an AIX machine. This issue was traced to the client requiring messages be sent to the all ones broadcast address (255.255.255.255) while the AIX server was sending to 192.168.0.255. You may be able to solve this by including a relay between the client and server with the relay configured to use a broadcast of all-ones. A second option that worked for AIX 5.1 but doesn't seem to work for AIX 5.3 was to: create a host file entry for all-ones (255.255.255.255) and then add a route: route add -host all-ones -interface <local-ip-address> The ISC DHCP distribution does not include a dhclient-script for AIX-- AIX comes with a DHCP client. Contribution of a working dhclient-script for AIX would be welcome. MacOS X The MacOS X system uses a TCP/IP stack derived from FreeBSD with a user-friendly interface named the System Configuration Framework. As it includes a builtin DHCPv4 client (you are better just using that), this text is only about the DHCPv6 client (``dhclient -6 ...''). The DNS configuration (domain search list and name servers' addresses) is managed by a System Configuration agent, not by /etc/resolv.conf (which is a link to /var/run/resolv.conf, which itself only reflects the internal state; the System Configuration framework's Dynamic Store). This means that modifying resolv.conf directly doesn't have the intended effect, instead the macos script sample creates its own resolv.conf.dhclient6 in /var/run, and inserts the contents of this file into the Dynamic Store. When updating the address configuration the System Configuration framework expects the prefix and a default router along with the configured address. As this extra information is not available via the DHCPv6 protocol the System Configuration framework isn't usable for address configuration, instead ifconfig is used directly. Note the Dynamic Store (from which /var/run/resolv.conf is built) is recomputed from scratch when the current location/set is changed. Running the dhclient-script reinstalls the resolv.conf.dhclient6 configuration. SUPPORT The Internet Systems Consortium DHCP server is developed and distributed by ISC in the public trust, thanks to the generous donations of its sponsors. ISC now also offers commercial quality support contracts for ISC DHCP, more information about ISC Support Contracts can be found at the following URL: https://www.isc.org/services/support/ Please understand that we may not respond to support inquiries unless you have a support contract. ISC will continue its practice of always responding to critical items that effect the entire community, and responding to all other requests for support upon ISC's mailing lists on a best-effort basis. However, ISC DHCP has attracted a fairly sizable following on the Internet, which means that there are a lot of knowledgeable users who may be able to help you if you get stuck. These people generally read the dhcp-users@isc.org mailing list. Be sure to provide as much detail in your query as possible. If you are going to use ISC DHCP, you should probably subscribe to the dhcp-users or dhcp-announce mailing lists. WHERE TO SEND FEATURE REQUESTS: We like to hear your feedback. We may not respond to it all the time, but we do read it. If ISC DHCP doesn't work well for you, or you have an idea that would improve it for your use, please send your suggestion to dhcp-suggest@isc.org. This is also an excellent place to send patches that add new features. WHERE TO REPORT BUGS: If you want the act of sending in a bug report to result in you getting help in the form of a fixed piece of software, you are asking for help. Your bug report is helpful to us, but fundamentally you are making a support request, so please use the addresses described in the previous paragraphs. If you are _sure_ that your problem is a bug, and not user error, or if your bug report includes a patch, you can send it to our ticketing system at dhcp-bugs@isc.org. If you have not received a notice that the ticket has been resolved, then we're still working on it. PLEASE DO NOT REPORT BUGS IN OLD SOFTWARE RELEASES! Fetch the latest release and see if the bug is still in that version of the software, and if it is still present, _then_ report it. ISC release versions always have three numbers, for example: 1.2.3. The 'major release' is 1 here, the 'minor release' is 2, and the 'maintenance release' is 3. ISC will accept bug reports against the most recent two major.minor releases: for example, 1.0.0 and 0.9.0, but not 0.8.* or prior. PLEASE take a moment to determine where the ISC DHCP distribution that you're using came from. ISC DHCP is sometimes heavily modified by integrators in various operating systems - it's not that we feel that our software is perfect and incapable of having bugs, but rather that it is very frustrating to find out after many days trying to help someone that the sources you're looking at aren't what they're running. When in doubt, please retrieve the source distribution from ISC's web page and install it. HOW TO REPORT BUGS OR REQUEST HELP When you report bugs or ask for help, please provide us complete information. A list of information we need follows. Please read it carefully, and put all the information you can into your initial bug report. This will save us a great deal of time and more informative bug reports are more likely to get handled more quickly overall. 1. The specific operating system name and version of the machine on which the DHCP server or client is running. 2. The specific operating system name and version of the machine on which the client is running, if you are having trouble getting a client working with the server. 3. If you're running Linux, the version number we care about is the kernel version and maybe the library version, not the distribution version - e.g., while we don't mind knowing that you're running Redhat version mumble.foo, we must know what kernel version you're running, and it helps if you can tell us what version of the C library you're running, although if you don't know that off the top of your head it may be hard for you to figure it out, so don't go crazy trying. 4. The specific version of the DHCP distribution you're running, as reported by dhcpd -t. 5. Please explain the problem carefully, thinking through what you're saying to ensure that you don't assume we know something about your situation that we don't know. 6. Include your dhcpd.conf and dhcpd.leases file as MIME attachments if they're not over 100 kilobytes in size each. If they are this large, please make them available to us eg via a hidden http:// URL or FTP site. If you're not comfortable releasing this information due to sensitive contents, you may encrypt the file to our release signing key, available on our website. 7. Include a log of your server or client running until it encounters the problem - for example, if you are having trouble getting some client to get an address, restart the server with the -d flag and then restart the client, and send us what the server prints. Likewise, with the client, include the output of the client as it fails to get an address or otherwise does the wrong thing. Do not leave out parts of the output that you think aren't interesting. 8. If the client or server is dumping core, please run the debugger and get a stack trace, and include that in your bug report. For example, if your debugger is gdb, do the following: gdb dhcpd dhcpd.core (gdb) where [...] (gdb) quit This assumes that it's the dhcp server you're debugging, and that the core file is in dhcpd.core. Please see https://www.isc.org/software/dhcp/ for details on how to subscribe to the ISC DHCP mailing lists. usr/share/doc/sharutils-4.13.3/README 0000644 00000005124 14721016045 0012650 0 ustar 00 This is the set of GNU shar utilities. "sharutils" is now licensed under the terms of the GNU GPL version 3 (or, at your option, any later version). `shar' makes so-called shell archives out of many files, preparing them for transmission by electronic mail services. `unshar' helps unpacking shell archives after reception. The core of both programs is initially derived from public domain. Some modules and other code sections are freely borrowed from other GNU distributions, bringing `shar' under the terms of the GNU General Public License. `uuencode' prepares a file for transmission over an electronic channel which ignores or otherwise mangles the eight bit (high order bit) of bytes. `uudecode' does the converse transformation. They are derived from the BSD NET/2 distribution, but enchanced with the features described in recent POSIX standards. If you have more powerful `uuencode' and `uudecode' already available, you may want to use `./configure --disable-uucode' to prevent their installation. The sharutils package now is internationalized. This includes the generated shell scripts. As described in the `ABOUT-NLS' file you have various options for handling this internationalization but this package is special in one point: it always needs the GNU message catalog files to be installed. Therefore it might be a good idea to always use the GNU gettext functions and not the functions provided by your system. This is of course not needed if your system uses GNU gettext in its system library. See file `ABOUT-NLS' for how to customize this program to your language. See file `COPYING' for copying conditions. See file `TODO' for a list of things people have thought about doing. See file `INSTALL' for compilation and installation instructions. See file `NEWS' for a list of major changes in the current release. See file `THANKS' for a list of contributors. The man pages are basically unsupported. Their installation is kept separate from `make install'. You use `make install-man' for them. Better think GNU and switch to Info. Your feedback will help us to make a better and more portable product. Mail suggestions and bug reports (including documentation errors) for this program to `bug-gnu-utils@gnu.org'. Language file updates: uk 2013-01-05 pl 2013-01-05 nl 2013-01-05 gl 2013-01-05 et 2013-01-05 cs 2013-01-05 tr 2012-12-24 sv 2012-08-28 vi 2012-08-14 fr 2012-08-14 sr 2012-03-31 de 2012-01-14 it 2011-12-05 ja 2011-10-20 es 2011-10-18 zh_CN 2011-04-28 ca 2011-04-11 fi 2011-02-08 da 2011-02-07 id 2010-02-27 ru 2006-05-22 ga 2006-05-22 bg 2006-05-22 hu 2002-08-05 zh_TW 2002-08-03 el 1998-06-20 usr/share/doc/tokyocabinet-1.4.48/README 0000644 00000002026 14721016242 0013330 0 ustar 00 ================================================================ Tokyo Cabinet: a modern implementation of DBM Copyright (C) 2006-2011 Fal Labs ================================================================ Please read the following documents with a WWW browser. How to install Tokyo Cabinet is explained in the specification. README - this file COPYING - license ChangeLog - history of enhancement doc/index.html - index of documents Contents of the directory tree is below. ./ - sources of Tokyo Cabinet ./doc/ - manuals and specifications ./man/ - manuals for nroff ./example/ - sample code of tutorial ./lab/ - for test and experiment ./bros/ - for comparison with other database managers Tokyo Cabinet is released under the terms of the GNU Lesser General Public License. See the file `COPYING' for details. Tokyo Cabinet was written by FAL Labs. You can contact the author by e-mail to `hirarin@gmail.com'. Thanks. == END OF FILE == usr/share/doc/perl-Text-Soundex-3.04/README 0000644 00000011116 14721016307 0013776 0 ustar 00 Text::Soundex - Implementation of the soundex algorithm. Basic Usage: Soundex is used to do a one way transformation of a name, converting a character string given as input into a set of codes representing the identifiable sounds those characters might make in the output. For example: use Text::Soundex; print soundex("Mark"), "\n"; # prints: M620 print soundex("Marc"), "\n"; # prints: M620 print soundex("Hansen"), "\n"; # prints: H525 print soundex("Hanson"), "\n"; # prints: H525 print soundex("Henson"), "\n"; # prints: H525 In many situations, code such as the following: if ($name1 eq $name2) { ... } Can be substituted with: if (soundex($name1) eq soundex($name2)) { ... } Installation: Once the archive has been unpacked then the following steps are needed to build, test and install the module (to be done in the directory which contains the Makefile.PL) perl Makefile.PL make make test If the make test succeeds then the next step may need to be run as root (on a Unix-like system) or with special privileges on other systems. make install If you do not want to use the XS code (for whatever reason) do the following instead of the above: perl Makefile.PL --no-xs make make test make install If any of the tests report 'not ok' and you are running perl 5.6.0 or later then please contact Mark Mielke <mark@mielke.cc> History: Version 3.03: Updated to allow the XS implementation to work properly under an EBCDIC/EBCDIC-UTF8 character set environment. Updated documentation to better describe the history of the soundex algorithm and how it applies to this module. Version 3.02: 3.01 and 3.00 used the 'U8' type incorrectly causing some strict compilers to complain or refuse to compile the XS code. Also, Unicode support did not work properly for Perl 5.6.x. Both of these problems are now fixed. Version 3.01: A bug with non-UTF 8 strings that contain non-ASCII alphabetic characters was fixed. The soundex_unicode() and soundex_nara_unicode() wrapper routines were included and the documentation refers the user to the excellent Text::Unidecode module to perform soundex encodings using unicode strings. The Perl versions of the routines have been further optimized, and correct a border case involving non-alphabetic characters at the beginning of the string. Version 3.00: Support for UTF-8 strings (unicode strings) is now in place. Note that this allows UTF-8 strings to be passed to the XS version of the soundex() routine. The Soundex algorithm treats characters outside the ascii range (0x00 - 0x7F) as if they were not alphabetical. The interface has been simplified. In order to explicitly use the non-XS implementation of soundex(): use Text::Soundex (); $code = Text::Soundex::soundex_noxs($name); In order to use the NARA soundex algorithm: use Text::Soundex 'soundex_nara'; $code = soundex_nara($name); Use of the ':NARA-Ruleset' import directive is now obsolete. To emulate the old behaviour: use Text::Soundex (); *soundex = \&Text::Soundex::soundex_nara; $code = soundex($name); Version 2.20: This version includes support for the algorithm used to index the U.S. Federal Censuses. There is a slight descrepancy in the definition for a soundex code which is not commonly known or recognized involved similar sounding letters being seperated by the characters H or W. This is defined as the NARA ruleset, as this descrepency was discovered by them. (Calling it "the US Census ruleset" was too unwieldy...) NARA can be found at: http://www.nara.gov/genealogy/ The algorithm used by NARA can be found at: http://home.utah-inter.net/kinsearch/Soundex.html Version 2.00: This version is a full re-write of the 1.0 engine by Mark Mielke. The goal was for speed... and this was achieved. There is an optional XS module which can be used completely transparently by the user which offers a further speed increase of a factor of more than 7.5X. Version 1.00: This version can be found in the perl core distribution from at least Perl 5.8.0 and down. It was written by Mike Stok. It can be identified by the fact that it does not contain a $VERSION in the beginning of the module, and as well it uses an RCS tag with a version of 1.x. This version, before some perl5'ish packaging was introduced, was actually written for perl4. usr/share/doc/elinks-0.12/README 0000644 00000005043 14721016311 0011745 0 ustar 00 ELinks - an advanced web browser ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ELinks is an advanced and well-established feature-rich text mode web (HTTP/FTP/..) browser. ELinks can render both frames and tables, is highly customizable and can be extended via scripts. It is very portable and runs on a variety of platforms. The ELinks official website is available at http://elinks.cz/ Please see the SITES file for mirrors or other recommended sites. If you want to install ELinks on your computer, see the INSTALL file for further instructions. A good start point is documentation files available in doc/, especially the file named index.txt. If you want to request features or report bugs, see community information at http://elinks.cz/community.html and feedback information available at http://elinks.cz/feedback.html. If you want to write some patches, please first read the doc/hacking.txt document. If you want to add a new language or update the translation for an existing one, please read po/README document. If you want to write some documentation, well, you're welcome! ;) Historical notes ~~~~~~~~~~~~~~~~ Initially, ELinks was a development version of Links (Lynx-like text WWW browser), with more liberal features policy and development style. Its purpose was to provide an alternative to Links, and to test and tune various new features, but still provide good rock-solid releases inside stable branches. Why not contribute to Links instead? Well, first I made a bunch of patches for the original Links, but Mikulas wasn't around to integrate them, so I started releasing my fork. When he came back, a significant number of them got refused because Mikulas did not like them, as he just wouldn't have any use for them himself. He wants to keep Links with a relatively closed feature set and merge only new features which he himself needs. It has advantages that the tree is very narrow and the code is small and contains very little bloat. ELinks, on the contrary, aims to provide a full-featured web browser, superior to both lynx and w3m and with the power (but not slowness and memory usage) of Mozilla, Konqueror and similar browsers. However, to prevent drastic bloating of the code, the development is driven in the course of modularization and separation of add-on modules (like cookies, bookmarks, ssl, scripting etc). For more details about ELinks history, please see http://elinks.cz/history.html If you are more interested in the history and various Links clones and versions, you can examine the website at http://links.sf.net/ vim: textwidth=80 usr/share/doc/perl-HTTP-Message-6.06/README 0000644 00000001737 14721016345 0013607 0 ustar 00 The HTTP-Message distribution contains classes useful for representing the messages passed in HTTP style communication. These are classes representing requests, responses and the headers contained within them. The following classes are provided: HTTP::Message base class (what's common between requests and responses) - HTTP::Request request on a resource (subclass of message) - HTTP::Response response from the resource (subclass of message) HTTP::Headers headers embedded in messages Other related modules: HTTP::Config configuration of request/response handling HTTP::Headers::Util helper functions for parsing of HTTP header values HTTP::Request::Common helper functions for constructing requests HTTP::Status symbolic names for the HTTP response status codes This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. Copyright 1995-2008 Gisle Aas. usr/share/doc/openssh-7.4p1/README 0000644 00000005076 14721016404 0012341 0 ustar 00 See https://www.openssh.com/releasenotes.html#7.4p1 for the release notes. Please read https://www.openssh.com/report.html for bug reporting instructions and note that we do not use Github for bug reporting or patch/pull-request management. - A Japanese translation of this document and of the release notes is - available at http://www.unixuser.org/~haruyama/security/openssh/index.html - Thanks to HARUYAMA Seigo <haruyama@unixuser.org> This is the port of OpenBSD's excellent OpenSSH[0] to Linux and other Unices. OpenSSH is based on the last free version of Tatu Ylonen's sample implementation with all patent-encumbered algorithms removed (to external libraries), all known security bugs fixed, new features reintroduced and many other clean-ups. OpenSSH has been created by Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos, Theo de Raadt, and Dug Song. It has a homepage at https://www.openssh.com/ This port consists of the re-introduction of autoconf support, PAM support, EGD[1]/PRNGD[2] support and replacements for OpenBSD library functions that are (regrettably) absent from other unices. This port has been best tested on AIX, Cygwin, HP-UX, Linux, MacOS/X, NetBSD, OpenBSD, OpenServer, Solaris, Unicos, and UnixWare. This version actively tracks changes in the OpenBSD CVS repository. The PAM support is now more functional than the popular packages of commercial ssh-1.2.x. It checks "account" and "session" modules for all logins, not just when using password authentication. OpenSSH depends on Zlib[3], OpenSSL[4] and optionally PAM[5]. There is now several mailing lists for this port of OpenSSH. Please refer to https://www.openssh.com/list.html for details on how to join. Please send bug reports and patches to the mailing list openssh-unix-dev@mindrot.org. The list is open to posting by unsubscribed users. Code contribution are welcomed, but please follow the OpenBSD style guidelines[6]. Please refer to the INSTALL document for information on how to install OpenSSH on your system. Damien Miller <djm@mindrot.org> Miscellania - This version of OpenSSH is based upon code retrieved from the OpenBSD CVS repository which in turn was based on the last free sample implementation released by Tatu Ylonen. References - [0] https://www.openssh.com/ [1] http://www.lothar.com/tech/crypto/ [2] http://www.aet.tu-cottbus.de/personen/jaenicke/postfix_tls/prngd.html [3] http://www.gzip.org/zlib/ [4] http://www.openssl.org/ [5] http://www.openpam.org http://www.kernel.org/pub/linux/libs/pam/ (PAM also is standard on Solaris and HP-UX 11) [6] http://man.openbsd.org/style.9 usr/share/doc/ncurses-5.9/README 0000644 00000023744 14721016506 0012113 0 ustar 00 ------------------------------------------------------------------------------- -- Copyright (c) 1998-2011,2012 Free Software Foundation, Inc. -- -- -- -- Permission is hereby granted, free of charge, to any person obtaining a -- -- copy of this software and associated documentation files (the -- -- "Software"), to deal in the Software without restriction, including -- -- without limitation the rights to use, copy, modify, merge, publish, -- -- distribute, distribute with modifications, sublicense, and/or sell copies -- -- of the Software, and to permit persons to whom the Software is furnished -- -- to do so, subject to the following conditions: -- -- -- -- The above copyright notice and this permission notice shall be included -- -- in all copies or substantial portions of the Software. -- -- -- -- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS -- -- OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF -- -- MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN -- -- NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, -- -- DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR -- -- OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE -- -- USE OR OTHER DEALINGS IN THE SOFTWARE. -- -- -- -- Except as contained in this notice, the name(s) of the above copyright -- -- holders shall not be used in advertising or otherwise to promote the -- -- sale, use or other dealings in this Software without prior written -- -- authorization. -- ------------------------------------------------------------------------------- -- $Id: README,v 1.25 2012/08/11 20:11:26 tom Exp $ ------------------------------------------------------------------------------- README file for the ncurses package See the file ANNOUNCE for a summary of ncurses features and ports. See the file INSTALL for instructions on how to build and install ncurses. See the file NEWS for a release history and bug-fix notes. See the file TO-DO for things that still need doing, including known bugs. Browse the file misc/ncurses-intro.html for narrative descriptions of how to use ncurses and the panel, menu, and form libraries. Browse the file doc/html/hackguide.html for a tour of the package internals. ROADMAP AND PACKAGE OVERVIEW: You should be reading this file in a directory called: ncurses-d.d, where d.d is the current version number (see the dist.mk file in this directory for that). There should be a number of subdirectories, including `c++', `form', `man', `menu', `misc', `ncurses', `panel', `progs', `test', 'tack' and `Ada95'. (The 'tack' program may be distributed separately). A full build/install of this package typically installs several libraries, a handful of utilities, and a database hierarchy. Here is an inventory of the pieces: The libraries are: libncurses.a (normal) libncurses.so (shared) libncurses_g.a (debug and trace code enabled) libncurses_p.a (profiling enabled) libpanel.a (normal) libpanel.so (shared) libpanel_g.a (debug and trace code enabled) libmenu.a (normal) libmenu.so (shared) libmenu_g.a (debug enabled) libform.a (normal) libform.so (shared) libform_g.a (debug enabled) If you configure using the --enable-widec option, a "w" is appended to the library names (e.g., libncursesw.a), and the resulting libraries support wide-characters, e.g., via a UTF-8 locale. The corresponding header files are compatible with the non-wide-character configuration; wide-character features are provided by ifdef's in the header files. The wide-character library interfaces are not binary-compatible with the non-wide-character version. If you configure using the --enable-reentrant option, a "t" is appended to the library names (e.g., libncursest.a) and the resulting libraries have a different binary interface which makes the ncurses interface more "opaque". The ncurses libraries implement the curses API. The panel, menu and forms libraries implement clones of the SVr4 panel, menu and forms APIs. The source code for these lives in the `ncurses', `panel', `menu', and `form' directories respectively. In the `c++' directory, you'll find code that defines an interface to the curses, forms, menus and panels library packaged as C++ classes, and a demo program in C++ to test it. These class definition modules are not installed by the 'make install.libs' rule as libncurses++. In the `Ada95' directory, you'll find code and documentation for an Ada95 binding of the curses API, to be used with the GNAT compiler. This binding is built by a normal top-level `make' if configure detects an usable version of GNAT (3.11 or above). It is not installed automatically. See the Ada95 directory for more build and installation instructions and for documentation of the binding. To do its job, the ncurses code needs your terminal type to be set in the environment variable TERM (normally set by your OS; under UNIX, getty(1) typically does this, but you can override it in your .profile); and, it needs a database of terminal descriptions in which to look up your terminal type's capabilities. In older (V7/BSD) versions of curses, the database was a flat text file, /etc/termcap; in newer (USG/USL) versions, the database is a hierarchy of fast-loading binary description blocks under /usr/lib/terminfo. These binary blocks are compiled from an improved editable text representation called `terminfo' format (documented in man/terminfo.5). The ncurses library can use either /etc/termcap or the compiled binary terminfo blocks, but prefers the second form. In the `misc' directory, there is a text file terminfo.src, in editable terminfo format, which can be used to generate the terminfo binaries (that's what make install.data does). If the package was built with the --enable-termcap option enabled, and the ncurses library cannot find a terminfo description for your terminal, it will fall back to the termcap file supplied with your system (which the ncurses package installation leaves strictly alone). The utilities are as follows: tic -- terminfo source to binary compiler infocmp -- terminfo binary to source decompiler/comparator clear -- emits clear-screen for current terminal tabs -- set tabs on a terminal tput -- shell-script access to terminal capabilities. toe -- table of entries utility tset -- terminal-initialization utility The first two (tic and infocmp) are used for manipulating terminfo descriptions; the next two (clear and tput) are for use in shell scripts. The last (tset) is provided for 4.4BSD compatibility. The source code for all of these lives in the `progs' directory. Detailed documentation for all libraries and utilities can be found in the `man' and `doc' directories. An HTML introduction to ncurses, panels, and menus programming lives in the `doc/html' directory. Manpages in HTML format are under `doc/html/man'. The `test' directory contains programs that can be used to verify or demonstrate the functions of the ncurses libraries. See test/README for descriptions of these programs. Notably, the `ncurses' utility is designed to help you systematically exercise the library functions. AUTHORS: Pavel Curtis: wrote the original ncurses Zeyd M. Ben-Halim: port of original to Linux and many enhancements. Thomas Dickey (maintainer for 1.9.9g through 4.1, resuming with FSF's 5.0): configuration scripts, porting, mods to adhere to XSI Curses in the areas of background color, terminal modes. Also memory leak testing, the wresize, default colors and key definition extensions and numerous bug fixes -- more than half of those enumerated in NEWS beginning with the internal release 1.8.9, see http://invisible-island.net/personal/changelogs.html Florian La Roche (official maintainer for FSF's ncurses 4.2) Beginning with release 4.2, ncurses is distributed under an MIT-style license. Eric S. Raymond: the man pages, infocmp(1), tput(1), clear(1), captoinfo(1), tset(1), toe(1), most of tic(1), trace levels, the HTML intro, wgetnstr() and many other entry points, the cursor-movement optimization, the scroll-pack optimizer for vertical motions, the mouse interface and xterm mouse support, and the ncurses test program. Juergen Pfeifer The menu and form libraries, C++ bindings for ncurses, menus, forms and panels, as well as the Ada95 binding. Ongoing support for panel. CONTRIBUTORS: Alexander V. Lukyanov for numerous fixes and improvements to the optimization logic. David MacKenzie for first-class bug-chasing and methodical testing. Ross Ridge for the code that hacks termcap parameterized strings into terminfo. Warren Tucker and Gerhard Fuernkranz, for writing and sending the panel library. Hellmuth Michaelis, for many patches and testing the optimization code. Eric Newton, Ulrich Drepper, and Anatoly Ivasyuk: the C++ code. Jonathan Ross, for lessons in using sed. Keith Bostic (maintainer of 4.4BSD curses) for help, criticism, comments, bug-finding, and being willing to deep-six BSD curses for this one when it grew up. Richard Stallman, for his commitment to making ncurses free software. Countless other people have contributed by reporting bugs, sending fixes, suggesting improvements, and generally whining about ncurses :-) BUGS: See the INSTALL file for bug and developer-list addresses. The Hacker's Guide in the doc directory includes some guidelines on how to report bugs in ways that will get them fixed most quickly. usr/share/doc/yajl-2.0.4/README 0000644 00000005363 14721016554 0011516 0 ustar 00 ********************************************************************** This is YAJL 2, for the legacy version of YAJL. see https://github.com/lloyd/yajl/tree/1.x ********************************************************************** Welcome to Yet Another JSON Library (YAJL) ## Why does the world need another C library for parsing JSON? Good question. In a review of current C JSON parsing libraries I was unable to find one that satisfies my requirements. Those are, 0. written in C 1. portable 2. robust -- as close to "crash proof" as possible 3. data representation independent 4. fast 5. generates verbose, useful error messages including context of where the error occurs in the input text. 6. can parse JSON data off a stream, incrementally 7. simple to use 8. tiny Numbers 3, 5, 6, and 7 where particularly hard to find, and were what caused me to ultimately create YAJL. This document is a tour of some of the more important aspects of YAJL. ## YAJL is Free. Permissive licensing means you can use it in open source and commercial products alike without any fees. My request beyond the licensing is that if you find bugs drop me a email, or better yet, fork and fix. Porting YAJL should be trivial, the implementation is ANSI C. If you port to new systems I'd love to hear of it and integrate your patches. ## YAJL is data representation independent. BYODR! Many JSON libraries impose a structure based data representation on you. This is a benefit in some cases and a drawback in others. YAJL uses callbacks to remain agnostic of the in-memory representation. So if you wish to build up an in-memory representation, you may do so using YAJL, but you must bring the code that defines and populates the in memory structure. This also means that YAJL can be used by other (higher level) JSON libraries if so desired. ## YAJL supports stream parsing This means you do not need to hold the whole JSON representation in textual form in memory. This makes YAJL ideal for filtering projects, where you're converting YAJL from one form to another (i.e. XML). The included JSON pretty printer is an example of such a filter program. ## YAJL is fast Minimal memory copying is performed. YAJL, when possible, returns pointers into the client provided text (i.e. for strings that have no embedded escape chars, hopefully the common case). I've put a lot of effort into profiling and tuning performance, but I have ignored a couple possible performance improvements to keep the interface clean, small, and flexible. My hope is that YAJL will perform comparably to the fastest JSON parser out there. YAJL should impose both minimal CPU and memory requirements on your application. ## YAJL is tiny. Fat free. No whip. enjoy, Lloyd - July, 2007 usr/share/doc/strace-4.24/README 0000644 00000002500 14721017033 0011745 0 ustar 00 This is strace - a diagnostic, debugging and instructional userspace utility with a traditional command-line interface for Linux. It is used to monitor and tamper with interactions between processes and the Linux kernel, which include system calls, signal deliveries, and changes of process state. The operation of strace is made possible by the kernel feature known as ptrace. strace is released under a Berkeley-style license at the request of Paul Kranenburg; see the file COPYING for details. See the file CREDITS for a list of authors and other contributors. See the file INSTALL for compilation and installation instructions. See the file NEWS for information on what has changed in recent versions. The project's homepage is at https://strace.io strace has a mailing list: strace-devel@lists.strace.io System requirements: * Linux kernel >= 2.6.18 is recommended. Older versions might still work but they haven't been thoroughly tested with this release. * Linux kernel >= 2.5.46 is required. Older versions without a decent PTRACE_SETOPTIONS support will not work. * On mips, Linux kernel >= 2.6.15 is required. Older versions without a decent PTRACE_GETREGS support will not work. * On s390 and s390x, Linux kernel >= 2.6.27 is required. Older versions without a decent PTRACE_GETREGSET support will not work. usr/share/doc/perl-version-0.99.07/README 0000644 00000024707 14721017226 0013367 0 ustar 00 version 0.9907 ================================== Full version object support, with patch for bug in Perl 5.10.0 core version support. YOU SHOULD INSTALL THIS RELEASE WHEN USING VERSION OBJECTS IN PERL 5.10.0. There was a bug caused by objects serialized by YAML that will cause Perl 5.10.0 to segfault. As long as some module calls 'use version', then the replacement code will take effect and Perl will not crash. Major Changes in 0.9907 - 2014-01-12 ===================================== Lots of optimizations of XS and C code courtesy of Daniel Dragan (bulk88@hotmail.com). Lots of minor tweaks as well. Resolves: https://rt.cpan.org/Ticket/Display.html?id=91892 https://rt.cpan.org/Ticket/Display.html?id=91867 https://rt.cpan.org/Ticket/Display.html?id=91987 https://rt.cpan.org/Ticket/Display.html?id=92051 IMPORTANT CHANGE - 0.9906 is the last release that fully supports Perl releases prior to 5.6.2. It is just too much trouble to continue to fight to maintain full backward compatibility. Major Changes in 0.9906 - 2014-01-04 ===================================== Applied C89 compatibility fix from Karl Williamson to vxs.inc. Added back support for $version::LAX and $version::STRICT to resolve: https://rt.cpan.org/Ticket/Display.html?id=88458 https://rt.cpan.org/Ticket/Display.html?id=91858 https://rt.cpan.org/Ticket/Display.html?id=91868 Major Changes in 0.9905 - 2014-01-04 ===================================== Major rewrite of XS code to permit easier inclusion in core Perl (mostly written by Father Chrysostomos <sprout@cpan.org>). XS code is no longer supported for any Perl < v5.10, although the pure Perl code still works going back to 5.005_04. In addition, the version::vpp class is now completely independent and can be use'd exactly like the base version class. It is still better to use the base class for compatibility purposes. Major Changes in 0.9904 - 2013-08-20 ===================================== Final upstream changes from bleadperl. Resolves RT tickets: https://rt.cpan.org/Ticket/Display.html?id=87513 https://rt.cpan.org/Ticket/Display.html?id=87983 Major Changes in 0.9903 - 2013-08-18 ===================================== Upstream test changes from bleadperl. Include version::vpp even when installing XS version. Subtle locale test changes. Major Changes in 0.9902 - 2013-03-05 ===================================== Upstream test changess from bleadperl. Support env PERL_ONLY=1 as well as --perl-only. version::new with no arguments reads past the end of the stack. Major Changes in 0.9901 - 2012-04-26 ===================================== Fix problem with short floating point alpha versions (e.g. 0.52_0). Major Changes in 0.99 - 2012-04-26 ===================================== Apply missing patch from core Perl to prevent overflow with ludicrous versions. Major Changes in 0.98 - 2012-04-25 ===================================== Apply patch from core Perl to prevent overflow with ludicrous versions. Major Changes in 0.97 - 2012-02-28 ===================================== Minor tweak to locale test to skip if no locales are installed at all. Major Changes in 0.96 - 2012-02-06 ===================================== Merge in upstream changes from bleadperl. Improved locale tests. Major Changes in 0.95 - 2011-11-12 ===================================== Restore compatibility in replacement UNIVERSAL::VERSION with the behavior of Perl 5.14.x, essentially by reverting the changes in https://rt.perl.org/rt3/Ticket/Display.html?id=95544 Fix segfault error with strings that begin with 'v', especially the string 'version'. Resolves: https://rt.cpan.org/Ticket/Display.html?id=72365 Forbid all math operations on version objects in base class (this was already the case for XS code but the pure Perl was lacking). Resolves: https://rt.cpan.org/Public/Bug/Display.html?id=70950 Major Changes in 0.94 - 2011-08-21 ===================================== Clarify documentation on advisability of using leading 'v' (it isn't mandatory, but it is much more likely to DTRT). Resolves: https://rt.cpan.org/Public/Bug/Display.html?id=70120 Use a localized DIE handler when attempting to load the XS code, in case the caller has its own DIE handler. Resolves: https://rt.cpan.org/Public/Bug/Display.html?id=70260 Major Changes in 0.93 - 2011-07-27 ===================================== Fix problem with UNIVERSAL::VERSION noted by Father Chrysostomos. Major Changes in 0.92 - 2011-07-26 ===================================== Forbid negative versions. Make replacement UNIVERSAL::VERSION return the original $VERSION scalar if called without a requested version. Resolves https://rt.perl.org/rt3/Ticket/Display.html?id=95544 Rewrite code so that we just override all subs for Perl >= 5.9.0 (when version.pm was added to the core). Major Changes in 0.91 - 2011-06-05 ===================================== Fix compilation/linking on Strawberry Perl, resolves https://rt.cpan.org/Ticket/Display.html?id=68611 Major Changes in 0.90 - 2011-06-01 ===================================== Make all tests pass even with older Test::More releases. Resolves https://rt.cpan.org/Ticket/Display.html?id=68588 Major Changes in 0.89 - 2011-05-31 ===================================== Change behavior of pure Perl qv/declare to match the core/XS behavior; do not use parent's new() class for derived classes. This breaks encapsulation but I can justify it because qv/declare is a very specific thing that shouldn't be casually overridden (unless you do it directly in the subclass). Major Changes in 0.88 - 2010-12-19 ===================================== Fix Makefile.PL to make Strawberry Perl happy. Resolves: https://rt.cpan.org/Public/Bug/Display.html?id=63991 Major Changes in 0.87 - 2010-12-09 ===================================== Remove Build.PL since there are modules in the Module::Build tool chain that require version.pm, leading to circular dependencies. This also allows Module::Build itself to depend on version.pm. Major Changes in 0.86 - 2010-11-26 ===================================== is_strict/is_lax were not exported correctly (which no one noticed). Also pull in strict/lax tests from core. Major Changes in 0.85 - 2010-10-25 ===================================== Don't include MYMETA.yml file in distro Major Changes in 0.84 - 2010-10-24 ===================================== Restore public API vcmp() broken in 0.83 Major Changes in 0.83 - 2010-10-17 ===================================== Changed vverify API (David Golden). Improved heuristic for non-magical v-strings (Perl 5.6.0-5.8.0). Install in proper patch post-@INC reordering. Major Changes in 0.82 - 2010-04-13 ===================================== Still more changes to sync with Perl 5.12.0-as-released. Rewritten POD thanks to many hands, but mostly David Golden. Vastly improved Regex definitions from Zephram. Major Changes in 0.81 - 2010-02-01 ===================================== Merge in changes from bleadperl that will be part of Perl 5.12.0. Completely rewrite pure Perl code to operate exactly like the XS code, through the creation of a character-array class called charstar. Now the pure Perl code and XS code can be more easily be synchronized. Major Changes in 0.80 - 2010-01-21 ===================================== No outwardly visible changes. This release is to fix an assertion error with certain picky/older compilers. NOTE: this is not the version object code that will be part of Perl 5.12.0, which will be released shortly as 0.81. Major Changes in 0.79 - 2010-01-03 ===================================== No outwardly visible changes. This release is to match the code that will part of Perl 5.12.0, but which doesn't affect the external API of the CPAN release. Major Changes in 0.78 - 2009-10-12 ===================================== More changes to improve the non-magic v-string heuristics, this time affecting both the pure Perl and XS backends. NOTE: these fixes only matter if you are running Perl 5.6.x to 5.8.0 (inclusive). Beginning with Perl 5.8.1, v-strings are now magical and version.pm no longer has to guess. Resolves: https://rt.cpan.org/Ticket/Display.html?id=50347 Also resolve the issue where attempting to install CPAN releases on top of core releases (e.g. 5.10.0 and 5.10.1) would not DTRT. Resolves: https://rt.cpan.org/Ticket/Display.html?id=49667 Major Changes in 0.7702 - 2009-09-07 ===================================== Add additional contraints to the code which tries to guess whether something is a v-string or not for Perl 5.6.0 through 5.8.0 (inclusive). Resolves: https://rt.cpan.org/Ticket/Display.html?id=49348 Major Changes in 0.7701 - 2009-07-28 ===================================== Special RHEL4.x/Fedora4.x Are Too Stupid to Live Release. Those distros have never updated beyond Perl 5.8.5/5.8.6 respectively. Consequently, they contain a complete broken Test::More::use_ok which doesn't load the package into the correct namespace: https://rt.cpan.org/Ticket/Display.html?id=48268 thus causing mysterious test failures. No version.pm code was changed at all. :( Major Changes in 0.77 - 2009-07-26 =================================== Complete POD rewrite to document common usage in version.pod and put all of the implementation details into version::Internals. Resolve a number of RT tickets: RT#48135 - Compilation failure using MS VC++ 7.0. RT#47980 - Remove need for runtime class loading in pure Perl code RT#46921 - locale and eval action at a distance. RT#45241 - mistaken regex to convert large exponential numbers to non-exponential form before scanning. Please read the POD documentation for usage/details. See the CHANGES file for full details of all changes to the module behavior. INSTALLATION To install this module type the following: $ perl Makefile.PL $ make $ make test # make install This release includes an optional pure Perl implementation (in case you don't have a C-compiler or if some reason you want your code to be much slower). You can test it by replacing the first line above with: $ perl Makefile.PL --perl_only and it will install the Perl only version. DEPENDENCIES The same C compiler used to build Perl (or not). Module::Build 0.2611 or better. Module::Build installs fine under 5.005_03 or better, though the optional dependency Archive::Tar doesn't. If you install Module::Build without any of the optional dependencies, you can safely install version.pm. COPYRIGHT AND LICENCE This module can be distributed under the same terms as Perl. Copyright (C) 2004-2010 John Peacock usr/share/doc/lynx-2.8.8/README 0000644 00000015022 14721017324 0011552 0 ustar 00 Lynx README file Lynx Version 2.8.7 is the latest release (July 2009). See the CHANGES file for a complete record of all changes and bug fixes. New releases are announced on the lynx-dev mailing list (see below). FOR REAL NOVICES To use this package, you need a compiler & a bit of experience at very simple programming. If you just want something which will work `out-of-the-box', you can get pre-compiled versions of Lynx by following the links from <URL: http://lynx.isc.org/> ; for DOS or Windows, goto <URL: http://www.fdisk.com/doslynx/lynxport.htm>. WHAT IS LYNX? Lynx is a fully-featured World Wide Web (WWW) client for users running cursor-addressable, character-cell display devices such as vt100 terminals, vt100 emulators running on Windows 95/NT or Macintoshes, or any other character-cell display. It will display Hypertext Markup Language (HTML) documents containing links to files on the local system, as well as files on remote systems running http, gopher, ftp, wais, nntp, finger, or cso/ph/qi servers, and services accessible via logins to telnet, tn3270 or rlogin accounts. Current versions of Lynx run on Unix, VMS, Windows95/NT, 386DOS and OS/2 EMX. Lynx can be used to access information on the WWW, or to establish information systems intended primarily for local access. Lynx has been used to build several Campus Wide Information Systems (CWIS). Lynx can also be used to build systems isolated within a single LAN. HOW TO GET LYNX For the latest release of Lynx goto: <URL: http://lynx.isc.org/release>; <URL: ftp://lynx.isc.org/release>; the latest development version is at: <URL: http://lynx.isc.org/current>. The Lynx homepage is <URL: http://lynx.isc.org/>. The on-line help page (enter `h') has links to many useful things. LICENSE Lynx is distributed under the GNU General Public License, version 2 (GPLv2) without restrictions on usage or redistribution. The Lynx copyright statement, "COPYHEADER", and GNU GPL, "COPYING", are included in the top-level directory of the distribution. Lynx is supported by the Lynx user community, an entirely volunteer (and unofficial) organization. Certain portions of the Lynx source distribution were originally created by CERN and have been modified during the development of Lynx. See WWW/FreeofCharge.html for copyright info regarding CERN products used in Lynx. Note that Lynx is not self-contained; typically it is built with a variety of add-on libraries, including those for compression, IPv6, SOCKS and SSL support. YEAR 2000 COMPLIANCE We believe Lynx works properly for the Year 2000 issues, since it does not store dates in 2-digit form. Since it must communicate with a wide range of web servers, it interprets dates in a variety of formats. In particular, if Lynx receives a date with a 2-digit year, it assumes that values less than 70 are in the range 2000-2069. INSTALLING LYNX To install Lynx, follow the steps in the INSTALLATION file, which is located in the top directory of the source distribution. DOCUMENTATION A users guide is included in this distribution along with a man page for Unix systems and a help file for VMS systems. All documentation is contained in the top directory and the docs, samples and lynx_help subdirectories. While running Lynx, type 'h', 'H', or '?' to invoke the help menu system. From the help menu you may access several useful documents pertaining to Lynx and the World Wide Web. The most important of these is the Lynx Users Guide. By default, Lynx will use the Lynx Enhanced Pages, which includes http links for help and FAQs concerning Lynx. It is recommended that you install your own help menu system at your site in order to lessen the load on http servers. This also will allow you to customize the help menu system for your site and greatly speed up access for those using Lynx over a slow connection. INSTALLING THE DOCUMENTATION For Unix and related systems which support the autoconf configure script, the help menu system is installed by the "make install-help" command. For other systems (such as VMS), copy COPYHEADER and COPYING into the lynx_help/ subdirectory. Then copy the lynx_help subdirectory to a public place on your system, or into your $HOME directory if you are a single user. Finally, edit the lynx.cfg file so that the HELPFILE line is defined as follows: HELPFILE:file://localhost/[public_path]/lynx_help/lynx_help_main.html where [public_path] is the absolute path to the lynx_help directory. Customizing the help menu system is just a matter of editing a set of HTML files. Additional information about installing and customizing the help file set is available at <URL:http://www.irm.nara.kindai.ac.jp/ lynxdev/README.help>. INSTALLING LYNX To install Lynx, follow the steps in the INSTALLATION file, which is located in the top directory of the source distribution. Win32 users who need pre-compiled distributions should visit the site <URL:http://www.fdisk.com/doslynx/lynxport.htm>. PROBLEMS If you experience problems configuring, compiling or installing Lynx, please read Section VI. "General installation instructions" in the INSTALLATION file. Instructions are given there for reporting your problem to the "lynx-dev" mailing list, which is frequented by experienced Lynx users. LYNX-DEV MAILING LIST To subscribe to lynx-dev, send email to <URL: mailto:lynx-dev-request@nongnu.org> with "subscribe" for a subject line. If you wish to unsubscribe from lynx-dev, send email to <URL: mailto:lynx-dev-request@nongnu.org> with "unsubscribe" for a subject line. Any messages you wish to post should be sent to <URL: mailto:lynx-dev@nongnu.org>. PLEASE use the lynx-dev list, NOT private email to the developers, for questions or discussion about Lynx, or contributions of patches. Patches should use the unified diff format (diff -u), which can be generated by building the target, "make lynx.patch" after unpacking a pristine copy of the source into a subdirectory called "orig". You need not be subscribed to the lynx-dev list in order to post. If you post without subscribing, though, you should read replies to your questions or comments in the archive since more often than not nobody will send a carbon copy to you. View the archives at: "lynx-dev Mailing list archives" <URL:http://mail.gnu.org/mailman/listinfo/lynx-dev/> usr/share/doc/desktop-file-utils-0.23/README 0000644 00000003330 14721017457 0014217 0 ustar 00 desktop-file-utils ================== http://www.freedesktop.org/wiki/Software/desktop-file-utils desktop-file-utils contains a few command line utilities for working with desktop entries. desktop-file-validate: validates a desktop file and prints warnings/errors about desktop entry specification violations. desktop-file-install: installs a desktop file to the applications directory, optionally munging it a bit in transit. update-desktop-database: updates the database containing a cache of MIME types handled by desktop files. More information about desktop files and the "Desktop Entry Specification" is available on: http://freedesktop.org/wiki/Specifications/desktop-entry-spec http://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html You may download updates to the package from: http://www.freedesktop.org/software/desktop-file-utils/releases/ To discuss desktop-file-utils, you may use the xdg mailing list: http://lists.freedesktop.org/mailman/listinfo/xdg Installation ============ See the file 'INSTALL'. If you are not using a released version of desktop-file-utils (for example, if you checked out the code from git), you first need to run './autogen.sh'. How to report bugs ================== Bugs should be reported to the freedesktop.org bug tracking system: https://bugs.freedesktop.org/ (product desktop-file-utils) You will need to create an account for yourself. Please read the following page on how to prepare a useful bug report: https://bugs.freedesktop.org/page.cgi?id=bug-writing.html Please read the HACKING file for information on where to send changes or bugfixes for this package. usr/share/doc/perl-Net-HTTP-6.06/README 0000644 00000022346 14721017476 0012756 0 ustar 00 NAME Net::HTTP - Low-level HTTP connection (client) SYNOPSIS use Net::HTTP; my $s = Net::HTTP->new(Host => "www.perl.com") || die $@; $s->write_request(GET => "/", 'User-Agent' => "Mozilla/5.0"); my($code, $mess, %h) = $s->read_response_headers; while (1) { my $buf; my $n = $s->read_entity_body($buf, 1024); die "read failed: $!" unless defined $n; last unless $n; print $buf; } DESCRIPTION The `Net::HTTP' class is a low-level HTTP client. An instance of the `Net::HTTP' class represents a connection to an HTTP server. The HTTP protocol is described in RFC 2616. The `Net::HTTP' class supports `HTTP/1.0' and `HTTP/1.1'. `Net::HTTP' is a sub-class of `IO::Socket::INET'. You can mix the methods described below with reading and writing from the socket directly. This is not necessary a good idea, unless you know what you are doing. The following methods are provided (in addition to those of `IO::Socket::INET'): $s = Net::HTTP->new( %options ) The `Net::HTTP' constructor method takes the same options as `IO::Socket::INET''s as well as these: Host: Initial host attribute value KeepAlive: Initial keep_alive attribute value SendTE: Initial send_te attribute_value HTTPVersion: Initial http_version attribute value PeerHTTPVersion: Initial peer_http_version attribute value MaxLineLength: Initial max_line_length attribute value MaxHeaderLines: Initial max_header_lines attribute value The `Host' option is also the default for `IO::Socket::INET''s `PeerAddr'. The `PeerPort' defaults to 80 if not provided. The `Listen' option provided by `IO::Socket::INET''s constructor method is not allowed. If unable to connect to the given HTTP server then the constructor returns `undef' and $@ contains the reason. After a successful connect, a `Net:HTTP' object is returned. $s->host Get/set the default value of the `Host' header to send. The $host must not be set to an empty string (or `undef') for HTTP/1.1. $s->keep_alive Get/set the *keep-alive* value. If this value is TRUE then the request will be sent with headers indicating that the server should try to keep the connection open so that multiple requests can be sent. The actual headers set will depend on the value of the `http_version' and `peer_http_version' attributes. $s->send_te Get/set the a value indicating if the request will be sent with a "TE" header to indicate the transfer encodings that the server can choose to use. The list of encodings announced as accepted by this client depends on availability of the following modules: `Compress::Raw::Zlib' for *deflate*, and `IO::Compress::Gunzip' for *gzip*. $s->http_version Get/set the HTTP version number that this client should announce. This value can only be set to "1.0" or "1.1". The default is "1.1". $s->peer_http_version Get/set the protocol version number of our peer. This value will initially be "1.0", but will be updated by a successful read_response_headers() method call. $s->max_line_length Get/set a limit on the length of response line and response header lines. The default is 8192. A value of 0 means no limit. $s->max_header_length Get/set a limit on the number of header lines that a response can have. The default is 128. A value of 0 means no limit. $s->format_request($method, $uri, %headers, [$content]) Format a request message and return it as a string. If the headers do not include a `Host' header, then a header is inserted with the value of the `host' attribute. Headers like `Connection' and `Keep-Alive' might also be added depending on the status of the `keep_alive' attribute. If $content is given (and it is non-empty), then a `Content-Length' header is automatically added unless it was already present. $s->write_request($method, $uri, %headers, [$content]) Format and send a request message. Arguments are the same as for format_request(). Returns true if successful. $s->format_chunk( $data ) Returns the string to be written for the given chunk of data. $s->write_chunk($data) Will write a new chunk of request entity body data. This method should only be used if the `Transfer-Encoding' header with a value of `chunked' was sent in the request. Note, writing zero-length data is a no-op. Use the write_chunk_eof() method to signal end of entity body data. Returns true if successful. $s->format_chunk_eof( %trailers ) Returns the string to be written for signaling EOF when a `Transfer-Encoding' of `chunked' is used. $s->write_chunk_eof( %trailers ) Will write eof marker for chunked data and optional trailers. Note that trailers should not really be used unless is was signaled with a `Trailer' header. Returns true if successful. ($code, $mess, %headers) = $s->read_response_headers( %opts ) Read response headers from server and return it. The $code is the 3 digit HTTP status code (see HTTP::Status) and $mess is the textual message that came with it. Headers are then returned as key/value pairs. Since key letter casing is not normalized and the same key can even occur multiple times, assigning these values directly to a hash is not wise. Only the $code is returned if this method is called in scalar context. As a side effect this method updates the 'peer_http_version' attribute. Options might be passed in as key/value pairs. There are currently only two options supported; `laxed' and `junk_out'. The `laxed' option will make read_response_headers() more forgiving towards servers that have not learned how to speak HTTP properly. The `laxed' option is a boolean flag, and is enabled by passing in a TRUE value. The `junk_out' option can be used to capture bad header lines when `laxed' is enabled. The value should be an array reference. Bad header lines will be pushed onto the array. The `laxed' option must be specified in order to communicate with pre-HTTP/1.0 servers that don't describe the response outcome or the data they send back with a header block. For these servers peer_http_version is set to "0.9" and this method returns (200, "Assumed OK"). The method will raise an exception (die) if the server does not speak proper HTTP or if the `max_line_length' or `max_header_length' limits are reached. If the `laxed' option is turned on and `max_line_length' and `max_header_length' checks are turned off, then no exception will be raised and this method will always return a response code. $n = $s->read_entity_body($buf, $size); Reads chunks of the entity body content. Basically the same interface as for read() and sysread(), but the buffer offset argument is not supported yet. This method should only be called after a successful read_response_headers() call. The return value will be `undef' on read errors, 0 on EOF, -1 if no data could be returned this time, otherwise the number of bytes assigned to $buf. The $buf is set to "" when the return value is -1. You normally want to retry this call if this function returns either -1 or `undef' with `$!' as EINTR or EAGAIN (see Errno). EINTR can happen if the application catches signals and EAGAIN can happen if you made the socket non-blocking. This method will raise exceptions (die) if the server does not speak proper HTTP. This can only happen when reading chunked data. %headers = $s->get_trailers After read_entity_body() has returned 0 to indicate end of the entity body, you might call this method to pick up any trailers. $s->_rbuf Get/set the read buffer content. The read_response_headers() and read_entity_body() methods use an internal buffer which they will look for data before they actually sysread more from the socket itself. If they read too much, the remaining data will be left in this buffer. $s->_rbuf_length Returns the number of bytes in the read buffer. This should always be the same as: length($s->_rbuf) but might be more efficient. SUBCLASSING The read_response_headers() and read_entity_body() will invoke the sysread() method when they need more data. Subclasses might want to override this method to control how reading takes place. The object itself is a glob. Subclasses should avoid using hash key names prefixed with `http_' and `io_'. SEE ALSO LWP, IO::Socket::INET, Net::HTTP::NB COPYRIGHT Copyright 2001-2003 Gisle Aas. This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. usr/share/doc/libgpg-error-1.12/README 0000644 00000007711 14721017554 0013072 0 ustar 00 libgpg-error ============ This is a library that defines common error values for all GnuPG components. Among these are GPG, GPGSM, GPGME, GPG-Agent, libgcrypt, Libksba, DirMngr, Pinentry, SmartCard Daemon and more. libgpg-error is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. See the file COPYING.LIB for copyright and warranty information. See the file AUTHORS for a list of authors and important mail addresses. However, some files (for example src/mkerrnos.awk) used in the build process of the library are covered by a different license. Please see the header of these files and the file COPYING for copyright and warranty information on these files. A special exception in the copyright license of these files makes sure that the output in the build process, which is used in libgpg-error, is not affected by the GPL. Installation ------------ Please read the file INSTALL! Here is a quick summary: 1) Check that you have unmodified sources. You can find instructions how to verify the sources below. Don't skip this - it is an important step! 2) Unpack the archive. With GNU tar you can do it this way: "tar xjvf libgpg-error-x.y.tar.bz2" 3) "cd libgpg-error-x.y" 4) "./configure" 5) "make" 6) "make install" How to Verify the Source ------------------------ In order to check that the version of libgpg-error which you are going to install is an original and unmodified copy of the original, you can do it in one of the following ways: a) If you already have a trusted version of GnuPG installed, you can simply check the supplied signature: $ gpg --verify libgpg-error-x.y.tar.bz2.sig This checks that the detached signature libgpg-error-x.y.tar.bz2.sig is indeed a a signature of libgpg-error-x.y.tar.bz2. Please note that you have to use an old version of GnuPG to do all this stuff. *Never* use the version which was built using the library you are trying to verify! b) If you don't have any a trusted version of GnuPG, you can attempt to verify the SHA1 checksum, using a trusted version of the sha1sum program: $ sha1sum libgpg-error-x.y.tar.bz2 This should yield an output _similar_ to this: 610064e5b77700f5771c8fde2691c4365e1ca100 libgpg-error-x.y.tar.bz2 Now check that this checksum is _exactly_ the same as the one published via the announcement list and probably via Usenet. Hints ----- To build for Windows you you may use the convenience command: ./autogen.sh --build-w32 which runs configure with suitable options. For WindowsCE the command is: ./autogen.sh --build-w32ce There is also _experimental_ support for building a 64 bit Windows version: ./autogen.sh --build-w64 Known Problems -------------- On Windows, WSA Error Codes can be provided as system error codes and will be transparently converted to the corresponding gpg error codes. There are two problems with this support: * Not all error codes corresponding to WSA Error codes have a detailed description when printed with gpg_strerror. Some will default to "Unknown error" for pretty printing. For example, WSAEHOSTDOWN will be translated to GPG_ERR_EHOSTDOWN, but there is no corresponding EHOSTDOWN in Windows and thus gpg_strerror will default to "Unknown error" as printed by the system's strerror function for the argument WSAEHOSTDOWN. (This could be fixed by adding our own error strings replacing or extending the system error strings, including their translations). * The translation to a gpg error code and back to a system error code in some cases does not preserve information. For example, the error code WSAEACCES translates to GPG_ERR_EACCES, which translates back to EACCES. Any WSA Error code has either the first problem or the second (but not both), depending on if there is a corresponding Windows error code. usr/share/doc/ethtool-4.8/README 0000644 00000000177 14721017565 0012106 0 ustar 00 ethtool is a small utility for examining and tuning your ethernet-based network interface. See the man page for more details. usr/share/doc/perl-Env-1.04/README 0000644 00000000506 14721017664 0012165 0 ustar 00 This archive contains the distribution Env, version 1.04: perl module that imports environment variables as scalars or arrays This software is copyright (c) 2013 by Chip Salzenberg. This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. usr/share/doc/mozjs17-17.0.0/README 0000644 00000000477 14721017771 0012156 0 ustar 00 This directory contains SpiderMonkey 17. This release is based on revision c7f42dec3730 of Mozilla ESR17: http://hg.mozilla.org/releases/mozilla-esr17/ The changes in the patches/ directory were applied. MDN hosts the latest SpiderMonkey 17 release notes: https://developer.mozilla.org/en-US/docs/SpiderMonkey/17 usr/share/doc/grep-2.20/README 0000644 00000004310 14721020030 0011403 0 ustar 00 Copyright (C) 1992, 1997-2002, 2004-2014 Free Software Foundation, Inc. Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. This is GNU grep, the "fastest grep in the west" (we hope). All bugs reported in previous releases have been fixed. Many exciting new bugs have probably been introduced in this revision. GNU grep is provided "as is" with no warranty. The exact terms under which you may use and (re)distribute this program are detailed in the GNU General Public License, in the file COPYING. GNU grep is based on a fast lazy-state deterministic matcher (about twice as fast as stock Unix egrep) hybridized with a Boyer-Moore-Gosper search for a fixed string that eliminates impossible text from being considered by the full regexp matcher without necessarily having to look at every character. The result is typically many times faster than Unix grep or egrep. (Regular expressions containing backreferencing will run more slowly, however.) See the files AUTHORS and THANKS for a list of authors and other contributors. See the file INSTALL for compilation and installation instructions. See the file NEWS for a description of major changes in this release. See the file TODO for ideas on how you could help us improve grep. See the file README-alpha for information on grep development and the CVS repository. Send bug reports to bug-grep@gnu.org. KNOWN BUGS: Several tests in fmbtest.sh and foad1.sh fail under the cs_CZ.UTF-8 locale and have been disabled. The combination of -o and -i options is broken and the known failing cases are disabled in foad1.sh The option -i does not work properly in some multibyte locales such as tr_TR.UTF-8 where the upper case and lower case forms of a character are not necessarily of the same byte length. Additional bug reports can be found at: http://savannah.gnu.org/bugs/?group=grep You can also browse the bug-grep mailing list archive at: http://lists.gnu.org/archive/html/bug-grep/ For any copyright year range specified as YYYY-ZZZZ in this package note that the range specifies every single year in that closed interval. usr/share/doc/time-1.7/README 0000644 00000001227 14721020173 0011344 0 ustar 00 `time' is a program that measures many of the CPU resources, such as time and memory, that other programs use. The GNU version can format the output in arbitrary ways by using a printf-style format string to include various resource measurements. Some systems do not provide much information about program resource use; `time' reports unavailable information as zero values. See the file INSTALL for compilation and installation instructions. Mail suggestions and bug reports for GNU time to bug-gnu-utils@prep.ai.mit.edu. Please include the version of `time', which you can get by running `time --version', and the operating system and C compiler you used. usr/share/doc/libusbx-1.0.21/README 0000644 00000002520 14721020232 0012261 0 ustar 00 # libusb [](https://travis-ci.org/libusb/libusb) [](https://ci.appveyor.com/project/LudovicRousseau/libusb) [](https://scan.coverity.com/projects/libusb-libusb) libusb is a library for USB device access from Linux, Mac OS X, Windows, OpenBSD/NetBSD and Haiku userspace. It is written in C (Haiku backend in C++) and licensed under the GNU Lesser General Public License version 2.1 or, at your option, any later version (see [COPYING](COPYING)). libusb is abstracted internally in such a way that it can hopefully be ported to other operating systems. Please see the [PORTING](PORTING) file for more information. libusb homepage: http://libusb.info/ Developers will wish to consult the API documentation: http://api.libusb.info Use the mailing list for questions, comments, etc: http://mailing-list.libusb.info - Pete Batard <pete@akeo.ie> - Hans de Goede <hdegoede@redhat.com> - Xiaofan Chen <xiaofanc@gmail.com> - Ludovic Rousseau <ludovic.rousseau@gmail.com> - Nathan Hjelm <hjelmn@cs.unm.edu> - Chris Dickens <christopher.a.dickens@gmail.com> (Please use the mailing list rather than mailing developers directly) usr/share/doc/dmidecode-3.2/README 0000644 00000011052 14721022335 0012317 0 ustar 00 ** INTRODUCTION ** Dmidecode reports information about your system's hardware as described in your system BIOS according to the SMBIOS/DMI standard. This information typically includes system manufacturer, model name, serial number, BIOS version, asset tag as well as a lot of other details of varying level of interest and reliability depending on the manufacturer. This will often include usage status for the CPU sockets, expansion slots (e.g. AGP, PCI, ISA) and memory module slots, and the list of I/O ports (e.g. serial, parallel, USB). DMI data can be used to enable or disable specific portions of kernel code depending on the specific hardware. Thus, one use of dmidecode is for kernel developers to detect system "signatures" and add them to the kernel source code when needed. Beware that DMI data have proven to be too unreliable to be blindly trusted. Dmidecode does not scan your hardware, it only reports what the BIOS told it to. ** INSTALLATION ** The home web page for dmidecode is hosted on Savannah: http://www.nongnu.org/dmidecode/ You will find the latest version (including CVS) there, as well as fresh news and other interesting material, such as a list of related projects and articles. This program was first written for Linux, and has since been reported to work on FreeBSD, NetBSD, OpenBSD, BeOS and Solaris as well. There's no configure script, so simply run "make" to build dmidecode, and "make install" to install it. You also can use "make uninstall" to remove all the files you installed. By default, files are installed in /usr/local but you can change this behavior by editing the Makefile file and setting prefix to wherever you want. You may change the C compiler and the compilation flags as well. Optionally, you can run "make strip" prior to "make install" if you want smaller binaries. However, be aware that this will prevent any further attempt to debug the programs. Two parameters can be set in the Makefile file to make dmidecode work on non-i386 systems. They should be used if your system uses the big endian byte ordering (Motorola) or doesn't support unaligned memory accesses, respectively. For example, compiling for a SPARC processor would require both (but I am not aware of SPARC-based systems implementing SMBIOS). Compiling for an IA64 processor requires the memory alignment workaround, and it is enabled automatically. ** DOCUMENTATION ** Each tool has a manual page, found in the "man" subdirectory. Manual pages are installed by "make install". See these manual pages for command line interface details and tool specific information. For an history of the changes made to dmidecode, see the NEWS file. If you need help, your best chances are to visit the web page (see the INSTALLATION section above) or to get in touch with the developers directly. Have a look at the AUTHORS file and contact one of the maintainers. If you want to help with the development of dmidecode, please consider joining the dmidecode-devel discussion list: http://lists.nongnu.org/mailman/listinfo/dmidecode-devel ** COMMON PROBLEMS ** IA-64 Non-Linux systems are not yet supported. MMAP Note that mmap() is now used by default wherever possible, since this seems to solve a number of problems. This default behavior can be changed in config.h. Just to make sure this is clear, mmap() is not used for performance reasons but to increase the number of systems on which dmidecode can be successfully run. CYGWIN Dmidecode used to work under Cygwin. However the /dev/mem interface was removed at some point in time so it no longer works. ** MISCELLANEOUS TOOLS ** Three other tools come along with dmidecode: biosdecode, ownership and vpddecode. These tools are only useful on systems with a BIOS, so they are not built on IA-64 by default. BIOSDECODE This one prints all BIOS related information it can find in /dev/mem. It used to be part of dmidecode itself, but as dmidecode was growing, we felt that the non-DMI part had to be moved to a separate tool. OWNERSHIP This tool was written on a request by Luc Van de Velde for use with Novell tools in his company. It retrieves the "ownership tag" that can be set on most Compaq computers. Since it uses the same mechanisms dmidecode and biosdecode use, and could be of some use for other people as well, we decided to make it part of the project. VPDDECODE This tool prints the contents of the "vital product data" structure as found in most IBM and Lenovo computers. It used to have a lookup table for the machine name, but it was unreliable and hard to maintain so it was ultimately dropped. It has a command line interface. usr/share/doc/tcp_wrappers-libs-7.6/README 0000644 00000136127 14721022351 0014063 0 ustar 00 @(#) README 1.30 97/03/21 19:27:21 This is the 7.6 version of the TCP/IP daemon wrapper package. Thank you for using this program. If you like it, send me a postcard. My postal address is at the bottom of this file. Read the BLURB file for a brief summary of what is new. The CHANGES file gives a complete account of differences with respect to previous releases. Announcements of new releases of this software are posted to Usenet (comp.security.unix, comp.unix.admin), to the cert-tools mailing list, and to a dedicated mailing list. You can subscribe to the dedicated mailing list by sending an email message to majordomo@wzv.win.tue.nl with in the body (not subject): subscribe tcp-wrappers-announce. Table of contents ----------------- 1 - Introduction 2 - Disclaimer 3 - Tutorials 3.1 - How it works 3.2 - Where the logging information goes 4 - Features 4.1 - Access control 4.2 - Host name spoofing 4.3 - Host address spoofing 4.4 - Client username lookups 4.5 - Language extensions 4.6 - Multiple ftp/gopher/www archives on one host 4.7 - Banner messages 4.8 - Sequence number guessing 5 - Other works 5.1 - Related documents 5.2 - Related software 6 - Limitations 6.1 - Known wrapper limitations 6.2 - Known system software bugs 7 - Configuration and installation 7.1 - Easy configuration and installation 7.2 - Advanced configuration and installation 7.3 - Daemons with arbitrary path names 7.4 - Building and testing the access control rules 7.5 - Other applications 8 - Acknowledgements 1 - Introduction ---------------- With this package you can monitor and filter incoming requests for the SYSTAT, FINGER, FTP, TELNET, RLOGIN, RSH, EXEC, TFTP, TALK, and other network services. It supports both 4.3BSD-style sockets and System V.4-style TLI. Praise yourself lucky if you don't know what that means. The package provides tiny daemon wrapper programs that can be installed without any changes to existing software or to existing configuration files. The wrappers report the name of the client host and of the requested service; the wrappers do not exchange information with the client or server applications, and impose no overhead on the actual conversation between the client and server applications. Optional features are: access control to restrict what systems can connect to what network daemons; client user name lookups with the RFC 931 etc. protocol; additional protection against hosts that pretend to have someone elses host name; additional protection against hosts that pretend to have someone elses host address. The programs are very portable. Build procedures are provided for many common (and not so common) environments, and guidelines are provided in case your environment is not among them. Requirements are that network daemons are spawned by a super server such as the inetd; a 4.3BSD-style socket programming interface and/or System V.4-style TLI programming interface; and the availability of a syslog(3) library and of a syslogd(8) daemon. The wrappers should run without modification on any system that satisfies these requirements. Workarounds have been implemented for several common bugs in systems software. What to do if this is your first encounter with the wrapper programs: 1) read the tutorial sections for an introduction to the relevant concepts and terminology; 2) glance over the security feature sections in this document; 3) follow the installation instructions (easy or advanced). I recommend that you first use the default security feature settings. Run the wrappers for a few days to become familiar with their logs, before doing anything drastic such as cutting off access or installing booby traps. 2 - Disclaimer -------------- The wrapper programs rely on source address information obtained from network packets. This information is provided by the client host. It is not 100 percent reliable, although the wrappers do their best to expose forgeries. In the absence of cryptographic protection of message contents, and of cryptographic authentication of message originators, all data from the network should be treated with sound scepticism. THIS RESTRICTION IS BY NO MEANS SPECIFIC TO THE TCP/IP PROTOCOLS. 3 - Tutorials ------------- The tutorial sections give a gentle introduction to the operation of the wrapper programs, and introduce some of the terminology that is used in the remainder of the document: client, server, the inetd and syslogd daemons, and their configuration files. 3.1 - How it works ------------------ Almost every application of the TCP/IP protocols is based on a client- server model. For example, when a user invokes the telnet command to connect to one of your systems, a telnet server process is executed on the target host. The telnet server process connects the user to a login process. A few examples of client and server programs are shown in the table below: client server application -------------------------------- telnet telnetd remote login ftp ftpd file transfer finger fingerd show users The usual approach is to run one single daemon process that waits for all kinds of incoming network connections. Whenever a connection is established, this daemon (usually called inetd) runs the appropriate server program and goes back to sleep, waiting for other connections. The wrapper programs rely on a simple, but powerful mechanism. Instead of directly running the desired server program, the inetd is tricked into running a small wrapper program. The wrapper logs the client host name or address and performs some additional checks. When all is well, the wrapper executes the desired server program and goes away. The wrapper programs have no interaction with the client user (or with the client process). Nor do the wrappers interact with the server application. This has two major advantages: 1) the wrappers are application-independent, so that the same program can protect many kinds of network services; 2) no interaction also means that the wrappers are invisible from outside (at least for authorized users). Another important property is that the wrapper programs are active only when the initial contact between client and server is established. Once a wrapper has done its work there is no overhead on the client-server conversation. The simple mechanism has one major drawback: the wrappers go away after the initial contact between client and server processes, so the wrappers are of little use with network daemons that service more than one client. The wrappers would only see the first client attempt to contact such a server. The NFS mount daemon is a typical example of a daemon that services requests from multiple clients. See the section on related software for ways to deal with such server programs. There are two ways to use the wrapper programs: 1) The easy way: move network daemons to some other directory and fill the resulting holes with copies of the wrapper programs. This approach involves no changes to system configuration files, so there is very little risk of breaking things. 2) The advanced way: leave the network daemons alone and modify the inetd configuration file. For example, an entry such as: tftp dgram udp wait root /usr/etc/tcpd in.tftpd -s /tftpboot When a tftp request arrives, inetd will run the wrapper program (tcpd) with a process name `in.tftpd'. This is the name that the wrapper will use when logging the request and when scanning the optional access control tables. `in.tftpd' is also the name of the server program that the wrapper will attempt to run when all is well. Any arguments (`-s /tftpboot' in this particular example) are transparently passed on to the server program. For an account of the history of the wrapper programs, with real-life examples, see the section below on related documents. 3.2 - Where the logging information goes ---------------------------------------- The wrapper programs send their logging information to the syslog daemon (syslogd). The disposition of the wrapper logs is determined by the syslog configuration file (usually /etc/syslog.conf). Messages are written to files, to the console, or are forwarded to a @loghost. Some syslogd versions can even forward messages down a |pipeline. Older syslog implementations (still found on Ultrix systems) only support priority levels ranging from 9 (debug-level messages) to 0 (alerts). All logging information of the specified priority level or more urgent is written to the same destination. In the syslog.conf file, priority levels are specified in numerical form. For example, 8/usr/spool/mqueue/syslog causes all messages with priority 8 (informational messages), and anything that is more urgent, to be appended to the file /usr/spool/mqueue/syslog. Newer syslog implementations support message classes in addition to priority levels. Examples of message classes are: mail, daemon, auth and news. In the syslog.conf file, priority levels are specified with symbolic names: debug, info, notice, ..., emerg. For example, mail.debug /var/log/syslog causes all messages of class mail with priority debug (or more urgent) to be appended to the /var/log/syslog file. By default, the wrapper logs go to the same place as the transaction logs of the sendmail daemon. The disposition can be changed by editing the Makefile and/or the syslog.conf file. Send a `kill -HUP' to the syslogd after changing its configuration file. Remember that syslogd, just like sendmail, insists on one or more TABs between the left-hand side and the right-hand side expressions in its configuration file. Solaris 2.x note: the syslog daemon depends on the m4 macro processor. The m4 program is installed as part of the software developer packages. Trouble shooting note: when the syslogging does not work as expected, run the program by hand (`syslogd -d') and see what really happens. 4 - Features ------------ 4.1 - Access control -------------------- When compiled with -DHOSTS_ACCESS, the wrapper programs support a simple form of access control. Access can be controlled per host, per service, or combinations thereof. The software provides hooks for the execution of shell commands when an access control rule fires; this feature may be used to install "booby traps". For details, see the hosts_access.5 manual page, which is in `nroff -man' format. A later section describes how you can test your access control rules. Access control can also be used to connect clients to the "right" service. What is right may depend on the requested service, the origin of the request, and what host address the client connects to. Examples: (1) A gopher or www database speaks native language when contacted from within the country, otherwise it speaks English. (2) A service provider offers different ftp, gopher or www services with different internet hostnames from one host (section 4.6). Access control is enabled by default. It can be turned off by editing the Makefile, or by providing no access control tables. The install instructions below describe the Makefile editing process. The hosts_options.5 manual page (`nroff -man' format) documents an extended version of the access control language. The extensions are disabled by default. See the section below on language extensions. Later System V implementations provide the Transport Level Interface (TLI), a network programming interface that performs functions similar to the Berkeley socket programming interface. Like Berkeley sockets, TLI was designed to cover multiple protocols, not just Internet. When the wrapper discovers that the TLI interface sits on top of a TCP/IP or UDP/IP conversation it uses this knowledge to provide the same functions as with traditional socket-based applications. When some other protocol is used underneath TLI, the host address will be some universal magic cookie that may not even be usable for access control purposes. 4.2 - Host name spoofing ------------------------ With some network applications, such as RSH or RLOGIN, the client host name plays an important role in the authentication process. Host name information can be reliable when lookups are done from a _local_ hosts table, provided that the client IP address can be trusted. With _distributed_ name services, authentication schemes that rely on host names become more problematic. The security of your system now may depend on some far-away DNS (domain name server) outside your own control. The wrapper programs verify the client host name that is returned by the address->name DNS server, by asking for a second opinion. To this end, the programs look at the name and addresses that are returned by the name->address DNS server, which may be an entirely different host. If any name or address discrepancies are found, or if the second DNS opinion is not available, the wrappers assume that one of the two name servers is lying, and assume that the client host pretends to have someone elses host name. When compiled with -DPARANOID, the wrappers will always attempt to look up and double check the client host name, and will always refuse service in case of a host name/address discrepancy. This is a reasonable policy for most systems. When compiled without -DPARANOID, the wrappers by default still perform hostname lookup. You can match hosts with a name/address discrepancy with the PARANOID wildcard and decide whether or not to grant service. Automatic hostname verification is enabled by default. Automatic hostname lookups and verification can be turned off by editing the Makefile. The configuration and installation section below describes the Makefile editing process. 4.3 - Host address spoofing --------------------------- While host name spoofing can be found out by asking a second opinion, it is much harder to find out that a host claims to have someone elses network address. And since host names are deduced from network addresses, address spoofing is at least as effective as name spoofing. The wrapper programs can give additional protection against hosts that claim to have an address that lies outside their own network. For example, some far-away host that claims to be a trusted host within your own network. Such things are possible even while the impersonated system is up and running. This additional protection is not an invention of my own; it has been present for at least five years in the BSD rsh and rlogin daemons. Unfortunately, that feature was added *after* 4.3 BSD came out, so that very few, if any, UNIX vendors have adopted it. Our site, and many other ones, has been running these enhanced daemons for several years, and without any ill effects. When the wrapper programs are compiled with -DKILL_IP_OPTIONS, the programs refuse to service TCP connections with IP source routing options. -DKILL_IP_OPTIONS is not needed on modern UNIX systems that can stop source-routed traffic in the kernel. Examples are 4.4BSD derivatives, Solaris 2.x, and Linux. See your system manuals for details. If you are going to use this feature on SunOS 4.1.x you should apply patch 100804-03+ or 101790-something depending on your SunOS version. Otherwise you may experience "BAD TRAP" and "Data fault" panics when the getsockopt() system call is executed after a TCP RESET has been received. This is a kernel bug, it is not the fault of the wrappers. The feature is disabled by default. It can be turned on by editing the Makefile. The configuration and installation section below describes the Makefile editing process. UDP services do not benefit from this additional protection. With UDP, all you can be certain of is the network packet's destination address. 4.4 - Client username lookups ----------------------------- The protocol proposed in RFC 931 provides a means to obtain the client user name from the client host. The requirement is that the client host runs an RFC 931-compliant daemon. The information provided by such a daemon is not intended to be used for authentication purposes, but it can provide additional information about the owner of a TCP connection. The RFC 931 protocol has diverged into different directions (IDENT, TAP, RFC 1413). To add to the confusion, they all use the same network port. The daemon wrappers implement a common subset of the protocols. There are some limitations: the number of hosts that run an RFC 931 (or compatible) daemon is limited (but growing); client user name lookups do not work for datagram (UDP) services. More seriously, client user name lookups can cause noticeable delays with connections from non-UNIX PCs. Recent PC software seem to have fixed this (for example NCSA telnet). The wrappers use a 10-second timeout for RFC931 lookups, to accommodate slow networks and slow hosts. By default, the wrappers will do username lookup only when the access control rules require them to do so (via user@host client patterns, see the hosts_access.5 manual page) or when the username is needed for %<letter> expansions. You can configure the wrappers to always perform client username lookups, by editing the Makefile. The client username lookup timeout period (10 seconds default) can be changed by editing the Makefile. The installation sections below describe the Makefile editing process. On System V with TLI-based network services, client username lookups will be possible only when the underlying network protocol is TCP/IP. 4.5 - Language extensions ------------------------- The wrappers sport only a limited number of features. This is for a good reason: programs that run at high privilege levels must be easy to verify. And the smaller a program, the easier to verify. There is, however, a provision to add features. The options.c module provides a framework for language extensions. Quite a few extensions have already been implemented; they are documented in the hosts_options.5 document, which is in `nroff -man' format. Examples: changing the severity level at which a request for service is logged; "allow" and "deny" keywords; running a customized server instead of the standard one; many others. The language extensions are not enabled by default because they introduce an incompatible change to the access control language syntax. Instructions to enable the extensions are given in the Makefile. 4.6 - Multiple ftp/gopher/www archives on one host -------------------------------------------------- Imagine one host with multiple internet addresses. These addresses do not need to have the same internet hostname. Thus, it is possible to offer services with different internet hostnames from just one host. Service providers can use this to offer organizations a presence on the "net" with their own internet hostname, even when those organizations aren't connected to the Internet at all. To the end user it makes no difference, because applications use internet hostnames. There are several ways to assign multiple addresses to one machine. The nice way is to take an existing network interface and to assign additional internet addresses with the `ifconfig' command. Examples: Solaris 2: ifconfig le0:1 <address> netmask <mask> up 4.4 BSD: ifconfig en0 alias <address> netmask <mask> On other systems one has to increase the number of network interfaces: either with hardware interfaces, or with pseudo interfaces like SLIP or PPP. The interfaces do not need to be attached to anything. They just need to be up and to be assigned a suitable internet address and mask. With the wrapper software, `daemon@host' access control patterns can be used to distinguish requests by the network address that they are aimed at. Judicious use of the `twist' option (see the hosts_options.5 file, `nroff -man' format) can guide the requests to the right server. These can be servers that live in separate chroot areas, or servers modified to take additional context from the command line, or a combination. Another way is to modify gopher or www listeners so that they bind to only one specific network address. Multiple gopher or www servers can then be run side by side, each taking requests sent to its respective network address. 4.7 - Banner messages --------------------- Some sites are required to present an informational message to users before they attempt to login. Banner messages can also be useful when denying service: instead of simply dropping the connection a polite explanation is given first. Finally, banners can be used to give your system a more personal touch. The wrapper software provides easy-to-use tools to generate pre-login banners for ftp, telnet, rlogin etc. from a single prototype banner textfile. Details on banners and on-the-fly %<letter> expansions are given in the hosts_options.5 manual page (`nroff -man' format). An example is given in the file Banners.Makefile. In order to support banner messages the wrappers have to be built with language extensions enabled. See the section on language extensions. 4.8 - Sequence number guessing ------------------------------ Recently, systems came under attack from intruders that exploited a well-known weakness in TCP/IP sequence number generators. This weakness allows intruders to impersonate trusted hosts. Break-ins have been reported via the rsh service. In fact, any network service can be exploited that trusts the client host name or address. A long-term solution is to stop using network services that trust the client host name or address, and to use data encryption instead. A short-term solution, as outlined in in CERT advisory CA-95:01, is to configure network routers so that they discard datagrams from "outside" with an "inside" source address. This approach is most fruitful when you do not trust any hosts outside your local network. The IDENT (RFC931 etc.) client username lookup protocol can help to detect host impersonation attacks. Before accepting a client request, the wrappers can query the client's IDENT server and find out that the client never sent that request. When the client host provides IDENT service, a negative IDENT lookup result (the client matches `UNKNOWN@host') is strong evidence of a host impersonation attack. A positive IDENT lookup result (the client matches `KNOWN@host') is less trustworthy. It is possible for an attacker to spoof both the client request and the IDENT lookup connection, although doing so should be much harder than spoofing just a client request. Another possibility is that the client's IDENT server is lying. Client username lookups are described in more detail in a previous section. Pointers to IDENT daemon software are described in the section on related software. 5 - Other works --------------- 5.1 - Related documents ----------------------- The war story behind the tcp wrapper tools is described in: W.Z. Venema, "TCP WRAPPER, network monitoring, access control and booby traps", UNIX Security Symposium III Proceedings (Baltimore), September 1992. ftp.win.tue.nl:/pub/security/tcp_wrapper.ps.Z (postscript) ftp.win.tue.nl:/pub/security/tcp_wrapper.txt.Z (flat text) The same cracker is also described in: W.R. Cheswick, "An Evening with Berferd, In Which a Cracker is Lured, Endured, and Studied", Proceedings of the Winter USENIX Conference (San Francisco), January 1992. research.att.com:/dist/internet_security/berferd.ps An updated version of the latter paper appeared in: W.R. Cheswick, S.M. Bellovin, "Firewalls and Internet Security", Addison-Wesley, 1994. Discussions on internet firewalls are archived on ftp.greatcircle.com. Subscribe to the mailing list by sending a message to majordomo@greatcircle.com With in the body (not subject): subscribe firewalls. 5.2 - Related software ---------------------- Network daemons etc. with enhanced logging capabilities can generate massive amounts of information: our 150+ workstations generate several hundred kbytes each day. egrep-based filters can help to suppress some of the noise. A more powerful tool is the Swatch monitoring system by Stephen E. Hansen and E. Todd Atkins. Swatch can process log files in real time and can associate arbitrary actions with patterns; its applications are by no means restricted to security. Swatch is available ftp.stanford.edu, directory /general/security-tools/swatch. Socks, described in the UNIX Security III proceedings, can be used to control network traffic from hosts on an internal network, through a firewall host, to the outer world. Socks consists of a daemon that is run on the firewall host, and of a library with routines that redirect application socket calls through the firewall daemon. Socks is available from s1.gov in /pub/firewalls/socks.tar.Z. For a modified Socks version by Ying-Da Lee (ylee@syl.dl.nec.com) try ftp.nec.com, directory /pub/security/socks.cstc. Tcpr is a set of perl scripts by Paul Ziemba that enable you to run ftp and telnet commands across a firewall. Unlike socks it can be used with unmodified client software. Available from ftp.alantec.com, /pub/tcpr. The TIS firewall toolkit provides a multitude of tools to build your own internet firewall system. ftp.tis.com, directory /pub/firewalls. Versions of rshd and rlogind, modified to report the client user name in addition to the client host name, are available for anonymous ftp (ftp.win.tue.nl:/pub/security/logdaemon-XX.tar.Z). These programs are drop-in replacements for SunOS 4.x, Ultrix 4.x, SunOS 5.x and HP-UX 9.x. This archive also contains ftpd/rexecd/login versions that support S/Key or SecureNet one-time passwords in addition to traditional UNIX reusable passwords. The securelib shared library by William LeFebvre can be used to control access to network daemons that are not run under control of the inetd or that serve more than one client, such as the NFS mount daemon that runs until the machine goes down. Available from eecs.nwu.edu, file /pub/securelib.tar. xinetd (posted to comp.sources.unix) is an inetd replacement that provides, among others, logging, username lookup and access control. However, it does not support the System V TLI services, and involves much more source code than the daemon wrapper programs. Available from ftp.uu.net, directory /usenet/comp.sources.unix. netlog from Texas A&M relies on the SunOS 4.x /dev/nit interface to passively watch all TCP and UDP network traffic on a network. The current version is on net.tamu.edu in /pub/security/TAMU. Where shared libraries or router-based packet filtering are not an option, an alternative portmap daemon can help to prevent hackers from mounting your NFS file systems using the proxy RPC facility. ftp.win.tue.nl:/pub/security/portmap-X.shar.Z was tested with SunOS 4.1.X Ultrix 3.0 and Ultrix 4.x, HP-UX 8.x and some version of AIX. The protection is less effective than that of the securelib library because portmap is mostly a dictionary service. An rpcbind replacement (the Solaris 2.x moral equivalent of portmap) can be found on ftp.win.tue.nl in /pub/security. It prevents hackers from mounting your NFS file systems by using the proxy RPC facility. Source for a portable RFC 931 (TAP, IDENT, RFC 1413) daemon by Peter Eriksson is available from ftp.lysator.liu.se:/pub/ident/servers. Some TCP/IP implementations come without syslog library. Some come with the library but have no syslog daemon. A replacement can be found in ftp.win.tue.nl:/pub/security/surrogate-syslog.tar.Z. The fakesyslog library that comes with the nntp sources reportedly works well, too. 6 - Limitations --------------- 6.1 - Known wrapper limitations ------------------------------- Many UDP (and rpc/udp) daemons linger around for a while after they have serviced a request, just in case another request comes in. In the inetd configuration file these daemons are registered with the `wait' option. Only the request that started such a daemon will be seen by the wrappers. Such daemons are better protected with the securelib shared library (see: Related software). The wrappers do not work with RPC services over TCP. These services are registered as rpc/tcp in the inetd configuration file. The only non- trivial service that is affected by this limitation is rexd, which is used by the on(1) command. This is no great loss. On most systems, rexd is less secure than a wildcard in /etc/hosts.equiv. Some RPC requests (for example: rwall, rup, rusers) appear to come from the server host. What happens is that the client broadcasts its request to all portmap daemons on its network; each portmap daemon forwards the request to a daemon on its own system. As far as the rwall etc. daemons know, the request comes from the local host. Portmap and RPC (e.g. NIS and NFS) (in)security is a topic in itself. See the section in this document on related software. 6.2 - Known system software bugs -------------------------------- Workarounds have been implemented for several bugs in system software. They are described in the Makefile. Unfortunately, some system software bugs cannot be worked around. The result is loss of functionality. IRIX has so many bugs that it has its own README.IRIX file. Older ConvexOS versions come with a broken recvfrom(2) implementation. This makes it impossible for the daemon wrappers to look up the client host address (and hence, the name) in case of UDP requests. A patch is available for ConvexOS 10.1; later releases should be OK. With early Solaris (SunOS 5) versions, the syslog daemon will leave behind zombie processes when writing to logged-in users. Workaround: increase the syslogd threshold for logging to users, or reduce the wrapper's logging severity. On some systems, the optional RFC 931 etc. client username lookups may trigger a kernel bug. When a client host connects to your system, and the RFC 931 connection from your system to that client is rejected by a router, your kernel may drop all connections with that client. This is not a bug in the wrapper programs: complain to your vendor, and don't enable client user name lookups until the bug has been fixed. Reportedly, SunOS 4.1.1, Next 2.0a, ISC 3.0 with TCP 1.3, and AIX 3.2.2 and later are OK. Sony News/OS 4.51, HP-UX 8-something and Ultrix 4.3 still have the bug. Reportedly, a fix for Ultrix is available (CXO-8919). The following procedure can be used (from outside the tue.nl domain) to find out if your kernel has the bug. From the system under test, do: % ftp 131.155.70.19 This command attempts to make an ftp connection to our anonymous ftp server (ftp.win.tue.nl). When the connection has been established, run the following command from the same system under test, while keeping the ftp connection open: % telnet 131.155.70.19 111 Do not forget the `111' at the end of the command. This telnet command attempts to connect to our portmap process. The telnet command should fail with: "host not reachable", or with a timeout error. If your ftp connection gets messed up, you have the bug. If the telnet command does not fail, please let me know a.s.a.p.! For those who care, the bug is that the BSD kernel code was not careful enough with incoming ICMP UNREACHABLE control messages (it ignored the local and remote port numbers, and therefore zapped *all* connections with the remote system). The bug is still present in the BSD NET/1 source release (1989) but apparently has been fixed in BSD NET/2 (1991). 7 - Configuration and installation ---------------------------------- 7.1 - Easy configuration and installation ----------------------------------------- The "easy" recipe requires no changes to existing software or configuration files. Basically, you move the daemons that you want to protect to a different directory and plug the resulting holes with copies of the wrapper programs. If you don't run Ultrix, you won't need the miscd wrapper program. The miscd daemon implements among others the SYSTAT service, which produces the same output as the WHO command. Type `make' and follow the instructions. The Makefile comes with ready-to-use templates for many common UNIX implementations (sun, ultrix, hp-ux, aix, irix,...). IRIX has so many bugs that it has its own README.IRIX file. When the `make' succeeds the result is five executables (six in case of Ultrix). You can use the `tcpdchk' program to identify the most common problems in your wrapper and inetd configuration files. With the `tcpdmatch' program you can examine how the wrapper would react to specific requests for service. The `safe_finger' command should be used when you implement booby traps: it gives better protection against nasty stuff that remote hosts may do in response to your finger probes. The `try-from' program tests the host and username lookup code. Run it from a remote shell command (`rsh host /some/where/try-from') and it should be able to figure out from what system it is being called. The tcpd program can be used to monitor the telnet, finger, ftp, exec, rsh, rlogin, tftp, talk, comsat and other tcp or udp services that have a one-to-one mapping onto executable files. The tcpd program can also be used for services that are marked as rpc/udp in the inetd configuration file, but not for rpc/tcp services such as rexd. You probably do not want to run rexd anyway. On most systems it is even less secure than a wildcard in /etc/hosts.equiv. With System V.4-style systems, the tcpd program can also handle TLI services. When TCP/IP or UDP/IP is used underneath TLI, tcpd provides the same functions as with socket-based applications. When some other protocol is used underneath TLI, functionality will be limited (no client username lookups, weird network address formats). Decide which services you want to monitor. Move the corresponding vendor-provided daemon programs to the location specified by the REAL_DAEMON_DIR constant in the Makefile, and fill the holes with copies of the tcpd program. That is, one copy of (or link to) the tcpd program for each service that you want to monitor. For example, to monitor the use of your finger service: # mkdir REAL_DAEMON_DIR # mv /usr/etc/in.fingerd REAL_DAEMON_DIR # cp tcpd /usr/etc/in.fingerd The example applies to SunOS 4. With other UNIX implementations the network daemons live in /usr/libexec, /usr/sbin or in /etc, or have no "in." prefix to their names, but you get the idea. File protections: the wrapper, all files used by the wrapper, and all directories in the path leading to those files, should be accessible but not writable for unprivileged users (mode 755 or mode 555). Do not install the wrapper set-uid. Ultrix only: If you want to monitor the SYSTAT service, move the vendor-provided miscd daemon to the location specified by the REAL_DAEMON_DIR macro in the Makefile, and install the miscd wrapper at the original miscd location. In the absence of any access-control tables, the daemon wrappers will just maintain a record of network connections made to your system. 7.2 - Advanced configuration and installation --------------------------------------------- The advanced recipe leaves your daemon executables alone, but involves simple modifications to the inetd configuration file. Type `make' and follow the instructions. The Makefile comes with ready-to-use templates for many common UNIX implementations (sun, ultrix, hp-ux, aix, irix, ...). IRIX users should read the warnings in the README.IRIX file first. When the `make' succeeds the result is five executables (six in case of Ultrix). You can use the `tcpdchk' program to identify the most common problems in your wrapper and inetd configuration files. With the `tcpdmatch' program you can examine how the wrapper would react to specific requests for service. The `try-from' program tests the host and username lookup code. Run it from a remote shell command (`rsh host /some/where/try-from') and it should be able to figure out from what system it is being called. The `safe_finger' command should be used when you implement a booby trap: it gives better protection against nasty stuff that remote hosts may do in response to your finger probes. The tcpd program can be used to monitor the telnet, finger, ftp, exec, rsh, rlogin, tftp, talk, comsat and other tcp or udp services that have a one-to-one mapping onto executable files. With System V.4-style systems, the tcpd program can also handle TLI services. When TCP/IP or UDP/IP is used underneath TLI, tcpd provides the same functions as with socket-based applications. When some other protocol is used underneath TLI, functionality will be limited (no client username lookups, weird network address formats). The tcpd program can also be used for services that are marked as rpc/udp in the inetd configuration file, but not for rpc/tcp services such as rexd. You probably do not want to run rexd anyway. On most systems it is even less secure than a wildcard in /etc/hosts.equiv. Install the tcpd command in a suitable place. Apollo UNIX users will want to install it under a different name because the name "tcpd" is already taken; a suitable name would be "frontd". File protections: the wrapper, all files used by the wrapper, and all directories in the path leading to those files, should be accessible but not writable for unprivileged users (mode 755 or mode 555). Do not install the wrapper set-uid. Then perform the following edits on the inetd configuration file (usually /etc/inetd.conf or /etc/inet/inetd.conf): finger stream tcp nowait nobody /usr/etc/in.fingerd in.fingerd ^^^^^^^^^^^^^^^^^^^ becomes: finger stream tcp nowait nobody /usr/etc/tcpd in.fingerd ^^^^^^^^^^^^^ Send a `kill -HUP' to the inetd process to make the change effective. Some IRIX inetd implementations require that you first disable the finger service (comment out the finger service and `kill -HUP' the inetd) before you can turn on the modified version. Sending a HUP twice seems to work just as well for IRIX 5.3, 6.0, 6.0.1 and 6.1. AIX note: you may have to execute the `inetimp' command after changing the inetd configuration file. The example applies to SunOS 4. With other UNIX implementations the network daemons live in /usr/libexec, /usr/sbin, or /etc, the network daemons have no "in." prefix to their names, or the username field in the inetd configuration file may be missing. When the finger service works as expected you can perform similar changes for other network services. Do not forget the `kill -HUP'. The miscd daemon that comes with Ultrix implements several network services. It decides what to do by looking at its process name. One of the services is systat, which is a kind of limited finger service. If you want to monitor the systat service, install the miscd wrapper in a suitable place and update the inetd configuration file: systat stream tcp nowait /suitable/place/miscd systatd Ultrix 4.3 allows you to specify a user id under which the daemon will be executed. This feature is not documented in the manual pages. Thus, the example would become: systat stream tcp nowait nobody /suitable/place/miscd systatd Older Ultrix systems still run all their network daemons as root. In the absence of any access-control tables, the daemon wrappers will just maintain a record of network connections made to your system. 7.3 - Daemons with arbitrary path names --------------------------------------- The above tcpd examples work fine with network daemons that live in a common directory, but sometimes that is not practical. Having soft links all over your file system is not a clean solution, either. Instead you can specify, in the inetd configuration file, an absolute path name for the daemon process name. For example, ntalk dgram udp wait root /usr/etc/tcpd /usr/local/lib/ntalkd When the daemon process name is an absolute path name, tcpd ignores the value of the REAL_DAEMON_DIR constant, and uses the last path component of the daemon process name for logging and for access control. 7.4 - Building and testing the access control rules --------------------------------------------------- In order to support access control the wrappers must be compiled with the -DHOSTS_ACCESS option. The access control policy is given in the form of two tables (default: /etc/hosts.allow and /etc/hosts.deny). Access control is disabled when there are no access control tables, or when the tables are empty. If you haven't used the wrappers before I recommend that you first run them a couple of days without any access control restrictions. The logfile records should give you an idea of the process names and of the host names that you will have to build into your access control rules. The syntax of the access control rules is documented in the file hosts_access.5, which is in `nroff -man' format. This is a lengthy document, and no-one expects you to read it right away from beginning to end. Instead, after reading the introductory section, skip to the examples at the end so that you get a general idea of the language. Then you can appreciate the detailed reference sections near the beginning of the document. The examples in the hosts_access.5 document (`nroff -man' format) show two specific types of access control policy: 1) mostly closed (only permitting access from a limited number of systems) and 2) mostly open (permitting access from everyone except a limited number of trouble makers). You will have to choose what model suits your situation best. Implementing a mixed policy should not be overly difficult either. Optional extensions to the access control language are described in the hosts_options.5 document (`nroff -man' format). The `tcpdchk' program examines all rules in your access control files and reports any problems it can find. `tcpdchk -v' writes to standard output a pretty-printed list of all rules. `tcpdchk -d' examines the hosts.access and hosts.allow files in the current directory. This program is described in the tcpdchk.8 document (`nroff -man' format). The `tcpdmatch' command can be used to try out your local access control files. The command syntax is: tcpdmatch process_name hostname (e.g.: tcpdmatch in.tftpd localhost) tcpdmatch process_name address (e.g.: tcpdmatch in.tftpd 127.0.0.1) This way you can simulate what decisions will be made, and what actions will be taken, when hosts connect to your own system. The program is described in the tcpdmatch.8 document (`nroff -man' format). Note 1: `tcpdmatch -d' will look for hosts.{allow,deny} tables in the current working directory. This is useful for testing new rules without bothering your users. Note 2: you cannot use the `tcpdmatch' command to simulate what happens when the local system connects to other hosts. In order to find out what process name to use, just use the service and watch the process name that shows up in the logfile. Alternatively, you can look up the name from the inetd configuration file. Coming back to the tftp example in the tutorial section above: tftp dgram udp wait root /usr/etc/tcpd in.tftpd -s /tftpboot This entry causes the inetd to run the wrapper program (tcpd) with a process name `in.tftpd'. This is the name that the wrapper will use when scanning the access control tables. Therefore, `in.tftpd' is the process name that should be given to the `tcpdmatch' command. On your system the actual inetd.conf entry may differ (tftpd instead of in.tftpd, and no `root' field), but you get the idea. When you specify a host name, the `tcpdmatch' program will use both the host name and address. This way you can simulate the most common case where the wrappers know both the host address and the host name. The `tcpdmatch' program will iterate over all addresses that it can find for the given host name. When you specify a host address instead of a host name, the `tcpdmatch' program will pretend that the host name is unknown, so that you can simulate what happens when the wrapper is unable to look up the client host name. 7.5 - Other applications ------------------------ The access control routines can easily be integrated with other programs. The hosts_access.3 manual page (`nroff -man' format) describes the external interface of the libwrap.a library. The tcpd program can even be used to control access to the mail service. This can be useful when you suspect that someone is trying out some obscure sendmail bug, or when a remote site is misconfigured and keeps hammering your mail daemon. In that case, sendmail should not be run as a stand-alone network listener, but it should be registered in the inetd configuration file. For example: smtp stream tcp nowait root /usr/etc/tcpd /usr/lib/sendmail -bs You will still need to run one sendmail background process to handle queued-up outgoing mail. A command like: /usr/lib/sendmail -q15m (no `-bd' flag) should take care of that. You cannot really prevent people from posting forged mail this way, because there are many unprotected smtp daemons on the network. 8 - Acknowledgements -------------------- Many people contributed to the evolution of the programs, by asking inspiring questions, by suggesting features or bugfixes, or by submitting source code. Nevertheless, all mistakes and bugs in the wrappers are my own. Thanks to Brendan Kehoe (cs.widener.edu), Heimir Sverrisson (hafro.is) and Dan Bernstein (kramden.acf.nyu.edu) for feedback on an early release of this product. The host name/address check was suggested by John Kimball (src.honeywell.com). Apollo's UNIX environment has some peculiar quirks: Willem-Jan Withagen (eb.ele.tue.nl), Pieter Schoenmakers (es.ele.tue.nl) and Charles S. Fuller (wccs.psc.edu) provided assistance. Hal R. Brand (addvax.llnl.gov) told me how to get the client IP address in case of datagram-oriented services, and suggested the optional shell command feature. Shabbir Safdar (mentor.cc.purdue.edu) provided a first version of a much-needed manual page. Granville Boman Goza, IV (sei.cmu.edu) suggested to use the client IP address even when the host name is available. Casper H.S. Dik (fwi.uva.nl) provided additional insight into DNS spoofing techniques. The bogus daemon feature was inspired by code from Andrew Macpherson (BNR Europe Ltd). Steve Bellovin (research.att.com) confirmed some of my suspicions about the darker sides of TCP/IP insecurity. Risks of automated fingers were pointed out by Borja Marcos (we.lc.ehu.es). Brad Plecs (jhuspo.ca.jhu.edu) was kind enough to try my early TLI code and to work out how DG/UX differs from Solaris. John P. Rouillard (cs.umb.edu) deserves special mention for his persistent, but constructive, nagging about wrong or missing things, and for trying out and discussing embryonic code or ideas. Last but not least, Howard Chu (hanauma.jpl.nasa.gov), Darren Reed (coombs.anu.edu.au), Icarus Sparry (gdr.bath.ac.uk), Scott Schwartz (cs.psu.edu), John A. Kunze (violet.berkeley.edu), Daniel Len Schales (engr.latech.edu), Chris Turbeville (cse.uta.edu), Paul Kranenburg (cs.few.eur.nl), Marc Boucher (cam.org), Dave Mitchell (dcs.shef.ac.uk), Andrew Maffei, Adrian van Bloois, Rop Gonggrijp, John C. Wingenbach, Everett F. Batey and many, many others provided fixes, code fragments, or ideas for improvements. Wietse Venema (wietse@wzv.win.tue.nl) Department of Mathematics and Computing Science Eindhoven University of Technology P.O. Box 513 5600 MB Eindhoven The Netherlands Currently visiting IBM T.J. Watson Research, Hawthorne NY, USA. usr/share/doc/at-3.1.13/README 0000644 00000002126 14721022402 0011224 0 ustar 00 This is version of 3.1.x of at, for running commands at a specified time. To install, do a $ ./configure You might want to change the default maximum load at which batch jobs are still started by specifying --with-loadavg_mx=... as argument to configure. The default is 0.8, so that, normally, no batch job will be started when there's still activity going on. For an SMP system, you will want to increase this. Then, do $ make and, as root, # make install at jobs are run by the atd daemon, which is normally started at boot time. Bug reports to: http://bugs.debian.org/ (Debian bug tracking system) or at@packages.debian.org (Debian at package maintainers) If at all possible, I'd appreciate you telling me which version you found a bug in; run at -V to find out which one. If you try to use at(1) on a system which does not support setreuid(2), i.e. if you get an error whch looks vaguely like undefined symbol _setreuid referenced from text segment DO NOT try to install at on your system by removing all that strange PRIV stuff. You will install a rather glaring security hole that way. usr/share/doc/perl-constant-1.27/README 0000644 00000002623 14721022536 0013267 0 ustar 00 NAME constant - Perl pragma to declare constants DESCRIPTION This pragma allows you to declare constants at compile-time. When a constant is used in an expression, Perl replaces it with its value at compile time, and may then optimize the expression further. In particular, any code in an "if (CONSTANT)" block will be optimized away if the constant is false. INSTALLATION To install this module, run the following commands: perl Makefile.PL make make test make install Alternatively, to install with Module::Build, you can use the following commands: perl Build.PL ./Build ./Build test ./Build install SUPPORT AND DOCUMENTATION After installing, you can find documentation for this module with the perldoc command. perldoc constant You can also look for information at: Search CPAN http://search.cpan.org/dist/constant CPAN Request Tracker: http://rt.cpan.org/Dist/Display.html?Name=constant AnnoCPAN, annotated CPAN documentation: http://annocpan.org/dist/constant CPAN Ratings: http://cpanratings.perl.org/d/constant COPYRIGHT AND LICENCE Copyright (C) 1997, 1999 Tom Phoenix. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. usr/share/doc/perl-Readonly-1.03/README 0000644 00000005620 14721022554 0013205 0 ustar 00 Readonly version 1.03 ===================== CHANGES FROM VERSION 1.02 (See "Changes" file for details) o Syntax of Readonly() function has changed, for users of Perl 5.8 and later. DESCRIPTION Readonly.pm provides a facility for creating non-modifiable scalars, arrays, and hashes. Perl provides a built-in mechanism (the "use constant" pragma) to create constant scalars and lists. That mechanism has several limitations, however: It creates only scalars and arrays (not hashes). It creates "variables" that have no leading $ or @ character. The variables it creates cannot be interpolated into strings. It works only at compile time. The variables it creates are global, never lexical. Sometimes you have to be careful with your syntax when using them (for example, when using one as a hash key). You can't pass these constants around like variables (for example, you can't take references to them). It is rather difficult to make and use complex data structures with use constant. "use constant" directives can be overridden by subsequent "use constant" directives. (this does generate a warning). Readonly.pm, by contrast: Creates scalars, arrays (not lists), and hashes. Creates variables that look and work like native perl variables. Creates global or lexical variables. Works at runtime or compile time. Works with deep or shallow data structures. Prevents reassignment of Readonly variables. EXAMPLES OF USE Readonly::Scalar $x => "A string value"; Readonly::Array @x => (1, 2, 3, 4); Readonly::Hash %x => (key1 => 'value1', key2 => 'value2'); If the program subsequently tries to modify $x, @x, or %x, the program will die with an error message. Deep structures are a breeze: Readonly::Hash %x => {key1 => [1, 2], key2 => [3, 4, 5]}; print $x{key1}[1]; Try that with "use constant"! INSTALLATION To install this module, do the standard Perl module four-step: perl Makefile.PL or perl Makefile.pl LIB='my/install/path' make make test make install DEPENDENCIES Test::Harness and Test::More, if you want to run the test suites (and yes, you should). Also, Carp.pm and Exporter.pm, but they come with Perl. Readonly::XS (available on CPAN) is a companion module to Readonly. If that module is present, Readonly will use it for handling scalars. This results in a significant speed improvement. This is transparent to your code; whether or not the XS module is present, Readonly works the same. COPYRIGHT AND LICENSE Eric J. Roode, roode@cpan.org Copyright (c) 2001-2004 by Eric J. Roode. All Rights Reserved. This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. If you have suggestions for improvement, please drop me a line. If you make improvements to this software, I ask that you please send me a copy of your changes. Thanks. usr/share/doc/fontconfig-2.13.0/README 0000644 00000240774 14721022757 0013004 0 ustar 00 Fontconfig Font configuration and customization library Version 2.13 2018-03-06 Check INSTALL for compilation and installation instructions. Report bugs to https://bugs.freedesktop.org in the fontconfig module. 2.13 Akira TAGOH (4): Add Simplified Chinese translations Fix a build issue on MinGW with enabling nls Initialize an array explicitly Bump the libtool revision 2.12.93 (2.13 RC3) Akira TAGOH (12): trivial fix Add files to enable ITS support in gettext Use the native ITS support in gettext Remove POTFILES.in until new release of gettext is coming... export GETTEXTDATADIR to refer the local .its/.loc file instead of using --its option clean up Do not add cflags and libs coming from pkg-config file. Revert some removal from 7ac6af6 Take effects on dir, cachedir, acceptfont, and rejectfont only when loading Do not mix up font dirs into the list of config dirs Ensure the user config dir is available in the list of config dirs on the fallback config Add missing files to ship Alexander Larsson (1): FcHashTableAddInternal: Compare against the right key Behdad Esfahbod (5): Remove hack for OS/2 weights 1..9 Support FC_WIDTH as double as well Fix leak Use FT_Done_MM_Var if available Fix undefined-behavior signed shifts Olivier Crête (1): Fix cross-compilation by passing CPPFLAGS to CPP Tom Anderson (1): Allow overriding symbol visibility. 2.12.92 (2.13 RC2) Akira TAGOH (13): cleanup files Update .uuid only when -r is given but not -f. Returns false if key is already available in the table Add missing doc of FcDirCacheCreateUUID Replace uuid in the table properly when -r Add a test case for uuid creation Do not update mtime with creating .uuid Disable uuid related code on Win32 Try to get current instance of FcConfig as far as possible do not check the existence of itstool on win32 Fix the mis-ordering of ruleset evaluation in a file with include element Fix compiler warnings Add FcReadLink to wrap up readlink impl. Alexander Larsson (1): fchash: Fix replace Behdad Esfahbod (7): Don't crash Remove a debug abort() Minor Set font-variations settings for standard axes in variable fonts Let pattern FC_FONT_VARIATIONS override standard axis variations Put back accidentally removed code Add FcWeightTo/FromOpenTypeDouble() 2.12.91 (2.13 RC1) Akira TAGOH (37): und_zsye.orth: polish to get for NotoEmoji-Regular.ttf Revert "Keep the same behavior to the return value of FcConfigParseAndLoad" Fix again to keep the same behavior to the return value of FcConfigParseAndLoad cleanup Fix a compiler warning Update libtool revision Bump version to 2.12.6 doc: trivial update Add the ruleset description support workaround to avoid modifying by gettextize missing an open parenthesis another workaround to avoid modifying by gettextize... Validate cache more carefully Allow autoreconf through autopoint for gettext things Correct debugging messages to load/scan config Add the check of PCF_CONFIG_OPTION_LONG_FAMILY_NAMES back Use uuid-based cache filename if uuid is assigned to dirs Add new API to find out a font from current search path Replace the font path in FcPattern to what it is actually located. Replace the original path to the new one Replace the path of subdirs in caches as well Don't call FcStat when the alias has already been added Destroy the alias and UUID tables when all of caches is unloaded cleanup abstract hash table functions update Fix memory leak Fix a typo Don't call FcStat when the alias has already been added Add a testcase for bind-mounted cachedir cleanup Use smaller prime for hash size Fix the testcase for env not enabled PCF_CONFIG_OPTION_LONG_FAMILY_NAMES in freetype thread-safe functions in fchash.c Fix distcheck error Fix "make check" fail again Bump the libtool revision Alban Browaeys (1): Fixes cleanup Alexander Kanavin (1): src/fcxml.c: avoid double free() of filename Bastien Nocera (1): conf: Prefer system emoji fonts to third-party ones Behdad Esfahbod (76): Minor Remove stray printf() [fc-query] Fix linking order Instead of loading glyphs (with FreeType), just check loca table Don't even check loca for glyph outline detection Check for non-empty outline for U+0000..U+001F Add back code for choosing strike, and cleanup Minor: adjust debug output Remove unnecessary check Remove a few unused blanks parameters Remove check that cannot fail Remove use of psnames for charset construction Remove unused variable Remove fc-glyphname Remove blanks facility from the library Remove blanks support from fc-scan Mark more parameters FC_UNUSED Move variables to narrower scope and indent Remove unneeded check Use multiplication instead of division Use inline functions instead of macros for a couple of things Simplify advance-width calculations Inline FcFreeTypeCheckGlyph() Call FT_Get_Advance() only as long as we need to determine font width type Minor Update documentation for removal of blanks Merge branch 'faster' Add FcFreeTypeQueryAll() Document FcFreeTypeQueryAll() Accept NULL in for spacing in FcFreeTypeCharSetAndSpacing() Remove FcCompareSize() Rename FcCompareSizeRange() to FcCompareRange() Rewrite FcCompareRange() In FcSubstituteDefault(), handle size range Check instance-index before accessing array Indent [varfonts] Add FC_FONT_VARIATIONS [varfonts] Add FC_VARIABLE [varfonts] Change id argument in FcFreeTypeQuery* to unsigned int Print ranges as closed as opposed to half-open [varfonts] Change FC_WEIGHT and FC_WIDTH into ranges [varfonts] Query varfonts if id >> 16 == 0x8000 Fix instance-num handling in collections [varfonts] Query variable font in FcFreeTypeQueryAll() [varfonts] Fetch optical-size for named instances In RenderPrepare(), handle ranges smartly [fc-query] Remove --ignore-blanks / -b [fc-match/fc-list/fc-query/fc-scan] Add --brief that is like --verbose without charset Add separate match compare function for size Fix range comparision operators implementation Adjust emboldening logic [varfonts] Map from OpenType to Fontconfig weight values Add FcDontCare value to FcBool Implement more config bool operations for boolean types Fix possible div-by-zero [varfonts] Use fvar data even if there's no variation in it Minor Revert "[varfonts] Use fvar data even if there's no variation in it" [varfonts] Minor [varfonts] Comment [varfonts] Don't set style for variable-font pattern [varfonts] Skip named-instance that is equivalent to base font [varfonts] Do not set postscriptname for varfont pattern [varfonts] Don't reopen face for each named instance Separate charset and spacing code [varfonts] Reuse charset for named instances Move whitespace-trimming code to apply to all name-table strings Fix whitespace-trimming loop and empty strings... Whitespace Don't convert nameds to UTF-8 unless we are going to use them Simplify name-table platform mathcing logic Use binary-search for finding name table entries [varfonts] Share lang across named-instances Merge branch 'varfonts2' Require freetype >= 2.8.1 Remove assert David Kaspar [Dee'Kej] (1): conf.d: Drop aliases for (URW)++ fonts Florian Müllner (1): build: Remove references to deleted file 2.12.6 Akira TAGOH (4): und_zsye.orth: polish to get for NotoEmoji-Regular.ttf Revert "Keep the same behavior to the return value of FcConfigParseAndLoad" Fix again to keep the same behavior to the return value of FcConfigParseAndLoad Update libtool revision Behdad Esfahbod (2): Minor [fc-query] Fix linking order David Kaspar [Dee'Kej] (1): conf.d: Drop aliases for (URW)++ fonts Florian Müllner (1): build: Remove references to deleted file 2.12.5 Akira TAGOH (17): Add FcPatternGetWithBinding() to obtain the binding type of the value in FcPattern. Add FcConfigParseAndLoadFromMemory() to load a configuration from memory. Bug 101726 - Sans config pulls in Microsoft Serifed font Fix gcc warnings with enabling libxml2 Add und-zsye.orth to support emoji in lang Add more code points to und-zsye.orth Keep the same behavior to the return value of FcConfigParseAndLoad Do not ship fcobjshash.gperf in archive Accept 4 digit script tag in FcLangNormalize(). Fix to work the debugging option on fc-validate Add und_zmth.orth to support Math in lang Polish und_zmth.orth for Libertinus Math Polish und_zmth.orth more for Cambria Math and Minion Math Update similar to emoji's fc-blanks: fall back to the static data available in repo if downloaded data is corrupted Update docs Update libtool versioning Behdad Esfahbod (14): Pass --pic to gperf Add generic family matching for "emoji" and "math" [fc-query] Support listing named instances Add Twitter Color Emoji Add EmojiOne Mozilla font [fc-lang] Allow using ".." instead of "-" in ranges Minor Remove unneeded codepoints Adjust color emoji config some more Ignore 'und-' prefix for in FcLangCompare Minor Fix sign-difference compare warning Fix warning Fix weight mapping 2.12.4 Akira TAGOH (5): Force regenerate fcobjshash.h when updating Makefile Fix the build failure when srcdir != builddir and have gperf 3.1 or later installed Add a testcase for Bug#131804 Update libtool revision Fix distcheck error Florent Rougon (6): FcCharSetHash(): use the 'numbers' values to compute the hash fc-lang: gracefully handle the case where the last language initial is < 'z' Fix an off-by-one error in FcLangSetIndex() Fix erroneous test on language id in FcLangSetPromote() FcLangSetCompare(): fix bug when two charsets come from different "buckets" FcCharSetFreezeOrig(), FcCharSetFindFrozen(): use all buckets of freezer->orig_hash_table Helmut Grohne (1): fix cross compilation Jan Alexander Steffens (heftig) (1): Fix testing PCF_CONFIG_OPTION_LONG_FAMILY_NAMES (CFLAGS need to be right) Josselin Mouette (1): Treat C.UTF-8 and C.utf8 locales as built in the C library. Masamichi Hosoda (1): Bug 99360 - Fix cache file update on MinGW 2.12.3 Akira TAGOH (1): Fix make check fail with freetype-2.7.1 and 2.8 with PCF_CONFIG_OPTION_LONG_FAMILY_NAMES enabled. 2.12.2 Akira TAGOH (8): Don't call perror() if no changes happens in errno Fix FcCacheOffsetsValid() Fix the build issue with gperf 3.1 Fix the build issue on GNU/Hurd Update a bit for the changes in FreeType 2.7.1 Add the description of FC_LANG envvar to the doc Bug 101202 - fontconfig FTBFS if docbook-utils is installed Update libtool revision Alan Coopersmith (1): Correct cache version info in doc/fontconfig-user.sgml Khem Raj (1): Avoid conflicts with integer width macros from TS 18661-1:2014 Masamichi Hosoda (2): Fix PostScript font alias name Update aliases for URW June 2016 2.12.1 Akira TAGOH (6): Add --with-default-hinting to configure Update CaseFolding.txt to Unicode 9.0 Check python installed in autogen.sh Fix some errors related to python3 Bug 96676 - Check range of FcWeightFromOpenType argument Update libtool revision Tobias Stoeckmann (1): Properly validate offsets in cache files. 2.12 Akira TAGOH (8): Modernize fc-blanks.py Update URL Bug 95477 - FcAtomicLock fails when SELinux denies link() syscall with EACCES 45-latin.conf: Add some Windows fonts to categorize them properly Correct one for the previous change Bug 95481 - Build fails on Android due to broken lconv struct Add the static raw data to generate fcblanks.h Remove unused code Erik de Castro Lopo (1): Fix a couple of minor memory leaks Petr Filipsky (1): Fix memory leak in FcDirCacheLock 2.11.95 (2.12 RC5) Akira TAGOH (22): Add one more debugging option to see transformation on font-matching Fix a crash when no objects are available after filtering No need to be public mark as private at this moment Don't return FcFalse even when no fonts dirs is configured Add a warning for blank in fonts.conf Fix a memory leak in FcFreeTypeQueryFace Update CaseFolding.txt to Unicode 8.0 Bug 90867 - Memory Leak during error case in fccharset Fix the broken cache more. Fail on make runtime as needed instead of configure if no python installed Use long long to see the same size between LP64 and LLP64 Fix build issue on MinGW Use int64_t instead of long long Fix compiler warnings on MinGW Fix assertion on 32bit arch remomve unnecessary code Bug 93075 - Possible fix for make check failure on msys/MinGW... Avoid an error message on testing when no fonts.conf installed Add hintstyle templates and make hintslight default Revert "Workaround another race condition issue" Update libtool revision Behdad Esfahbod (6): Revert changes made to FcConfigAppFontAddDir() recently Call FcFreeTypeQueryFace() from fcdir.c, instead of FcFreeTypeQuery() [GX] Support instance weight, width, and style name [GX] Enumerate all named-instances in TrueType GX fonts Improve OpenType to Fontconfig weight mapping [GX] Improve weight mapping Patrick Haller (1): Optimizations in FcStrSet 2.11.94 (2.12 RC4) Akira TAGOH (16): Remove the dead code Bug 89617 - FcConfigAppFontAddFile() returns false on any font file Fix unknown attribute in Win32 Fix SIGFPE Fix a typo for the latest cache version Fix a typo in fontconfig-user.sgml Drop unmaintained code Observe blanks to compute correct languages in fc-query/fc-scan Add missing description for usage Make FC_SCALE deprecated Bug 90148 - Don't warn if cachedir isn't specified Fix memory leaks after FcFini() Fix a typo Fix a crash Detect the overflow for the object ID Revert the previous change Behdad Esfahbod (11): Fix bitmap scaling Add su[pport for symbol fonts Write ranges using a [start finish) format Only set FC_SIZE for scalable fonts if OS/2 version 5 is present Add bitmap-only font size as Double, not Range Accept Integer for FC_SIZE Don't set FC_SIZE for bitmap fonts Fix compiler warnings Simplify FcRange Reduce number of places that cache version is specified to 1 Bump cache version number to 6, because of recent FcRange changes Руслан Ижбулатов (1): W32: Support cache paths relative to the root directory 2.11.93 (2.12 RC3) Akira TAGOH (18): Fix a typo in docs Add pkg.m4 to git Fix a build fail on some non-POSIX platforms ifdef'd the unnecessary code for win32 Fix pointer cast warning on win32 filter can be null Copy the real size of struct dirent Rework again to copy the struct dirent Hardcode the blanks in the library Update the script to recognize the escaped space Fix a build issue when $(srcdir) != $(builddir) Don't add FC_LANG when it has "und" Fix the array allocation Improve the performance on searching blanks Fix a segfault when OOM happened. Fix a bug in the previous change forFcBlanksIsMember() Fix an infinite loop in FcBlanksIsMember() Fix a trivial bug for dist Alan Coopersmith (1): Fix configure to work with Solaris Studio compilers Behdad Esfahbod (3): Fix symbol cmap handling Remove dead code after previous commit Simplify some more Michael Haubenwallner (1): Ensure config.h is included first, bug#89336. 2.11.92 (2.12 RC2) Akira TAGOH (1): Add missing docs 2.11.91 (2.12 RC1) Akira TAGOH (28): Bug 71287 - size specific design selection support in OS/2 table version 5 Fix a build issue with freetype <2.5.1 Fix missing docs Fix a typo Fix fc-cache fail with -r Rebase ja.orth against Joyo kanji characters Allow the modification on FcTypeVoid with FcTypeLangSet and FcTypeCharSet Workaround another race condition issue Read the config files and fonts on the sysroot when --sysroot is given to fc-cache Fix a segfault Update CaseFolding.txt to Unicode 7.0 Don't read/write from/to the XDG dirs if the home directory is disabled Rework for 5004e8e01f5de30ad01904e57ea0eda006ab3a0c Fix a crash when no sysroot is given and failed to load the default fonts.conf Fix a gcc warning Don't add duplicate lang fallback to the another method to lock when link() failed Increase the refcount in FcConfigSetCurrent() Fix the memory leak in fc-cat Note FcConfigSetCurrent() increases the refcount in document Add FcRangeGetDouble() Revert "Bug 73291 - poppler does not show fl ligature" Update aliases for new URW fonts Returns False if no fonts found fc-cache: make a fail if no fonts processed on a given path fc-cache: Add an option to raise an error if no fonts found Bump the cache version to 5 Fix a typo Behdad Esfahbod (39): Remove unused code Simplify hash code Further simplify hash code Rewrite hashing to use FT_Stream directly Allow passing NULL for file to FcFreeTypeQueryFace() [ko.orth] Remove U+3164 HANGUL FILLER Deprecate FC_HASH and don't compute it Remove unused FcHash code now that FC_HASH is deprecated Update list of blanks to Unicode 6.3.0 Update blanks to Unicode 7.0 Change charset parse/unparse format to be human readable Minor Fix charset unparse after recent changes Comments Remove HASH from matching priorities Fixup previous commit Update mingw32 MemoryBarrier from HarfBuzz More mingw32 MemoryBarrier() fixup Symlinks fix for DESTDIR Revert "Symlinks fix for DESTDIR" Call FcInitDebug from FcFreeTypeQueryFace Decode MacRoman encoding in name table without iconv Ouch, fix buffer Use lang=und instead of lang=xx for "undetermined" Remove unused regex code Improve / cleanup namelang matching Add FC_WEIGHT_DEMILIGHT Change DemiLight from 65 to 55 Linearly interpolate weight values Export recently added API Remove unneeded FcPublic Fix assertion failure If OS/2 table says weight is 1 to 9, multiply by 100 Trebuchet MS is a sans-serif font, not serif Fix previous commit Revert "[fcmatch] When matching, reserve score 0 for when elements don't exist" Fix buffer overflow in copying PS name Add FC_COLOR Treat color fonts as scalable Nick Alcock (1): Generate documentation for FcWeight* functions. 2.11.1 Akira TAGOH (31): do not build test-migration for Win32 Fix build issue on Debian/kFreeBSD 7.0 Update ax_pthread.m4 to the latest version Fix the dynamic loading issue on NetBSD Use stat() if there are no d_type in struct dirent Fix a build issue on Solaris 10 Change the default weight on match to FC_WEIGHT_NORMAL Warn if no <test> nor <edit> elements in <match> Correct DTD Re-scan font directories only when it contains subdirs Fix typo Bug 72086 - Check for gperf in autogen.sh Simplify to validate the availability of posix_fadvise Simplify to validate the availability of scandir Fix a typo Fix a build issue on platforms where doesn't support readlink() Improve the performance issue on rescanning directories Bug 73686 - confdir is not set correctly in fontconfig.pc Update zh_hk.orth clean up the unused files Add missing license headers Update the use of autotools' macro Fix a crash issue when empty strings are set to the BDF properties Add a doc for FcDirCacheRescan Add missing #include <sys/statvfs.h> in fcstat.c Fix incompatible API on AIX with random_r and initstate_r Fallback to lstat() in case the filesystem doesn't support d_type in struct dirent Update doc to include the version info of `since when' Bug 73291 - poppler does not show fl ligature Add README describes the criteria to add/modify the orthography files Fix autoconf warning, warning: AC_COMPILE_IFELSE was called before AC_USE_SYSTEM_EXTENSIONS Alan Coopersmith (3): Leave room for null terminators in arrays Avoid memory leak when NULL path passed to FcStrBuildFilename Avoid null pointer dereference in FcNameParse if malloc fails Behdad Esfahbod (1): Bug 72380 - Never drop first font when trimming Frederic Crozat (2): Fix inversion between Tinos and Cousine in the comment Add metric aliases for additional Google ChromeOS fonts Jehan (1): Defaulting <cachedir> to LOCAL_APPDATA_FONTCONFIG_CACHE for Win32 build Ross Burton (1): fc-cache: --sysroot option takes an argument 2.11 Akira TAGOH (15): Do not create a config dir for migration when no config files nor dirs Add a test case of the migration for config place Fix memory leaks in FcFreeTypeQueryFace Bug 68955 - Deprecate / remove FC_RASTERIZER Copy all values from the font to the pattern if the pattern doesn't have the element Fix a crash when FcPattern is set to null on FcFontSetList() and FcFontList() Add the description of -q option to the man page avoid reading config.h twice clean up Add the relative path for <include> to fonts.conf if the parent path is same to fonts.conf Workaround the race condition issue on updating cache exit with the error code when FcNameParse() failed Add missing doc for FcStrListFirst and fix a typo Bump libtool revision Update CaseFolding.txt to Unicode 6.3 Jan Alexander Steffens (heftig) (1): Further changes to 30-metric-aliases.conf W. Trevor King (1): doc/fccharset.fncs: Describe the map format in more detail 2.10.95 (2.11 RC5) Akira TAGOH (2): Fix a typo Fix a crash 2.10.94 (2.11 RC4) Akira TAGOH (25): Bug 64906 - FcNameParse() should ignore leading whitespace in parameters Fix a comparison of constant warning with clang Fix a shift count overflow on 32bit box Fix a incompatible pointer warning on NetBSD Add FcTypeUnknown to FcType to avoid comparison of constant -1 Fix the behavior of intermixed tests end edits in match Ignore scandir() check on mingw Use INT_MAX instead of unreliable hardcoding value Add FC_UNUSED to FC_ASSERT_STATIC macro to avoid compiler warning Rework to apply the intermixed test and edit elements in one-pass trivial code optimization Correct fontconfig.pc to add certain dependencies for build Correct fontconfig.pc to add certain dependencies for static build Fix wrong edit position Bug 67809 - Invalid read/write with valgrind when assigning something twice warn deprecated only when migration failed Bug 67845 - Match on FC_SCALABLE Bug 16818 - fontformat in match pattern is not respected? Bug 68340 - More metric compat fonts Bug 63399 - Add default aliases for Georgia, Garamond, Palatino Linotype, Trebuchet MS Fix a typo Fix a crash when non-builtin objects are edited Fix a wrong edit position when 'kind' is different Bug 68587 - copy qu.orth to quz.orth Add quz.orth to Makefile.am Behdad Esfahbod (2): Minor Fix assertion 2.10.93 (2.11 RC3) Akira TAGOH (10): Bug 62980 - matching native fonts with even :lang=en Ensure closing fp on error Obtain fonts data via FT_Face instead of opening a file directly Revert the previous change and rework to not export freetype API outside fcfreetype.c documented FC_HASH and FC_POSTSCRIPT_NAME Bug 63329 - make check fails: .. contents:: :depth: 2 Use the glob matching for filename Bug 63452 - conf.d/README outdated Fix missing OSAtomicCompareAndSwapPtrBarrier() on Mac OS X 10.4 Bug 63922 - FcFreeTypeQueryFace fails on postscripts fonts loaded from memory Sebastian Freundt (1): build-chain, replace INCLUDES directive by AM_CPPFLAGS 2.10.92 (2.11 RC2) Akira TAGOH (33): Fix the build fail on MinGW Bug 50497 - RFE: Add OpenType feature tags support Improve FcGetPrgname() to work on BSD Better fix for 2fe5ddfd Add missing file descriptor to F_DUPFD_CLOEXEC Fix mkstemp absence for some platform Fix installation on MinGW32 Add another approach to FC_PRGNAME for Solaris 10 or before remove the unnecessary code Bug 59385 - Do the right thing for intermixed edit and test elements Bug 23757 - Add mode="delete" to <edit> Modernize configure.ac Use AM_MISSING_PROG instead of hardcoding missing Revert "test: Use SH_LOG_COMPILER and AM_TESTS_ENVIRONMENT" Use AM_MISSING_PROG instead of hardcoding missing Bug 50733 - Add font-file hash? Bug 60312 - DIST_SUBDIRS should never appear in a conditional Update _FcMatchers definition logic Bump the cache version to 4 Add Culmus foundry to the vendor list Bug 60748 - broken conf.d/10-autohint.conf and conf.d/10-unhinted.conf Bug 60783 - Add Liberation Sans Narrow to 30-metric-aliases.conf Fix a typo Fix a crash when the object is non-builtin object Fix broken sort order with FcFontSort() Fix a memory leak Bug 59456 - Adding a --sysroot like option to fc-cache Do not copy FC_*LANG_OBJECT even if it's not available on the pattern Fix a SIGSEGV on FcPatternGet* with NULL pattern Bug 38737 - Wishlist: support FC_POSTSCRIPT_NAME Minor cleanup Bump libtool revision Minor fix Behdad Esfahbod (12): Resepct $NOCONFIGURE Ensure we find the uninstalled fontconfig header Copy all values from pattern to font if the font doesn't have the element Minor Bug 59379 - FC_PRGNAME Remove unused checks for common functions Minor Fix fc-cache crash caused by looking up NULL object incorrectly Fix FC_PRGNAME default Fix readlink failure Accept digits as part of OpenType script tags Fix crash with FcConfigSetCurrent(NULL) Christoph J. Thompson (1): Use the PKG_INSTALLDIR macro. Colin Walters (1): build: Only use PKG_INSTALLDIR if available Quentin Glidic (2): test: Use SH_LOG_COMPILER and AM_TESTS_ENVIRONMENT Use LOG_COMPILER and AM_TESTS_ENVIRONMENT 2.10.91 (2.11 RC1) Akira TAGOH (19): Fix a potability issue about stdint.h Fix build issues on clean tree Do not show the deprecation warning if it is a symlink Fix a typo Fix the wrong estimation for the memory usage information in fontconfig Remove the duplicate null-check Remove the dead code clean up Fix a typo that accessing to the out of array Fix a memory leak Check the system font to be initialized Missing header file for _mkdir declaration Clean up the unused variable Bug 47705 - Using O_CLOEXEC missing header file to declare _mkdir Fix a build fail on mingw Fix a typo in the manpages template Bug 29312 - RFE: feature to indicate which characters are missing to satisfy the language support Update the date in README properly Behdad Esfahbod (73): Fix typo Parse matrices of expressions Fix compiler warnings Fix unused-parameter warnings Fix more warnings Fix sign-compare warnings Fix warning Fix more warnings Fixup from 4f6767470f52b287a2923e7e6d8de5fae1993f67 Remove memory accounting and reporting Allow target="font/pattern/default" in <name> elements Don't warn if an unknown element is used in an expression Unbreak build when FC_ARCHITECTURE is defined Remove unneeded stuff Enable fcarch assert checks even when FC_ARCHITECTURE is explicitly given Make tests run on Windows Initialize matrix during name parsing Adjust docs for recent changes Warn if <name target="font"> appears in <match target="pattern"> Make FC_DBG_OBJTYPES debug messages into warnings Refuse to set value to unsupported types during config too Add NULL check Don't crash in FcPatternDestroy with NULL pattern Don't crash in FcPatternFormat() with NULL pattern Minor Whitespace Deprecate FcName(Un)RegisterObjectTypes / FcName(Un)RegisterConstants Use a static perfect hash table for object-name lookup Switch .gitignore to git.mk Remove shared-str pool Fix build stuff Add build stuff for threadsafety primitives Add thread-safety primitives Make refcounts, patterns, charsets, strings, and FcLang thread-safe Make FcGetDefaultLang and FcGetDefaultLangs thread-safe Make FcInitDebug() idempotent Make FcDefaultFini() threadsafe Refactor; contain default config in fccfg.c Minor Make default-FcConfig threadsafe Minor Make FcCacheIsMmapSafe() threadsafe Minor Make cache refcounting threadsafe Add a big cache lock Make random-state initialization threadsafe Make cache hash threadsafe Make FcDirCacheDispose() threadsafe Make fcobjs.c thread-safe Warn about undefined/invalid attributes during config parsing Fixup fcobjs.c Remove FcSharedStr* Fix compiler warnings Minor Fix build and warnings on win32 Use CC_FOR_BUILD to generate source files Fix more warnings. Trying to fix distcheck Fix build around true/false Work around Sun CPP Really fix cross-compiling and building of tools this time Second try to make Sun CPP happy Ugh, add Tools.mk Minor Don't use blanks for fc-query Remove FcInit() calls from tools Add 10-scale-bitmap-fonts.conf and enable by default Oops, add the actual file Fix pthreads setup Fix memory corruption! Add pthread test Add atomic ops for Solaris Make linker happy Jon TURNEY (1): Fix build when srcdir != builddir 2.10.2 Akira TAGOH (13): Bug 53585 - Two highly-visible typos in src/fcxml.c Fix for libtoolize's warnings Bug 54138 - X_OK permission is invalid for win32 access(..) calls Bug 52573 - patch required to build 2.10.x with oldish GNU C library headers deal with warnings as errors for the previous change Fix wrongly squashing for the network path on Win32. Fix syntax errors in fonts.dtd. autogen.sh: Add -I option to tell aclocal a place for external m4 files Use automake variable instead of cleaning files in clean-local Bug 56531 - autogen.sh fails due to missing 'm4' directory Bug 57114 - regression on FcFontMatch with namelang Update CaseFolding.txt to Unicode 6.2 Bug 57286 - Remove UnBatang and Baekmuk Batang from monospace in 65-nonlatin.conf Behdad Esfahbod (1): Fix N'ko orthography Jeremy Huddleston Sequoia (1): Remove _CONFIG_FIXUPS_H_ guards, so multiple includes of "config.h" result in the correct values 2.10.1 Akira TAGOH (2): Fix a typo in fontconfig.pc Install config files first 2.10.0 Akira TAGOH (5): Bug 34266 - configs silently ignored if libxml2 doesn't support SAX1 interface Update CaseFolding.txt to Unicode 6.1 Fix a build fail with gcc 2.95, not supporting the flexible array members. Bump libtool revision Update INSTALL 2.9.92 (2.10 RC2) Akira TAGOH (9): Bug 50835 - Deprecate FC_GLOBAL_ADVANCE Fix a typo and build fail. Fix a build fail on MINGW Fix the fail of make install with --disable-shared on Win32 clean up the lock file properly on even hardlink-not-supported filesystem. Rename configure.in to configure.ac Bug 18726 - RFE: help write locale-specific tests Bump libtool revision Update INSTALL Marius Tolzmann (2): Fix newline in warning about deprecated config includes Fix warning about deprecated, non-existent config includes 2.9.91 (2.10 RC1) Akira TAGOH (60): [doc] Update the path for cache files and the version. [doc] Update for cachedir. Revert "Fix a build fail on some environment." Revert "Fix a build fail on some environment" Fix a build issue due to the use of non-portable variables Get rid of the prerequisites from the sufix rules Bug 39914 - Please tag the cache directory with CACHEDIR.TAG fc-cache: improvement of the fix for Bug#39914. fcmatch: Set FcResultMatch at the end if the return value is valid. Bug 47703 - SimSun default family Bug 17722 - Don't overwrite user's configurations in default config Fix a memory leak in FcDirScanConfig() Bug 17832 - Memory leaks due to FcStrStaticName use for external patterns fcpat: Increase the number of buckets in the shared string hash table Fix the hardcoded cache file suffix Move workaround macros for fat binaries into the separate header file Bug 48020 - Fix for src/makealias on Solaris 10 Bug 24729 - [ne_NP] Fix ortho file doc: Add contains and not_contains operators and elements Use AC_HELP_STRING instead of formatting manually Use pkgconfig to check builddeps Bug 29341 - Make some fontconfig paths configurable Bug 22862 - <alias> ignores <match> <test>s Bug 26830 - Add search for libiconv non-default directory Bug 28491 - Allow matching on FC_FILE Bug 48573 - platform without regex do not have also REG_XXX defines Bug 27526 - Compatibility fix for old windows sytems Add --with-expat, --with-expat-includes and --with-expat-lib back. doc: Fix a typo of the environment variable name. Bug 25151 - Move cleanCacheDirectory() from fc-cache.c into Rework to avoid adding the unexpected value to ICONV_CFLAGS and ICONV_LIBS Fix a build issue again when no regex functions available C++11 requires a space between literal and identifier Bug 47721 - Add ChromeOS fonts to 30-metric-aliases.conf Create CACHEDIR.TAG when fc-cache is run or only when the cache directory is created at the runtime. Add --enable-iconv option to configure Bug 27765 - FcMatch() returns style in wrong language Disable iconv support anyway... Bug 39278 - make usage of mmap optional Output more verbose debugging log to show where to insert the element into the value list fonts.conf: keeps same binding for alternatives fcarch.c: get rid of the duplicate definition of FC_MAX Bug 19128 - Handling whitespace in aliases Bug 20411 - fontconfig doesn't match FreeDesktop directories specs Correct the example Bug 33644 - Fontconfig doesn't match correctly in <test> fcatomic: fallback to create a directory with FcAtomicLock Move statfs/statvfs wrapper to fcstat.c and add a test for the mtime broken fs Fix the build fail on Solaris Fix a typo and polish the previous change Fix the wrong estimation for the memory usage information in fontconfig Bug 32853 - Export API to get the default language fcdefault: fallback if the environment variables are empty Add the default language to the pattern prior to do build the substitution fcdefault: no need to set FC_LANG in FcDefaultSubstitute() anymore fcdefault: Add the lang object at FcConfigSubstituteWithPat() only when kind is FcMatchPattern Bug 50525 - superfluous whitespace in the style Bump libtool revision doc: Fix distcheck error again... Generate bzip2-compressed tarball too Jeremy Huddleston (1): fcarch: Check for architecture signature at compile time rather than configure time Keith Packard (3): Use posix_fadvise to speed startup Extra ',' in AC_ARG_WITH(arch causes arch to never be autodetected Deal with architectures where ALIGNOF_DOUBLE < 4 Mark Brand (1): fix building for WIN32 Mikhail Gusarov (2): Move FcStat to separate compilation unit Fix cache aging for fonts on FAT filesystem under Linux 2.9 Akira TAGOH (28): Add charset editing feature. add some document for range and charset. Add the range support in blank element Add editing langset feature. add some documents Bug 24744 - No n'ko orthography Remove the unnecessary comment in ks.orth Bug 32965 - Asturian (ast-ES) language matching missing ḷḷḥ Add a missing file Bug 35517 - Remove Apple Roman cmap support Bug 40452 - Running 'fc-match --all' core dumps when no fonts are installed Get rid of the unexpected family name Bug 44826 - <alias> must contain only a single <family> Bug 46169 - Pointer error in FcConfigGlobMatch Do not update stream->pos when seeking is failed. Bug 27385 - lcdfilter settings for freetype-2.3.12 not available in fontconfig-2.8.0 Add brx.orth and sat.orth Bug 41694 - FcCache functions have random-number-generator side effects Bug 23336 - unable to display bitmap-only (SFNT) TrueType or OpenType Check null value for given object to avoid possibly segfaulting Bug 19128 - Handling whitespace in aliases Fix distcheck error Update the version info Update to detect the uncommited changes properly Fix a build issue Fix a build fail on some environment Fix a build fail on some environment. Get rid of $< from Makefile.am Alan Coopersmith (1): Fix compiler warnings Behdad Esfahbod (54): [fc-cache] Document -r argument in man page [doc] Fix typo Bug 25508 configure assumes bash > 2.0 is on system Update INSTALL Add note about autogen.sh to INSTALL Fix doc typo More doc typo fixes Bug 18886 installation crashes if fontconfig already installed Bug 26157 Solaris/Sun C 5.8: compilation of 2.8.0 and 2.7.3 fails Bug 25152 Don't sleep(2) if all caches were uptodate Don't include unistd.h in fontconfig.h Accept TT_PLATFORM_MICROSOFT, TT_MS_ID_SYMBOL_CS from name table Whitespace More whitespace Remove all training whitespaces Fix comment Add fc-pattern cmdline tool Bug 29338 - fc-pattern.sgml, open para tag Add comments Bug 29995 - fc-cat does not invoke FcFini() Add new public API: FcCharSetDelChar() [fc-lang] Support excluding characters Bug 24729 - [ne_NP] Fix ortho file Add more copyright owners Cleanup copyright notices to replace "Keith Packard" with "the author(s)" Fix returned value Bug 28958 - lang=en matches other langs Make most generated-files cross-compiling-safe Make fc-arch stuff cross-compiling-safe Bump version Allow editing charset and lang in target="scan" Add <range> support for <blank> into the DTD Skip <range> elements with begin > end Doc nit Fix assertion failure on le32d4 Remove AM_MAINTAINER_MODE Update CaseFolding.txt to Unicode 6.0 Remove --enable-maintainer-mode from autogen.sh Bug 20113 - Uighur (ug) orthography incomplete Bug 30566 - fcformat.c:interpret_enumerate() passes uninitialized idx to FcPatternGetLangSet() Mark constant strings as constant More doc typo fixes Always define FcStat as a function Fix warning Bug 35587 - Add padding to make valgrind and glibc not hate each other [.gitignore] Update Bug 36577 - Updating cache with no-bitmaps disables bitmap fonts... Bug 26718 - "fc-match sans file" doesn't work Switch fc-match to use FcPatternFormat() Switch fc-cat to use FcPatternFormat() Fix stupid bug in FcFontSort() Bug 41171 - Invalid use of memset Fix parallel build Add FcPublic to FcLangSetUnion and FcLangSetSubtract Brad Hards (1): Documentation fixes Jeremy Huddleston (2): fontconfig.pc: Add variables for confdir and cachedir fontconfig.pc.in: Add sysconfdir, localstatedir, and PACKAGE Jinkyu Yi (1): Bug 42423 - make default Korean font from Un to Nanum MINAMI Hirokazu (1): Bug 43406 - typo of Japanese font name in conf.d/65-nonlatin.conf Mike Frysinger (9): FcStrPlus: optimize a little delete unused variables FcStat: change to FcChar8 for first arg fc-cat: fix pointer warning FcName{,Get}Constant: constify string input fc-{list,match}: constify format string fix build warnings when using --with-arch FcObjectValidType: tweak -1 checking makealias: handle missing funcs better Parag Nemade (2): Bug 25651 - Add ortho file for locale brx_IN Bug 25650 - Add ortho file for locale sat_IN Pravin Satpute (4): Bug 27195 - need updates to ks.orth file Bug 43321 - Required corrections in urdu.orth file Bug 25653 - Add ortho file for locale doi_IN Bug 25652 - Add ortho file for locale mni_IN 2.8 Behdad Esfahbod (24): Clarify default confdir and cachedir better. Move FcAlign to fcint.h [fc-arch] Add FcAlign to arch signature [int] Define MIN/MAX/ABS macros Bump cache version up from 2 to 3 and fix FcLangSet caching/crash Remove unused macros [int] Remove fc_storage_type() in favor of direct access to v->type [int] Remove fc_value_* macros that did nothing other than renaming Enable automake silent rules [int] Remove more unused macros [xml] Remove unused code [arch] Try to ensure proper FcLangSet alignment in arch [lang] Fix serializing LangSet from older versions Make sure fclang.h and fcarch.h are built Remove bogus comment [fc-glyphname] Cleanup Makefile.am [src] Create fcglyphname.h automatically [fc-glyphname] Rename internal arrays to prefix with _fc_ Clean up Makefile's a bit [fc-glyphname] Remove Adobe glyphlist [fc-case] Update CaseFolding.txt to Unicode 5.2.0 [fc-arch] Beautify the arch template [fc-arch] Rename architecture names to better reflect what they are Bump libtool revision in preparation for release 2.7.3 Behdad Esfahbod (2): Use default config in FcFileScan() and FcDirScan() Bump libtool version in preparation for release Roozbeh Pournader (2): Correct Ewe (ee) orthography to use U+025B (bug #20711) Updated Arabic, Persian, and Urdu orthographies 2.7.2 Behdad Esfahbod (6): Improve charset printing [ja.orth] Comment out FULLWIDTH YEN SIGN (#22942) Bug 22037 - No Fonts installed on a default install on Windows Server 2003 Bug 23419 - "contains" expression seems not working on the fontconfig rule Revert "Fix FcNameUnparseLangSet()" and redo it Bump libtool version for release Tor Lillqvist (3): Fix MinGW compilation Fix heap corruption on Windows in FcEndElement() Use multi-byte codepage aware string function on Windows 2.7.1 Behdad Esfahbod (16): git-tag -s again Fix win32 build Replace spaces with tabs in conf files Remove unused ftglue code Add Inconsolata to monospace config (#22710) Fix leak with string VStack objects Improve libtool version parsing (#22122) Use GetSystemWindowsDirectory() instead of GetWindowsDirectory() (#22037) Remove unused macros Fix FcNameUnparseLangSet() Fix doc syntax (#22902) TT_MS_ID_UCS_4 is really UTF-16BE, not UTF-32 [doc] Add ~/fonts.conf.d to user docs Hardcode /etc/fonts instead of @CONFDIR@ in docs (#22911) Bump libtool versions that 2.7.0 (I forgot to do back then) Update .gitignore Karl Tomlinson (1): Don't change the order of names unnecessarily (#20128) 2.7 Alexey Khoroshilov (1): Use human-readable file names in the docs (bug #16278) Behdad Esfahbod (119): Avoid C99ism in Win32 code (#16651) [doc] Fix inaccuracy in FcFontRenderPrepare docs (#16985) When canonizing filenames, squash // and remove final / (#bug 16286) Add orth file for Maithili mai.orth (#15821) Replace RCS Id tags with the file name [doc] Fix signatures of FcPatternGetFTFace and FcPatternGetLangSet (#16272) Update Thai default families (#16223) Add ~/.fonts.conf.d to default config (#17100) [fc-match] Fix list of getopt options in --help Update man pages Add fc-query (#13019) Implement fc-list --verbose (#13015) [doc] Add const decorator for FcPatternDuplicate() Add FcPatternFilter() (#13016) [doc] Document that a zero rescanInterval disables automatic checks (#17103) Get rid of $Id$ tags [doc] Fix signature of FcConfigHome() Fix docs re 'orig' argument of FcPatternBuild and family Update sr.orth to actul subset of Cyrillic used by Serbian (#17208) Add Sindhi .orth file. (#17140) Add WenQuanYi fonts to default conf (#17262, from Mandriva) Handle -h and --help according to GNU Coding Standards (#17104) Document when config can be NULL (#17105) Add FcConfigReference() (#17124) Document how to free return value of FcNameUnparse() Don't leak FcValues string loaded through fcxml.c (#17661) Don't call FcPatternGetCharSet in FcSortWalk unless we need to (#17361) Fix two more doc typos [.gitignore] Update Cleanup symlinks in "make uninstall" (bug #18885) [fccache] Consistently use FcStat() over stat() (bug #18195) Consistently use FcStat() over stat() in all places Use __builtin_popcount() when available (bug #17592) Fix compile with old FreeType that doesn't have FT_Select_Size() (bug #17498) Implement fc-list --quiet ala grep (bug #17141) [65-fonts-persian.conf] Set foundry in target=scan instead of target=font Don't use identifier named complex Explicitly chmod() directories (bug #18934) Remove special-casing of FC_FILE in FcPatternPrint() [.gitignore] Update Implement FcPatternFormat and use it in cmdline tools (bug #17107) Fix comparison of family names to ignore leading space properly [fcmatch.c] Fix debug formatting [fcmatch] Use larger multipliers to enforce order [fcmatch] When matching, reserve score 0 for when elements don't exist [fcmatch] Move FcFontSetMatch() functionality into FcFontSetMatchInternal() [doc] Note that fontset returned by FcConfigGetFonts should not be modified Make FcCharSetMerge() public Don't use FcCharSetCopy in FcCharSetMerge Oops. Fix usage output. Revive FcConfigScan() (bug #17121) Add fc-scan too that runs FcFileScan/FcDirScan Oops, fix FcPatternFilter [fc-match] Accept list of elements like fc-list (bug #13017) Cleanup all manpage.* files [fcmatch] Fix crash when no fonts are available. [fcfreetype] Fix typo in GB2312 encoding name string (#19845) Add ICONV_LIBS to fontconfig.pc.in (#19606) [win32] Fix usage of GetFullPathName() [win32] Expand "APPSHAREFONTDIR" to ../share/fonts relative to binary location [win32] Do not remove leading '\\' such that network paths work [fccache] Make sure the cache is current when reusing from open caches Update Sinhala orthography (#19288) [cache] After writing cache to file, update the internal copy to reflect this Further update Sinhala orthography (#19288) [fcformat] Add support for width modifiers [fcformat] Refactor and restructure code for upcoming changes [fcformat] Add support for subexpressions [fcformat] Add element filtering and deletion [fcformat] Add conditionals [fcformat] Add simple converters [fcformat] Implement 'cescape', 'shescape', and 'xmlescape' converters [FcStrBuf] better handle malloc failure [fcformat] Add value-count syntax [fcformat] Implement 'delete', 'escape', and 'translate' filter functions [fcformat] Start adding builtins [fcformat] Refactor code to avoid malloc [fcformat] Add support for builtin formats [fcformat] Support indexing simple tags [fcformat] Support 'default value' for simple tags [fcformat] Implement array enumeration [fclang] Implement FcLangSetGetLangs() (#18846) [fcformat] Enumerate langsets like we do arrays of values [fcformat] Add a 'pkgkit' builtin that prints tags for font packages [fcformat] Add list of undocumented language features [fc-lang] Continue parsing after an "include" (#20179) Fix Fanti (fat) orth file (#20390) Fix Makefile's to not create target file in case of failure [fcstr.c] Embed a static 64-byte buffer in FcStrBuf [fcstr,fcxml] Don't copy FcStrBuf contents when we would free it soon [fcxml] Don't allocate attr array if there are no attributes [fcxml] Embed 8 static FcPStack objects in FcConfigParse [fcxml] Embed 64 static FcVStack objects in FcConfigParse [fcxml.c] Embed a static 64-byte attr buffer in FcPStack Call git tools using "git cmd" instead of "git-cmd" syntax Replace 'KEITH PACKARD' with 'THE AUTHOR(S)' in license text in all files [fcformat] Fix default-value handling Document FcPatternFormat() format [Makefile.am] Don't clean ChangeLog in distclean Revert "[conf] Disable hinting when emboldening (#19904)" (#20599) [fc-lang] Fix bug in country map generation [fcstr] Remove unused variable [fc-lang] Make LangSet representation in the cache files stable [fc-cache] Remove obsolete sentence from man page Detect TrueType Collections by checking the font data header Mark matchers array const (#21935) Use/prefer WWS family/style (name table id 21/22) Simplify FcValueSave() semantics Add XXX note about Unicode Plane 16 Always set *changed in FcCharsetMerge [charset] Grow internal FcCharset arrays exponentially Remove unused prototypes and function [xml] Centralize FcExpr allocation [xml] Mark more symbols static [xml] Allocate FcExpr's in a pool in FcConfig [xml] Intern more strings Bug 22154 -- fontconfig.pc doesn't include libxml2 link flags Fix distcheck Remove keithp's GPG key id Benjamin Close (1): Remove build manpage logfile if it exists Chris Wilson (1): Reduce number of allocations during FcSortWalk(). Dan Nicholson (1): Let make expand fc_cachedir/FC_CACHEDIR (bug #18675) Harald Fernengel (1): Don't use variables named 'bool' (bug #18851) Harshula Jayasuriya (1): Fix Sinhala coverage (bug #19288) Karl Tomlinson (1): Change FcCharSetMerge API Mike FABIAN (1): [conf] Disable hinting when emboldening (#19904) Peter (1): Make sure alias files are built first (bug 16464) Rahul Bhalerao (1): Add config for new Indic fonts (bug #17856) Roozbeh Pournader (60): Correct Sindhi orthography to use Arabic script (bug #17140) Remove Sinhala characters not in modern use (bug #19288) Add Filipino orth, alias Tagalog to Filipino (bug #19846) Split Mongolian orth to Mongolia and China (bug #19847) Fix doubly encoded UTF-8 in comments (bug #19848) Change Turkmen orth from Cyrillic to Latin (bug #19849) Rename Venda from "ven" to "ve" (bug #19852) Rename "ku" to "ku_am", add "ku_iq" (bug #19853). Add Kashubian (csb) orth file (bug #19866) Add Malay (ms) orthography (bug #19867) Add Kinyarwanda (rw) orthography (bug #19868) Add Upper Sorbian (hsb) orthography (bug #19870) Add Berber orthographies in Latin and Tifinagh scripts (bug #19881) Renamed az to az_az (bug #19889) Rename Igbo from "ibo" to "ig" (bug #19892) Remove punctuation symbols from Asturian orthography (bug #19893) Add Chhattisgarhi (hne) orthography (bug #19891) Use newly added Cyrillic letters for Kurdish (bug #20049) Add Kurdish in Turkey (ku_tr) orthography (bug #19891) Add Aragonese (an) orthography (bug #19891) Add Haitian Creole (ht) orthography (bug #19891) Ad Ganda (lg) orthography (bug #19891) Add Limburgan (li) orthography (bug #19891) Add Sardinian (sc) orthography (bug #19891) Add Sidamo (sid) and Wolaitta (wal) orthographies (bug #19891) Fix Bengali (bn) and Assamese (as) orthographies (bug #22924) Remove Euro Sign from all orthographies (bug #19865) Add Ottoman Turkish (ota) orthography (bug #20114) Divide Panjabi (pa) to that of Pakistan and India (bug #19890) Add Blin (byn) orthography (bug #19891) Add Papiamento (pap_aw, pap_an) orthographies (bug #19891) Add Crimean Tatar (crh) orthography (bug #19891) Switch Uzbek (uz) orthography to Latin (bug #19851) Update Azerbaijani in Latin (az_az) to present usage (bug #20173) Rename Avaric orthography from 'ava' to 'av' (bug #20174) Rename Bambara orthography from 'bam' to 'bm' (bug #20175) Rename Fulah orthography from 'ful' to 'ff' (bug #20177) Change Kashmiri (ks) orthography to Arabic script (bug #20200) Tighten Central Khmer (km) orthography (bug #20202) Remove digits and symbols from some Indic orthographies (bug #20204) Add Divehi (dv) orthography (bug #20207) Extend Crimean Tatar (crh) orthography (bug #19891) Update Serbo-Croatian (sh) orthography (bug #20368) Add Ewe (ee) orthography (bug #20386) Add Herero (hz) orthograhy (bug #20387) Add Akan (ak) and Fanti (fat) orthographies (bug #20390) Added Quechua (qu) orthography (bug #20392) Add Sango (sg) orthography (bug #20393) Add Tahitian (ty) orthography (bug #20391) Add Navajo (nv) orthography (bug #20395) Add Rundi (rn) orthography (bug #20398) Add Zhuang (za) orthography (bug #20399) Add orthographies for Oshiwambo languages (bug #20401) Add Shona (sn) orthography (bug #20394) Add Sichuan Yi (ii) orthography (bug #20402) Add Javanese (jv) orthography (bug #20403) Add Nauru (na) orthography (bug #20418) Add Kanuri (kr) orthography (bug #20438) Add Sundanese (su) orthography (bug #20440) Reorganize Panjabi/Punjabi and Lahnda orthographies (bug #19890) Serge van den Boom (1): Correctly handle mmap() failure (#21062) 2.6 2.5.93 (2.6 RC3) Alexey Khoroshilov (1): Fix FcStrDirname documentation. (bug 16068) Behdad Esfahbod (1): Persian conf update. (bug 16066). Evgeniy Stepanov (1): Fix index/offset for 'decorative' matcher. Bug 15890. Glen Low (1): Fix Win32 build error: install tries to run fc-cache locally (bug 15928). Keith Packard (8): Call FcFini to make memory debugging easier Fix a few memory tracking mistakes. Add extended, caps, dunhill style mappings. Freetype 2.3.5 (2007-jul-02) fixes indic font hinting. re-enable (bug 15822) Add a copy of dolt.m4 to acinclude.m4. Libs.private needs freetype libraries Oops. Fix for bug 15928 used wrong path for installed fc-cache. Ignore empty <dir></dir> elements Neskie Manuel (1): Add Secwepemctsin Orthography. Bug 15996. Sayamindu Dasgupta (1): FcConfigUptoDate breaks if directory mtime is in the future. Bug 14424. 2.5.92 (2.6 RC2) Carlo Bramini (1): Add FreeType-dependent functions to fontconfig.def file. (bug 15415) Changwoo Ryu (1): Korean font in the default config - replacing baekmuk with un (bug 13569) Dennis Schridde (1): Proper config path for static libraries in win32 Eric Anholt (1): Fix build with !ENABLE_DOCS and no built manpages. Frederic Crozat (1): Merge some of Mandriva configuration into upstream configuration. Bug 13247 Keith Packard (11): Use DOLT if available Work around for bitmap-only TrueType fonts that are missing the glyf table. Remove size and dpi values from bitmap fonts. Bug 8765. Add some sample cursive and fantasy families. Add --all flag to fc-match to show the untrimmed list. Bug 13018. Remove doltcompile in distclean Use of ":=" in src/Makefile.am is unportable (bug 14420) Make fc-match behave better when style is unknown (bug 15332) Deal with libtool 2.2 which doesn't let us use LT_ variables. (bug 15692) Allow for RC versions in README update git ignore doltcompile Ryan Schmidt (1): fontconfig build fails if "head" is missing or unusable (bug 14304) Sylvain Pasche (1): Fontconfig options for freetype sub-pixel filter configuration 2.5.91 (2.6 RC1) Hongbo Zhao (1): Not_contain should use strstr, not strcmp on strings. (bug 13632) Keith Packard (11): Move conf.avail/README to conf.d/README (bug 13392) Fix OOM failure case in FcPStackPush. Remove freetype requirement for build-time applications. Include fcftaliastail.h so that the freetype funcs are exported. Eliminate references to freetype from utility Makefile.am's Distribute new fcftint.h file Create new-version.sh to help with releases, update INSTALL instructions Distribute khmer font aliases Add more files to .gitignore new-version.sh was mis-editing files git-tag requires space after -m flag 2.5 Keith Packard (4): Document several function return values (Bug 13145). Document that Match calls FcFontRenderPrepare (bug 13162). Document that FcConfigGetFonts returns the internal fontset (bug 13197) Revert "Remove fcprivate.h, move the remaining macros to fcint.h." Tor Lillqvist (1): Workaround for stat() brokenness in Microsoft's C library (bug 8526) 2.4.92 (2.5 RC2) Behdad Esfahbod (14): Make fc-match --sort call FcFontRenderPrepare. Port fonts-persian.conf to new alias syntax with binding="same" Fix trivial bugs in edit-sgml.c Add FcGetLangs() and FcLangGetCharSet(). Add/update config files from Fedora. Split 40-generic.conf into 40-nonlatin.conf and 45-latin.conf Use binding="same" in 30-urw-aliases.conf and remove duplicate entries. Remove redundant/obsolete comments from conf files. Remove 20-lohit-gujarati.conf. It's covered by 25-unhint-nonlatin.conf now. Oops, fix Makefile.am. Remove 25-unhint-nonlatin.conf from default configuration by not linking it. Fix documented conf-file naming format in README Remove list of available conf files from README. Simplify/improve 30-metric-aliases.conf Keith Packard (25): Also check configDirs mtimes in FcConfigUptoDate Respect "binding" attribute in <alias> entries. Correct documentation for FcAtomicLock (Bug 12947). Remove fcprivate.h, move the remaining macros to fcint.h. Correct documentation for FcConfigUptoDate (bug 12948). Document skipping of fonts from FcFileScan/FcDirScan. Make file_stat argument to FcDirCacheLoadFile optional. Clean up exported names in fontconfig.h. Track line numbers in sgml edit tool input. Typo error in function name: Inverval -> interval Don't check cache file time stamps when cleaning cache dir. Use FcLangDifferentTerritory instead of FcLangDifferentCountry. Verify documentation covers exposed symbols. Document previously undocumented functions. (bug 12963) Update documentation for FcStrCopyFilename (bug 12964). Update documentation for stale FcConfigGetConfig function. Have FcConfigSetCurrent accept the current configuration and simply return Remove references to FcConfigParse and FcConfigLoad. Replace incorrect documentation uses of 'char' with 'FcChar8' (bug 13002). Fix formatting syntax in doc/fccache.fncs Generate fccache.sgml, fcdircache.sgml and fclangset.sgml. Formatting syntax mistake in doc/fclangset.fncs. Link new function documentation into the fontconfig-devel.sgml Ignore new generated documentation Export FcConfig{G,S}etRescanInverval from .so, mark as deprecated. 2.4.91 (2.5 RC1) Behdad Esfahbod (1): Update CaseFolding.txt to Unicode 5.1.0 Dwayne Bailey (1): Add/fix *.orth files for South African languages Hideki Yamane (1): Handle Japanese fonts better. (debian bug #435971) Keith Packard (32): rehash increment could be zero, causing rehash infinite loop. Work around FreeType bug when glyph name buffer is too small. Free temporary string in FcDirCacheUnlink (Bug #11758) Fix ChangeLog generation to avoid circular make dependency Store font directory mtime in cache file. Comment about mmaping cache files was misleading. Make FC_FULLNAME include all fullname entries, elide nothing. [bug 12827] Remove unneeded call to access(2) in fc-cache. Improve verbose messages from fc-cache. Verbose message about cleaning directories was imprecise Don't use X_OK bit when checking for writable directories (bug 12438) Have fc-cache remove invalid cache files from cache directories. FcConfigParseAndLoad doc was missing the last param. Place language name in constant array instead of pointer. Must not insert cache into hash table before completely validating. Eliminate relocations for glyph name table. Eliminate relocations from FcCodePageRange structure (bug 10982). Leave generated headers out of distribution (bug 12734). Move <cachedir> elements to the end of fonts.conf. Add BRAILLE PATTERN BLANK to list of blank glyphs. Replace makealias pattern with something supported by POSIX grep (bug 11083) FcInit should return FcFalse when FcInitLoadConfigAndFonts fails. (bug 10976) There is no U+1257 (bug 10899). Spelling errors in documentation. (bug 10879). Oops. Left debugging printf in previous commit. Handle UltraBlack weight. Fix parallel build in fontconfig/docs (bug 10481). Distribute man source files for command line programs (bug 9678). Ensure weight/slant values present even when style is supplied (bug 9313). fontconfig needs configure option to use gnu iconv (bug 4083). Match 'ultra' on word boundaries to detect ultra bold fonts. (bug 2511) Build fix for Solaris 10 with GCC. Mike FABIAN (1): Avoid crashes if config files contain junk. Stephan Kulow (1): Make FcPatternDuplicate copy the binding instead of always using Strong. Tilman Sauerbeck (2): Store FcNoticeFoundries in read-only memory. Store FcVendorFoundries in read-only memory. 2.4.2 Han-Wen Nienhuys: FcStrCanonFileName buggy for mingw. (bug 8311) More fixes for Win32 building (bug 8311) Kean Johnston: Don't use varargs CPP macros in fccache.c. (bug 8733) Keith Packard: Remove documentation for non-existant FcConfigNormalizeFontDir. Build fontconfig.def from header files when needed. Detect and use available random number generator (bug 8308) Add sparc64 architecture string. FcStrCanonAbsoluteFilename should be static. Use explicit platform/nameid order when scanning ttf files. Warn (and recover) from config file without <cachedir> elements. Avoid writing uninitialized structure pad bytes to cache files. Fix grep pattern in makealias to work on non-Gnu grep (bug 8368). Add FcFreeTypeQueryFace external API. Bug #7311. Segfault scanning non-font files. Disallow scan edit of user vars. (#8767) Add space between type and formal in devel man pages (bug 8935) Mike FABIAN: Do not clean cache files for different architectures Peter Breitenlohner: A VPATH build of fontconfig-2.4.1 fails for various reasons. Bug 8933. Use <literal> instead of <sgmltag> when documenting fonts.conf. Bug 8935. Fix fc-cat documentation (bug 8935). 2.4.1 Keith Packard: Update installation notes for 2.4 base. Add ppc64 signature. Bug 8227 Add signatures for m68k and mipsel (thanks debian buildd) Add warning flags to fc-cache build. Clean up warnings in fc-cache. Reimplement FcConfigAppFontAddDir; function was lost in 2.4.0. 2.4.0 David Turner: Replace character discovery loop with simpler, faster version. James Cloos: Move files from conf.d to conf.avail Standardize conf.avail number prefixing convention Support all five possibilities for sub-pixel Move user and local conf file loading into conf.avail files Number the remaining conf.avail files Update Makefile.am to match conf.avail changes Replace load of conf.d in fonts.conf.in Make room for chunks from fonts.conf in conf.avail Re-order old conf.d files Move some section from fonts.conf into conf.avail files Update Makefile.am files Make conf.avail and conf.d work Keith Packard: Create fc_cachedir at install time. Bug 8157. Reference patterns in FcCacheCopySet. Replace gnu-specific sed command with simple grep. Attempt to fix makealias usage for build on Mac OS X. Accept locale environment variables that do not contain territory. Merge branch 'jhcloos' Insert newly created caches into reference data structure. Add XML headers to new conf files. Move link make commands to conf.avail dir Rename conf.avail to conf.d Fix conf.d directory sorting. Include cachedir in fonts.dtd. Don't display tests for DESTDIR on make install. Split much of the configuration into separate files. Renumber files 2.3.97 Carl Worth: Rename FcPatternThawAll to FcPatternFini. Add a configuration file that disables hinting for the Lohit Gujarati font Keith Packard: Various GCC 4 cleanups for signed vs unsigned char Finish INSTALL changes. .gitignore ChangeLog Merge branch 'fc-2_4_branch' to master Remove all .cvsignore files Hide private functions in shared library. Export functionality for utilities. Hide FreeType glue code from library ABI. Can't typecheck values for objects with no known type. Leave cache files mapped permanently. Reference count cache objects. Make cache reference counting more efficient. Oops, fc-lang broke when I added cache referencing. Correct reference count when sharing cache file objects. Eliminate .so PLT entries for local symbols. (thanks to Arjan van de Ven) Update architecture signatures for x86-64 and ppc. Parallel build fix for fcalias.h and fcaliastail.h Charset hashing depended on uniqueness of leaves. Patrick Lam: file Makefile.am was initially added on branch fc-2_4_branch. Modify config file to use Greek fonts before Asian fonts with Greek glyphs. Use libtool -no-undefined flag on all platforms. file ftglue.c was initially added on branch fc-2_4_branch. 2005-11-23 Frederic Crozat <fcrozat@mandriva.com>: reviewed by: plam file 10-fonts-persian.conf was initially added on branch fc-2_4_branch. Sort directory entries while scanning them from disk; prevents Heisenbugs file ln.orth was initially added on branch fc-2_4_branch. Fix typos in orth files. Reported by Denis Jacquerye. On Windows, unlink before rename. Reported by Tim Evans. file fc-match.sgml was initially added on branch fc-2_4_branch. 2.3.96 Keith Packard: Make path names in cache files absolute (NB, cache format change) Stop Eliminate pattern freezing Add .gitignore Construct short architecture name from architecture signature. Write caches to first directory with permission. Valid cache in FcDirCacheOpen. Eliminate NormalizeDir. Eliminate gratuitous stat/access calls per dir. Add architecture to cache filename. Eliminate global cache. Eliminate multi-arch cache code. Fix up fc-cache and fc-cat for no global cache changes. Eliminate ./ and ../ elements from font directory names when scanning. Regenerate x86 line in fcarch.tmpl.h to match change in cache data. Add x86-64 architecture and signature. During test run, remove cache directory to avoid stale cache usage. Add ppc architecture Revert to original FcFontSetMatch algorithm to avoid losing fonts. Rework cache files to use offsets for all data structures. Fix build problems caused by cache rework. FcCharSetSerialize was using wrong offset for leaves. Make fc-cat work. Rework Object name database to unify typechecking and object lookup. Skip broken caches. Cache files are auto-written, don't rewrite in fc-cache. Fix fc-cat again. Sigh. Use intptr_t instead of off_t inside FcCache structure. Serialized value lists were only including one value. Automatically remove invalid cache files. With no args, fc-cat now dumps all directories. Revert ABI changes from version 2.3 Change $(pkgcachedir) to $(fc_cachedir) in fc-cat and fc-cache Makefile.am Allow FcTypeLangSet to match either FcTypeLangSet or FcTypeString. Remove stale architecture signatures. Pass directory information around in FcCache structure. Freeze charsets. Fix fc-lang to use new charset freezer API. Fontset pattern references are relative to fontset, not array. Add some ignores Only rebuild caches for system fonts at make install time. Fix memory leaks in fc-cache directory cleaning code. Add @EXPAT_LIBS@ to Libs.private in fontconfig.pc (bug 7683) Avoid #warning directives on non-GCC compilers. (bug 7683) Chinese/Macau needs the Hong Kong orthography instead of Taiwan (bug 7884) Add Assamese orthography (as.orth). Bug #8050 Really only rebuild caches for system fonts at make install time. Fonts matching lang not territory should satisfy sort pattern lang. Prefer Bitstream Vera to DejaVu families. Guess that mac roman names with lots of high bits are actually SJIS. Document FC_DEBUG values (bug 6393). Document name \ escape syntax. Move Free family names to bottom of respective aliases. (bug 7429) Unify directory canonicalization into FcStrAddFilename. Allow font caches to contain newer version numbers Add FcMatchScan to resolve Delicious font matching issues (bug #6769) Fix missing initialization/destruction of new 'scan' target subst list. Don't segfault when string values can't be parsed as charsets or langsets. Using uninitialized (and wrong) variable in FcStrCopyFilename. Oops; missed the 60-delicious.conf file. Patrick Lam: Keith Packard <keithp@keithp.com> 2006-04-27 Paolo Borelli (pborelli@katamail.com) reviewed by: plam 2006-05-31 Yong Li (rigel863@gmail.com) reviewed by: plam, Bedhad Esfahbod 2006-07-19 Jon Burgess (jburgess@uklinux.net) reviewed by: plam 2006-08-04 Keith Packard (keithp@keithp.com) reviewed by: plam 2.3.95 Match 'Standard Symbols L' for 'Symbol'. Add URW fonts as aliases for all of the PostScript fonts. (reported by Miguel Rodriguez). Fix a number of Coverity defects (Frederic Crozat). Speed up FcFontSort (fix suggested by Kenichi Handa). Fix error with charsets. Survive missing docbook2pdf. Compile on HP-UX, AIX, SGI and Windows (Cygwin, MinGW). Fix intel compiler warnings. Fix multiarch support (don't destroy multiarch files!) Require pkg-config. (Thanks Behdad; better solution wanted for libxml2 detection!) Fix typos in orth files and add orth for Lingala (reported by Denis Jacquerye). Remove debian/ directory. Add a configuration file that disables hinting for the Lohit Gujarati font (since the hinting distorts some glyphs quite badly). Sort directory entries while scanning them from disk; prevents Heisenbugs due to file ordering in a directory (due to Egmont Koblinger). Fix Wine's problem with finding fonts. (Reported by Bernhard Rosenkraenzer.) Fix the issues with GNU libiconv vs. libc iconv (which especially appear on Solarii); patch by Behdad Esfahbod, approach suggested by Tim Mooney. 2.3.94 fc-cat can take directories as input and creates old-style fonts.cache listings. fc-cache takes -r --really-force which blows away all old caches and regenerates. Robustness fixes, integer overflow fixes (notably to cache handling code), toast broken global cache files. Change binary format to make it compatible with static langset information (thanks to Takashi Iwai). Open hashed caches before fonts.cache-2 (Takashi Iwai). Fix FcFontSetMatch's algorithm, which used to unjustly kill fonts for not declaring certain elements (Takashi Iwai). Fix matching bug when multiple elements match; don't use the sum of all scores, but the best score (James Su). Make fc-lang more friendly to Windows systems. Remove archaic chars from Georgian charset; add Euro character to charsets for European languages. Fix treatment of broken PCF fonts that don't declare family names. Pass O_BINARY to open if appropriate (reported by Doodle). Normalize font directories to the form in which they appear in config files. Add a record of the cached directory to the cache file. Perf optimizations (Dirk Mueller; some reported by Michael Meeks.) Don't loop infinitely on recursive symlinks. Make 'make distcheck' work with automake 1.6.3. Replace 'stamp' target with mkinstalldirs. Don't stop scanning if a directory in fonts.conf doesn't exist, because subsequent directories might exist. Put directory names into global cache (reported by Ronny V. Vindenes). Treat zh-hk fonts differently from zh-tw fonts. This patch may cause fontconfig to treat A-X fonts differently from A-Y fonts; please mail the fontconfig list if this causes any problems. Fix for unaligned memory accesses (Andreas Schwab). Fix treatment of cache directory as read from cache file; don't use string equality to determine if we have the right file, use inode equality. Properly skip past dir caches that contain zero fonts, as occurs in global caches (reported by Mike Fabian). Print out full pathname in fc-match -v (reported by Frederic Crozat). Fix bug where fc-match crashes when given __DUMMY__ property to match on. 2.3.93 Create cache files in /var/cache/fontconfig with hashed filenames, if possible, for added FHS compliance. Make fc-cat read both per-directory and global cache files. Add config file for Persian fonts from Sharif FarsiWeb, Inc. Major performance improvements by Dirk Mueller, Stephen Kulow, and Michael Matz at SuSE: in particular, speed up FcFontSetMatch, and inline many functions. Fix treatment of globs in config files, broken since 2.3.2 and discovered by Mathias Clasen. Don't use freetype internal headers (patch by Matthias Clasen). Further space improvements: create langsets statically, so that they can live in .rodata. Properly align mmapped data structures to make e.g. ia64 happy. Bug fixes. 2.3.92 Fix corrupted caches bugs from 2.3.91 (reported by Mike Fabian). Store only basename in the cache, reconstitute on demand (reported by James Cloos). Change the rule for artificial emboldening in fonts.conf.in. This enables the support for artificial emboldening included in cairo (patch by Zhe Su). Add FC_EMBEDDED_BITMAP object type to tell Xft/Cairo whether to load embedded bitmaps or not (patch by Jinghua Luo). Fix GCC4 warnings (some by Behdad Esfahbod). Support localized font family and style names; this has been reported to break old apps like xfd, but modern (gtk+/qt/mozilla) apps work fine (patch by Zhe Su). Prevent fc-list from escaping strings when printing them (reported by Matthias Clasen). Add valist sentinel markup for FcObjectSetBuild and FcPatternBuild (patch by Marcus Meissner). Add consts to variables so as to move arrays into .rodata (patch by Ross Burton). Modify config file to use Greek fonts before Asian fonts with Greek glyphs. (patch by Simos Xenitellis). Use libtool -no-undefined flag on all platforms (patch by Christian Biesinger). 2.3.91 Use libxml2 if requested or if expat not available. (Mathias Hasselmann) Fix multi-arch cache files: compute the position for the block to be added using info from OrigFile, not NewFile. (plam) Cast results of sizeof() to unsigned int to get rid of warnings on x86_64 (reported by Matthias Clasen). Use FcAtomic to rewrite cache files; don't unlink the fonts.cache-2 file even if there's no data to write; just write an empty cache file. (Reported by Lubos Lunak) Allocate room for the subdirectory names in each directory cache. (Reported by James Cloos) 2.3.90 Development release of mmap patch: load pattern information directly from cache files. (Patrick Lam) 2.3.2 Patch memory leaks in using iconv. (Reported by Chris Capoccia) Patch memory leaks in fc-cache. (Reported by Chris Capoccia) Fetch bitmap glyphs to get widths during font evaluation. (keithp) Share strings through FcObjectStaticName (Ross Burton) Windows build updates (Tor Lillqvist) 2.3.1 Be more careful about broken GSUB/GPOS tables (Manish Singh) Include debian packaging stuff in CVS (Josselin Mouette) Add more conf.d examples (Keith Packard) Make manuals build again (Keith Packard) Johap -> Johab (Funda Wang) 2.3.0 Fix memory leak of patterns rejected by configuration (#2518) Create prototype /etc/fonts/conf.d directory and populate it with a few sample files. These samples are unused as the file names don't start with numbers. Update documentation. 2.2.99 Verify cache for FC_FILE and FC_FAMILY in every entry (#2219) Update blanks list from recent Unicode docs (#86) Various small build fixes (#280, #2278, Documentation fixes (#2085, #2284, #2285) Add polite typechecking to config file loader (#229) 2.2.98 Share object name strings (Michael Meeks) Eliminate a couple of codepoints from Russian orthography (John Thacker) Add synthetic emboldening configuration changes (Jakub Pavelek) Change FcFontSetSort to ignore language after fonts with the requested languages have been found. (Owen Taylor) Add some RedHat font configuration changes (Owen Tayler). Add full Unicode case folding support to case-ignoring string functions (Keith Packard) Remove Han characters from Korean orthography (Tor Andersson) 2.2.97 Fc-cache sleeps before exiting to ensure filesystem timestamps are well ordered. Added Punjai orthography. The timestamp in fonts.conf is gone now. Too many problems. The default font path includes all of the X fonts; use selectfont/rejectfont to eliminate bitmaps, as shown in the sample local.conf file. <include> configuration elements may now reference a directory. Files in that directory matching [0-9]* are loaded in UTF-8 collating sequence order. <selectfont> configuration added to control which fonts are used. fontformat font pattern elements built from the FT_Get_X11_Font_Format function in newer versions of FreeType. 'capability' list constructed from gsub/gpos and silf values in TrueType files. Multi-lingual names (style, family, fullname) extracted and stored with parallel <foo>lang properties marking language. 2.2.96 Fix FcConfigUpToDate to actually check all font directories and eliminate a typo which completely prevented it from working (Lubos Lunak <l.lunak@suse.cz>) Remove comma at end of FcResult enum definition for picky compilers. 2.2.95 Add FcResultOutOfMemory so FcFontSetMatch can return accurate error. Replace MIN/MAX/ABS macros which happened to be in old FreeType releases with FC_MIN/FC_MAX/FC_ABS macros owned by fontconfig. 2.2.94 The 2.2.93 release was prepared with a broken libtool which created the shared library without the '.so' in the file names. 2.2.93 This is the third prerelease of fontconfig 2.3. Significant changes from 2.2.92 are: o Use new FreeType #include syntax o use y_ppem field instead of 'height' in bitmap sizes rec - FreeType changed the semantics. Still uses height for older versions of FreeType o Don't construct program manuals unless docbook is available 2.2.92 o make distcheck work 2.2.91 o Switch to SGML manuals o Add FC_DUAL width spacing value o Add FcFini to close out fontconfig and release all memory 2.2 This is the third public release of fontconfig, a font configuration and customization library. Fontconfig is designed to locate fonts within the system and select them according to requirements specified by applications. Fontconfig is not a rasterization library, nor does it impose a particular rasterization library on the application. The X-specific library 'Xft' uses fontconfig along with freetype to specify and rasterize fonts. Keith Packard keithp@keithp.com usr/share/doc/fprintd-pam-0.8.1/README 0000644 00000002217 14721023071 0012766 0 ustar 00 PAM module for fingerprint authentication ----------------------------------------- Using: * Modify the appropriate PAM configuration file (/etc/pam.d/system-auth-ac on Fedora systems), and add the line: auth sufficient pam_fprintd.so before the line: auth sufficient pam_unix.so ... * You can now enroll fingerprints using fprintd-enroll. The first available fingerprint available will be used to log you in. Options: * You can add the "debug" option on the pam configuration file line above, this will log more information from PAM to the file specified in your syslog configuration (/var/log/secure by default on Fedora) Known issues: * pam_fprintd does not support identifying the user itself as that would mean having the fingerprint reader on for all the time the user selection is displayed, and could damage the hardware. It could be fixed by having gdm/login only start the PAM conversation when there is activity * pam_fprintd doesn't support entering either the password or a fingerprint, as pam_thinkfinger does, because it's a gross hack, and could be fixed by having the login managers run 2 separate PAM stacks etc/pki/ca-trust/extracted/pem/README 0000644 00000001602 14721023112 0013260 0 ustar 00 This directory /etc/pki/ca-trust/extracted/pem/ contains CA certificate bundle files which are automatically created based on the information found in the /usr/share/pki/ca-trust-source/ and /etc/pki/ca-trust/source/ directories. All files are in the BEGIN/END CERTIFICATE file format, as described in the x509(1) manual page. Distrust information cannot be represented in this file format, and distrusted certificates are missing from these files. If your application isn't able to load the PKCS#11 module p11-kit-trust.so, then you can use these files in your application to load a list of global root CA certificates. Please never manually edit the files stored in this directory, because your changes will be lost and the files automatically overwritten, each time the update-ca-trust command gets executed. Please refer to the update-ca-trust(8) manual page for additional information. usr/share/doc/libreport-2.1.11/README 0000644 00000000137 14721023145 0012624 0 ustar 00 Generic library for reporting various problems. Please see INSTALL for build and install steps. usr/share/doc/sysstat-10.1.5/README 0000644 00000010430 14721023503 0012331 0 ustar 00 sysstat: System performance tools for the Linux operating system... -- (C) 1999-2012 Sebastien GODARD (sysstat <at> orange.fr) The latest version of sysstat can always be found on my web site at: http://pagesperso-orange.fr/sebastien.godard/ sysstat package is also available at ibiblio's Linux archive in the following directory: ftp://ibiblio.org/pub/Linux/system/status/ See the CHANGES file to know the new features/improvements/bug fixes added in this release of sysstat. INSTALLATION ------------ The sysstat utilities are a collection of performance monitoring tools for Linux. These include mpstat, iostat, nfsiostat, cifsiostat, pidstat, sar, sadc, sadf and sa tools. The first stage is to configure sysstat for your system: ./configure You can set several variables and parameters on the command line. Please enter "./configure --help" to display them. There is another way to configure sysstat instead of entering "./configure": this is the Interactive Configuration script (iconfig) which will ask you for the value of the main sysstat variables and parameters. Enter "./iconfig" then answer the questions or enter Return to accept the (sane) default values. For yes/no questions, please answer 'y' or 'n' (without the quotes): It is case sensitive! You can also enter '?' to get a help message that will explain the meaning of each variable or parameter. The next stage is to build the various binary files. Enter: make Then log in as root and enter: make install (see next section to know the files that are installed). That's all! Of course tell me if there are any problems. This is the only way I can improve 'sysstat'. Please also remember to read the FAQ included in this package. Patches and suggestions for improvements are always welcome! Send them to (sysstat <at> orange.fr). FILES THAT ARE INSTALLED ------------------------ I _hate_ when packages install files everywhere on my disk and I don't know where... So here is the list of files installed by sysstat, when you ask for a complete installation. ${PREFIX} is the value of the PREFIX variable defined in the Makefile (usually set to /usr/local or /usr). ${PREFIX}/lib/sa/sadc ${PREFIX}/lib/sa/sa1 ${PREFIX}/lib/sa/sa2 ${PREFIX}/bin/sar ${PREFIX}/bin/sadf ${PREFIX}/bin/iostat ${PREFIX}/bin/mpstat ${PREFIX}/bin/pidstat ${PREFIX}/bin/nfsiostat ${PREFIX}/bin/cifsiostat ${PREFIX}(/share)/man/man8/sadc.8 ${PREFIX}(/share)/man/man8/sa1.8 ${PREFIX}(/share)/man/man8/sa2.8 ${PREFIX}(/share)/man/man1/sar.1 ${PREFIX}(/share)/man/man1/sadf.1 ${PREFIX}(/share)/man/man1/iostat.1 ${PREFIX}(/share)/man/man1/mpstat.1 ${PREFIX}(/share)/man/man1/pidstat.1 ${PREFIX}(/share)/man/man1/nfsiostat.1 ${PREFIX}(/share)/man/man1/cifsiostat.1 ${PREFIX}/share/locale/*/LC_MESSAGES/sysstat.mo ${PREFIX}/share/doc/sysstat-x.y.z/* /var/log/sa ${INIT_DIR}/sysstat /lib/systemd/system/sysstat.service if OS uses systemd /etc/sysconfig/sysstat /etc/sysconfig/sysstat.ioconf /etc/cron.d/sysstat /etc/rc.d/rc.sysstat for [SLACKWARE] ${RC_DIR}/rc2.d/S03sysstat ${RC_DIR}/rc3.d/S03sysstat ${RC_DIR}/rc5.d/S03sysstat with: ${INIT_DIR}=/etc/rc.d/init.d/ for [REDHAT] [CALDERA] [MANDRIVA] [TURBOLINUX] [KONDARA] ${INIT_DIR}=/sbin/init.d/ for [SUSE <= 7.0] ${INIT_DIR}=/etc/init.d/ for [SUSE >= 7.1] [DEBIAN] ${RC_DIR}=/etc/rc.d/ for [REDHAT] [CALDERA] [MANDRIVA] [TURBOLINUX] [KONDARA] [SLACKWARE] ${RC_DIR}=/sbin/init.d/ for [SUSE <= 7.0] ${RC_DIR}=/etc/init.d/ for [SUSE >= 7.1] ${RC_DIR}=/etc/ for [DEBIAN] sysstat may also install some links in ${RC_DIR}/rc[0146].d/ directory if chkconfig is used. MISCELLANEOUS ------------- The sysstat commands are only front-ends to the kernel proc filesystem... They cannot display statistics that Linux does not provide, nor can they be more accurate than Linux is. The sysstat package now only supports 2.6.x kernels. Note that all kernels do not necessarily have all the statistics that sysstat commands can display, depending on their version or their configuration options. It has been designed with National Language Support (NLS) in mind, using the GNU gettext package (available at http://www.gnu.org). sysstat has been translated into several languages. Anyway you are welcome if you want to make other translations available ;-) Please read the README-nls file in the nls directory before. -- Sebastien GODARD (sysstat <at> orange.fr) usr/share/doc/perl-Encode-Locale-1.03/README 0000644 00000000547 14721023511 0014017 0 ustar 00 Encode-Locale ============== The purpose of this Perl module is try determine what encodings should be used when interfacing to various external interfaces. You will need perl-5.8 or better to use this module. © 2010 Gisle Aas `<gisle@aas.no>`. This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. usr/share/doc/tcl-8.5.13/README 0000644 00000014565 14721023655 0011440 0 ustar 00 README: Tcl This is the Tcl 8.5.13 source distribution. http://tcl.sourceforge.net/ You can get any source release of Tcl from the file distributions link at the above URL. Contents -------- 1. Introduction 2. Documentation 3. Compiling and installing Tcl 4. Development tools 5. Tcl newsgroup 6. The Tcler's Wiki 7. Mailing lists 8. Support and Training 9. Tracking Development 10. Thank You 1. Introduction --------------- Tcl provides a powerful platform for creating integration applications that tie together diverse applications, protocols, devices, and frameworks. When paired with the Tk toolkit, Tcl provides the fastest and most powerful way to create GUI applications that run on PCs, Unix, and Mac OS X. Tcl can also be used for a variety of web-related tasks and for creating powerful command languages for applications. Tcl is maintained, enhanced, and distributed freely by the Tcl community. The home for Tcl/Tk releases and bug/patch database is on SourceForge: http://tcl.sourceforge.net/ with the Tcl Developer Xchange hosted at: http://www.tcl.tk/ Tcl is a freely available open source package. You can do virtually anything you like with it, such as modifying it, redistributing it, and selling it either in whole or in part. See the file "license.terms" for complete information. 2. Documentation ---------------- Extensive documentation is available at our website. The home page for this release, including new features, is http://www.tcl.tk/software/tcltk/8.5.html Detailed release notes can be found at the file distributions page by clicking on the relevant version. http://sourceforge.net/projects/tcl/files/ Information about Tcl itself can be found at http://www.tcl.tk/about/ There have been many Tcl books on the market. Many are mentioned in the Wiki: http://wiki.tcl.tk/_/ref?N=25206 To view the complete set of reference manual entries for Tcl 8.5 online, visit the URL: http://www.tcl.tk/man/tcl8.5/ 2a. Unix Documentation ---------------------- The "doc" subdirectory in this release contains a complete set of reference manual entries for Tcl. Files with extension ".1" are for programs (for example, tclsh.1); files with extension ".3" are for C library procedures; and files with extension ".n" describe Tcl commands. The file "doc/Tcl.n" gives a quick summary of the Tcl language syntax. To print any of the man pages on Unix, cd to the "doc" directory and invoke your favorite variant of troff using the normal -man macros, for example ditroff -man Tcl.n to print Tcl.n. If Tcl has been installed correctly and your "man" program supports it, you should be able to access the Tcl manual entries using the normal "man" mechanisms, such as man Tcl 2b. Windows Documentation ------------------------- The "doc" subdirectory in this release contains a complete set of Windows help files for Tcl. Once you install this Tcl release, a shortcut to the Windows help Tcl documentation will appear in the "Start" menu: Start | Programs | Tcl | Tcl Help 3. Compiling and installing Tcl ------------------------------- There are brief notes in the unix/README, win/README, and macosx/README about compiling on these different platforms. There is additional information about building Tcl from sources at http://www.tcl.tk/doc/howto/compile.html 4. Development tools --------------------------- ActiveState produces a high quality set of commercial quality development tools that is available to accelerate your Tcl application development. Tcl Dev Kit builds on the earlier TclPro toolset and provides a debugger, static code checker, single-file wrapping utility, bytecode compiler and more. More information can be found at http://www.ActiveState.com/Tcl 5. Tcl newsgroup ---------------- There is a USENET news group, "comp.lang.tcl", intended for the exchange of information about Tcl, Tk, and related applications. The newsgroup is a great place to ask general information questions. For bug reports, please see the "Support and bug fixes" section below. 6. Tcl'ers Wiki --------------- A Wiki-based open community site covering all aspects of Tcl/Tk is at: http://wiki.tcl.tk/ It is dedicated to the Tcl programming language and its extensions. A wealth of useful information can be found there. It contains code snippets, references to papers, books, and FAQs, as well as pointers to development tools, extensions, and applications. You can also recommend additional URLs by editing the wiki yourself. 7. Mailing lists ---------------- Several mailing lists are hosted at SourceForge to discuss development or use issues (like Macintosh and Windows topics). For more information and to subscribe, visit: http://sourceforge.net/projects/tcl/ and go to the Mailing Lists page. 8. Support and Training ------------------------ We are very interested in receiving bug reports, patches, and suggestions for improvements. We prefer that you send this information to us via the bug form at SourceForge, rather than emailing us directly. The bug database is at: http://tcl.sourceforge.net/ The bug form was designed to give uniform structure to bug reports as well as to solicit enough information to minimize followup questions. We will log and follow-up on each bug, although we cannot promise a specific turn-around time. Enhancements, reported via the Feature Requests form at the same web site, may take longer and may not happen at all unless there is widespread support for them (we're trying to slow the rate at which Tcl/Tk turns into a kitchen sink). It's very difficult to make incompatible changes to Tcl/Tk at this point, due to the size of the installed base. The Tcl community is too large for us to provide much individual support for users. If you need help we suggest that you post questions to comp.lang.tcl. We read the newsgroup and will attempt to answer esoteric questions for which no one else is likely to know the answer. In addition, see the following Web site for links to other organizations that offer Tcl/Tk training: http://wiki.tcl.tk/training 9. Tracking Development ----------------------- Tcl is developed in public. To keep an eye on how Tcl is changing, see http://core.tcl.tk/ 10. Thank You ------------- We'd like to express our thanks to the Tcl community for all the helpful suggestions, bug reports, and patches we have received. Tcl/Tk has improved vastly and will continue to do so with your help. usr/share/doc/libdwarf-20130207/README 0000644 00000023026 14721024140 0012570 0 ustar 00 To build libdwarf.a, type ./configure make To build libdwarf.so, type ./configure --enable-shared --disable-nonshared make To build both, type ./configure --enable-shared make January 30, 2013: libdwarf.h is no longer in the distribution, but libdwarf.h.in is identical to libdwarf.h. 'configure' copies libdwarf.h.in to libdwarf.h and whether libelf.h defines 'struct _Elf' or 'struct Elf' configure attempts to create libdwarf.h appropriately. No real install target is provided here, so 'make install' does not do much. One can copy either or both of libdwarf.a libdwarf.so to somewhere fairly standard (but intended for software you build) like '/usr/local/lib'. Or anywhere else you want to copy it. To use dwarf or libdwarf, you may want to copy dwarf.h and a generated libdwarf.h somewhere convenient (possibly /usr/local/include), and you may need to copy the libdwarf to a convenient spot (/usr/local/lib is a traditional place for libraries one builds oneself on Unix and Linux). This copying is not needed to build dwarfdump. Multi Threading, or using threads with libdwarf (Thread Safety): Nothing in libdwarf does any locking. Every Dwarf_Debug (such as returned by dwarf_init()) is fully independent of all other Dwarf_Debug-s. However, calls to libdwarf can change a Dwarf_Debug. So it is unsafe to have two different threads accessing a single Dwarf_Debug simultaneously. It is therefore sufficient to ensure than any one Dwarf_Debug is only accessed from a single thread. Warnings like "warning: cast from pointer to integer of different size" at compile time are to be expected in dwarf_frame.c and dwarf_frame2.c. Do not be alarmed. Warnings like "warning: passing argument 1 of ‘dbg->de_callback_func_c’ discards ‘const’ qualifier from pointer target type [enabled by default]" at compile time are to be expected in some pro*.c source files. Fixing the public prototype could cause some producer-library user's code to fail to compile so we live with the warnings for now. If your headers are not in the expected places, use the make command line to add flags and include directories. For example ./configure PREINCS="-I /usr/local/share/include" POSTINCS="-I /home/x/include" make PREINCS content is inserted before CFLAGS as make(1) is running. POSTINCS content is added after the CFLAGS value. To set LDFLAGS (which is used when building a .so and in building gennames to create some source here), do so at configure time, for example: ./configure LDFLAGS="-L /var/tmp" Or use PRELIBS and/or POSTLIBS at 'make' time similar to the use of PREINCS and POSTINCS. If you are using the old frame interfaces and depend on the use of DW_FRAME_CFA_COL you must add --enable-oldframecol to the ./configure options to configure libdwarf. See NEWS and libdwarf2.1.mm/pdf . To generate SGI IRIX 64 bit offsets (in the producer code) configure with --enable-dwarf-format-sgi-irix. To configure with only 32bit offsets (aka DWARF2) configure with --enable-dwarf-format-strict-32bit. By default the producer now generates 32bit offsets by default but one can turn on DWARF3 64bit offset generation at runtime by ORing DW_DLC_OFFSET_SIZE_64 onto the flags in the call to dwarf_producer_init() (or dwarf_producer_init_b) [when the address size is specified as 64 bit]. Mac OSX (June 2010): Since MacOSX does not use elf, there is no elf.h header in the headers provided on MacOSX. Use a search engine (like google) to find an elf.h you can use. http://www.rockbox.org/tracker/9006?getfile=16683 might be useful. In addition, the archive (ar) program on MacOSX does not automatically generate some data so modify the generated Makefile to add -s to the options to ar. To enable dection of Windows pathnames as full paths add --enable-windowspath. Doing this does mean things like A:foo and \anything are treated as full paths (these are unlikely path names on a POSIX system but are legal POSIX partial paths). It is possible to request a shared library (libdwarf.so) build with --enable-shared To turn off the build of the archive library (libdwarf.a) specify --disable-nonshared but in this case you must specify --enable-shared or nothing will build! TARGET DEPENDENCIES of .debug_frame: dwarf.h These should be revised if you have more than the defined 63 'normal' registers. It's not harmful to have these too large! Too small will lead to errors reading .debug_frame and .eh_frame. DW_FRAME_HIGHEST_NORMAL_REGISTER DW_FRAME_LAST_REG_NUM These you might revise, but can safely ignore if simply using dwarfdump. If using the producer code you will want to get these exactly right for your architecture. DW_FRAME_RA_COL DW_FRAME_STATIC_LINK DW_FRAME_CFA_COL libdwarf.h The DW_FRAME_REG_INITIAL_VALUE #define should be set to the value appropriate to your architecture. See libdwarf.h for details. If DW_REG_TABLE_SIZE is not set large enough attempts to fill in the .debug_frame tables will get an error. Should be at least as large as DW_FRAME_LAST_REG_NUM. If it's too large nothing is harmed (but some extra space taken at run time). If your printf does not support C standard %llx etc, (such as MSWindows with long long), configure option --enable-nonstandardprintf and defines like DW_PR_DUx etc in libdwarf.h provide a way to configure for that relatively easily. The .debug_frame is so very architecture dependent and because the host (where libdwarf/dwarfdump are executed) and target (the objects read) could be different. It's currently not supported to have dwarfdump/libdwarf determine the architecture on-the-fly and do-the-right-thing. Just setting DW_FRAME_LAST_REG_NUM and DW_FRAME_HIGHEST_NORMAL_REGISTER and DW_REG_TABLE_SIZE high enough will likely suffice for most purposes and most compilers/architectures.. See comments in dwarf.h/libdwarf.h. It's perfectly safe to ignore the above suggestions as long as libdwarf does not get a DW_DLE_DF_REG_NUM_TOO_HIGH error. (which would only happen on reading .debug_frame or .eh_frame data). If you intend to use the libdwarf dwarf-producer code for .debug_frame information you must do a thorough analysys and revise dwarf.h substantially to match the output target architecture. In general, in the producer code, numbers are copied from and to integers with memcpy(). In case of endianness problems, constants set in dwarf_producer_init() can fix the problems. If one wants to produce a *different-endian* output the best solution is to change the integer memcpy calls to call thru a new dbg-based function pointer and have it 'do the right thing' to adjust endianness. Set the function pointer correctly in dwarf_producer_init() and the rest of the code will just call thru the function pointer. Tedious work to find and change the memcpy calls to be dbg->de_memcpy(), but once done the code is no longer endian dependent (right now there is no way to ask for cross-endian: a new flag needed or ?). leb128 numbers are endian-independent, so nothing need be done with those for cross-endian support (the storage of leb128 on disk is always little-endian). The .ps files are postscript. So those who cannot deal with mm format files but do have a postscript printer (or have ghostscript) can print the documents. This form was chosen before pdf format existed... libdwarf2.1.pdf documents a way for a debugger to read dwarf information. libdwarf2p.1.pdf documents a way for a compiler to generate dwarf information. dwarf.v2.pdf documents Dwarf Version 2. index.v2.pdf is an index to dwarf.v2.ps. indexDW.v2 is a plain text index of dwarf #defines to dwarf.v2.ps mips_extensions.ps documents the mips/sgi extensions to dwarf. See the Makefile for the commands used to build pdf files libdwarf.2.1.pdf and libdwarf1p.1.pdf. pic is a picture processing tool (ATT command). tbl is a table-processing tool. (part of Documentor's Work Bench on ATT-like systems). tbl and pic are available on linux. psroff is a name for a troff-like processor, part of Documentor's Work Bench on IRIX. Substitute a troff-like or nroff-like processor (GNU groff works fine). The index.v2.mm was generated by the dwarf-document writer using some local ATT/USL tools (which neither SGI nor the open-source community generally has, so there is no way I know of to regenerate this). To use dwarf or libdwarf, you may want to install dwarf.h and libdwarf.h somewhere convenient. You will also need libelf (libelf.a and/or libelf.so) and libelf.h installed. These are available from GNU repositories and from the normal Linux repositories for Linux releases. On Ubuntu Linux for example: sudo apt-get install libelf-dev libelf1 Compiler warnings: A few Warnings like: dwarf_frame.c:715:29: warning: cast from pointer to integer of different size [- Wpointer-to-int-cast] dwarf_arange.c:113:13: warning: variable ‘local_extension_size’ set but not used [-Wunused-but-set-variable] are considered normal. As of January 2013 the code compiles with gcc without problems with -Wall and -Wsign-compare aside from the warnings hinted at above. The following gcc/clang options have not all been tried as of January 2013, but will be as time permits. -Wsystem-headers -Wall -Wsign-compare -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign $Source: /home/davea/dwarf/dwarf-working/trunk/libdwarf/README,v $ $Revision: 1.1 $ $Date: 2009/11/23 17:15:37 $ usr/share/doc/perl-HTTP-Date-6.02/README 0000644 00000011527 14721024152 0013065 0 ustar 00 NAME HTTP::Date - date conversion routines SYNOPSIS use HTTP::Date; $string = time2str($time); # Format as GMT ASCII time $time = str2time($string); # convert ASCII date to machine time DESCRIPTION This module provides functions that deal the date formats used by the HTTP protocol (and then some more). Only the first two functions, time2str() and str2time(), are exported by default. time2str( [$time] ) The time2str() function converts a machine time (seconds since epoch) to a string. If the function is called without an argument or with an undefined argument, it will use the current time. The string returned is in the format preferred for the HTTP protocol. This is a fixed length subset of the format defined by RFC 1123, represented in Universal Time (GMT). An example of a time stamp in this format is: Sun, 06 Nov 1994 08:49:37 GMT str2time( $str [, $zone] ) The str2time() function converts a string to machine time. It returns `undef' if the format of $str is unrecognized, otherwise whatever the `Time::Local' functions can make out of the parsed time. Dates before the system's epoch may not work on all operating systems. The time formats recognized are the same as for parse_date(). The function also takes an optional second argument that specifies the default time zone to use when converting the date. This parameter is ignored if the zone is found in the date string itself. If this parameter is missing, and the date string format does not contain any zone specification, then the local time zone is assumed. If the zone is not "`GMT'" or numerical (like "`-0800'" or "`+0100'"), then the `Time::Zone' module must be installed in order to get the date recognized. parse_date( $str ) This function will try to parse a date string, and then return it as a list of numerical values followed by a (possible undefined) time zone specifier; ($year, $month, $day, $hour, $min, $sec, $tz). The $year returned will not have the number 1900 subtracted from it and the $month numbers start with 1. In scalar context the numbers are interpolated in a string of the "YYYY-MM-DD hh:mm:ss TZ"-format and returned. If the date is unrecognized, then the empty list is returned. The function is able to parse the following formats: "Wed, 09 Feb 1994 22:23:32 GMT" -- HTTP format "Thu Feb 3 17:03:55 GMT 1994" -- ctime(3) format "Thu Feb 3 00:00:00 1994", -- ANSI C asctime() format "Tuesday, 08-Feb-94 14:15:29 GMT" -- old rfc850 HTTP format "Tuesday, 08-Feb-1994 14:15:29 GMT" -- broken rfc850 HTTP format "03/Feb/1994:17:03:55 -0700" -- common logfile format "09 Feb 1994 22:23:32 GMT" -- HTTP format (no weekday) "08-Feb-94 14:15:29 GMT" -- rfc850 format (no weekday) "08-Feb-1994 14:15:29 GMT" -- broken rfc850 format (no weekday) "1994-02-03 14:15:29 -0100" -- ISO 8601 format "1994-02-03 14:15:29" -- zone is optional "1994-02-03" -- only date "1994-02-03T14:15:29" -- Use T as separator "19940203T141529Z" -- ISO 8601 compact format "19940203" -- only date "08-Feb-94" -- old rfc850 HTTP format (no weekday, no time) "08-Feb-1994" -- broken rfc850 HTTP format (no weekday, no time) "09 Feb 1994" -- proposed new HTTP format (no weekday, no time) "03/Feb/1994" -- common logfile format (no time, no offset) "Feb 3 1994" -- Unix 'ls -l' format "Feb 3 17:03" -- Unix 'ls -l' format "11-15-96 03:52PM" -- Windows 'dir' format The parser ignores leading and trailing whitespace. It also allow the seconds to be missing and the month to be numerical in most formats. If the year is missing, then we assume that the date is the first matching date *before* current month. If the year is given with only 2 digits, then parse_date() will select the century that makes the year closest to the current date. time2iso( [$time] ) Same as time2str(), but returns a "YYYY-MM-DD hh:mm:ss"-formatted string representing time in the local time zone. time2isoz( [$time] ) Same as time2str(), but returns a "YYYY-MM-DD hh:mm:ssZ"-formatted string representing Universal Time. SEE ALSO perlfunc, Time::Zone COPYRIGHT Copyright 1995-1999, Gisle Aas This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. usr/share/doc/ea-apache24/README 0000644 00000011052 14721024365 0012061 0 ustar 00 Apache HTTP Server What is it? ----------- The Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server. Originally designed as a replacement for the NCSA HTTP Server, it has grown to be the most popular web server on the Internet. As a project of the Apache Software Foundation, the developers aim to collaboratively develop and maintain a robust, commercial-grade, standards-based server with freely available source code. The Latest Version ------------------ Details of the latest version can be found on the Apache HTTP server project page under https://httpd.apache.org/. Documentation ------------- The documentation available as of the date of this release is included in HTML format in the docs/manual/ directory. The most up-to-date documentation can be found at https://httpd.apache.org/docs/2.4/. Installation ------------ Please see the file called INSTALL. Platform specific notes can be found in README.platforms. Licensing --------- Please see the file called LICENSE. Cryptographic Software Notice ----------------------------- This distribution may include software that has been designed for use with cryptographic software. The country in which you currently reside may have restrictions on the import, possession, use, and/or re-export to another country, of encryption software. BEFORE using any encryption software, please check your country's laws, regulations and policies concerning the import, possession, or use, and re-export of encryption software, to see if this is permitted. See <https://www.wassenaar.org/> for more information. The U.S. Government Department of Commerce, Bureau of Industry and Security (BIS), has classified this software as Export Commodity Control Number (ECCN) 5D002.C.1, which includes information security software using or performing cryptographic functions with asymmetric algorithms. The form and manner of this Apache Software Foundation distribution makes it eligible for export under the License Exception ENC Technology Software Unrestricted (TSU) exception (see the BIS Export Administration Regulations, Section 740.13) for both object code and source code. The following provides more details on the included files that may be subject to export controls on cryptographic software: Apache httpd 2.0 and later versions include the mod_ssl module under modules/ssl/ for configuring and listening to connections over SSL encrypted network sockets by performing calls to a general-purpose encryption library, such as OpenSSL or the operating system's platform-specific SSL facilities. In addition, some versions of apr-util provide an abstract interface for symmetrical cryptographic functions that make use of a general-purpose encryption library, such as OpenSSL, NSS, or the operating system's platform-specific facilities. This interface is known as the apr_crypto interface, with implementation beneath the /crypto directory. The apr_crypto interface is used by the mod_session_crypto module available under modules/session for optional encryption of session information. Some object code distributions of Apache httpd, indicated with the word "crypto" in the package name, may include object code for the OpenSSL encryption library as distributed in open source form from <https://www.openssl.org/source/>. The above files are optional and may be removed if the cryptographic functionality is not desired or needs to be excluded from redistribution. Distribution packages of Apache httpd that include the word "nossl" in the package name have been created without the above files and are therefore not subject to this notice. Contacts -------- o If you want to be informed about new code releases, bug fixes, security fixes, general news and information about the Apache server subscribe to the apache-announce mailing list as described under <https://httpd.apache.org/lists.html#http-announce> o If you want freely available support for running Apache please see the resources at <https://httpd.apache.org/support.html> o If you have a concrete bug report for Apache please see the instructions for bug reporting at <https://httpd.apache.org/bug_report.html> o If you want to participate in actively developing Apache please subscribe to the `dev@httpd.apache.org' mailing list as described at <https://httpd.apache.org/lists.html#http-dev> usr/share/doc/diffutils-3.3/README 0000644 00000005446 14721024500 0012402 0 ustar 00 README for GNU DIFF This directory contains the GNU diff, diff3, sdiff, and cmp utilities. Their features are a superset of the Unix features and they are significantly faster. Please see the file COPYING for copying conditions. Please see the file doc/version.texi for version information. Please see the file doc/diffutils.texi (or doc/diffutils.info) for documentation that can be printed with TeX, or read with the 'info' program or with Emacs's 'M-x info'. Brief man pages are in man/*, but they are no substitute for the documentation. Please see the file ABOUT-NLS for notes about translations. Please see the file INSTALL for generic compilation and installation instructions. Briefly, you can run "./configure; make install". The command "./configure --help" lists the supported --enable and --with options. If you have a problem with internationalization, you might be able to work around it as described in ABOUT-NLS by invoking './configure --disable-nls'. Many of the problems arise from dynamic linking issues on non-GNU platforms (e.g. with the iconv library). Such problems tend to be shared by other GNU applications on these platforms, and can usually be fixed by carefully tweaking your non-GNU installation. If you have an older version of libiconv, please upgrade to the latest one; see <ftp://ftp.gnu.org/gnu/libiconv/>. If the problem seems isolated to diffutils, though, please report a bug. This program requires a Standard C compiler (C89 or later). If you have a nonstandard compiler, please install GCC first. If you make changes to the source code, you may need appropriate versions of GNU build tools to regenerate the intermediate files. The following versions were used to generate the intermediate files in this distribution: * Autoconf 2.59 <ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.59.tar.gz> * Automake 1.8.3 <ftp://ftp.gnu.org/gnu/automake/automake-1.8.3.tar.gz> * gettext 0.14.1 <ftp://ftp.gnu.org/gnu/gettext/gettext-0.14.1.tar.gz> * help2man 1.33 <ftp://ftp.gnu.org/gnu/help2man/help2man-1.33.1.tar.gz> * Texinfo 4.7 <ftp://ftp.gnu.org/gnu/texinfo/texinfo-4.7.tar.gz> For any copyright year range specified as YYYY-ZZZZ in this package note that the range specifies every single year in that closed interval. Please report bugs to <bug-gnu-utils@gnu.org>. ----- Copyright (C) 1992, 1998, 2001-2002, 2004, 2009-2013 Free Software Foundation, Inc. This file is part of GNU Diffutils. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the "GNU Free Documentation License" file as part of this distribution. usr/share/doc/ed-1.9/README 0000644 00000013415 14721024561 0011007 0 ustar 00 Description GNU ed is a line-oriented text editor. It is used to create, display, modify and otherwise manipulate text files, both interactively and via shell scripts. A restricted version of ed, red, can only edit files in the current directory and cannot execute shell commands. Ed is the "standard" text editor in the sense that it is the original editor for Unix, and thus widely available. For most purposes, however, it is superseded by full-screen editors such as GNU Emacs or GNU Moe. Extensions to and deviations from the POSIX standard are described below. See the file INSTALL for compilation and installation instructions. Try "ed --help" for usage instructions. Report bugs to <bug-ed@gnu.org>. Ed home page: http://www.gnu.org/software/ed/ed.html For a description of the ed algorithm, see Kernighan and Plauger's book "Software Tools in Pascal", Addison-Wesley, 1981. GNU ed(1) is not strictly POSIX compliant, as described in the POSIX 1003.1-2004 document. The following is a summary of omissions and extensions to, and deviations from, the POSIX standard. OMISSIONS --------- * Locale(3) is not supported. EXTENSIONS ---------- * Though GNU ed is not a stream editor, it can be used to edit binary files. To assist in binary editing, when a file containing at least one ASCII NUL character is written, a newline is not appended if it did not already contain one upon reading. In particular, reading /dev/null prior to writing prevents appending a newline to a binary file. For example, to create a file with GNU ed containing a single NUL character: $ ed file a ^@ . r /dev/null wq Similarly, to remove a newline from the end of binary 'file': $ ed file r /dev/null wq * BSD commands have been implemented wherever they do not conflict with the POSIX standard. The BSD-ism's included are: * 's' (i.e., s[n][rgp]*) to repeat a previous substitution, * 'W' for appending text to an existing file, * 'wq' for exiting after a write, and * 'z' for scrolling through the buffer. * The POSIX interactive global commands 'G' and 'V' are extended to support multiple commands, including 'a', 'i' and 'c'. The command format is the same as for the global commands 'g' and 'v', i.e., one command per line with each line, except for the last, ending in a backslash (\). * The file commands 'E', 'e', 'r', 'W' and 'w' process a <file> argument for backslash escapes; i.e., any character preceded by a backslash is interpreted literally. If the first unescaped character of a <file> argument is a bang (!), then the rest of the line is interpreted as a shell command, and no escape processing is performed by GNU ed. * For SunOS ed(1) compatibility, GNU ed runs in restricted mode if invoked as red. This limits editing of files in the local directory only and prohibits shell commands. DEVIATIONS ---------- * For backwards compatibility, the POSIX rule that says a range of addresses cannot be used where only a single address is expected has been relaxed. * To support the BSD 's' command (see EXTENSIONS above), substitution patterns cannot be delimited by numbers or the characters 'r', 'g' and 'p'. In contrast, POSIX specifies any character expect space or newline can used as a delimiter. * Since the behavior of 'u' (undo) within a 'g' (global) command list is not specified by POSIX, GNU ed follows the behavior of the SunOS ed: undo forces a global command list to be executed only once, rather than for each line matching a global pattern. In addtion, each instance of 'u' within a global command undoes all previous commands (including undo's) in the command list. This seems the best way, since the alternatives are either too complicated to implement or too confusing to use. * The 'm' (move) command within a 'g' command list also follows the SunOS ed implementation: any moved lines are removed from the global command's 'active' list. * If GNU ed is invoked with a name argument prefixed by a bang (!), then the remainder of the argument is interpreted as a shell command. To invoke ed on a file whose name starts with bang, prefix the name with a (quoted) backslash. * For backwards compatibility, errors in piped scripts do not force ed to exit. POSIX only specifies ed's response for input via regular files (including here documents) or tty's. TESTSUITE --------- The files in the 'testsuite' directory with suffixes '.t', '.d', '.r', '.pr' and '.err' are used for testing ed. To run the tests, configure the package and type 'make check' from the build directory. The tests do not exhaustively verify POSIX compliance nor do they verify correct 8-bit or long line support. The test file suffixes have the following meanings: .t Template - a list of ed commands from which an ed script is constructed .d Data - read by an ed script .r Result - the expected output after processing data via an ed script. .pr Result from a piped ed script. .err Error - invalid ed commands that should generate an error The output of the tests is written to files with .o and .ro suffixes and compared with their corresponding .r and .pr result files. If any test fails, the error messages look like: *** The script u.ed exited abnormally *** or: *** Output u.o of script u.ed is incorrect *** Copyright (C) 1993, 1994 Andrew Moore Copyright (C) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013 Free Software Foundation, Inc. This file is free documentation: you have unlimited permission to copy, distribute and modify it. The file Makefile.in is a data file used by configure to produce the Makefile. It has the same copyright owner and permissions that configure itself. usr/share/doc/libstoragemgmt-1.8.1/README 0000644 00000000210 14721024723 0013562 0 ustar 00 libStorageMgmt : A library for storage management Full documentation can be found at: http://libstorage.github.io/libstoragemgmt-doc/ usr/share/doc/socat-1.7.3.2/README 0000644 00000026576 14721024751 0012044 0 ustar 00 about ----- socat is a relay for bidirectional data transfer between two independent data channels. Each of these data channels may be a file, pipe, device (serial line etc. or a pseudo terminal), a socket (UNIX, IP4, IP6 - raw, UDP, TCP), an SSL socket, proxy CONNECT connection, a file descriptor (stdin etc.), the GNU line editor (readline), a program, or a combination of two of these. These modes include generation of "listening" sockets, named pipes, and pseudo terminals. socat can be used, e.g., as TCP port forwarder (one-shot or daemon), as an external socksifier, for attacking weak firewalls, as a shell interface to UNIX sockets, IP6 relay, for redirecting TCP oriented programs to a serial line, to logically connect serial lines on different computers, or to establish a relatively secure environment (su and chroot) for running client or server shell scripts with network connections. Many options are available to refine socats behaviour: terminal parameters, open() options, file permissions, file and process owners, basic socket options like bind address, advanced socket options like IP source routing, linger, TTL, TOS (type of service), or TCP performance tuning. More capabilities, like daemon mode with forking, client address check, "tail -f" mode, some stream data processing (line terminator conversion), choosing sockets, pipes, or ptys for interprocess communication, debug and trace options, logging to syslog, stderr or file, and last but not least precise error messages make it a versatile tool for many different purposes. In fact, many of these features already exist in specialized tools; but until now, there does not seem to exists another tool that provides such a generic, flexible, simple and almost comprehensive (UNIX) byte stream connector. packages -------- before bothering with compilers, dependencies and include files, you might try to get a binary distribution that matches your platform. Have a look at the projects home page for actual information regarding socat binary distributions. platforms --------- socat 1.7.0 was compiled and more or less successfully tested under the following operating systems: Debian lenny/sid on x86, kernel 2.6.24 FreeBSD 6.1 on x86 NetBSD 4.0 on x86 OpenBSD 4.3 on x86 OpenSolaris 10 on x86 with gcc Mac OS X 10.5.5 on iMac G5, with libreadline HP-UX 11.23 AIX 5.3 on 64bit Power4 with gcc Cygwin 1.5.25 on i686 tests on Tru64 can no longer be performed because HP testdrive has taken down these hosts. Some versions of socat have been reported to successfully compile under older Linux versions back to RedHat 2.1 (kernel 1.2.13, gcc 2.7.0), under AIX 4.1 and 4.3, SunOS 5.7-5.8, FreeBSD 4.2 - 4.9, MacOS X 10.1, Cygwin, Solaris 8 on x86, OSR 5.0.6, NetBSD 1.6.1 and 2.0.2, OpenBSD 3.4 and 3.8, Tru64 5.1B, Mac OS X 10.1-10.2, and HP-UX 11 It might well compile and run under other UNIX like operating systems. install ------- Get the tarball and extract it: tar xzf socat.tar.gz cd socat-1.7.3.0 ./configure make su make install # installs socat, filan, and procan in /usr/local/bin For compiling socat, gcc (or egc) is recommended. If gcc is not available, the configure script will fail to determine some features; then you'd better begin with one of the Makefiles and config.h's from the Config directory. If you have problems with the OpenSSL library, you can apply the option "--disable-openssl" to configure. If you have problems with the readline library or (n)curses, you can apply the option "--disable-readline" to configure. If you have problems with the tcp wrappers library, you can apply the option "--disable-libwrap" to configure. If you still get errors or a tremendous amount of warnings you can exclude the features for system call tracing and file descriptor analyzing by applying the options "--disable-sycls --disable-filan" to configure. You still need the functions vsnprintf and snprintf that are in the GNU libc, but might not be available with some proprietary libc's. The configure script looks for headers and libraries of openssl, readline, and tcp wrappers in the OS'es standard places and in the subdirectories include/ and lib/ of the following places: /sw/ /usr/local/ /opt/freeware/ /usr/sfw/ and for openssl also in: /usr/local/ssl/ In case of unexpected behaviour it is important to understand that configure first searches for the appropriate include file and then expects to find the library in the associated lib directory. That means, when e.g. a OpenSSL installation resides under /usr/local and there is a symbolic link from /usr/include/ssl/ssl.h to /usr/local/ssl/include/ssl/ssl.h, configure will find the /usr/include/... header and will therefore expect libssl in /usr/lib instead of /usr/local/... If configure does not find a header file or library but you know where it is, you can specify additional search locations, e.g.: export LIBS="-L$HOME/lib" export CPPFLAGS="-I$HOME/include" before running configure and make. For other operating systems, if socat does not compile without errors, refer to the file PORTING. platform specifics - redhat --------------------------- Install the following packages before building socat: tcp_wrappers-devel readline-devel openssl-devel On RedHat Linux 9.0, including openssl/ssl.h might fail due to problems with the krb5-devel package. configure reacts with disabling openssl integration. To solve this issue, help cpp to find the krb5.h include file: CPPFLAGS="-I/usr/kerberos/include" ./configure platform specifics - aix ------------------------ The flock() prototype is not available but the function is. Thus, to enable the socat flock options, run configure and then change in config.h the line /* #undef HAVE_FLOCK */ to #define HAVE_FLOCK 1 and continue the build process. When using the OpenSSL rpm provided by IBM, configure might need the environment variable setting: LIBS="-L/opt/freeware/lib" When using the OpenSSL bundle provided by IBM, egd needs to be installed too to get enough entropy. socat compiles not only with gcc, but also with xlc. Just adapt the Makefile: replace gcc by /usr/vac/bin/xlc and remove gcc specific options "-Wall -Wno-parentheses". When linking with the OpenSSL library provided by IBM, errors may occur: ld: 0711-317 ERROR: Undefined symbol: .__umoddi3 In this case, you need to link with libgcc or compile libcrypt yourself using xlc, or disable SSL (in config.h, undefine WITH_OPENSSL and recompile) The score of test.sh can be improved by uncommenting MISCDELAY=1 in this script. platform specifics - solaris ---------------------------- If libreadline or libssl are in a directory not searched by the loader per default, e.g. /opt/sfw/lib, you must add this directory to $LD_LIBRARY_PATH, for running both configure and the socat executables, e.g.: export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/sfw/lib For some shell scripts, it is preferable to have /usr/xpg4/bin at a prominent position in $PATH. With the default compiler define _GNU_SOURCE, the CMSG_* macros are not available, and therefore ancillary messages cannot be used. To enable these try the following: After running ./configure, edit Makefile and replace "-D_GNU_SOURCE" with "-D_XPG4_2 -D__EXTENSIONS__" and run make platform specifics - hp-ux -------------------------- Ancillary messages cannot be compiled in with socat: both struct msghdr and struct cmsghdr are required. Compiling with -D_XOPEN_SOURCE_EXTENDED provides struct msghdr but disables struct cmsghdr while -D_OPEN_SOURCE disables struct msghdr but disables struct cmsghdr. Please contact socat development if you know a solution. Shutting down the write channel of a UNIX domain socket does not seem to trigger an EOF on the peer socket. This makes problems with the exec and system addresses. This OS provides the type "long long", but not the strtoll() function to read data into a long long variable. UNIX domain sockets are only supported with SOCK_STREAM, not with datagrams (see man 7 unix). With UDP sockets it seems to happen that the select() call reports available data (or EOF) but a subsequent read() call hangs. platform specifics - tru64 -------------------------- When the use of the readline address fails with an error like: socat: /sbin/loader: Fatal Error: Reference to unresolvable symbol "tgetent" in ".../libreadline.so.4" and you still want to use shared libraries, try the following workaround: $ make distclean; LIBS="-static" ./configure remove the "-static" occurrence in Makefile $ make documentation ------------- These files reside in the doc subdirectory: socat.1 is the man page, socat.html is the HTML based man page. It is actual, but describes only the more useful options. xio.help is an older, but more exact description in text form; with socat version 1.6.0 it is outdated. doc/socat-openssltunnel.html is a simple tutorial for a private SSL connection. doc/socat-multicast.html is a short tutorial for multicast and broadcast communications. doc/socat-tun shows how to build a virtual network between two hosts. socat.1 and socat.html can be generated from socat.yo (which is released with socat 1.6.0.1 and later) using the yodl document language package. Maintenance of yodl had been discontinued by its author (http://www.xs4all.nl/~jantien/yodl/) (there seems to be a revival at http://yodl.sourceforge.net/ though). For socat, the old version 1.31 is used; an rpm is still distributed with recent OpenSuSE versions (confirmed for OpenSuSE 10.1 in suse/i586/yodl-1.31.18-1142.i586.rpm). It appears to install smoothly also under RedHat Linux. After yodl 1.31 installation, the following correction must be performed in /usr/share/yodl/shared.yo in two places: < whenhtml(htmlcommand(<!)ARG1+htmlcommand(>))) > whenhtml(htmlcommand(<!--)ARG1+htmlcommand(-->))) license ------- socat is distributed under the terms of the GNU GPLv2; except for install-sh, which is copyright MIT, with its own license; In addition, as a special exception, the copyright holder gives permission to link the code of this program with any version of the OpenSSL library which is distributed under a license identical to that listed in the included COPYING.OpenSSL file, and distribute linked combinations including the two. You must obey the GNU General Public License in all respects for all of the code used other than OpenSSL. If you modify this file, you may extend this exception to your version of the file, but you are not obligated to do so. If you do not wish to do so, delete this exception statement from your version. 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 This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. contact ------- For questions, bug reports, ideas, contributions etc. please contact socat@dest-unreach.org For socat source distribution, bug fixes, and latest news see http://www.dest-unreach.org/socat/ www.socat.org is an alternate site providing the same contents. public git repository: git://repo.or.cz/socat.git http://repo.or.cz/r/socat.git usr/share/doc/zip-3.0/README 0000644 00000030714 14721025453 0011214 0 ustar 00 Zip 3.0 is the first Zip update adding large file support. For now Zip 2.3x remains available and supported, but users should switch to this new release. Testing for Zip 3.0 has focused mainly on Unix, VMS, Max OS X, and Win32, and some other ports may not be fully supported yet. If you find your favorite port is broke, send us the details or, better, send bug fixes. It's possible that support for some older ports may be dropped in the future. Copyright (c) 1990-2008 Info-ZIP. All rights reserved. See the accompanying file LICENSE (the contents of which are also included in unzip.h, zip.h and wiz.h) for terms of use. If, for some reason, all of these files are missing, the Info-ZIP license also may be found at: ftp://ftp.info-zip.org/pub/infozip/license.html and http://www.info-zip.org/pub/infozip/license.html. Zip 3.0 is a compression and file packaging utility. It is compatible with PKZIP 2.04g (Phil Katz ZIP) for MSDOS systems. There is a companion to zip called unzip (of course) which you should be able to find in the same place you got zip. See the file 'WHERE' for details on ftp sites and mail servers. So far zip has been ported to a wide array of Unix and other mainframes, minis, and micros including VMS, OS/2, Minix, MSDOS, Windows, Atari, Amiga, BeOS and VM/CMS. Although highly compatible with PKware's PKZIP and PKUNZIP utilities of MSDOS fame, our primary objective has been one of portability and other-than-MSDOS functionality. Features not found in the PKWare version include creation of zip files in a pipe or on a device; VMS, BeOS and OS/2 extended file attributes; conversion from Unix to MSDOS text file format; and, of course, the ability to run on most of your favorite operating systems. And it's free. See the file zip30.ann for a summary of new features in Zip 3.0 and WhatsNew for the detailed list of new features and changes since Zip 2.32. The file CHANGES details all day-to-day changes during development. Notes: Multi-volume support. This version does not support multi-volume spanned archives as in pkzip 2.04g, and there is no intention at this point to support spanned archives, but Zip 3.0 supports split archives. A split archive is an archive split into a set of files, each file a piece of the archive and each file using an extension, such as .z02 as in the file name archive.z02, that provides the order of the splits. In contrast, a spanned archive is the original multi-floppy archive supported by pkzip 2.0g where the split order is contained in the volume labels. The contents of split and spanned archives are mostly identical and there is a simple procedure to convert between the formats. Many current unzips now support split archives. Zip64 support. This version supports Zip64 archives as described in the PKWare AppNote. These archives use additional fields to support archives greater than 2 GB and files in archives over the 2 GB previous limit (4 GB on some ports). The Zip64 format also allows more than 64k entries in an archive. Support by the OS for files larger than 4 GB is needed for Zip to create and read large files and archives. On Unix, Win32, and some other ports, large file and Zip64 support is automatically checked for and compiled in if available. Use of Zip64 by Zip is automatic and to maximize backward compatibility the Zip64 fields will only be used if needed. A Zip64 archive requires a pkzip 4.5 compatible unzip, such as UnZip 6.0. Unicode support. This version has initial Unicode support. This allows paths and names of files in other character sets to be accurately recreated on OS that have sufficient character set support. On Win32, if wide character calls are supported (not Win 9x unless Unicode support has been added) all files (including paths with illegal characters in the current character set) should now be readable by zip. Unicode support is provided using a new set of UTF-8 path and comment extra fields and a new UTF-8 bit for flagging when the current character set is already UTF-8. Zip 3.0 maintains backward compatibility with older archives and is mostly compliant with the new Unicode additions in the latest PKWare AppNote. The exception is UTF-8 comments, which are not supported if UTF-8 is not the native character set, but should be fully implemented in Zip 3.1. 16-bit OS support. Though Zip 3.0 is designed to support the latest zip standards and modern OS, some effort has been made to maintain support for older and smaller systems. If you find Zip 3.0 does not fit on or otherwise does not work well on a particular OS, send in the details and we might be able to help. Compression methods. In addition to the standard store and deflate methods, Zip now can use the bzip2 compression format using the bzip2 library. Though bzip2 compression generally takes longer, in many cases using bzip2 results in much better compression. However, many unzips may not yet support bzip2 compressed entries in archives, so test your unzip first before using bzip2 compression. Installation. Please read the file INSTALL for information on how to compile and install zip, zipsplit, zipcloak, and zipnote and please read the manual pages ZIP.txt, ZIPSPLIT.txt, ZIPCLOAK.txt, and ZIPNOTE.txt for information on how to use them. Also, if you are using MSDOS or Windows, note that text files in the distribution are generally in Unix line end format (LF only) and Windows and DOS users will need to either convert the files as needed to DOS line ends (CR LF) or extract the distribution contents using unzip -a. Utilities. At this point zipsplit, zipcloak, and zipnote should work with large files, but they currently do not handle split archives. A work around is to use zip to convert a split archive to a single file archive and then use the utilities on that archive. Encryption. This version supports standard zip encryption. Until recently the encryption code was distributed separately because of the US export regulations but now is part of the main distribution. See crypt.c for details. Decryption can be made with unzip 5.0p1 or later, or with zipcloak. Bug reports. All bug reports or patches should go to zip-bugs via the web site contact form at http://www.info-zip.org/zip-bug.html (we have discontinued the old email address zip-bugs@lists.wku.edu because of too much spam lately) and suggestions for new features can be submitted there also (although we don't promise to use all of them). We also are on SourceForge at http://sourceforge.net/projects/infozip/ and now automatically get Bug Reports and Feature Requests submitted there. In addition, a new Info-ZIP discussion forum is available as well. See below. Though bug reports can be posted there, we don't have automatic monitoring of all postings set up yet so you may want to use the web form or SoureForge for a quicker response. A good approach may be to post the details on the forum so others can benefit from the posting, then use the web reply form to let us know you did that if you don't get a reply in a reasonable time. Ports. If you're considering a port, please check in with zip-bugs FIRST, since the code is constantly being updated behind the scenes. We'll arrange to give you access to the latest source. Discussion group. If you'd like to keep up to date with our Zip (and companion UnZip utility) development, join the ranks of BETA testers, add your own thoughts and contributions, etc., check out the new discussion forum. This is the latest offering, after the various Info-ZIP mailing-lists on mxserver@lists.wku.edu (courtesy of Hunter Goatley) were no longer available and the temporary QuickTopic discussion group for Info-ZIP issues at http://www.quicktopic.com/27/H/V6ZQZ54uKNL died a horrible death due to large amounts of spam. The new discussion forum is now available at http://www.info-zip.org/board/board.pl (thanks again to Hunter Goatley) and can be used to discuss issues, request features, and is one place new betas and releases are announced. It also is a place to post bug reports, and patches can be submitted as attachments. However, we don't yet get automatic notification of all postings there so try one of the other methods if you don't get a response. You can also post Bug Reports and Feature Requests at Source Forge. However, the web site contact form remains available if you would rather not post on the public forums. Frequently asked questions on zip and unzip: Q. When unzipping I get an error message about "compression method 8". A. This is standard deflate, which has been around for awhile. Please get a current version of unzip. See the file 'WHERE' for details. Q. How about "compression method 12"? A. Compression method 12 is bzip2 and requires a relatively modern unzip. Please get the latest version of unzip. Q. I can't extract this zip file that I just downloaded. I get "zipfile is part of multi-disk archive" or some other message. A. Please make sure that you made the transfer in binary mode. Check in particular that your copy has exactly the same size as the original. Note that the above message also may actually mean you have only part of a multi-part archive. Also note that UnZip 5.x does not and UnZip 6.0 probably won't have multi-disk (split) archive support. A work around is to use Zip 3.0 to convert the split archive to a single-file archive then use UnZip on that archive. As a last result, if there's something readable in what you have, zip -FF should be able to recover it. Q. When running unzip, I get a message about "End-of-central-directory signature not found". A. This usually means that your zip archive is damaged, or that you have an uncompressed file with the same name in the same directory. In the first case, it makes more sense to contact the person you obtained the zip file from rather than the Info-ZIP software developers, and to make sure that your copy is strictly identical to the original. In the second case, use "unzip zipfile.zip" instead of "unzip zipfile", to let unzip know which file is the zip archive you want to extract. Q. Why doesn't zip do <something> just like PKZIP does? A. Zip is not a PKZIP clone and is not intended to be one. In some cases we feel PKZIP does not do the right thing (e.g., not including pathnames by default); in some cases the operating system itself is responsible (e.g., under Unix it is the shell which expands wildcards, not zip). Info-ZIP's and PKWARE's zipfiles are interchangeable, not the programs. For example, if you are used to the following PKZIP command: pkzip -rP foo *.c you must use instead on Unix: zip -R foo "*.c" (the quotes are needed to let the shell know that it should not expand the *.c argument but instead pass it on to the program, but are not needed on ports that do not expand file paths like MSDOS) Q. Can I distribute zip and unzip sources and/or executables? A. You may redistribute the latest official distributions without any modification, without even asking us for permission. You can charge for the cost of the media (CDROM, diskettes, etc...) and a small copying fee. If you want to distribute modified versions please contact us at www.Info-ZIP.org first. You must not distribute beta versions. The latest official distributions are always on ftp.Info-ZIP.org in directory /pub/infozip and subdirectories and at SourceForge. Q. Can I use the executables of zip and unzip to distribute my software? A. Yes, so long as it is made clear in the product documentation that zip or unzip are not being sold, that the source code is freely available, and that there are no extra or hidden charges resulting from its use by or inclusion with the commercial product. See the Info-ZIP license for more. Here is an example of a suitable notice: NOTE: <Product> is packaged on this CD using Info-ZIP's compression utility. The installation program uses UnZip to read zip files from the CD. Info-ZIP's software (Zip, UnZip and related utilities) is freely distributed under the Info-ZIP license and can be obtained as source code or executables from various anonymous-ftp sites, including ftp://ftp.info-zip.org/pub/infozip. Q. Can I use the source code of zip and unzip in my commercial application? A. Yes, as long as the conditions in the Info-ZIP license are met. We recommend you include in your product documentation an acknowledgment and note that the original compression sources are available at www.Info-ZIP.org. If you have special requirements contact us. usr/share/doc/perl-File-Fetch-0.42/README 0000644 00000002000 14721025713 0013325 0 ustar 00 This is the README file for File::Fetch, a perl module for generic file fetching. Please refer to 'perldoc File::Fetch' after installation for details. ##################################################################### * Description File::Fetch File::Fetch is a generic file fetching mechanism. It allows you to fetch any file pointed to by a ftp, http or file uri by a number of different means. ##################################################################### * Installation File::Fetch follows the standard perl module install process perl Makefile.PL make make test make install The module uses no C or XS parts, so no c-compiler is required. ###################################################################### AUTHOR This module by Jos Boumans <kane@cpan.org>. COPYRIGHT This module is copyright (c) 2002 Jos Boumans <kane@cpan.org>. All rights reserved. This library is free software; you may redistribute and/or modify it under the same terms as Perl itself. usr/share/doc/psacct-6.6.1/README 0000644 00000007660 14721026014 0012035 0 ustar 00 Welcome to the GNU Accounting Utilities package! This is a set of utilities which reports and summarizes data about user connect times and process execution statistics under u*x. This package contains: ac: summarize login accounting accton: turn process accounting on or off last: show the people who have logged in lastcomm: show which commands have been used sa: summarizes process accounting dump-utmp: print a utmp file in a human-readble format dump-acct: same as above for acct/pacct files See the file `INSTALL' for generic instructions on how to compile and install this software. See the file `NEWS' for late-breaking news about this version. See the file `ChangeLog' for an up-to-date list of source-level modifications. A big thanks to Dirk Eddelbuettel <edd@econ.queensu.ca> for motivation! NOTE: if you're installing this package to replace your system's accounting utilities, you will need to delete the "usracct" and "savacct" files written by your system's sa, as GNU sa is not able to read them (formats vary too widely between systems). ---------------------------------------------------------------------- The usual: * If you run into a bug, please send a "good" bug report -- a message that contains detailed instructions that allow me to reproduce the bug. * If you can make a patch for a particular problem, great! But if you modify more than 10 lines, I need to worry about disclaimers and copyright stuff. Let's try this: if you find a bug, report it and I'll let you know whether or not I've been working on the problem (or want to do so). We can proceed from there. As a maintainer, I want to make sure that folks are not duplicating work. * Straightforward testing: "./configure; make compare" and check the output files (compare-*) in the source directory (should show times and etc.). * If this package isn't finding your utmp/pacct files correctly, check the file configure.in script (files.h is now automatically generated from the results of that script). * Any suggestions for better output from the dump-acct and dump-utmp programs? I'm not sure what format will be easiest to parse. * If you see slightly different numbers for output with GNU sa compared with your system's sa, it's probably due to round-off error (vendor utils use floats, we use doubles). Check it, however, and send me a report. * PLEASE SUGGEST FEATURES THAT YOU WOULD LIKE! I realize that the standard options aren't great, so I'm looking for suggestions to make the output more digestible. Would anyone be interested in scripts/options to produce graphic output (postscript, xplot, gnuplot, etc.)? Coming up: * The next major release will introduce utmpx support for those of you lucky enough to have it. It's good to know that people are willing to donate their time and effort to getting the GNU Accounting Utilities up and working on many machines. Thanks a lot for the help! -Noel Noel Cragg \\ 6244 Aberdeen Avenue \\ Goleta CA 93117-2002 \\ 805 964 1892 noel@cs.oberlin.edu \\ noel@red-bean.com \\ noel@gnu.ai.mit.edu ---------------------------------------------------------------------- The GNU Accounting Utilities are Copyright (C) 1993, 1996, 1997, 2008, 2009, 2010 Free Software Foundation, Inc. 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, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. usr/share/doc/slang-2.2.4/README 0000644 00000002204 14721026055 0011651 0 ustar 00 The documentation here is provided in text format. Documentation in SGML, HTML, TeX, and postscript formats are also available from <ftp://space.mit.edu/pub/davis/slang/v2.0/slang-doc.tar.gz> as well as the mirror sites. In addition, the documentation is available on-line from <http://www.jedsoft.org/slang/docs.html>. The text subdirectory contains: text/slang.txt Documentation describing the slang language text/cslang.txt C programmer's guide to the library text/cref.txt Reference Manual for the C functions text/slangfun.txt Reference Manual for the slang intrinsic functions There may be additional subdirectories: tm/ Text-Macro source for documentation html/ Documentation in HTML form text/ Documentation in text form ps/ Documentation in postscript (from LaTeX) pdf/ Documentation in postscript (from pdflatex) The documentation was created by linuxdoc-tools from an SGML format, which itself was created from text-macro source. The LaTeX2e output produced by linuxdoc-tools needed some additional tweaking by the script tm/fixtex.sl. usr/share/doc/rpcbind-0.2.0/README 0000644 00000000160 14721026101 0012147 0 ustar 00 This release was a native source release from Sun. It has been ported from FreeBSD 5.2.1 to GNU/Linux in 2004. usr/share/doc/readline-6.2/README 0000644 00000017000 14721026164 0012173 0 ustar 00 Introduction ============ This is the Gnu Readline library, version 6.2. The Readline library provides a set of functions for use by applications that allow users to edit command lines as they are typed in. Both Emacs and vi editing modes are available. The Readline library includes additional functions to maintain a list of previously-entered command lines, to recall and perhaps reedit those lines, and perform csh-like history expansion on previous commands. The history facilites are also placed into a separate library, the History library, as part of the build process. The History library may be used without Readline in applications which desire its capabilities. The Readline library is free software, distributed under the terms of the [GNU] General Public License as published by the Free Software Foundation, version 3 of the License. For more information, see the file COPYING. To build the library, try typing `./configure', then `make'. The configuration process is automated, so no further intervention should be necessary. Readline builds with `gcc' by default if it is available. If you want to use `cc' instead, type CC=cc ./configure if you are using a Bourne-style shell. If you are not, the following may work: env CC=cc ./configure Read the file INSTALL in this directory for more information about how to customize and control the build process. The file rlconf.h contains C preprocessor defines that enable and disable certain Readline features. The special make target `everything' will build the static and shared libraries (if the target platform supports them) and the examples. Examples ======== There are several example programs that use Readline features in the examples directory. The `rl' program is of particular interest. It is a command-line interface to Readline, suitable for use in shell scripts in place of `read'. Shared Libraries ================ There is skeletal support for building shared versions of the Readline and History libraries. The configure script creates a Makefile in the `shlib' subdirectory, and typing `make shared' will cause shared versions of the Readline and History libraries to be built on supported platforms. If `configure' is given the `--enable-shared' option, it will attempt to build the shared libraries by default on supported platforms. Configure calls the script support/shobj-conf to test whether or not shared library creation is supported and to generate the values of variables that are substituted into shlib/Makefile. If you try to build shared libraries on an unsupported platform, `make' will display a message asking you to update support/shobj-conf for your platform. If you need to update support/shobj-conf, you will need to create a `stanza' for your operating system and compiler. The script uses the value of host_os and ${CC} as determined by configure. For instance, FreeBSD 4.2 with any version of gcc is identified as `freebsd4.2-gcc*'. In the stanza for your operating system-compiler pair, you will need to define several variables. They are: SHOBJ_CC The C compiler used to compile source files into shareable object files. This is normally set to the value of ${CC} by configure, and should not need to be changed. SHOBJ_CFLAGS Flags to pass to the C compiler ($SHOBJ_CC) to create position-independent code. If you are using gcc, this should probably be set to `-fpic'. SHOBJ_LD The link editor to be used to create the shared library from the object files created by $SHOBJ_CC. If you are using gcc, a value of `gcc' will probably work. SHOBJ_LDFLAGS Flags to pass to SHOBJ_LD to enable shared object creation. If you are using gcc, `-shared' may be all that is necessary. These should be the flags needed for generic shared object creation. SHLIB_XLDFLAGS Additional flags to pass to SHOBJ_LD for shared library creation. Many systems use the -R option to the link editor to embed a path within the library for run-time library searches. A reasonable value for such systems would be `-R$(libdir)'. SHLIB_LIBS Any additional libraries that shared libraries should be linked against when they are created. SHLIB_LIBPREF The prefix to use when generating the filename of the shared library. The default is `lib'; Cygwin uses `cyg'. SHLIB_LIBSUFF The suffix to add to `libreadline' and `libhistory' when generating the filename of the shared library. Many systems use `so'; HP-UX uses `sl'. SHLIB_LIBVERSION The string to append to the filename to indicate the version of the shared library. It should begin with $(SHLIB_LIBSUFF), and possibly include version information that allows the run-time loader to load the version of the shared library appropriate for a particular program. Systems using shared libraries similar to SunOS 4.x use major and minor library version numbers; for those systems a value of `$(SHLIB_LIBSUFF).$(SHLIB_MAJOR)$(SHLIB_MINOR)' is appropriate. Systems based on System V Release 4 don't use minor version numbers; use `$(SHLIB_LIBSUFF).$(SHLIB_MAJOR)' on those systems. Other Unix versions use different schemes. SHLIB_DLLVERSION The version number for shared libraries that determines API compatibility between readline versions and the underlying system. Used only on Cygwin. Defaults to $SHLIB_MAJOR, but can be overridden at configuration time by defining DLLVERSION in the environment. SHLIB_DOT The character used to separate the name of the shared library from the suffix and version information. The default is `.'; systems like Cygwin which don't separate version information from the library name should set this to the empty string. SHLIB_STATUS Set this to `supported' when you have defined the other necessary variables. Make uses this to determine whether or not shared library creation should be attempted. You should look at the existing stanzas in support/shobj-conf for ideas. Once you have updated support/shobj-conf, re-run configure and type `make shared'. The shared libraries will be created in the shlib subdirectory. If shared libraries are created, `make install' will install them. You may install only the shared libraries by running `make install-shared' from the top-level build directory. Running `make install' in the shlib subdirectory will also work. If you don't want to install any created shared libraries, run `make install-static'. Documentation ============= The documentation for the Readline and History libraries appears in the `doc' subdirectory. There are three texinfo files and a Unix-style manual page describing the facilities available in the Readline library. The texinfo files include both user and programmer's manuals. HTML versions of the manuals appear in the `doc' subdirectory as well. Reporting Bugs ============== Bug reports for Readline should be sent to: bug-readline@gnu.org When reporting a bug, please include the following information: * the version number and release status of Readline (e.g., 4.2-release) * the machine and OS that it is running on * a list of the compilation flags or the contents of `config.h', if appropriate * a description of the bug * a recipe for recreating the bug reliably * a fix for the bug if you have one! If you would like to contact the Readline maintainer directly, send mail to bash-maintainers@gnu.org. Since Readline is developed along with bash, the bug-bash@gnu.org mailing list (mirrored to the Usenet newsgroup gnu.bash.bug) often contains Readline bug reports and fixes. Chet Ramey chet.ramey@case.edu etc/pki/ca-trust/extracted/openssl/README 0000644 00000001423 14721026410 0014167 0 ustar 00 This directory /etc/pki/ca-trust/extracted/openssl/ contains CA certificate bundle files which are automatically created based on the information found in the /usr/share/pki/ca-trust-source/ and /etc/pki/ca-trust/source/ directories. All files are in the BEGIN/END TRUSTED CERTIFICATE file format, as described in the x509(1) manual page. If your application isn't able to load the PKCS#11 module p11-kit-trust.so, then you can use these files in your application to load a list of global root CA certificates. Please never manually edit the files stored in this directory, because your changes will be lost and the files automatically overwritten, each time the update-ca-trust command gets executed. Please refer to the update-ca-trust(8) manual page for additional information. usr/share/doc/gdisk-0.8.10/README 0000644 00000032034 14721026463 0011736 0 ustar 00 GPT fdisk (aka gdisk, cgdisk, and sgdisk) and FixParts by Roderick W. Smith, rodsmith@rodsbooks.com Introduction ------------ This package includes the source code for four related disk partitioning programs: - gdisk -- This program is modeled after Linux fdisk, but it operates on GUID Partition Table (GPT) disks rather than the Master Boot Record (MBR) disks that fdisk modifies. As such, gdisk is an interactive text-mode tool for manipulating partitions, but it does nothing to the contents of those partitions (usually filesystems, but sometimes swap space or other data). - cgdisk -- This program is modeled after Linux cfdisk, but it operates on GPT disks rather than the MBR disks that cfdisk modifies. As such, cgdisk is a curses-based text-mode tool for manipulating partitions, which is to say that it uses an interface that relies on arrow keys and a dynamic display rather than the command letters and a scrolling display like gdisk uses. - sgdisk -- This program is conceptually similar to the Linux sfdisk and FreeBSD gpt programs, but its operational details differ. It enables manipulation of GPT disks using command-line options, so it's suitable for use in scripts or by experts to perform specific tasks that might take several commands in gdisk to accomplish. - fixparts -- This program, unlike the preceding three, operates on MBR disks. It's intended to fix certain problems that can be created by various utilities. Specifically, it can fix mis-sized extended partitions and primary partitions located in the middle of extended partitions. It also enables changing primary vs. logical partition status (within limits of what's legal in the MBR scheme) and making a few other minor changes. It does NOT support creating new partitions; for that, you should use fdisk, parted, or some other tool. More details about the abilities of these tools follows. All four programs rely on the same set of underlying code base; they differ only in their control interfaces (defined in gdisk.cc, cgdisk.cc, sgdisk.cc, and fixparts.cc, respectively) and in which support code they use. GPT fdisk (gdisk, cgdisk, and sgdisk) Details --------------------------------------------- The gdisk program is intended as a (somewhat) fdisk-workalike program for GPT-partitioned disks, cgdisk is similarly a workalike for fdisk, and sgdisk provides most of gdisk's functionality in a more script-friendly program. Although libparted and programs that use it (GNU Parted, gparted, etc.) provide the ability to handle GPT disks, they have certain limitations that gdisk overcomes. Specific advantages of gdisk, cgdisk, and sgdisk include: * The ability to convert MBR-partitioned disks in-place to GPT format, without losing data * The ability to convert BSD disklabels in-place to create GPT partitions, without losing data * The ability to convert from GPT format to MBR format without data loss (gdisk and sgdisk only) * More flexible specification of filesystem type code GUIDs, which GNU Parted tends to corrupt * Clear identification of the number of unallocated sectors on a disk * A user interface that's familiar to long-time users of Linux fdisk and cfdisk (gdisk and cgdisk only) * The MBR boot loader code is left alone * The ability to create a hybrid MBR, which permits GPT-unaware OSes to access up to three GPT partitions on the disk (gdisk and sgdisk only) Of course, GPT fdisk isn't without its limitations. Most notably, it lacks the filesystem awareness and filesystem-related features of GParted. You can't resize a partition's filesystem or create a partition with a filesystem already in place with gdisk, for instance. There's no GUI version of gdisk. The GPT fdisk package provides three program files: the interactive text-mode gdisk, the curses-based interactive cgdisk, and the command-line-driven sgdisk. The first two are intended for use in manually partitioning disks or changing partitioning details; sgdisk is intended for use in scripts to help automate tasks such as disk cloning or preparing multiple disks for Linux installation. FixParts Details ---------------- This program's creation was motivated by cries for help I've seen in online forums from users who have found their partition tables to be corrupted by various buggy partitioning tools. Although most OSes can handle the afflicted disks fine, libparted-based tools (GParted, parted, most Linux installers, etc.) tend to flake out when presented with these disks. Typically, the symptom is a disk that appears to hold no partitions; however, sometimes the libparted tool presents partitions other than those that the OS sees. I've observed four causes of these symptoms, three of which FixParts can correct: * Old GPT data -- If a disk is used as a GPT disk and then re-used as an MBR disk, the GPT data may be incompletely erased. This happens if the disk is repartitioned with fdisk or the Microsoft Windows installer, for instance. (Tools based on libparted correctly remove the old GPT data when converting from GPT to MBR format.) FixParts checks for this problem when it starts and offers to correct it. If you opt to erase the GPT data, this erasure occurs immediately, unlike other changes the program makes. * Mis-sized extended partitions -- Some tools create an extended partition that's too large, typically ending after the last sector of the disk. FixParts automatically corrects this problem (if you use the 'w' option to save the partition table). * Primary partitions inside an extended partition -- Some utilities create or move primary partitions to within the range covered by the extended partition. FixParts can usually correct this problem by turning the primary partition into a logical partition or by changing one or more other logical partitions into primaries. Such corrections aren't always possible, though, at least not without deleting or resizing other partitions. * Leftover RAID data -- If a disk is used in a RAID array and then re-used as a non-RAID disk, some utilities can become confused and fail to see the disk. FixParts can NOT correct this problem. You must destroy the old RAID data, or possibly remove the dmraid package from the system, to fix this problem. When run, FixParts presents an fdisk-like interface, enabling you to adjust partition types (primary, logical, or omitted), change type codes, change the bootable flag, and so on. Although you can delete a partition (by omitting it), you can't create new partitions with the program. If you're used to partitioning disks, particularly with Linux fdisk, two unusual features of FixParts require elaboration: * No extended partitions -- Internally, FixParts reads the partition table and discards data on any extended partition(s) it finds. When you save the partition table, the program generates a new extended partition. This design means that the program automatically corrects many problems related to the extended partition. It also means that you'll see no evidence of extended partitions in the FixParts user interface, although it keeps track of the requirements and prevents you from creating illegal layouts, such as a primary between two logicals. * Partition numbering -- In most Linux tools, partitions 1-4 are primaries and partitions 5 and up are logicals. Although a legal partition table loaded into FixParts will initially conform to this convention, some types of damaged table might not, and various changes you make can also cause deviations. When FixParts writes the partition table, its numbering will be altered to conform to the standard MBR conventions, but you should use the explicit labeling of partitions as primary or logical rather than the partition numbers to determine a partition's status. Installing ---------- To compile GPT fdisk, you must have appropriate development tools installed, most notably the GNU Compiler Collection (GCC) and its g++ compiler for C++. I've also tested compilation with Clang, which seems to work; however, I've not done extensive testing of the resulting binaries, beyond checking a few basics. Under Windows, Microsoft Visual C++ 2008 can be used instead. In addition, note these requirements: * On Linux, FreeBSD, OS X, and Solaris, libuuid must be installed. This is the standard for Linux and OS X, although you may need to install a package called uuid-dev or something similar to get the headers. On FreeBSD, the e2fsprogs-libuuid port must be installed. * The ICU library (http://site.icu-project.org), which provides support for Unicode partition names, is optional on all platforms except Windows, on which it's not supported. Using this library was required to get proper UTF-16 partition name support in GPT fdisk versions prior to 0.8.9, but as of that version it should not longer be required. Nonetheless, you can use it if you're having problems with the new UTF-16 support. This library is normally installed in Linux and OS X, but you may need to install the development headers (libicu-dev or something similar in Linux; or the libicu36-dev Fink package in OS X). To compile with ICU support, you must modify the Makefile: Look for commented-out lines that refer to USE_UTF16, -licuuc, -licudata, or -licucore. Uncomment them and comment out the equivalents that lack these lines. * The cgdisk program requires the ncurses library and its development files (headers). Most Linux distributions install ncurses by default, but you may need to install a package called libncurses5-dev, ncurses-devel, or something similar to obtain the header files. These files were installed already on my Mac OS X development system; however, they may have been installed as dependencies of other programs I've installed. If you're having problems installing ncurses, you can compile gdisk and/or sgdisk without cgdisk by specifying only the targets you want to compile to make. * The sgdisk program requires the popt library and its development files (headers). Most Linux distributions install popt by default, but you may need to install a package called popt-dev, popt-devel, or something similar to obtain the header files. Mac OS users can find a version of popt for Mac OS from Darwin Ports (http://popt.darwinports.com) or Fink (http://www.finkproject.org); however, you'll first need to install DarwinPorts or Fink (instructions exist on the relevant projects' pages). Alternatively, you can compile gdisk and/or cgdisk alone, without sgdisk; gdisk doesn't require popt. When all the necessary development tools and libraries are installed, you can uncompress the package and type "make" at the command prompt in the resulting directory. (You may need to type "make -f Makefile.mac" on Mac OS X, "make -f Makefile.freebsd" on FreeBSD, "make -f Makefile.solaris" on Solaris, or "make -f Makefile.mingw" to compile using MinGW for Windows.) You may also need to add header (include) directories or library directories by setting the CXXFLAGS environment variable or by editing the Makefile. The result should be program files called gdisk, cgdisk, sgdisk, and fixparts. Typing "make gdisk", "make cgdisk", "make sgdisk", or "make fixparts" will compile only the requested programs. You can use these programs in place or copy the files to a suitable directory, such as /usr/local/sbin. You can copy the man pages (gdisk.8, cgdisk.8, sgdisk.8, and fixparts.8) to /usr/local/man/man8 to make them available. Caveats ------- THIS SOFTWARE IS BETA SOFTWARE! IF IT WIPES OUT YOUR HARD DISK OR EATS YOUR CAT, DON'T BLAME ME! To date, I've tested the software on several USB flash drives, physical hard disks, and virtual disks in the QEMU and VirtualBox environments. Many others have now used the software on their computers, as well. I believe all data-corruption bugs to be squashed, but I know full well that the odds of my missing something are high. This is particularly true for large (over-2TiB) drives; my only direct testing with such disks is with virtual QEMU and VirtualBox disks. I've received user reports of success with RAID arrays over 2TiB in size, though. My main development platform is a system running the 64-bit version of Gentoo Linux. I've also tested on several other 32- and 64-bit Linux distributions, Intel-based Mac OS X 10.5 and 10.6, 64-bit FreeBSD 7.1, and Windows 7. Redistribution -------------- This program is licensed under terms of the GNU GPL (see the file COPYING). Acknowledgements ---------------- This code is mostly my own; however, I've used three functions from two other GPLed programs: - The code used to generate CRCs is taken from the efone program by Krzysztof Dabrowski and ElysiuM deeZine. (See the crc32.h and crc32.cc source code files.) - A function to find the disk size is taken from Linux fdisk by A. V. Le Blanc. This code has subsequently been heavily modified. Additional code contributors include: - Yves Blusseau (1otnwmz02@sneakemail.com) - David Hubbard (david.c.hubbard@gmail.com) - Justin Maggard (justin.maggard@netgear.com) - Dwight Schauer (dschauer@ti.com) - Florian Zumbiehl (florz@florz.de) - Guillaume Delacour (contributed the gdisk_test.sh script) usr/share/doc/perl-Crypt-DES-2.05/README 0000644 00000006012 14721026521 0013137 0 ustar 00 Crypt::DES - an XS-based DES implimentation for Perl. The 2.XX tree represents a major improvement over the 1.XX tree. This package builds on big-endian machines and many more x86 platforms than before. (with a few rare exceptions, like gcc on DUX against 5.004). mod_ssl conflicts have also been resolved. Thank you to Jan 'Kozo' Vajda for pointing out the des_SPtrans overlap between these two packages. In release 2.04, des.h was renamed to _des.h in an attempt to solve the build-on-Solaris problem. Reports would be appreciated. In release 2.05, all references to des_ were changed to _des_ since the 2.04 release didn't seem to fix the problem on Solaris. Prerequisites ------------- For the full test suite to run, Crypt::CBC, version 1.22 or higher is required (recommended is 1.25 or higher), however this module is not mandatory for standalone DES use, and all other tests will run to completion. Installing Crypt::DES --------------------- nothing unusual: 1. perl Makefile.PL 2. make 3. make test 4. make install Notes ----- The following is a list of known good platforms: FreeBSD 3.5-RELEASE / x86 / 5.005 OpenBSD 2.7 / x86 / 5.6 Linux / x86 / 5.005 & 5.6 Linux / PPC / 5.005 & 5.6 Solaris7 / SPARC / 5.005 Solaris / x86 / 5.005 DUX / Alpha / 5.005 (using DEC cc) Win32 / x86 / 5.005 (using VC++5) OS/2 / x86 / 5.6 Reports of builds against 5.004 have been equally positive. Building on Win32 with VC++6 may prove problematic. Complaints about build problems on Win32 will be sent to /dev/null. Please report any other successful OS/Platform combinations to amused@pobox.com. Thank you. What you can expect in the way of speed: Linux/x86 dual PII400 non-cached cipher speed test. 5000 encrypt iterations 0 wallclock secs ( 0.52 usr + 0.01 sys = 0.53 CPU) non-cached cipher speed test. 5000 decrypt iterations 1 wallclock secs ( 0.52 usr + 0.01 sys = 0.53 CPU) cached cipher speed test. 10000 encrypt iterations 0 wallclock secs ( 0.20 usr + 0.00 sys = 0.20 CPU) cached cipher speed test. 10000 decrypt iterations 0 wallclock secs ( 0.22 usr + 0.00 sys = 0.22 CPU) Windows NT4(SP6)/x86 dual PPro 200 non-cached cipher speed test. 5000 encrypt iterations 1 wallclock secs ( 1.25 usr + 0.00 sys = 1.25 CPU) non-cached cipher speed test. 5000 decrypt iterations 2 wallclock secs ( 1.22 usr + 0.00 sys = 1.22 CPU) cached cipher speed test. 10000 encrypt iterations 0 wallclock secs ( 0.58 usr + 0.00 sys = 0.58 CPU) cached cipher speed test. 10000 decrypt iterations 1 wallclock secs ( 0.59 usr + 0.00 sys = 0.59 CPU) Solaris7/SPARC UltraSPARCIIi 277Mhz non-cached cipher speed test. 5000 encrypt iterations 1 wallclock secs ( 1.08 usr + 0.20 sys = 1.28 CPU) non-cached cipher speed test. 5000 decrypt iterations 2 wallclock secs ( 1.14 usr + 0.12 sys = 1.26 CPU) cached cipher speed test. 10000 encrypt iterations 0 wallclock secs ( 0.52 usr + 0.00 sys = 0.52 CPU) cached cipher speed test. 10000 decrypt iterations 1 wallclock secs ( 0.50 usr + 0.00 sys = 0.50 CPU) usr/share/doc/rcs-5.9.0/README 0000644 00000025756 14721026616 0011366 0 ustar 00 Welcome! ======== This directory contains sources and documentation for GNU RCS. GNU RCS (Revision Control System) manages multiple revisions of files. RCS can store, retrieve, log, identify, and merge revisions. It is useful for files that are revised frequently, e.g., programs, documentation, graphics, and papers. See the following files and directories for more information. AUTHORS - authorship information COPYING - copying conditions INSTALL - generic installation instructions NEWS - recent changes doc/ - documentation in info format, plus source (texinfo) lib/ - portability code, from gnulib m4/ - configure script infrastructure, from gnulib man/ - manual page entries, plus source src/ - source code for programs tests/ - test suite Prerequisites and compatibility issues ====================================== RCS requires a diff that supports the -n option. Get GNU diffutils (version 2.7 or later) if your diff lacks -n. RCS works best with a diff that supports -a and --label, and a diff3 that supports -A, -E and -m. GNU diffutils supports these options. RCS version 5 reads RCS files written by any RCS version released since 1982. It also writes RCS files that these older versions of RCS can read, unless you use one of the following new features: - checkin dates after 1999-12-31 - checking in non-text files - identifiers containing ‘.’ or non-ASCII bytes, or starting with a digit - ‘rcs -bX’, where X is nonempty - ‘rcs -kX’, where X is not ‘kv’ - RCS files that exceed hardcoded limits in older RCS versions A working file written by RCS 5.5 or later contains four-digit years in its keyword strings. If you check out a working file with RCS 5.5 or later, an older RCS version's ‘ci -k’ may insist on two-digit years. Similarly, a working file written with ‘-zZONE’ contains times in its keyword strings that older ‘ci -k’s may not understand. Work around this with ‘co -V4 -z’, or edit the working file. RCS should run on any host that conforms to the POSIX 1003.1-1990 standard. It also runs on a wide variety of non-POSIX hosts. Configuration and installation ============================== See INSTALL for general instructions on configuring and building RCS. Use ‘configure --help’ to see a list of options for customizing the installation directories (.e.g, --prefix). * Another option is ‘--enable-compat2’. It enables reading RCS 2.x file formats. Most likely you can safely ignore this (that file format became obsolete in 1982). However, if you do indeed find a version 2 file around, you can migrate the file to a recent format as follows: Suppose the working file was ‘f.c’; rename the RCS file ‘f.c.v’ to ‘f.c,v’, and the RCS file ‘f.v’ to ‘f.c,v’. Thus suffixes are no longer dropped and RCS files end in ‘,v’ rather than ‘.v’. After all version 2 RCS files have been updated with new versions of ci or rcs, you can remake RCS with --enable-compat2=no. !!! NB: This option (and 2.x compatability) will be removed soon. * Another option is ‘--with-mailer=PROG’. This specifies that PROG (an absolute filename if not findable on PATH) should be used to send mail to the original locker when a lock is broken. PROG will be called with one argument, the recipient, and its standard input will be: Subject: Broken lock on <FILENAME> <REASON> That is, the first line is the subject, followed by an empty line, followed by the message body. Omitting this option disables sending mail. * For speed, RCS uses the ‘mmap’ system call if available. Unfortunately, many mmap implementations are broken. For instance, mmap does not work properly in HP-UX 8 or 9, or in Solaris 2.4, without kernel patches. We don't know details about the bugs, so we can't test for them automatically. You can build RCS without mmap by specifying ‘--disable-mmap’ to the configure script. * By default, RCS supports running its commands setuid, using ‘seteuid’. If your ‘seteuid’ (typically on older BSDs, e.g., SunOS 3.5) does not let you switch back and forth between any pair of users as specified in POSIX 1003.1a Draft 5, you should specify ‘--enable-suid=setreuid’, instead. (One must be root to test this reliably, so the configure script just checks availability.) To build RCS without setuid support, specify ‘--disable-suid’. !!! NB: Support for setuid operation will be removed in GNU RCS 6.x. !!! NB: Don't run RCS setuid under AIX 3.2 if you use NFS, since it's badly broken. To see the AIX 3.2 bug, run the following program setuid X where the NFS file "abc" already exists, owned by X, permission -rw-r--r--, and where the invoker is not X. #include <stdio.h> int main () { FILE *f = fopen ("abc", "w"); setuid (getuid ()); fputc ('\n', f); if (fclose (f) != 0) perror ("fclose"); } The program fails with "fclose: Permission denied". If your system type is in the following list, look for the corresponding strings in the notes below before configuring. system type - identifiers ------------------------------------ AIX 3.2 - --prefix=/usr GCC 2.5.8 Intel x86 - CFLAGS HP-UX 8.07 and 9.* - MMAP_SIGNAL Solaris 2.4 - MMAP_SIGNAL SCO Unix V.3.2 - bad_NFS_rename Ultrix - HAVE_SETEUID If the configure script tells you that your platform might be desupported in the future, then consider yourself very lucky! As a courageous builder of free software you are now empowered to clue in the RCS maintainer on the desirability of continued support for your platform, thereby quietening your fears and increasing the connectedness of the RCS-using community. You do this by mailing the warning text output by the configure script to bug-rcs@gnu.org, with a suitably detailed (i.e., optional) explanation of your platform, including why it should (or shouldn't) be supported. If building succeeds, do "make check" (optional) and "make install". To check the installation, do "make installcheck". AIX NOTE: Do not configure with ‘--prefix=/’ or ‘--prefix=/usr’ in AIX. An AIX boot shell script (/etc/rc.boot4 in AIX 3.2) invokes ‘merge’, meaning /etc/merge, and fails if RCS merge is installed in /bin or /usr/bin. IBM says that installing new programs into /usr/bin is a customer error (!). Configuration environment ========================= The configuration procedure normally inspects the current host to determine how RCS is to be built. The variables listed in this section override this default. They should be specified on the configure script command-line, like so: $ ./configure [--prefix and other options...] VAR=VALUE VAR=VALUE CC is the name of your C compiler. CPPFLAGS are C preprocessor options. CFLAGS are C compiler options that do not affect correctness, typically options that affect optimization or debugging. Omit -O if your compiler's optimizer is not trustworthy (e.g. GCC 2.5.8 x86). If your ancient BSD compiler has the -R option, -R can improve performance by making all initialized data read-only (not just string literals); modern compilers don't need this, since they have ‘const’. DIFF is the name of your diff program. It's normally best to use GNU diffutils. On some versions of Unix, the standard diff does not support RCS and you must instead use diffutils, or something like /usr/lib/rdiff. DIFF3 is the name of the diff3 program. With GNU diffutils, this is simply its user-visible diff3 program. But with traditional diff3 it is the name of the undocumented diff3 auxiliary, whose name is /usr/lib/diff3 or /usr/5lib/rdiff3prog or something similar. INSTALL is the command that installs commands, e.g. ‘../install-sh’. INSTALL_DATA installs data, and INSTALL_PROGRAM installs programs. SOELIM is the name of your soelim program. This is typically the standard one from groff. It is used only if you edit man/*.[15]in or make ‘maintainer-clean’. PIC is the name of your pic program, configured to avoid extensions so that a portable man page is generated. This is typically GNU pic with the ‘-n’ option, or traditional pic with ‘-D’. It is used only if you edit the documentation or make ‘maintainer-clean’. cross-compilation ================= There are several variables set by the configure script that are assigned "pessimistic" defaults when cross-compiling (info "(autoconf) Runtime"): (variable) (value) rcs_cv_tinyinit_ok no rcs_cv_fopen_truncates no rcs_cv_wac_ok no rcs_cv_unlink_mw_ok no rcs_cv_rename_mw hopeless rcs_cv_sane_mmap no rcs_cv_mmap_signal unknown rcs_cv_tolerant_wait no To set the "correct" value for a particular VAR, overriding its default, you can specify VAR=VALUE on the configure script command-line. For example: ./configure \ rcs_cv_tinyinit_ok=yes \ rcs_cv_unlink_mw_ok=no Note that the value of ‘rcs_cv_mmap_signal’ has meaning only if ‘rcs_cv_sane_mmap’ is ‘yes’. Valid values are documented only in the configure script source, i.e., configure.ac -- don't guess, use the Source! If you get good results cross-compiling, with or without such variable overrides, please consider sharing the good news by posting the configure script invocation to the bug-report address with subject "cross-compilation success" or similar. src/base.h notes ================ This section covers unusual situations requiring hand patches to src/base.h. bad_NFS_rename - Some buggy NFS file servers (e.g. some NAC releases) can report that rename(A,B) succeeded even though it failed. Set bad_NFS_rename to nonzero to work around the problem. Warning: the workaround introduces a rare race condition that can falsely report I/O errors; this is why the workaround is disabled unless you specify otherwise. has_NFS - Set this if the target host might use NFS. NFS's ``stateless server'' protocol has well-known problems with the non-idempotent operations link(2), rename(2), and unlink(2). For example, unlink(2) can run twice on the NFS server, causing the client to think that the unlink failed with errno==ENOENT. has_NFS enables code that works around these problems. However, has_NFS does not work around NFS implementation bugs; if your NFS implementation is buggy, get another! For example, make sure that your NFS uses UDP checksums, if it uses UDP. Modern systems checksum by default; ask your vendor if you're not sure. bad_NFS_rename - This should be 1 in SCO Unix V.3.2. Its NFS rename(2) is broken, but if configure runs in a non-NFS file system, it thinks rename(2) works. TZ_must_be_set - set this to 1 on hosts where gmtime(3) yields bogus values unless the TZ environment variable is set. X_DEFAULT - This is normally ",v/" on Unix hosts, and "" on hosts that do not allow commas in file names (e.g. DOS). Copyright (C) 2010-2013 Thien-Thi Nguyen Copying and distribution of this file, with or without modification, are permitted provided the copyright notice and this notice are preserved. usr/share/doc/net-snmp-libs-5.7.2/README 0000644 00000032521 14721026703 0013250 0 ustar 00 README file for net-snmp Version: 5.7.2 DISCLAIMER The Authors assume no responsibility for damage or loss of system performance as a direct or indirect result of the use of this software. This software is provided "as is" without express or implied warranty. TABLE OF CONTENTS Disclaimer Table Of Contents Introduction * Supported Architectures Availability Web Page * Installation Copying And Copyrights * Frequently Asked Questions Helping Out * Code Update Announcements * Mailing Lists Agent Extensibility Example Agent Configuration and Usage Configuration Submitting Bug Reports Closing Thanks * = Required Reading. INTRODUCTION This package was originally based on the CMU 2.1.2.1 snmp code. It has been greatly modified, restructured, enhanced and fixed. It hardly looks the same as anything that CMU has ever released. It was renamed from cmu-snmp to ucd-snmp in 1995 and later renamed from ucd-snmp to net-snmp in November 2000. This README file serves as a starting place to learn about the package, but very little of the documentation is contained within this file. The FAQ is an excellent place to start as well. Additionally, there are a bunch of README files for specific architectures and specific features. You might wish to look at some of these other files as well. SUPPORTED ARCHITECTURES Please see the FAQ for this information. Please let us know if you compile it on other OS versions and it works for you so we can add them to the above list. Porting: Please! read the PORTING file. Also note that many architecture have architecture specific README files, so you should check to see if there is one appropriate to your platform. AVAILABILITY Download: - http://www.net-snmp.org/download/ - ftp://ftp.net-snmp.org/pub/sourceforge/net-snmp/ Web page: - http://www.net-snmp.org/ Project Wiki: - http://www.net-snmp.org/wiki/ Sourceforge Project page: - http://sourceforge.net/projects/net-snmp Mirrors: - US: ftp://ftp.freesnmp.com/mirrors/net-snmp/ The old ucd-snmp.ucdavis.edu web site and ftp server is now offline and should not be accessed any longer. WEB PAGES http://www.net-snmp.org/ http://sourceforge.net/projects/net-snmp http://www.net-snmp.org/wiki/ INSTALLATION See the INSTALL file distributed with this package. COPYING AND COPYRIGHTS See the COPYING file distributed with this package. FREQUENTLY ASKED QUESTIONS See the FAQ file distributed with this package. This is also available on the project Wiki at http://www.net-snmp.org/wiki/index.php/FAQ so that the wider Net-SNMP community can help maintain it! HELPING OUT This is a project worked on by people around the net. We'd love your help, but please read the PORTING file first. Also, subscribe to the net-snmp-coders list described below and mention what you're going to work on to make sure no one else is already doing so! You'll also need to keep up to date with the latest code snap shot, which can be obtained from CVS using the information found at http://www.net-snmp.org/cvs/. Contributions to the Net-SNMP source code in any form are greatly appreciated. We expect the parties providing such contributions to have the right to contribute them to the Net-SNMP project or that the parties that do have the right have directed the person submitting the contribution to do so. In addition, all contributors need to be aware that if the contribution is accepted and incorporated into the Net-SNMP project, it will be redistributed under the terms of the license agreement used for the entire body of work that comprises the Net-SNMP project (see the COPYING file for details). If this license agreement ever changes the contribution will continue to be released under any new licenses as well. Thank you, in advance, for your gracious contributions. CODE UPDATE ANNOUNCEMENTS See the NEWS file and the ChangeLog file for details on what has changed between releases. We hate broadcasting announce messages to other mailing lists and newsgroups, so there is a mailing list set up to handle release announcements. Any time we put new software out for ftp, we'll mail this fact to net-snmp-announce@lists.sourceforge.net. See the MAILING LISTS section described below to sign up for these announcements. We will post new announcements on a very infrequent basis to the other channels (the other snmp mailing lists and newsgroups like comp.protocols.snmp), but only for major code revisions and not for bug-fix patches or small feature upgrades. MAILING LISTS The lists: A number of mailing lists have been created for support of the project: The main ones are: net-snmp-announce@lists.sourceforge.net -- For official announcements net-snmp-users@lists.sourceforge.net -- For usage discussions net-snmp-coders@lists.sourceforge.net -- For development discussions The -coders list is intended for discussion on development of code that will be shipped as part of the package. The -users list is for general discussion on configuring and using the package, including issues with coding user-developed applications (clients, managers, MIB modules, etc). Please do *NOT* send messages to both -users and -coders lists. This is completely unnecessary, and simply serves to further overload (and annoy) the core development team. If in doubt, just use the -users list. The other lists of possible interest are: net-snmp-cvs@lists.sourceforge.net -- For cvs update announcements net-snmp-bugs@lists.sourceforge.net -- For Bug database update announcements net-snmp-patches@lists.sourceforge.net -- For Patch database update announcements Please do NOT post messages to these lists (or to the announce list above). Bug reports and Patches should be submitted via the Source Forge tracker system. See the main project web pages for details. To subscribe to any of these lists, please see: http://www.net-snmp.org/lists/ Archives: The archives for these mailing lists can be found by following links at http://www.net-snmp.org/lists/ AGENT EXTENSIBILITY The agent that comes with this package is extensible through use of shell scripts and other methods. See the configuration manual pages (like snmpd.conf) and run the snmpconf perl script for further details. You can also extend the agent by writing C code directly. The agent is extremely modular in nature and you need only create new files, re-run configure and re-compile (or link against its libraries). No modification of the distributed source files are necessary. See the following files for details on how to go about this: http://www.net-snmp.org/tutorial-5/toolkit/, agent/mibgroup/examples/*.c Also, see the local/mib2c program and its README file for help in turning a textual mib description into a C code template. We now support AgentX for subagent extensibility. The net-snmp agent can run as both a master agent and a subagent. Additionally, a toolkit is provided that enables users of it to easily embed a agentx client into external applications. See the tutorial at http://www.net-snmp.org/tutorial-5/toolkit/ for an example of how go about doing this. CONFIGURATION See the man/snmp.conf.5 manual page. For the agent, additionally see the man/snmpd.conf.5 manual page. For the snmptrapd, see the man/snmptrapd.conf.5 manual page. You can also run the snmpconf perl script to help you create some of these files. SUBMITTING BUG REPORTS Important: *Please* include what version of the net-snmp (or ucd-snmp) package you are using and what architecture(s) you're using, as well as detailed information about exactly what is wrong. To submit a bug report, please use the web interface at http://www.net-snmp.org/bugs/. It is a full-fledged bug-tracking system that will allow you to search for already existing bug reports as well as track the status of your report as it is processed by the core developers. If you intend to submit a patch as well, please read the PORTING file before you do so and then submit it to http://www.net-snmp.org/patches/. CLOSING We love patches. Send some to us! But before you do, please see the 'PORTING' file for information on helping us out with the process of integrating your patches (regardless of whether its a new feature implementation or a new port). Also, We're interested if anyone actually uses/likes/hates/whatever this package... Mail us a note and let us know what you think of it! Have fun and may it make your life easier, The net-snmp developers THANKS The following people have contributed various patches and improvements. To them we owe our deepest thanks (and you do too!): Wes Hardaker <hardaker@users.sourceforge.net> Steve Waldbusser <waldbusser@nextbeacon.com> Dan A. Dickey <ddickey@transition.com> Dave Shield <D.T.Shield@csc.liv.ac.uk> Giovanni S. Marzot <gmarzot@nortelnetworks.com> Niels Baggesen <nba@users.sourceforge.net> Simon Leinen <simon@limmat.switch.ch> David T. Perkins <dperkins@dsperkins.com> Mike Perik <mikep@crt.com> Sanjai Narain <narain@thumper.bellcore.com> francus@metsny.delphi.com Gary Palmer <gpalmer@freebsd.org> Marc G. Fournier <scrappy@ki.net> Gary A. Hayward <gah@bellcore.com> Jennifer Bray <jbray@origin-at.co.uk> Philip Guenther <guenther@gac.edu> Elwyn B Davies <edavies@origin-at.co.uk> Simon Burge <simonb@telstra.com.au> David Paul Zimmerman <dpz@apple.com> Alan Batie <batie@aahz.jf.intel.com> Michael Douglass <mikedoug@texas.net> Ted Rule <Ted_Rule@FLEXTECH.CO.UK> Craig Bevins <craigb@bitcom.net.au> Arther Hyun <arthur@psi.com> Cristian Estan <Cristian.Estan@net.utcluj.ro> Eugene Polovnikov <eugen@rd.zgik.zaporizhzhe.ua> Jakob Ellerstedt <jakob@dynarc.se> Michael J. Slifcak <slif@bellsouth.net> Jonas Olsson <jolsson@erv.ericsson.se> James H. Young <sysjhy@gsu.edu> Jeff Johnson <jbj@redhat.com> Markku Laukkanen <marlaukk@stybba.ntc.nokia.com> Derek Simkowiak <dereks@kd-dev.com> David F. Newman <dnewman@epnet.com> Nick Amato <naamato@merit.edu> Mike Baer <baerm@calweb.com> Patrick Lawrence <pjlawrence@ucdavis.edu> Russ Mundy <mundy@tislabs.com> Olafur Gudmundsson <ogud@tislabs.com> David Reeder <dreeder@tislabs.com> Ed Lewis <lewis@tislabs.com> Bill Babson <wbabson@tislabs.com> Chris Smith <csmith@platform.com> Mike Michaud <mikemichaud@earthlink.net> Andy Hood <ahood@westpac.com.au> Robert Story <rstory@freesnmp.com> Bert Driehuis <driehuis@playbeing.org> Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de> Frank Strauss <strauss@ibr.cs.tu-bs.de> Ragnar Kjørstad <ucd@ragnark.vestdata.no> Jochen Kmietsch <jochen.kmietsch@tu-clausthal.de> Jun-ichiro itojun Hagino <itojun@iijlab.net> John L Villalovos <john.l.villalovos@intel.com> Christoph Mammitzsch <Christoph.Mammitzsch@tu-clausthal.de> Arne Oesleboe <Arne.Oesleboe@item.ntnu.no> Jeff Cours <jeff@ultradns.com> Karl Schilke <karl_schilke@eli.net> John Naylon <jbpn@cambridgebroadband.com> Ken Hornstein <kenh@cmf.nrl.navy.mil> Martin Oldfield <m@mail.tc> Harrie Hazewinkel <harrie@users.sourceforge.net> Mark Ferlatte <ferlatte@users.sourceforge.net> Marus Meissner <marcusmeissner@users.sourceforge.net> Stephan Wenzer <stephanwenzel@users.sourceforge.net> Ron Mevissen <ron.mevissen@eed.ericsson.se> T.J. Mather <tjmather@tjmather.com> Craig Setera <seterajunk@charter.net> Katsuhisa ABE <abekatsu@cysols.com> Axel Kittenberger <Axel.Kittenberger@maxxio.com> Johannes Schmidt-Fischer <jsf@InterFace-AG.com> Jeffrey Watson <nostaw@users.sourceforge.net> Bruce Shaw <Bruce.Shaw@gov.ab.ca> Stefan Radman <sradman@users.sourceforge.net> Stephen J. Friedl <sjfriedl@users.sourceforge.net> Alex Burger <alex_b@users.sourceforge.net> Christophe Varoqui <ext.devoteam.varoqui@sncf.fr> Srikanth Pindiproli <sripindip@users.sourceforge.net> Kevin Graham <kevgraham7@users.sourceforge.net> Xiaofeng Ling <xfling@users.sourceforge.net> Brandon Knitter <knitterb@bl...> Andrew Findlay <andrew.findlay@skills-1st.co.uk> Ron Tabor <rtabor@users.sourceforge.net> Peter Warasin <drg-r3@users.sourceforge.net> Bob Rowlands <robert.rowlands@sun.com> Peter Hicks <Peter.Hicks@POGGS.CO.UK> Andy Smith <wasmith32@earthlink.net> Nick Barkas <nbarkas@users.sourceforge.net> Noah Friedman <friedman@prep.ai.mit.edu> Geert De Peuter <geert@depeuter.org> Magnus Fromreide <magfr@lysator.liu.se> Marcus Meissner <marcusmeissner@users.sourceforge.net> Andrew Rucker Jones <arjones@users.sourceforge.net> Dai.H. <dg-f@users.sourceforge.net> Thomas Anders <tanders@users.sourceforge.net> Vladislav Bogdanov <slava_reg@nsys.by> Peter Martin <pnmartin@users.sourceforge.net> Thomas Lackey <telackey@users.sourceforge.net> Joe Buehler <jbuehler@spirentcom.com> Anders Persson <apersson@users.sourceforge.net> Rojer <rojer@users.sourceforge.net> Bart Van Assche <bart.vanassche@gmail.com> We've probably forgotten people on this list. Let us know if you've contributed code and we've left you out. usr/share/doc/kbd-1.15.5/README 0000644 00000001175 14721026766 0011410 0 ustar 00 This is kbd-1.15.3.tar.gz This package contains keytable files and keyboard utilities compatible with kernel version 1.1.54 and later. Setfont requires 1.1.92 or later. Major changes in keyboard and console handling occurred in 1.3.1. The current version of kbd might not work anymore on kernels older than that. This distribution contains no binaries - the sources depend on the kernel version - compile them yourself. The home site of this package is ftp://ftp.kernel.org/pub/linux/utils/kbd/ ftp://ftp.altlinux.org/pub/people/legion/kbd/ Report problems with this package to Alexey Gladkov <gladkov.alexey@gmail.com>. Apr 2011 usr/share/doc/perl-Params-Check-0.38/README 0000644 00000001767 14721027050 0013701 0 ustar 00 This is the README file for Params::Check, a perl module for powerful template based param validation Please refer to 'perldoc Params::Check' after installation for details. ##################################################################### * Description Params::Check Allows for generic input checking and validating using a powerfull templating system, providing default values and so on. ##################################################################### * Installation Params::Check follows the standard perl module install process perl Makefile.PL make make test make install The module uses no C or XS parts, so no c-compiler is required. ###################################################################### AUTHOR This module by Jos Boumans <kane@cpan.org>. COPYRIGHT This module is copyright (c) 2002 Jos Boumans <kane@cpan.org>. All rights reserved. This library is free software; you may redistribute and/or modify it under the same terms as Perl itself. usr/share/doc/pygpgme-0.3/README 0000644 00000002312 14721027114 0012047 0 ustar 00 A Python binding for the gpgme library, used to drive the gpg command line program. More information about gpgme can be found here: http://www.gnupg.org/(en)/related_software/gpgme/index.html This binding stays fairly close to the C API with the following exceptions: * Memory management is not exposed to the user * Functions like gpgme_get_foo()/gpgme_set_foo() are converted to attribute access on gpgme.Context objects. * Functions that take gpgme_data_t arguments take arbitrary Python file-like objects. The read(), write(), seek() and tell() methods may be used on the object. * Non-zero gpgme_error_t return values are converted to gpgme.error exceptions. * Only the synchronous versions of functions have been wrapped. However, the Python global interpreter lock is dropped, so should play nicely in multi-threaded Python programs. * Function pairs like gpgme_op_import()/gpgme_op_import_result() are combined into single method calls. * The Python version of gpgme_op_keylist() returns an iterator over the matched keys, rather than requiring the user to use a special iteration function. This library is licensed under the LGPL, the same license as the gpgme library. usr/share/doc/kmod-20/README 0000644 00000006702 14721027330 0011261 0 ustar 00 kmod - Linux kernel module handling Information =========== Mailing list: linux-modules@vger.kernel.org (no subscription needed) Signed packages: http://www.kernel.org/pub/linux/utils/kernel/kmod/ Git: git://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git http://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git Gitweb: http://git.kernel.org/?p=utils/kernel/kmod/kmod.git Irc: #kmod on irc.freenode.org License: LGPLv2.1+ for libkmod, testsuite and helper libraries GPLv2+ for tools/* OVERVIEW ======== kmod is a set of tools to handle common tasks with Linux kernel modules like insert, remove, list, check properties, resolve dependencies and aliases. These tools are designed on top of libkmod, a library that is shipped with kmod. See libkmod/README for more details on this library and how to use it. The aim is to be compatible with tools, configurations and indexes from module-init-tools project. Compilation and installation ============================ In order to compiler the source code you need following software packages: - GCC compiler - GNU C library Optional dependencies: - ZLIB library - LZMA library Typical configuration: ./configure CFLAGS="-g -O2" --prefix=/usr \ --sysconfdir=/etc --libdir=/usr/lib Configure automatically searches for all required components and packages. To compile and install run: make && make install Hacking ======= Run 'bootstrap' script before configure. If you want to accept the recommended flags, you just need to run 'bootstrap-configure'. Make sure to read the CODING-STYLE file and the other READMEs: libkmod/README and testsuite/README. Compatibility with module-init-tools ==================================== kmod replaces module-init-tools, which is end-of-life. Most of its tools are rewritten on top of libkmod so it can be used as a drop in replacements. Somethings however were changed. Reasons vary from "the feature was already long deprecated on module-init-tools" to "it would be too much trouble to support it". There are several features that are being added in kmod, but we don't keep track of them here. modprobe -------- * 'modprobe -l' was marked as deprecated and does not exist anymore * 'modprobe -t' is gone, together with 'modprobe -l' * modprobe doesn't parse configuration files with names not ending in '.alias' or '.conf'. modprobe used to warn about these files. * modprobe doesn't parse 'config' and 'include' commands in configuration files. * modprobe from m-i-t does not honour softdeps for install commands. E.g.: config: install bli "echo bli" install bla "echo bla" softdep bla pre: bli With m-i-t, the output of 'modprobe --show-depends bla' will be: install "echo bla" While with kmod: install "echo bli" install "echo bla" * kmod doesn't dump the configuration as is in the config files. Instead it dumps the configuration as it was parsed. Therefore, comments and file names are not dumped, but on the good side we know what the exact configuration kmod is using. We did this because if we only want to know the entire content of configuration files, it's enough to use find(1) in modprobe.d directories depmod ------ * there's no 'depmod -m' option: legacy modules.*map files are gone lsmod ----- * module-init-tools used /proc/modules to parse module info. kmod uses /sys/module/*, but there's a fallback to /proc/modules if the latter isn't available usr/share/doc/libseccomp-2.3.1/README 0000644 00000004641 14721027512 0012671 0 ustar 00 libseccomp: An Enhanced Seccomp (mode 2) Helper Library =============================================================================== https://github.com/seccomp/libseccomp The libseccomp library provides an easy to use, platform independent, interface to the Linux Kernel's syscall filtering mechanism. The libseccomp API is designed to abstract away the underlying BPF based syscall filter language and present a more conventional function-call based filtering interface that should be familiar to, and easily adopted by, application developers. * Online Resources The library source repository currently lives on GitHub at the following URL: -> https://github.com/seccomp/libseccomp The project mailing list is currently hosted on Google Groups at the URL below, please note that a Google account is not required to subscribe to the mailing list. -> https://groups.google.com/forum/#!forum/libseccomp -> https://groups.google.com/forum/#!forum/libseccomp/join * Documentation The "doc/" directory contains all of the currently available documentation, mostly in the form of manpages. The top level directory also contains a README file (this file) as well as the LICENSE, CREDITS, SUBMITTING_PATCHES, and CHANGELOG files. Those who are interested in contributing to the the project are encouraged to read the SUBMITTING_PATCHES in the top level directory. * Building and Installing the Library If you are building the libseccomp library from an official release tarball, you should follow the familiar three step process used by most autotools based applications: # ./configure # make [V=0|1] # make install However, if you are building the library from sources retrieved from the source repository you may need to run the autogen.sh script before running configure. In both cases, running "./configure -h" will display a list of build-time configuration options. * Testing the Library There are a number of tests located in the "tests/" directory and a make target which can be used to help automate their execution. If you want to run the standard regression tests you can execute the following after building the library: # make check Be warned that the test run can take a while to run and produces a lot of output. * Other Useful Tools The "tools/" directory includes a number of tools which may be helpful in the development of the library, or applications using the library. Not all of these tools are installed by default. usr/share/doc/perl-Module-Pluggable-4.8/README 0000644 00000024107 14721027665 0014516 0 ustar 00 NAME Module::Pluggable - automatically give your module the ability to have plugins SYNOPSIS Simple use Module::Pluggable - package MyClass; use Module::Pluggable; and then later ... use MyClass; my $mc = MyClass->new(); # returns the names of all plugins installed under MyClass::Plugin::* my @plugins = $mc->plugins(); EXAMPLE Why would you want to do this? Say you have something that wants to pass an object to a number of different plugins in turn. For example you may want to extract meta-data from every email you get sent and do something with it. Plugins make sense here because then you can keep adding new meta data parsers and all the logic and docs for each one will be self contained and new handlers are easy to add without changing the core code. For that, you might do something like ... package Email::Examiner; use strict; use Email::Simple; use Module::Pluggable require => 1; sub handle_email { my $self = shift; my $email = shift; foreach my $plugin ($self->plugins) { $plugin->examine($email); } return 1; } .. and all the plugins will get a chance in turn to look at it. This can be trivally extended so that plugins could save the email somewhere and then no other plugin should try and do that. Simply have it so that the "examine" method returns 1 if it has saved the email somewhere. You might also wnat to be paranoid and check to see if the plugin has an "examine" method. foreach my $plugin ($self->plugins) { next unless $plugin->can('examine'); last if $plugin->examine($email); } And so on. The sky's the limit. DESCRIPTION Provides a simple but, hopefully, extensible way of having 'plugins' for your module. Obviously this isn't going to be the be all and end all of solutions but it works for me. Essentially all it does is export a method into your namespace that looks through a search path for .pm files and turn those into class names. Optionally it instantiates those classes for you. ADVANCED USAGE Alternatively, if you don't want to use 'plugins' as the method ... package MyClass; use Module::Pluggable sub_name => 'foo'; and then later ... my @plugins = $mc->foo(); Or if you want to look in another namespace package MyClass; use Module::Pluggable search_path => ['Acme::MyClass::Plugin', 'MyClass::Extend']; or directory use Module::Pluggable search_dirs => ['mylibs/Foo']; Or if you want to instantiate each plugin rather than just return the name package MyClass; use Module::Pluggable instantiate => 'new'; and then # whatever is passed to 'plugins' will be passed # to 'new' for each plugin my @plugins = $mc->plugins(@options); alternatively you can just require the module without instantiating it package MyClass; use Module::Pluggable require => 1; since requiring automatically searches inner packages, which may not be desirable, you can turn this off package MyClass; use Module::Pluggable require => 1, inner => 0; You can limit the plugins loaded using the except option, either as a string, array ref or regex package MyClass; use Module::Pluggable except => 'MyClass::Plugin::Foo'; or package MyClass; use Module::Pluggable except => ['MyClass::Plugin::Foo', 'MyClass::Plugin::Bar']; or package MyClass; use Module::Pluggable except => qr/^MyClass::Plugin::(Foo|Bar)$/; and similarly for only which will only load plugins which match. Remember you can use the module more than once package MyClass; use Module::Pluggable search_path => 'MyClass::Filters' sub_name => 'filters'; use Module::Pluggable search_path => 'MyClass::Plugins' sub_name => 'plugins'; and then later ... my @filters = $self->filters; my @plugins = $self->plugins; PLUGIN SEARCHING Every time you call 'plugins' the whole search path is walked again. This allows for dynamically loading plugins even at run time. However this can get expensive and so if you don't expect to want to add new plugins at run time you could do package Foo; use strict; use Module::Pluggable sub_name => '_plugins'; our @PLUGINS; sub plugins { @PLUGINS ||= shift->_plugins } 1; INNER PACKAGES If you have, for example, a file lib/Something/Plugin/Foo.pm that contains package definitions for both "Something::Plugin::Foo" and "Something::Plugin::Bar" then as long as you either have either the require or instantiate option set then we'll also find "Something::Plugin::Bar". Nifty! OPTIONS You can pass a hash of options when importing this module. The options can be ... sub_name The name of the subroutine to create in your namespace. By default this is 'plugins' search_path An array ref of namespaces to look in. search_dirs An array ref of directorys to look in before @INC. instantiate Call this method on the class. In general this will probably be 'new' but it can be whatever you want. Whatever arguments are passed to 'plugins' will be passed to the method. The default is 'undef' i.e just return the class name. require Just require the class, don't instantiate (overrides 'instantiate'); inner If set to 0 will not search inner packages. If set to 1 will override "require". only Takes a string, array ref or regex describing the names of the only plugins to return. Whilst this may seem perverse ... well, it is. But it also makes sense. Trust me. except Similar to "only" it takes a description of plugins to exclude from returning. This is slightly less perverse. package This is for use by extension modules which build on "Module::Pluggable": passing a "package" option allows you to place the plugin method in a different package other than your own. file_regex By default "Module::Pluggable" only looks for *.pm* files. By supplying a new "file_regex" then you can change this behaviour e.g file_regex => qr/\.plugin$/ include_editor_junk By default "Module::Pluggable" ignores files that look like they were left behind by editors. Currently this means files ending in ~ (~), the extensions .swp or .swo, or files beginning with .#. Setting "include_editor_junk" changes "Module::Pluggable" so it does not ignore any files it finds. follow_symlinks Whether, when searching directories, to follow symlinks. Defaults to 1 i.e do follow symlinks. min_depth, max_depth This will allow you to set what 'depth' of plugin will be allowed. So, for example, "MyClass::Plugin::Foo" will have a depth of 3 and "MyClass::Plugin::Foo::Bar" will have a depth of 4 so to only get the former (i.e "MyClass::Plugin::Foo") do package MyClass; use Module::Pluggable max_depth => 3; and to only get the latter (i.e "MyClass::Plugin::Foo::Bar") package MyClass; use Module::Pluggable min_depth => 4; TRIGGERS Various triggers can also be passed in to the options. If any of these triggers return 0 then the plugin will not be returned. before_require <plugin> Gets passed the plugin name. If 0 is returned then this plugin will not be required either. on_require_error <plugin> <err> Gets called when there's an error on requiring the plugin. Gets passed the plugin name and the error. The default on_require_error handler is to "carp" the error and return 0. on_instantiate_error <plugin> <err> Gets called when there's an error on instantiating the plugin. Gets passed the plugin name and the error. The default on_instantiate_error handler is to "carp" the error and return 0. after_require <plugin> Gets passed the plugin name. If 0 is returned then this plugin will be required but not returned as a plugin. METHODs search_path The method "search_path" is exported into you namespace as well. You can call that at any time to change or replace the search_path. $self->search_path( add => "New::Path" ); # add $self->search_path( new => "New::Path" ); # replace BEHAVIOUR UNDER TEST ENVIRONMENT In order to make testing reliable we exclude anything not from blib if blib.pm is in %INC. However if the module being tested used another module that itself used "Module::Pluggable" then the second module would fail. This was fixed by checking to see if the caller had (^|/)blib/ in their filename. There's an argument that this is the wrong behaviour and that modules should explicitly trigger this behaviour but that particular code has been around for 7 years now and I'm reluctant to change the default behaviour. You can now (as of version 4.1) force Module::Pluggable to look outside blib in a test environment by doing either require Module::Pluggable; $Module::Pluggable::FORCE_SEARCH_ALL_PATHS = 1; import Module::Pluggable; or use Module::Pluggable force_search_all_paths => 1; FUTURE PLANS This does everything I need and I can't really think of any other features I want to add. Famous last words of course Recently tried fixed to find inner packages and to make it 'just work' with PAR but there are still some issues. However suggestions (and patches) are welcome. DEVELOPMENT The master repo for this module is at https://github.com/simonwistow/Module-Pluggable AUTHOR Simon Wistow <simon@thegestalt.org> COPYING Copyright, 2006 Simon Wistow Distributed under the same terms as Perl itself. BUGS None known. SEE ALSO File::Spec, File::Find, File::Basename, Class::Factory::Util, Module::Pluggable::Ordered usr/share/doc/libidn-devel-1.28/examples/README 0000644 00000002176 14721045102 0014650 0 ustar 00 Libidn examples/README -- Information about files in examples/ directory. Copyright (C) 2003-2013 Simon Josefsson See the end for copying conditions. This directory contains examples on how to use Libidn. * Example 1:: Example using stringprep. This example demonstrates how the stringprep functions are used. * Example 2:: Example using punycode. This example demonstrates how the punycode functions are used. * Example 3:: Example using IDNA ToASCII. This example demonstrates how the library is used to convert internationalized domain names into ASCII compatible names. * Example 4:: Example using IDNA ToUnicode. This example demonstrates how the library is used to convert ASCII compatible names to internationalized domain names. * Example 5:: Example using TLD checking. This example demonstrates how the library is used to check a string for invalid characters within a specific TLD. ---------------------------------------------------------------------- Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. usr/share/doc/cpanel-php81-mdb2-2.4.1/docs/README 0000644 00000017301 14721045132 0014517 0 ustar 00 ** Introduction: PEAR MDB2 is a project to merge PEAR DB and Metabase into one DB abstraction layer. You can get info on these at: PEAR DB: http://pear.php.net Metabase: http://phpclasses.upperdesign.com/browse.html/package/20/ At these URLs you will also find the licensing information on these two projects along with the credits. Actually MDB2 is the second major version of MDB. The main differences between the new MDB2 and the old MDB version is that the API has been drastically refactored to clean up the API and improve performance. If you have any questions or suggestions you can contact me (Lukas Smith) at this email address: smith@backendmedia.com Co-Author is Christopher Linn: clinn@backendmedia.com Or even better post a message to pear-dev@lists.php.net mailinglist for development related questions of the MDB2 package itself. For questions using MDB2 pelase direct your questions at pear-general@lists.php.net. ** Features MDB2 provides a common API for all support RDBMS. The main difference to most other DB abstraction packages is that MDB2 goes much further to ensure portability. Among other things MDB2 features: * An OO-style query API * A DSN (data source name) or array format for specifying database servers * Datatype abstraction and on demand datatype conversion * Portable error codes * Sequential and non sequential row fetching as well as bulk fetching * Ordered array and associative array for the fetched rows * Buffered and Unbuffered fetching * Prepare/execute (bind) emulation * Sequence emulation * Replace emulation * Limited Subselect emulation * Row limit support * Transactions support * Large Object support * Index/Unique support * Extension Framework to load advanced functionality on demand * Table information interface * RDBMS management methods (creating, dropping, altering) * RDBMS independent xml based schema definition management * Altering of a DB from a changed xml schema * Reverse engineering of xml schemas from an existing DB (currently MySQL and PgSQl) * Full integration into the PEAR Framework * PHPDoc API documentation ** Getting started: I would first recommend taking a look at example.php. This should give you a general feel of how to interact with MDB2. After that you may want to take a look at the rather large API at www.backendmedia.com/MDB2/docs. There you will also find a document describing the xml schema format and a little tutorial (it was just recently ported from Metabase, so it may contain errors). ** Current State: The current release can be found at the PEAR webpage: http://pear.php.net/package-info.php?package=MDB2 ** Package Content: As a user the only php script you will need to include is MDB2.php which will install to your PEAR root directory. All other files and their containing classes will be included via MDB2::factory(), MDB2::connect(), MDB2::singleton(). These will load additional classes. Most classes are loaded on demand. Furthermore MDB2 provides an extensive testing framework that works through a browser and command line interface. There are several other test that test the two wrappers. These files will install into your test dir found in the PEAR root dir. ** Documentation: You can find the still incomplete documentation for MDB2 here: http://pear.php.net/manual/en/package.database.mdb2.php PHPDoc generated documentation can be found at: http://www.backendmedia.com/MDB2/docs/ The entire "public" API and most of the "private" methods (except for some of the lob classes) have been documented with PHPDoc comments. Most of the API is borrowed from extPDO, so you can look there for detailed documentation. Since there are a large number of new methods available thanks to the Metabase heritage of MDB2 you will also have to take a look in the Metabase documentation (which can be found at the URL mentioned above, but does require that you register with phpclasses). Most of these Metabase functions have been renamed and changed considerably. The main things left are the datatypes and the manager module. For example ($db being an MDB2 object): $converted_value = MetabaseGetTimestampFieldValue($database, $value); would now be $converted_value = $db->quote($value, 'timestamp'); If you want to help out with documentation please email me. ** Testing: For most of the tests you can set the username/password/hostname in the relevant config file. The user will need to have the right to create new databases. test.php/clitest.php/testchoose.php: Is the native testing suite provided by MDB2. Please see the README in the tests directory for details. example.php: Several test calls to MDB2's native API. It require PEAR::VAR_Dump package and are configured to use the following settings: username = metapear password = funky hostname = localhost ** How to write new Drivers: Skeleton drivers are provided in the docs directory of the MDB2 package. The best course of action would be to take a MDB2 driver and hack it to fit the new RDBMS. This will surely be faster and it will ensure that the new driver takes full advantage of the MDB2 framework. I would however recommend working with the existing Metabase driver for inspiration that RDBMS when doing those changes. In order to check compliance of the driver with MDB2 you can use the testing suite (see the "testing" section above) ** History MDB was started after Manuel broad be into the discussion about getting the features of Metabase into PEAR that was going on (again) in December 2001. He suggested that I could take on this project. After alot of discussion about how when and if etc I started development in February 2002. MDB is based on Metabase but has been reworked severely to better match the PEAR DB API and PEAR CS. The approach I have taken so far is to take DB.php from PEAR DB and make it create a Metabase object. I have changed the Metabase structure slightly. The formatting has been reworked considerably to better fit the final structure (MDB standalone with a BC-wrapper for Metabase and PEAR DB), to fit the PEAR CS and to make it easier for other people to contribute. The metabase_interface.php was been renamed to metabase_wrapper.php and now only serves as a wrapper to keep BC with Metabase. A wrapper will have to be created for PEAR DB as well. Basically the result is a Metabase that is really close to the PEAR DB structure. I have also added any missing methods from PEAR DB. Work on moving the error handling to PEAR error handling is under way but still needs some work. In MDB2 the API was heavily refactored to be even more streamlined. Redundant features have been removed. Some features where moved out of the core into separate loadable modules. Instead of resources resultsets are now wrapped into objects similar to PEAR DB. ** Credits (never to early for those huh? :-) ): I would especially like to thank Manuel Lemos (Author of Metabase) for getting me involved in this and generally being around to ask questions. I would also like to thank Tomas Cox and Stig S. Bakken from the PEAR projects for help in undertstanding PEAR, solving problems and trusting me enough. Paul Cooper for the work on the pgsql driver. Furthermore I would like to thank Alex Black for being so enthusiastic about this project and offering binarycloud as a test bed for this project. Christian Dickmann for being the first to put MDB to some real use, making MDB use PEAR Error and working on the XML schema manager. Finally Peter Bowyer for starting the discussion that made people pick up this project again after the first versions of what was then called "metapear" have been ideling without much feedback. I guess I should also thank BackendMedia (my company :-) ) for providing the necessary means to develop this on company time (actually for the most part my entire life is company time ... so it goes) opt/alt/python35/share/doc/alt-python35-3.5.9/README 0000644 00000020767 14721057001 0015300 0 ustar 00 This is Python version 3.5.9 ============================ Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019 Python Software Foundation. All rights reserved. Python 3.x is a new version of the language, which is incompatible with the 2.x line of releases. The language is mostly the same, but many details, especially how built-in objects like dictionaries and strings work, have changed considerably, and a lot of deprecated features have finally been removed. Using Python ------------ Installable Python kits, and information about using Python, are available at `python.org`_. .. _python.org: https://www.python.org/ Build Instructions ------------------ On Unix, Linux, BSD, OSX, and Cygwin: ./configure make make test sudo make install This will install Python as python3. You can pass many options to the configure script; run "./configure --help" to find out more. On OSX and Cygwin, the executable is called python.exe; elsewhere it's just python. On Mac OS X, if you have configured Python with --enable-framework, you should use "make frameworkinstall" to do the installation. Note that this installs the Python executable in a place that is not normally on your PATH, you may want to set up a symlink in /usr/local/bin. On Windows, see PCbuild/readme.txt. If you wish, you can create a subdirectory and invoke configure from there. For example: mkdir debug cd debug ../configure --with-pydebug make make test (This will fail if you *also* built at the top-level directory. You should do a "make clean" at the toplevel first.) To get an optimized build of Python, "configure --enable-optimizations" before you run make. This sets the default make targets up to enable Profile Guided Optimization (PGO) and may be used to auto-enable Link Time Optimization (LTO) on some platforms. For more details, see the sections bellow. Profile Guided Optimization --------------------------- PGO takes advantage of recent versions of the GCC or Clang compilers. If ran, "make profile-opt" will do several steps. First, the entire Python directory is cleaned of temporary files that may have resulted in a previous compilation. Then, an instrumented version of the interpreter is built, using suitable compiler flags for each flavour. Note that this is just an intermediary step and the binary resulted after this step is not good for real life workloads, as it has profiling instructions embedded inside. After this instrumented version of the interpreter is built, the Makefile will automatically run a training workload. This is necessary in order to profile the interpreter execution. Note also that any output, both stdout and stderr, that may appear at this step is suppressed. Finally, the last step is to rebuild the interpreter, using the information collected in the previous one. The end result will be a Python binary that is optimized and suitable for distribution or production installation. Link Time Optimization ---------------------- Enabled via configure's --with-lto flag. LTO takes advantages of recent compiler toolchains ability to optimize across the otherwise arbitrary .o file boundary when building final executables or shared libraries for additional performance gains. What's New ---------- We have a comprehensive overview of the changes in the "What's New in Python 3.5" document, found at http://docs.python.org/3.5/whatsnew/3.5.html For a more detailed change log, read Misc/NEWS (though this file, too, is incomplete, and also doesn't list anything merged in from the 2.7 release under development). If you want to install multiple versions of Python see the section below entitled "Installing multiple versions". Documentation ------------- Documentation for Python 3.5 is online, updated daily: http://docs.python.org/3.5/ It can also be downloaded in many formats for faster access. The documentation is downloadable in HTML, PDF, and reStructuredText formats; the latter version is primarily for documentation authors, translators, and people with special formatting requirements. If you would like to contribute to the development of Python, relevant documentation is available at: http://docs.python.org/devguide/ For information about building Python's documentation, refer to Doc/README.txt. Converting From Python 2.x to 3.x --------------------------------- Python starting with 2.6 contains features to help locating code that needs to be changed, such as optional warnings when deprecated features are used, and backported versions of certain key Python 3.x features. A source-to-source translation tool, "2to3", can take care of the mundane task of converting large amounts of source code. It is not a complete solution but is complemented by the deprecation warnings in 2.6. See http://docs.python.org/3.5/library/2to3.html for more information. Testing ------- To test the interpreter, type "make test" in the top-level directory. The test set produces some output. You can generally ignore the messages about skipped tests due to optional features which can't be imported. If a message is printed about a failed test or a traceback or core dump is produced, something is wrong. By default, tests are prevented from overusing resources like disk space and memory. To enable these tests, run "make testall". IMPORTANT: If the tests fail and you decide to mail a bug report, *don't* include the output of "make test". It is useless. Run the failing test manually, as follows: ./python -m test -v test_whatever (substituting the top of the source tree for '.' if you built in a different directory). This runs the test in verbose mode. Installing multiple versions ---------------------------- On Unix and Mac systems if you intend to install multiple versions of Python using the same installation prefix (--prefix argument to the configure script) you must take care that your primary python executable is not overwritten by the installation of a different version. All files and directories installed using "make altinstall" contain the major and minor version and can thus live side-by-side. "make install" also creates ${prefix}/bin/python3 which refers to ${prefix}/bin/pythonX.Y. If you intend to install multiple versions using the same prefix you must decide which version (if any) is your "primary" version. Install that version using "make install". Install all other versions using "make altinstall". For example, if you want to install Python 2.6, 2.7 and 3.5 with 2.7 being the primary version, you would execute "make install" in your 2.7 build directory and "make altinstall" in the others. Issue Tracker and Mailing List ------------------------------ We're soliciting bug reports about all aspects of the language. Fixes are also welcome, preferably in unified diff format. Please use the issue tracker: http://bugs.python.org/ If you're not sure whether you're dealing with a bug or a feature, use the mailing list: python-dev@python.org To subscribe to the list, use the mailman form: http://mail.python.org/mailman/listinfo/python-dev/ Proposals for enhancement ------------------------- If you have a proposal to change Python, you may want to send an email to the comp.lang.python or `python-ideas`_ mailing lists for initial feedback. A Python Enhancement Proposal (PEP) may be submitted if your idea gains ground. All current PEPs, as well as guidelines for submitting a new PEP, are listed at http://www.python.org/dev/peps/. .. _python-ideas: https://mail.python.org/mailman/listinfo/python-ideas/ Release Schedule ---------------- See PEP 478 for release details: http://www.python.org/dev/peps/pep-0478/ Copyright and License Information --------------------------------- Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019 Python Software Foundation. All rights reserved. Copyright (c) 2000 BeOpen.com. All rights reserved. Copyright (c) 1995-2001 Corporation for National Research Initiatives. All rights reserved. Copyright (c) 1991-1995 Stichting Mathematisch Centrum. All rights reserved. See the file "LICENSE" for information on the history of this software, terms & conditions for usage, and a DISCLAIMER OF ALL WARRANTIES. This Python distribution contains *no* GNU General Public License (GPL) code, so it may be used in proprietary projects. There are interfaces to some GNU code but these are entirely optional. All trademarks referenced herein are property of their respective holders. opt/alt/openssl/share/doc/alt-openssl-1.0.2k/README 0000644 00000012546 14721057123 0015422 0 ustar 00 OpenSSL 1.0.2k 26 Jan 2017 Copyright (c) 1998-2015 The OpenSSL Project Copyright (c) 1995-1998 Eric A. Young, Tim J. Hudson All rights reserved. WARNING ------- This version of OpenSSL is built in a way that supports operation in the so called FIPS mode. Note though that the library as we build it is not FIPS 140-2 validated and the FIPS mode is present for testing purposes only. This version also contains a few differences from the upstream code some of which are: * The FIPS validation support is significantly different from the upstream FIPS support. For example the FIPS integrity verification check is implemented differently as the FIPS module is built inside the shared library. The HMAC-SHA256 checksums of the whole shared libraries are verified. Also note that the FIPS integrity verification check requires that the libcrypto and libssl shared library files are unmodified which means that it will fail if these files are changed for example by prelink. * If the file /etc/system-fips is present the integrity verification and selftests of the crypto algorithms are run inside the library constructor code. * With the /etc/system-fips present the module respects the kernel FIPS flag /proc/sys/crypto/fips and tries to initialize the FIPS mode if it is set to 1 aborting if the FIPS mode could not be initialized. With the /etc/system-fips present it is also possible to force the OpenSSL library to FIPS mode especially for debugging purposes by setting the environment variable OPENSSL_FORCE_FIPS_MODE. * If the environment variable OPENSSL_NO_DEFAULT_ZLIB is set the module will not automatically load the built in compression method ZLIB when initialized. Applications can still explicitely ask for ZLIB compression method. * The library was patched so the certificates, CRLs and other objects signed with use of MD5 fail verification as the MD5 is too insecure to be used for signatures. If the environment variable OPENSSL_ENABLE_MD5_VERIFY is set, the verification can proceed normally. * If the OPENSSL_ENFORCE_MODULUS_BITS environment variable is set, the library will not allow generation of DSA and RSA keys with other lengths than specified in the FIPS 186-4 standard. DESCRIPTION ----------- The OpenSSL Project is a collaborative effort to develop a robust, commercial-grade, fully featured, and Open Source toolkit implementing the Secure Sockets Layer (SSLv3) and Transport Layer Security (TLS) protocols as well as a full-strength general purpose cryptograpic library. The project is managed by a worldwide community of volunteers that use the Internet to communicate, plan, and develop the OpenSSL toolkit and its related documentation. OpenSSL is descended from the SSLeay library developed by Eric A. Young and Tim J. Hudson. The OpenSSL toolkit is licensed under a dual-license (the OpenSSL license plus the SSLeay license), which means that you are free to get and use it for commercial and non-commercial purposes as long as you fulfill the conditions of both licenses. OVERVIEW -------- The OpenSSL toolkit includes: libssl.a: Provides the client and server-side implementations for SSLv3 and TLS. libcrypto.a: Provides general cryptographic and X.509 support needed by SSL/TLS but not logically part of it. openssl: A command line tool that can be used for: Creation of key parameters Creation of X.509 certificates, CSRs and CRLs Calculation of message digests Encryption and decryption SSL/TLS client and server tests Handling of S/MIME signed or encrypted mail And more... INSTALLATION ------------ See the appropriate file: INSTALL Linux, Unix, etc. INSTALL.DJGPP DOS platform with DJGPP INSTALL.NW Netware INSTALL.OS2 OS/2 INSTALL.VMS VMS INSTALL.W32 Windows (32bit) INSTALL.W64 Windows (64bit) INSTALL.WCE Windows CE SUPPORT ------- See the OpenSSL website www.openssl.org for details on how to obtain commercial technical support. If you have any problems with OpenSSL then please take the following steps first: - Download the latest version from the repository to see if the problem has already been addressed - Configure with no-asm - Remove compiler optimisation flags If you wish to report a bug then please include the following information and create an issue on GitHub: - On Unix systems: Self-test report generated by 'make report' - On other systems: OpenSSL version: output of 'openssl version -a' OS Name, Version, Hardware platform Compiler Details (name, version) - Application Details (name, version) - Problem Description (steps that will reproduce the problem, if known) - Stack Traceback (if the application dumps core) Just because something doesn't work the way you expect does not mean it is necessarily a bug in OpenSSL. HOW TO CONTRIBUTE TO OpenSSL ---------------------------- See CONTRIBUTING LEGALITIES ---------- A number of nations restrict the use or export of cryptography. If you are potentially subject to such restrictions you should seek competent professional legal advice before attempting to develop or distribute cryptographic code. opt/alt/python35/share/doc/alt-python35-libs-3.5.9/README 0000644 00000020767 14721060244 0016232 0 ustar 00 This is Python version 3.5.9 ============================ Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019 Python Software Foundation. All rights reserved. Python 3.x is a new version of the language, which is incompatible with the 2.x line of releases. The language is mostly the same, but many details, especially how built-in objects like dictionaries and strings work, have changed considerably, and a lot of deprecated features have finally been removed. Using Python ------------ Installable Python kits, and information about using Python, are available at `python.org`_. .. _python.org: https://www.python.org/ Build Instructions ------------------ On Unix, Linux, BSD, OSX, and Cygwin: ./configure make make test sudo make install This will install Python as python3. You can pass many options to the configure script; run "./configure --help" to find out more. On OSX and Cygwin, the executable is called python.exe; elsewhere it's just python. On Mac OS X, if you have configured Python with --enable-framework, you should use "make frameworkinstall" to do the installation. Note that this installs the Python executable in a place that is not normally on your PATH, you may want to set up a symlink in /usr/local/bin. On Windows, see PCbuild/readme.txt. If you wish, you can create a subdirectory and invoke configure from there. For example: mkdir debug cd debug ../configure --with-pydebug make make test (This will fail if you *also* built at the top-level directory. You should do a "make clean" at the toplevel first.) To get an optimized build of Python, "configure --enable-optimizations" before you run make. This sets the default make targets up to enable Profile Guided Optimization (PGO) and may be used to auto-enable Link Time Optimization (LTO) on some platforms. For more details, see the sections bellow. Profile Guided Optimization --------------------------- PGO takes advantage of recent versions of the GCC or Clang compilers. If ran, "make profile-opt" will do several steps. First, the entire Python directory is cleaned of temporary files that may have resulted in a previous compilation. Then, an instrumented version of the interpreter is built, using suitable compiler flags for each flavour. Note that this is just an intermediary step and the binary resulted after this step is not good for real life workloads, as it has profiling instructions embedded inside. After this instrumented version of the interpreter is built, the Makefile will automatically run a training workload. This is necessary in order to profile the interpreter execution. Note also that any output, both stdout and stderr, that may appear at this step is suppressed. Finally, the last step is to rebuild the interpreter, using the information collected in the previous one. The end result will be a Python binary that is optimized and suitable for distribution or production installation. Link Time Optimization ---------------------- Enabled via configure's --with-lto flag. LTO takes advantages of recent compiler toolchains ability to optimize across the otherwise arbitrary .o file boundary when building final executables or shared libraries for additional performance gains. What's New ---------- We have a comprehensive overview of the changes in the "What's New in Python 3.5" document, found at http://docs.python.org/3.5/whatsnew/3.5.html For a more detailed change log, read Misc/NEWS (though this file, too, is incomplete, and also doesn't list anything merged in from the 2.7 release under development). If you want to install multiple versions of Python see the section below entitled "Installing multiple versions". Documentation ------------- Documentation for Python 3.5 is online, updated daily: http://docs.python.org/3.5/ It can also be downloaded in many formats for faster access. The documentation is downloadable in HTML, PDF, and reStructuredText formats; the latter version is primarily for documentation authors, translators, and people with special formatting requirements. If you would like to contribute to the development of Python, relevant documentation is available at: http://docs.python.org/devguide/ For information about building Python's documentation, refer to Doc/README.txt. Converting From Python 2.x to 3.x --------------------------------- Python starting with 2.6 contains features to help locating code that needs to be changed, such as optional warnings when deprecated features are used, and backported versions of certain key Python 3.x features. A source-to-source translation tool, "2to3", can take care of the mundane task of converting large amounts of source code. It is not a complete solution but is complemented by the deprecation warnings in 2.6. See http://docs.python.org/3.5/library/2to3.html for more information. Testing ------- To test the interpreter, type "make test" in the top-level directory. The test set produces some output. You can generally ignore the messages about skipped tests due to optional features which can't be imported. If a message is printed about a failed test or a traceback or core dump is produced, something is wrong. By default, tests are prevented from overusing resources like disk space and memory. To enable these tests, run "make testall". IMPORTANT: If the tests fail and you decide to mail a bug report, *don't* include the output of "make test". It is useless. Run the failing test manually, as follows: ./python -m test -v test_whatever (substituting the top of the source tree for '.' if you built in a different directory). This runs the test in verbose mode. Installing multiple versions ---------------------------- On Unix and Mac systems if you intend to install multiple versions of Python using the same installation prefix (--prefix argument to the configure script) you must take care that your primary python executable is not overwritten by the installation of a different version. All files and directories installed using "make altinstall" contain the major and minor version and can thus live side-by-side. "make install" also creates ${prefix}/bin/python3 which refers to ${prefix}/bin/pythonX.Y. If you intend to install multiple versions using the same prefix you must decide which version (if any) is your "primary" version. Install that version using "make install". Install all other versions using "make altinstall". For example, if you want to install Python 2.6, 2.7 and 3.5 with 2.7 being the primary version, you would execute "make install" in your 2.7 build directory and "make altinstall" in the others. Issue Tracker and Mailing List ------------------------------ We're soliciting bug reports about all aspects of the language. Fixes are also welcome, preferably in unified diff format. Please use the issue tracker: http://bugs.python.org/ If you're not sure whether you're dealing with a bug or a feature, use the mailing list: python-dev@python.org To subscribe to the list, use the mailman form: http://mail.python.org/mailman/listinfo/python-dev/ Proposals for enhancement ------------------------- If you have a proposal to change Python, you may want to send an email to the comp.lang.python or `python-ideas`_ mailing lists for initial feedback. A Python Enhancement Proposal (PEP) may be submitted if your idea gains ground. All current PEPs, as well as guidelines for submitting a new PEP, are listed at http://www.python.org/dev/peps/. .. _python-ideas: https://mail.python.org/mailman/listinfo/python-ideas/ Release Schedule ---------------- See PEP 478 for release details: http://www.python.org/dev/peps/pep-0478/ Copyright and License Information --------------------------------- Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019 Python Software Foundation. All rights reserved. Copyright (c) 2000 BeOpen.com. All rights reserved. Copyright (c) 1995-2001 Corporation for National Research Initiatives. All rights reserved. Copyright (c) 1991-1995 Stichting Mathematisch Centrum. All rights reserved. See the file "LICENSE" for information on the history of this software, terms & conditions for usage, and a DISCLAIMER OF ALL WARRANTIES. This Python distribution contains *no* GNU General Public License (GPL) code, so it may be used in proprietary projects. There are interfaces to some GNU code but these are entirely optional. All trademarks referenced herein are property of their respective holders. opt/alt/python35/share/doc/alt-python35-click-6.6/README 0000644 00000001303 14721061322 0016202 0 ustar 00 $ click_ Click is a Python package for creating beautiful command line interfaces in a composable way with as little code as necessary. It's the "Command Line Interface Creation Kit". It's highly configurable but comes with sensible defaults out of the box. It aims to make the process of writing command line tools quick and fun while also preventing any frustration caused by the inability to implement an intended CLI API. Click in three points: - arbitrary nesting of commands - automatic help page generation - supports lazy loading of subcommands at runtime Read the docs at http://click.pocoo.org/ This library is stable and active. Feedback is always welcome! opt/alt/python35/share/doc/alt-python35-PyYAML-3.13/README 0000644 00000002471 14721062321 0016252 0 ustar 00 PyYAML - The next generation YAML parser and emitter for Python. To install, type 'python setup.py install'. By default, the setup.py script checks whether LibYAML is installed and if so, builds and installs LibYAML bindings. To skip the check and force installation of LibYAML bindings, use the option '--with-libyaml': 'python setup.py --with-libyaml install'. To disable the check and skip building and installing LibYAML bindings, use '--without-libyaml': 'python setup.py --without-libyaml install'. When LibYAML bindings are installed, you may use fast LibYAML-based parser and emitter as follows: >>> yaml.load(stream, Loader=yaml.CLoader) >>> yaml.dump(data, Dumper=yaml.CDumper) PyYAML includes a comprehensive test suite. To run the tests, type 'python setup.py test'. For more information, check the PyYAML homepage: 'http://pyyaml.org/wiki/PyYAML'. For PyYAML tutorial and reference, see: 'http://pyyaml.org/wiki/PyYAMLDocumentation'. Post your questions and opinions to the YAML-Core mailing list: 'http://lists.sourceforge.net/lists/listinfo/yaml-core'. Submit bug reports and feature requests to the PyYAML bug tracker: 'https://bitbucket.org/xi/pyyaml/issues/new'. PyYAML is written by Kirill Simonov <xi@resolvent.net>. It is released under the MIT license. See the file LICENSE for more details. opt/alt/freetds11/usr/share/doc/alt-freetds11-1.1.24/README 0000644 00000006012 14721065447 0016372 0 ustar 00 README for FreeTDS 1.1 Release date 13 March 2019 * to build FreeTDS read the file INSTALL or the FreeTDS Users Guide (doc/userguide/index.html) and http://www.freetds.org/userguide/ FreeTDS is a free implementation of Sybase's DB-Library, CT-Library, and ODBC libraries. FreeTDS builds and runs on every flavor of unix-like systems we've heard of (and some we haven't) as well as Win32 (with or without Cygwin), VMS, and Mac OS X. Failure to build on your system is probably considered a bug. It has C language bindings, and works also with Perl and PHP, among others. FreeTDS is licensed under the GNU LGPL license. See COPYING.LIB for details. Other files you might want to peruse: AUTHORS Who's involved BUGS Some things we fixed, or think we did NEWS Summary of feature changes and fixes README This file TODO The roadmap, such as it is Also, doc/api_status.txt shows which functions are implemented. For details on what's new in this version, see NEWS. For unbearable detail, see git log. Documentation ============= A User Guide, in xml and html form, is included in this distribution. Also included is a reference manual, generated in HTML with Doxygen. "make install" installs the HTML documentation, by default to /usr/local/share/doc/freetds-<version>. Note to Users ============= Submissions of test programs (self-contained programs that demonstrate functionality or problems) are greatly appreciated. They should create any tables needed (since we obviously don't have access to your database) and populate them. Unit tests for any of the libraries is appreciated Notes to Developers =================== The code is split into several pieces. 1) tds directory is the wire level stuff, it should be independent of the library using it, this will allow db-lib, ct-lib, and ODBC to sit on top. 2) db-lib directory. This is the actual db-lib code which runs on top of tds. 3) ct-lib directory. This is the ct-lib code which runs on top of tds. 4) server directory. This will be a set of server routines basically to impersonate a dataserver, functions like send_login_ack() etc... 5) odbc directory. ODBC implementation over tds. Uses iODBC or unixODBC as a driver manager. You need to have one of those if you are using the ODBC CLI. 6) unittests directories. Test harness code for ct-lib, db-lib, ODBC and libtds. 6) samples directories. Sample code for getting started with Perl, PHP, etc... 7) pool directory. A connection pooling server for TDS. Useful if you have a connection limited license. Needs some hacking to get configured but is quite stable once configured correctly. Contact the list if interested in how to use it. Please look at doc/getting_started.txt for a description of what is going on in the code. Side note: Brian, as many free software authors, appreciates postcards from all over. So if you live someplace neat (read: not Michigan) and want to send one, email him (brian@bruns.org) for his current snail mail address. $Id: 8d6325cefccb4c080f590aaab24fd8c7559ceb06 $ opt/alt/libxml2/usr/share/doc/alt-libxml2-2.9.7/README 0000644 00000002245 14721077755 0015663 0 ustar 00 XML toolkit from the GNOME project Full documentation is available on-line at http://xmlsoft.org/ This code is released under the MIT Licence see the Copyright file. To build on an Unixised setup: ./configure ; make ; make install To build on Windows: see instructions on win32/Readme.txt To assert build quality: on an Unixised setup: run make tests otherwise: There is 3 standalone tools runtest.c runsuite.c testapi.c, which should compile as part of the build or as any application would. Launch them from this directory to get results, runtest checks the proper functionning of libxml2 main APIs while testapi does a full coverage check. Report failures to the list. To report bugs, follow the instructions at: http://xmlsoft.org/bugs.html A mailing-list xml@gnome.org is available, to subscribe: http://mail.gnome.org/mailman/listinfo/xml The list archive is at: http://mail.gnome.org/archives/xml/ All technical answers asked privately will be automatically answered on the list and archived for public access unless privacy is explicitly required and justified. Daniel Veillard $Id$ etc/pki/ca-trust/README 0000644 00000000246 14722141252 0010526 0 ustar 00 This directory /etc/pki/ca-trust is used by a system of consolidated CA certificates. Please refer to the update-ca-trust(8) manual page for additional information.
| ver. 1.4 |
Github
|
.
| PHP 8.0.30 | Génération de la page: 0.09 |
proxy
|
phpinfo
|
Réglages