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 hardc usr/share/doc/fprintd-pam-0.8.1/README 0000644 00000002217 14721023071 0012766 0 ustar 00 etc/pki/ca-trust/extracted/pem/README 0000644 00000001602 14721023112 0013260 0 ustar 00 usr/share/doc/libreport-2.1.11/README 0000644 00000000137 14721023145 0012624 0 ustar 00 usr/share/doc/sysstat-10.1.5/README 0000644 00000010430 14721023503 0012331 0 ustar 00 usr/share/doc/perl-Encode-Locale-1.03/README 0000644 00000000547 14721023511 0014017 0 ustar 00 usr/share/doc/tcl-8.5.13/README 0000644 00000014565 14721023655 0011440 0 ustar 00 usr/share/doc/libdwarf-20130207/README 0000644 00000023026 14721024140 0012570 0 ustar 00 usr/share/doc/perl-HTTP-Date-6.02/README 0000644 00000011527 14721024152 0013065 0 ustar 00 usr/share/doc/ea-apache24/README 0000644 00000011052 14721024365 0012061 0 ustar 00 usr/share/doc/diffutils-3.3/README 0000644 00000005446 14721024500 0012402 0 ustar 00 usr/share/doc/ed-1.9/README 0000644 00000013415 14721024561 0011007 0 ustar 00 usr/share/doc/libstoragemgmt-1.8.1/README 0000644 00000000210 14721024723 0013562 0 ustar 00 usr/share/doc/socat-1.7.3.2/README 0000644 00000026576 14721024751 0012044 0 ustar 00 usr/share/doc/zip-3.0/README 0000644 00000030714 14721025453 0011214 0 ustar 00 usr/share/doc/perl-File-Fetch-0.42/README 0000644 00000002000 14721025713 0013325 0 ustar 00 usr/share/doc/psacct-6.6.1/README 0000644 00000007660 14721026014 0012035 0 ustar 00 usr/share/doc/slang-2.2.4/README 0000644 00000002204 14721026055 0011651 0 ustar 00 usr/share/doc/rpcbind-0.2.0/README 0000644 00000000160 14721026101 0012147 0 ustar 00 usr/share/doc/readline-6.2/README 0000644 00000017000 14721026164 0012173 0 ustar 00 etc/pki/ca-trust/extracted/openssl/README 0000644 00000001423 14721026410 0014167 0 ustar 00 usr/share/doc/gdisk-0.8.10/README 0000644 00000032034 14721026463 0011736 0 ustar 00 usr/share/doc/perl-Crypt-DES-2.05/README 0000644 00000006012 14721026521 0013137 0 ustar 00 usr/share/doc/rcs-5.9.0/README 0000644 00000025756 14721026616 0011366 0 ustar 00 usr/share/doc/net-snmp-libs-5.7.2/README 0000644 00000032521 14721026703 0013250 0 ustar 00 usr/share/doc/kbd-1.15.5/README 0000644 00000001175 14721026766 0011410 0 ustar 00 usr/share/doc/perl-Params-Check-0.38/README 0000644 00000001767 14721027050 0013701 0 ustar 00 usr/share/doc/pygpgme-0.3/README 0000644 00000002312 14721027114 0012047 0 ustar 00 usr/share/doc/kmod-20/README 0000644 00000006702 14721027330 0011261 0 ustar 00 usr/share/doc/libseccomp-2.3.1/README 0000644 00000004641 14721027512 0012671 0 ustar 00 usr/share/doc/perl-Module-Pluggable-4.8/README 0000644 00000024107 14721027665 0014516 0 ustar 00 usr/share/doc/libidn-devel-1.28/examples/README 0000644 00000002176 14721045102 0014650 0 ustar 00 usr/share/doc/cpanel-php81-mdb2-2.4.1/docs/README 0000644 00000017301 14721045132 0014517 0 ustar 00 opt/alt/python35/share/doc/alt-python35-3.5.9/README 0000644 00000020767 14721057001 0015300 0 ustar 00 opt/alt/openssl/share/doc/alt-openssl-1.0.2k/README 0000644 00000012546 14721057123 0015422 0 ustar 00 opt/alt/python35/share/doc/alt-python35-libs-3.5.9/README 0000644 00000020767 14721060244 0016232 0 ustar 00 opt/alt/python35/share/doc/alt-python35-click-6.6/README 0000644 00000001303 14721061322 0016202 0 ustar 00 opt/alt/python35/share/doc/alt-python35-PyYAML-3.13/README 0000644 00000002471 14721062321 0016252 0 ustar 00 opt/alt/freetds11/usr/share/doc/alt-freetds11-1.1.24/README 0000644 00000006012 14721065447 0016372 0 ustar 00 opt/alt/libxml2/usr/share/doc/alt-libxml2-2.9.7/README 0000644 00000002245 14721077755 0015663 0 ustar 00 etc/pki/ca-trust/README 0000644 00000000246 14722141252 0010526 0 ustar 00 usr/share/libtool/libltdl/README 0000644 00000001260 14722162475 0012442 0 ustar 00 usr/share/doc/tmpwatch-2.11/README 0000644 00000001051 14722164470 0012316 0 ustar 00 usr/share/doc/cpio-2.11/README 0000644 00000005460 14722164522 0011427 0 ustar 00 usr/share/doc/pyliblzma-0.5.3/README 0000644 00000001357 14722164620 0012562 0 ustar 00 usr/share/doc/php-cli-5.4.16/README 0000644 00000001474 14722164704 0012206 0 ustar 00 usr/share/doc/xdg-utils-1.1.0/README 0000644 00000007430 14722164761 0012475 0 ustar 00 usr/share/doc/python-six-1.9.0/README 0000644 00000001402 14722165002 0012665 0 ustar 00 usr/share/doc/python-keyczar-0.71c/README 0000644 00000001206 14722165014 0013622 0 ustar 00 usr/share/doc/setserial-2.17/README 0000644 00000001506 14722165131 0012470 0 ustar 00 usr/share/doc/gamin-0.1.10/README 0000644 00000002754 14722165344 0011732 0 ustar 00 usr/share/doc/perl-JSON-2.59/README 0000644 00000161512 14722165500 0012220 0 ustar 00 usr/share/doc/nano-2.3.1/README 0000644 00000004731 14722165540 0011511 0 ustar 00 usr/share/doc/perl-IO-Compress-2.061/README 0000644 00000005200 14722165552 0013616 0 ustar 00 usr/share/doc/gettext-0.19.8.1/README 0000644 00000004411 14722165556 0012477 0 ustar 00 usr/share/doc/ruby-libs-2.0.0.648/README 0000644 00000012670 14722165621 0013003 0 ustar 00 usr/share/doc/libXcursor-1.1.15/README 0000644 00000001264 14722165633 0012775 0 ustar 00 usr/share/doc/t1lib-5.1.2/README 0000644 00000015662 14722165730 0011601 0 ustar 00 usr/share/doc/perl-HTML-Template-2.95/README 0000644 00000000474 14722165752 0013774 0 ustar 00 usr/share/doc/usb_modeswitch-2.5.1/README 0000644 00000023746 14722165756 0013617 0 ustar 00 usr/share/doc/bc-1.06.95/README 0000644 00000006702 14722165765 0011332 0 ustar 00 usr/share/doc/perl-Log-Message-0.08/README 0000644 00000002262 14722166077 0013550 0 ustar 00 usr/share/doc/sg3_utils-1.37/README 0000644 00000051102 14722166217 0012415 0 ustar 00 usr/share/doc/iproute-4.11.0/README 0000644 00000002524 14722166231 0012321 0 ustar 00 usr/share/doc/make-3.82/README 0000644 00000015757 14722166327 0011442 0 ustar 00 usr/share/doc/libutempter-1.1.6/README 0000644 00000001206 14722167060 0013105 0 ustar 00 usr/share/doc/perl-JSON-XS-3.01/README 0000644 00000202410 14722167321 0012530 0 ustar 00 usr/share/doc/python-libs-2.7.5/README 0000644 00000150766 14722167457 0013061 0 ustar 00 usr/share/doc/libcroco-0.6.12/README 0000644 00000000756 14722167522 0012442 0 ustar 00 usr/share/doc/pkgconfig-0.27.1/README 0000644 00000005047 14722167644 0012621 0 ustar 00 usr/share/doc/perl-Pod-Parser-1.61/README 0000644 00000013677 14722167674 0013441 0 ustar 00 usr/share/doc/yum-3.4.3/README 0000644 00000002066 14722170344 0011371 0 ustar 00 usr/share/doc/json-c-0.11/README 0000644 00000001665 14722170635 0011671 0 ustar 00 usr/share/doc/pcre-8.32/README 0000644 00000123476 14722170647 0011454 0 ustar 00 usr/share/doc/libpcap-1.5.3/README 0000644 00000010043 14722171157 0012165 0 ustar 00 usr/share/doc/libssh2-1.8.0/README 0000644 00000000734 14722171327 0012126 0 ustar 00 usr/share/doc/rsync-3.1.2/README 0000644 00000010112 14722171375 0011705 0 ustar 00 usr/share/doc/pinfo-0.6.10/README 0000644 00000001720 14722172067 0011747 0 ustar 00 usr/share/doc/librsvg2-2.40.20/README 0000644 00000004245 14722172130 0012443 0 ustar 00 usr/share/doc/libwmf-lite-0.2.8.4/README 0000644 00000020114 14722172133 0013124 0 ustar 00 usr/share/doc/acl-2.2.51/README 0000644 00000000632 14722172340 0011371 0 ustar 00 usr/share/doc/parted-3.1/README 0000644 00000004613 14722172634 0011676 0 ustar 00 usr/share/doc/httpd-2.4.6/README 0000644 00000012046 14722173102 0011676 0 ustar 00 usr/share/doc/libxslt-1.1.28/README 0000644 00000001217 14722173143 0012317 0 ustar 00 usr/share/doc/polkit-0.112/README 0000644 00000001440 14722174015 0012047 0 ustar 00 usr/share/doc/systemtap-runtime-4.0/README 0000644 00000013152 14722174124 0014123 0 ustar 00 usr/share/doc/python-urlgrabber-3.10/README 0000644 00000001743 14722174343 0014145 0 ustar 00 usr/share/doc/openssl-1.0.2k/README 0000644 00000012546 14722174433 0012415 0 ustar 00 usr/share/doc/perl-5.16.3/README 0000644 00000012632 14722174702 0011610 0 ustar 00 usr/share/doc/usbutils-007/README 0000644 00000000253 14722175004 0012264 0 ustar 00 usr/share/doc/libproxy-0.4.11/README 0000644 00000000156 14722175156 0012507 0 ustar 00 usr/share/doc/psmisc-22.20/README 0000644 00000002717 14722175457 0012070 0 ustar 00 usr/share/doc/python-kitchen-1.1.1/README 0000644 00000005331 14722175577 0013527 0 ustar 00 usr/share/doc/net-snmp-5.7.2/README 0000644 00000032521 14722176300 0012321 0 ustar 00 usr/share/doc/perl-Term-UI-0.36/README 0000644 00000001724 14722177107 0012666 0 ustar 00 usr/share/doc/libXdamage-1.1.4/README 0000644 00000001440 14722177274 0012614 0 ustar 00 usr/lib64/python2.7/Demo/pdist/README 0000644 00000010250 14722177364 0012747 0 ustar 00 usr/share/doc/ustr-1.0.4/README 0000644 00000000514 14722177726 0011556 0 ustar 00 usr/share/doc/rng-tools-6.3.1/README 0000644 00000000546 14722200722 0012476 0 ustar 00 usr/share/doc/pth-2.0.7/README 0000644 00000007732 14722201117 0011347 0 ustar 00 usr/share/doc/perl-common-sense-3.6/README 0000644 00000042133 14722202224 0013753 0 ustar 00 usr/share/doc/perl-Scalar-List-Utils-1.27/README 0000644 00000001433 14722202263 0014646 0 ustar 00 usr/share/doc/perl-Sub-Install-0.926/README 0000644 00000000301 14722202310 0013640 0 ustar 00 etc/pki/ca-trust/extracted/java/README 0000644 00000001326 14722207330 0013432 0 ustar 00 opt/alt/curl/usr/share/doc/alt-curl-7.64.0/README 0000644 00000003112 14722237440 0014712 0 ustar 00 usr/share/doc/cloud-init/examples/seed/README 0000644 00000001264 14722243507 0014722 0 ustar 00 opt/alt/t1lib/usr/share/doc/alt-t1lib-5.1.2/README 0000644 00000015662 14722246277 0014762 0 ustar 00 opt/alt/libssh211/usr/share/doc/alt-libssh211-1.10.0/README 0000644 00000000734 14722251074 0016207 0 ustar 00 opt/alt/curlssl11/usr/share/doc/alt-curlssl11-7.87.0/README 0000644 00000003200 14722252544 0016467 0 ustar 00 usr/lib/firmware/rtw88/README 0000644 00000002001 14723024160 0011603 0 ustar 00 usr/lib64/python3.6/distutils/README 0000644 00000000447 14723024743 0012764 0 ustar 00 usr/share/doc/giflib-4.1.6/README 0000644 00000004106 14723032577 0012017 0 ustar 00 usr/share/doc/perl-Capture-Tiny-0.24/README 0000644 00000030123 14723033470 0013753 0 ustar 00 usr/share/doc/libffi-3.0.13/README 0000644 00000033772 14723033760 0012100 0 ustar 00 usr/share/doc/libuser-0.60/README 0000644 00000001070 14723034175 0012136 0 ustar 00 usr/share/mysql/charsets/README 0000644 00000003325 14723034253 0012326 0 ustar 00 usr/share/doc/perl-DBIx-Simple-1.35/README 0000644 00000001112 14723043046 0013443 0 ustar 00 usr/lib64/python2.7/Demo/curses/README 0000644 00000001524 14723044124 0013120 0 ustar 00 usr/lib64/python2.7/Demo/classes/README 0000644 00000001012 14723044736 0013252 0 ustar 00 usr/lib64/python2.7/Demo/rpc/README 0000644 00000002355 14723046463 0012413 0 ustar 00 usr/share/doc/ca-certificates-2024.2.69_v7.0.306/README 0000644 00000002662 14723505472 0015214 0 ustar 00 usr/lib64/perl5/vendor_perl/XML/Parser/Encodings/README 0000644 00000003636 14723707016 0016347 0 ustar 00 opt/alt/freetds/usr/share/doc/alt-freetds-1.1.15/README 0000644 00000006013 14723717734 0016074 0 ustar 00 opt/alt/libssh2/usr/share/doc/alt-libssh2-1.8.0/README 0000644 00000000734 14726452717 0015645 0 ustar 00 usr/share/doc/curl-7.29.0/README 0000644 00000003110 14754414112 0011602 0 ustar 00 etc/pki/ca-trust/source/README 0000644 00000001644 14754764664 0012060 0 ustar 00 usr/share/doc/libtool-2.4.2/README 0000644 00000030305 14754770067 0012233 0 ustar 00 usr/share/doc/freetype-2.8/README 0000644 00000004550 14754770407 0012257 0 ustar 00 usr/share/doc/libxml2-devel-2.9.1/README 0000644 00000002245 14754770575 0013247 0 ustar 00 usr/share/doc/dmraid-1.0.0.rc16/README 0000644 00000006233 14754770636 0012577 0 ustar 00 usr/share/doc/coreutils-8.22/README 0000644 00000025752 14754771247 0012541 0 ustar 00 usr/share/doc/mlocate-0.26/README 0000644 00000002422 14754771741 0012134 0 ustar 00 usr/share/doc/tclx-8.4.0/README 0000644 00000015062 14754771775 0011557 0 ustar 00 usr/share/doc/perl-Curses-UI-0.9609/README 0000644 00000002673 14754772051 0013412 0 ustar 00 usr/share/doc/smartmontools-7.0/README 0000644 00000005667 14754772162 0013364 0 ustar 00 usr/share/doc/ncurses-devel-5.9/test/README 0000644 00000107616 14755000540 0014166 0 ustar 00 usr/share/doc/python-gobject-base-3.22.0/README 0000644 00000006732 14755441547 0014520 0 ustar 00 usr/share/doc/perl-Module-Implementation-0.06/README 0000644 00000000444 14755441614 0015652 0 ustar 00 usr/share/doc/libtirpc-0.2.4/README 0000644 00000004212 14755441740 0012365 0 ustar 00 usr/share/doc/systemtap-sdt-devel-4.0/README 0000644 00000013152 14755442115 0014333 0 ustar 00 usr/share/doc/mysql-community-client-5.7.44/README 0000644 00000001066 14755442115 0015317 0 ustar 00 usr/share/doc/perl-HTML-Parser-3.71/README 0000644 00000003673 14755442140 0013447 0 ustar 00 usr/share/doc/util-linux-2.23.2/README 0000644 00000002171 14755442501 0012750 0 ustar 00 usr/share/doc/perl-Package-DeprecationManager-0.13/README 0000644 00000000424 14755442552 0016521 0 ustar 00 usr/share/doc/libtar-1.2.11/README 0000644 00000006366 14755442626 0012131 0 ustar 00 usr/share/doc/python2-passlib-1.7.1/README 0000644 00000005203 14755443162 0013617 0 ustar 00 usr/share/doc/setools-libs-3.3.8/README 0000644 00000037066 14755443245 0013223 0 ustar 00 etc/rc.d/init.d/README 0000644 00000002210 14755617206 0010222 0 ustar 00 usr/share/doc/python-iniparse-0.4/README 0000644 00000002305 14755622114 0013543 0 ustar 00 usr/share/doc/abrt-2.1.11/README 0000644 00000000557 14755622721 0011574 0 ustar 00 usr/share/doc/ncurses-base-5.9/README 0000644 00000023744 14755622740 0013035 0 ustar 00 usr/share/doc/OpenEXR-libs-1.7.1/README 0000644 00000004106 14755623145 0012772 0 ustar 00 usr/share/doc/perl-File-CheckTree-4.42/README 0000644 00000000453 14755623147 0014163 0 ustar 00 usr/share/doc/smartmontools-7.0/examplescripts/README 0000644 00000003325 14755623323 0016407 0 ustar 00 usr/share/doc/libnfnetlink-1.0.1/README 0000644 00000002775 14755623556 0013253 0 ustar 00 usr/share/doc/yum-utils-1.1.31/README 0000644 00000000246 14755623561 0012613 0 ustar 00 usr/share/doc/shared-mime-info-1.8/README 0000644 00000001516 14755623562 0013556 0 ustar 00 usr/share/doc/gawk-4.0.2/README 0000644 00000006467 14755623576 0011535 0 ustar 00 usr/lib64/python2.7/Tools/README 0000755 00000003334 14755623646 0012055 0 ustar 00 usr/share/doc/libassuan-2.1.0/README 0000644 00000002376 14755624136 0012546 0 ustar 00 usr/share/doc/wget-1.14/README 0000644 00000007726 14755624145 0011464 0 ustar 00 usr/share/doc/iso-codes-3.46/README 0000644 00000013407 14755624205 0012400 0 ustar 00 usr/share/doc/libtool-ltdl-devel-2.4.2/README 0000644 00000001260 14755624315 0014256 0 ustar 00 usr/share/doc/perl-CPAN-Meta-Requirements-2.122/README 0000644 00000016651 14755624453 0015624 0 ustar 00 usr/share/doc/libevent-2.0.21/README 0000644 00000007743 14755624456 0012467 0 ustar 00 usr/share/doc/glibc-2.17/README 0000644 00000006704 14755624536 0011601 0 ustar 00 usr/share/doc/mysql-community-libs-5.7.44/README 0000644 00000001066 14755624661 0015002 0 ustar 00 usr/share/doc/perl-HTTP-Negotiate-6.01/README 0000644 00000017124 14755624716 0014150 0 ustar 00 usr/share/doc/perl-Tree-DAG_Node-1.12/README 0000644 00000010351 14755624732 0013677 0 ustar 00 usr/share/doc/perl-IPC-Run-0.92/README 0000644 00000204117 14755624754 0012637 0 ustar 00 usr/share/doc/perl-Getopt-Long-2.40/README 0000644 00000015131 14755624775 0013613 0 ustar 00 usr/share/doc/flex-2.5.37/README 0000644 00000005162 14755624775 0011626 0 ustar 00 usr/share/doc/libxml2-2.9.1/README 0000644 00000002245 14755625034 0012140 0 ustar 00 usr/share/doc/perl-DBD-MySQL-4.023/README 0000644 00000007427 14755625062 0013072 0 ustar 00 usr/share/doc/libpaper-1.1.24/README 0000644 00000002755 14755625322 0012447 0 ustar 00 usr/share/doc/gdb-7.6.1/README 0000644 00000003267 14755625354 0011337 0 ustar 00 usr/share/doc/perl-Expect-1.21/README 0000644 00000004233 14755625505 0012673 0 ustar 00 usr/share/doc/perl-File-Copy-Recursive-0.38/README 0000644 00000001733 14755625520 0015205 0 ustar 00 usr/share/doc/perl-CPAN-Meta-2.120921/README 0000644 00000022325 14755625611 0013365 0 ustar 00 usr/share/doc/GeoIP-1.5.0/README 0000644 00000017406 14755625623 0011535 0 ustar 00 usr/share/doc/harfbuzz-1.7.5/README 0000644 00000001564 14755625636 0012436 0 ustar 00 usr/share/doc/bash-completion-2.1/README 0000644 00000041552 14755625722 0013514 0 ustar 00 usr/share/doc/hesiod-3.2.1/README 0000644 00000003650 14755625734 0012044 0 ustar 00 usr/share/doc/nmap-ncat-6.40/README 0000644 00000011374 14755625735 0012400 0 ustar 00 usr/share/doc/bison-3.0.4/README 0000644 00000004361 14755626030 0011672 0 ustar 00 usr/share/doc/perl-HTTP-Daemon-6.01/README 0000644 00000024122 14755626111 0013417 0 ustar 00 usr/share/doc/perl-File-Temp-0.23.01/README 0000644 00000101143 14755626216 0013443 0 ustar 00 usr/share/doc/libmpc-1.0.1/README 0000644 00000000742 14755626242 0012025 0 ustar 00 usr/share/doc/perl-Module-Metadata-1.000018/README 0000644 00000017117 14755626264 0014724 0 ustar 00 usr/share/doc/perl-threads-shared-1.43/README 0000644 00000000735 14755626352 0014351 0 ustar 00 usr/share/doc/perl-Text-ParseWords-3.29/README 0000644 00000002433 14755626363 0014473 0 ustar 00 usr/share/doc/ledmon-0.92/README 0000644 00000002514 14755626401 0011764 0 ustar 00 usr/share/doc/perl-Socket6-0.23/README 0000644 00000005021 14755626403 0012754 0 ustar 00 usr/share/doc/collectd-5.8.1/README 0000644 00000107523 14755626411 0012367 0 ustar 00 usr/share/doc/attr-2.4.46/README 0000644 00000000646 14755626453 0011636 0 ustar 00 usr/share/doc/perl-DateTime-1.04/README 0000644 00000000347 14755626456 0013150 0 ustar 00 usr/share/doc/mailx-12.5/README 0000644 00000015146 14755626474 0011634 0 ustar 00 usr/share/doc/mysql-community-libs-compat-5.7.44/README 0000644 00000001066 14755626524 0016263 0 ustar 00 usr/share/doc/euca2ools-3.4.1/README 0000644 00000003223 14755626562 0012463 0 ustar 00 usr/share/doc/os-prober-1.58/README 0000644 00000006602 14755626611 0012426 0 ustar 00 usr/share/doc/blktrace-1.0.5/README 0000644 00000011646 14755626637 0012367 0 ustar 00 usr/share/doc/perl-ExtUtils-MakeMaker-6.68/README 0000644 00000000661 14755626643 0015104 0 ustar 00 usr/share/doc/perl-Proc-PID-File-1.27/README 0000644 00000001603 14755626646 0013650 0 ustar 00 usr/share/doc/libdaemon-0.14/README 0000644 00000016006 14755626700 0012435 0 ustar 00 usr/share/doc/perl-Sys-Syslog-0.33/README 0000644 00000003027 14755626700 0013477 0 ustar 00 usr/share/doc/libzip-0.10.1/README 0000644 00000002163 14755626712 0012131 0 ustar 00 usr/share/doc/rfkill-0.4/README 0000644 00000000606 14755626726 0011714 0 ustar 00 usr/share/doc/screen-4.1.0/README 0000644 00000006555 14755626740 0012054 0 ustar 00 usr/share/doc/nfs-utils-1.3.0/README 0000644 00000004401 14755626744 0012510 0 ustar 00 usr/share/doc/setuptool-1.19.11/README 0000644 00000002357 14755626747 0013006 0 ustar 00 usr/share/doc/libmnl-1.0.3/README 0000644 00000002305 14755626753 0012042 0 ustar 00 usr/share/doc/perl-Error-0.17020/README 0000644 00000004552 14755626754 0012775 0 ustar 00 usr/share/doc/perl-Module-Build-0.40.05/README 0000644 00000106754 14755627015 0014161 0 ustar 00 usr/share/doc/libXau-1.0.8/README 0000644 00000021216 14755627060 0012010 0 ustar 00 usr/share/doc/libcgroup-0.41/README 0000644 00000014473 14755627105 0012477 0 ustar 00 usr/share/doc/libXfixes-5.0.3/README 0000644 00000001540 14755627106 0012517 0 ustar 00 usr/share/doc/libXft-2.3.2/README 0000644 00000003021 14755627123 0012004 0 ustar 00 usr/share/doc/python-ply-3.4/README 0000644 00000020603 14755627145 0012552 0 ustar 00 usr/share/doc/mysql-community-server-5.7.44/README 0000644 00000001066 14755627153 0015356 0 ustar 00 usr/share/doc/perl-Net-SSLeay-1.55/README 0000644 00000034122 14755627206 0013336 0 ustar 00 usr/share/doc/perl-XML-SAX-Base-1.08/README 0000644 00000020217 14755627246 0013415 0 ustar 00 usr/share/doc/perl-YAML-Tiny-1.51/README 0000644 00000040741 14755627251 0013135 0 ustar 00 usr/share/doc/python-requestbuilder-0.7.1/README 0000644 00000000000 14755627303 0015125 0 ustar 00 usr/share/doc/autoconf-2.69/README 0000644 00000005313 14755627316 0012340 0 ustar 00 usr/share/doc/expect-5.45/README 0000644 00000034553 14755627317 0012020 0 ustar 00 usr/share/doc/yum-metadata-parser-1.1.4/README 0000644 00000001222 14755627345 0014444 0 ustar 00 usr/share/doc/pm-utils-1.4.1/README 0000644 00000004114 14755627346 0012340 0 ustar 00 usr/share/doc/cpanel-exim-4.96.2/README 0000644 00000037435 14755627374 0013104 0 ustar 00 usr/share/doc/perl-Carp-1.26/README 0000644 00000002246 14755627424 0012341 0 ustar 00 usr/share/doc/stunnel-4.56/README 0000644 00000001301 14755627437 0012205 0 ustar 00 usr/share/doc/cairo-1.15.12/README 0000644 00000015311 14755627522 0012024 0 ustar 00 usr/share/doc/aspell-0.60.6.1/README 0000644 00000040473 14755627563 0012304 0 ustar 00 usr/share/doc/perl-HTTP-Tiny-0.033/README 0000644 00000036342 14755627563 0013241 0 ustar 00 usr/share/doc/htop-2.2.0/README 0000644 00000004220 14755627600 0011525 0 ustar 00 usr/share/doc/perl-Test-Harness-3.28/README 0000644 00000001035 14755627624 0013775 0 ustar 00 usr/share/doc/perl-XML-LibXML-2.0018/README 0000644 00000022606 14755627624 0013347 0 ustar 00 usr/share/doc/perl-Mozilla-CA-20130114/README 0000644 00000005237 14755627724 0013657 0 ustar 00 usr/share/doc/ilmbase-1.0.3/README 0000644 00000003360 14755627752 0012203 0 ustar 00 usr/share/doc/jasper-libs-1.900.1/README 0000644 00000002002 14755627773 0013144 0 ustar 00 usr/share/doc/perl-Pod-POM-0.27/README 0000644 00000003665 14755630026 0012625 0 ustar 00 usr/share/doc/perl-DateTime-TimeZone-1.70/README 0000644 00000024157 14755630041 0014671 0 ustar 00 usr/share/doc/perl-FCGI-0.74/README 0000644 00000005012 14755630044 0012150 0 ustar 00 usr/share/doc/pango-1.42.4/README 0000644 00000005063 14755630046 0011752 0 ustar 00 usr/share/doc/chrony-3.4/README 0000644 00000017636 14755630064 0011737 0 ustar 00 usr/share/doc/python-slip-dbus-0.4.0/README 0000644 00000002045 14755630070 0013772 0 ustar 00 usr/share/doc/perl-Image-Info-1.33/README 0000644 00000001164 14755630107 0013353 0 ustar 00 usr/share/doc/virt-what-1.18/README 0000644 00000005317 14755630121 0012430 0 ustar 00 usr/share/doc/perl-TermReadKey-2.30/README 0000644 00000014325 14755630123 0013613 0 ustar 00 usr/share/doc/libnfsidmap-0.25/README 0000644 00000012421 14755630127 0012770 0 ustar 00 usr/share/doc/xz-5.2.2/README 0000644 00000032325 14755630132 0011222 0 ustar 00 usr/share/doc/python-enum34-1.0.4/README 0000644 00000000200 14755630144 0013175 0 ustar 00 usr/share/doc/libyaml-0.1.4/README 0000644 00000001507 14755630203 0012203 0 ustar 00 usr/share/doc/perl-Image-Base-1.07/README 0000644 00000011360 14755630206 0013332 0 ustar 00 usr/share/doc/man-db-2.6.3/README 0000644 00000027235 14755630210 0011722 0 ustar 00 usr/share/doc/perl-Pod-LaTeX-0.61/README 0000644 00000006655 14755630220 0013143 0 ustar 00 usr/share/doc/perl-Image-Xbm-1.08/README 0000644 00000020716 14755630236 0013217 0 ustar 00 usr/share/doc/perl-Time-Local-1.2300/README 0000644 00000000470 14755630237 0013530 0 ustar 00 usr/share/doc/dbus-python-1.1.1/README 0000644 00000003746 14755630250 0013035 0 ustar 00 usr/share/doc/perl-IPC-Cmd-0.80/README 0000644 00000002006 14755630251 0012551 0 ustar 00 usr/share/doc/perl-CGI-3.63/README 0000644 00000002226 14755630252 0012050 0 ustar 00 usr/share/doc/perl-Class-Singleton-1.4/README 0000644 00000022575 14755630267 0014403 0 ustar 00 usr/share/doc/perl-Template-Toolkit-2.24/README 0000644 00000027773 14755630302 0014652 0 ustar 00 usr/share/doc/qrencode-libs-3.4.1/README 0000644 00000011121 14755630313 0013277 0 ustar 00 usr/share/doc/perl-Thread-Queue-3.02/README 0000644 00000001107 14755630323 0013724 0 ustar 00 usr/share/doc/perl-DB_File-1.830/README 0000644 00000056360 14755630330 0012757 0 ustar 00 usr/share/doc/fprintd-0.8.1/README 0000644 00000002070 14755630347 0012231 0 ustar 00 usr/share/doc/libestr-0.1.9/README 0000644 00000000014 14755630403 0012215 0 ustar 00 usr/share/doc/perl-Storable-2.45/README 0000644 00000010603 14755630417 0013221 0 ustar 00 usr/share/doc/tk-8.5.13/README 0000644 00000002523 14755630444 0011272 0 ustar 00 usr/share/doc/perl-File-Listing-6.04/README 0000644 00000004421 14755630513 0013731 0 ustar 00 usr/share/doc/which-2.20/README 0000644 00000010521 14755630547 0011604 0 ustar 00 etc/fonts/conf.d/README 0000644 00000001722 14756046636 0010522 0 ustar 00 opt/alt/python35/lib64/python3.5/distutils/README 0000644 00000000447 14756052604 0015230 0 ustar 00 opt/alt/python35/lib64/python3.5/site-packages/README 0000644 00000000167 14756053507 0015726 0 ustar 00 usr/lib/dracut/modules.d/98syslog/README 0000644 00000001500 14756117333 0013666 0 ustar 00 usr/share/doc/perl-Expect-1.21/tutorial/README 0000644 00000001204 14756122022 0014514 0 ustar 00 usr/share/httpd/icons/README 0000644 00000011764 14756122464 0011621 0 ustar 00 usr/share/httpd/error/README 0000644 00000004005 14756122560 0011622 0 ustar 00 usr/share/doc/nmap-ncat-6.40/examples/README 0000644 00000000714 14756122630 0014175 0 ustar 00 usr/share/doc/perl-Getopt-Long-2.40/examples/README 0000644 00000000502 14756123023 0015402 0 ustar 00 usr/share/doc/cpanel-dovecot-2.3.21.1/README 0000644 00000011570 14756123715 0013706 0 ustar 00 usr/share/doc/man-pages-overrides-7.9.0/man-pages/README 0000644 00000002432 14756124246 0016311 0 ustar 00 usr/share/doc/man-pages-overrides-7.9.0/ipvsadm/README 0000644 00000004403 14756125625 0016106 0 ustar 00 usr/lib/kbd/unimaps/README 0000644 00000000211 14756140220 0011212 0 ustar 00 usr/share/doc/compat-db47-4.7.25/db-4.7.25/README 0000644 00000000312 14756143435 0014010 0 ustar 00 usr/share/doc/python-ply-3.4/example/README 0000644 00000000473 14756144440 0014201 0 ustar 00 usr/share/doc/python-slip-dbus-0.4.0/example/README 0000644 00000001773 14756145245 0015442 0 ustar 00 usr/share/doc/perl-Test-Harness-3.28/examples/README 0000644 00000004153 14756146034 0015607 0 ustar 00 usr/lib/dracut/modules.d/10i18n/README 0000644 00000010504 14756146175 0013117 0 ustar 00 usr/share/doc/python-ply-3.4/example/GardenSnake/README 0000644 00000000365 14756275370 0016372 0 ustar 00 usr/share/doc/python-ply-3.4/example/ansic/README 0000644 00000000130 14756310424 0015261 0 ustar 00 usr/share/doc/nmap-ncat-6.40/examples/scripts/README 0000644 00000000355 14756314462 0015673 0 ustar 00 usr/share/doc/python-ply-3.4/example/BASIC/README 0000644 00000004717 14756340547 0015035 0 ustar 00 usr/share/doc/perl-Error-0.17020/examples/next-in-loop/README 0000644 00000000244 14756342010 0017113 0 ustar 00 usr/share/doc/nmap-ncat-6.40/examples/scripts/http-scan/README 0000644 00000000707 14756405067 0017577 0 ustar 00 opt/cpanel/ea-php74/root/usr/share/doc/ea-php74-runtime-7.4.33/README 0000644 00000003732 14756460111 0020232 0 ustar 00 opt/cpanel/ea-php71/root/usr/share/doc/ea-php71-php-cli-7.1.33/README 0000644 00000001472 14756533210 0020072 0 ustar 00 opt/cpanel/ea-php56/root/usr/share/doc/ea-php56-runtime-5.6.40/README 0000644 00000003732 14756534710 0020237 0 ustar 00 opt/cpanel/ea-php56/root/usr/share/doc/ea-php56-php-cli-5.6.40/README 0000644 00000001474 14756537667 0020127 0 ustar 00 opt/cpanel/ea-php72/root/usr/share/doc/ea-php72-runtime-7.2.34/README 0000644 00000003732 14756557600 0020237 0 ustar 00 opt/cpanel/ea-ruby24/root/usr/share/doc/ea-ruby24-runtime-2.4.10/README 0000644 00000002603 14756562052 0020575 0 ustar 00 etc/cloud/cloud.cfg.d/README 0000644 00000000247 14757625236 0011417 0 ustar 00 usr/share/apache2/icons/README 0000644 00000011764 14757656674 0012021 0 ustar 00 usr/share/doc/pyparsing-1.5.6/README 0000644 00000003633 14757674217 0012616 0 ustar 00 usr/share/doc/perl-Archive-Tar-1.92/README 0000644 00000001030 14757674275 0013562 0 ustar 00 usr/lib64/python2.7/Demo/cgi/README 0000644 00000000665 14757676033 0012404 0 ustar 00 usr/lib64/python2.7/Demo/sockets/README 0000644 00000001164 14757677160 0013312 0 ustar 00 usr/lib64/python2.7/Demo/threads/README 0000644 00000000670 14757703111 0013254 0 ustar 00 usr/lib64/python2.7/Demo/md5test/README 0000644 00000000665 14757703130 0013214 0 ustar 00 usr/lib64/python2.7/Demo/parser/README 0000644 00000002006 14757703547 0013126 0 ustar 00 usr/lib64/python2.7/lib-tk/test/README 0000644 00000001066 14757703633 0013110 0 ustar 00 usr/lib64/python2.7/Demo/embed/README 0000644 00000001466 14757704210 0012703 0 ustar 00 usr/lib64/python2.7/Demo/tkinter/README 0000644 00000000635 14757706363 0013317 0 ustar 00 usr/lib64/python2.7/Demo/tkinter/matt/README 0000644 00000001001 14757731651 0014246 0 ustar 00 opt/alt/python38/share/doc/alt-python38-click-6.6/README 0000644 00000001303 14757762366 0016241 0 ustar 00 opt/alt/python38/lib64/python3.8/distutils/README 0000644 00000000362 14757762411 0015237 0 ustar 00 opt/alt/python38/share/doc/alt-python38-PyYAML-5.4.1/README 0000644 00000003014 14757763112 0016352 0 ustar 00 opt/cpanel/ea-php70/root/usr/share/doc/ea-php70-runtime-7.0.33/README 0000644 00000003732 14760026411 0020212 0 ustar 00 opt/cpanel/ea-php70/root/usr/share/doc/ea-php70-php-cli-7.0.33/README 0000644 00000001474 14760030255 0020065 0 ustar 00 opt/cpanel/ea-php80/root/usr/share/doc/ea-php80-runtime-8.0.30/README 0000644 00000003732 14760035640 0020216 0 ustar 00 opt/cpanel/ea-php72/root/usr/share/doc/ea-php72-php-cli-7.2.34/README 0000644 00000001472 14760061144 0020073 0 ustar 00 opt/cpanel/ea-php71/root/usr/share/doc/ea-php71-runtime-7.1.33/README 0000644 00000003732 14761317653 0020231 0 ustar 00 usr/share/doc/git-1.8.3.1/README 0000644 00000005101 14764636507 0011512 0 ustar 00 usr/share/doc/PyYAML-3.10/README 0000644 00000002473 14764640330 0011553 0 ustar 00 usr/share/doc/expat-2.1.0/README 0000644 00000013236 14764640571 0011704 0 ustar 00 usr/share/doc/perl-IO-Tty-1.10/README 0000644 00000003226 14764647361 0012533 0 ustar 00 usr/share/doc/libfontenc-1.1.3/README 0000644 00000001240 14764650452 0012677 0 ustar 00 usr/share/tk8.5/images/README 0000644 00000000502 14764747321 0011471 0 ustar 00 usr/share/doc/langtable-0.0.31/README 0000644 00000003063 14764752435 0012575 0 ustar 00 usr/lib64/python2.7/Demo/scripts/README 0000644 00000001761 14764753340 0013322 0 ustar 00 usr/share/doc/perl-Config-Tiny-2.14/README 0000644 00000011141 14764754673 0013601 0 ustar 00 usr/share/doc/perl-IO-stringy-2.110/README 0000644 00000031041 14764754673 0013535 0 ustar 00 usr/lib64/python2.7/Demo/README 0000644 00000003640 14764770146 0011634 0 ustar 00 usr/share/doc/zlib-1.2.7/README 0000644 00000012101 14764770317 0011522 0 ustar 00 usr/share/doc/fuse-2.9.2/README 0000644 00000025152 14764770321 0011534 0 ustar 00 usr/share/doc/file-libs-5.11/README 0000644 00000012212 14764770744 0012356 0 ustar 00 usr/share/doc/pinentry-0.8.1/README 0000644 00000005621 14764770744 0012446 0 ustar 00 usr/share/doc/p11-kit-0.23.5/README 0000644 00000000453 14764770744 0012043 0 ustar 00 P11-KIT Provides a way to load and enumerate PKCS#11 modules. Provides a standard configuration setup for installing PKCS#11 modules in such a way that they're discoverable. Also solves problems with coordinating the use of PKCS#11 by different components or libraries living in the same process. usr/share/doc/lua-5.1.4/README 0000644 00000002542 14764770747 0011362 0 ustar 00 usr/share/doc/libwebp-0.3.0/README 0000644 00000051062 14764771301 0012202 0 ustar 00 usr/share/doc/pyxattr-0.5.1/README 0000644 00000002660 14764771301 0012274 0 ustar 00 usr/share/doc/cronie-1.4.11/README 0000644 00000001037 14764771301 0012116 0 ustar 00 usr/share/doc/perl-IO-HTML-1.00/README 0000644 00000001676 14764772025 0012521 0 ustar 00 usr/share/doc/grub2-common-2.02/README 0000644 00000001556 14764772034 0013017 0 ustar 00 usr/share/doc/perl-PlRPC-0.2020/README 0000644 00000027603 14764772036 0012533 0 ustar 00 usr/share/doc/perl-XML-SAX-0.99/README 0000644 00000002144 14764772036 0012553 0 ustar 00 usr/share/doc/libjpeg-turbo-1.2.90/README 0000644 00000033162 14764772604 0013424 0 ustar 00 usr/share/doc/perl-DBD-SQLite-1.39/README 0000644 00000150007 14764772606 0013212 0 ustar 00 usr/share/doc/perl-Class-Load-0.20/README 0000644 00000000462 14764772723 0013370 0 ustar 00 usr/share/doc/perl-Digest-SHA-5.85/README 0000644 00000002263 14764772761 0013321 0 ustar 00 usr/share/doc/yum-langpacks-0.4.2/README 0000644 00000002014 14764773225 0013334 0 ustar 00 usr/lib64/python2.7/site-packages/README 0000644 00000000167 14764773232 0013470 0 ustar 00 usr/share/doc/perl-File-Path-2.09/README 0000644 00000002756 14764773411 0013233 0 ustar 00 usr/share/doc/git-1.8.3.1/contrib/README 0000644 00000004101 14764773425 0013152 0 ustar 00 usr/share/doc/perl-Data-OptList-0.107/README 0000644 00000000475 14764774021 0013776 0 ustar 00 usr/share/doc/cpanel-exim-4.98.1/README 0000644 00000037507 14764774022 0013076 0 ustar 00 usr/share/doc/perl-Sub-Uplevel-0.24/README 0000644 00000012104 14764774463 0013614 0 ustar 00 usr/share/doc/perl-libwww-perl-6.05/README 0000644 00000005105 14764774466 0013737 0 ustar 00 usr/share/doc/perl-Pod-Checker-1.60/README 0000644 00000005152 14764774467 0013547 0 ustar 00 usr/share/doc/python-prettytable-0.7.2/README 0000644 00000042675 14764775066 0014470 0 ustar 00
| ver. 1.4 |
Github
|
.
| PHP 8.0.30 | Génération de la page: 0.04 |
proxy
|
phpinfo
|
Réglages