lsb_release(1) [redhat man page]
FSG(1) FSG FSG(1) NAME
FSG - manual page for FSG lsb_release v1.4 SYNOPSIS
lsb_release [OPTION]... DESCRIPTION
FSG lsb_release v1.4 prints certain LSB (Linux Standard Base) and Distribution information. With no OPTION specified it is the same as -v. OPTIONS
-v, --version Display the version of the LSB specification against which the distribution is compliant. -i, --id Display the string id of the distributor. -d, --description Display the single line text description of the distribution. -r, --release Display the release number of the distribution. -c, --codename Display the codename according to the distribution release. -a, --all Display all of the above information. -s, --short Display all of the above information in short output format. -h, --help Display this message. FILES
If the installation is LSB compliant, the "/etc/lsb-release" file should contain the LSB_VERSION field. The value of the field should be the version number of the LSB specification against which the installation is compliant. If the installation is not compliant, the above field should not be present. Optional fields are DISTRIB_ID, DISTRIB_RELEASE, DISTRIB_CODENAME, DISTRIB_DESCRIPTION and can be used to overwrite information which is parsed from the next file. The "/etc/[distrib]-release" file contains a description line which is parsed to get information (especially on currently non-LSB compliant systems). The required line style is: "Distributor release x.x (Codename)" Where Distributor can be a couple of words, but then concatenated (i.e. Linux Foo BarLinux Linux -> FooBarLinux), x.x starts with a digit followed by any non-blank characters, Codename will also be concatenated (blanks cleanup only). And release is a keyword not to be used in DISTRIB_DESCRIPTION if you don't want to overwrite "/etc/[distrib]-release" data. Notice: To support the Debian distributions' lack of information (see "/etc/debian_version" file) some have been directly added into the lsb_release script. EXAMPLES
The /etc/lsb-release file contains: LSB_VERSION="1.0" DISTRIB_DESCRIPTION="I enjoy using my distrib" And the /etc/foobar-release file contains: My Linux Distrib release 1.0RC4 (TryIt) $ ./lsb_release --all LSB Version: 1.0 Distributor ID: MyDistrib Description: I enjoy using my distrib Release: 1.0RC4 Codename: TryIt $ ./lsb_release -a -s 1.0 MyDistrib "I enjoy using my distrib" 1.0RC4 TryIt Then simply without the "/etc/lsb-release" file, that means result on a non-LSB compliant distrib: $ ./lsb_release -a LSB Version: n/a Distributor ID: MyDistrib Description: My Linux Distrib release 1.0RC4 (TryIt) Release: 1.0RC4 Codename: TryIt AUTHOR
Written by Dominique MASSONIE. REPORTING BUGS
Report bugs to <mdomi@users.sourceforge.net>. Include a complete, self contained example that will allow the bug to be reproduced, and say which version of lsb_release you are using. COPYRIGHT
Copyright (C) 2000 Free Software Group, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU- LAR PURPOSE. FSG lsb_release v1.4 February 2003 FSG(1)
Check Out this Related Man Page
epm(1) Easy Software Products epm(1) NAME
epm - create software packages. SYNOPSIS
epm [ -a architecture ] [ -f format ] [ -g ] [ -k ] [ -m name ] [ -n[mrs] ] [ -s setup.xpm ] [ --depend ] [ --help ] [ --keep-files ] [ --output-dir directory ] [ --setup-image setup.xpm ] [ --setup-program /foo/bar/setup ] [ --setup-types setup.types ] [ -v ] [ name=value ... name=value ] product [ listfile ] DESCRIPTION
epm generates software packages complete with installation, removal, and (if necessary) patch scripts. Unless otherwise specified, the files required for product are read from a file named "product.list". The -a option ("architecture") specifies the actual architecture for the software. Without this option the generic processor architecture is used ("intel", "sparc", "mips", etc.) The -f option ("format") specifies the distribution format: aix Generate an AIX distribution suitable for installation on an AIX system. bsd Generate a BSD distribution suitable for installation on a FreeBSD, NetBSD, or OpenBSD system. deb Generate a Debian distribution suitable for installation on a Debian Linux system. inst, tardist Generate an IRIX distribution suitable for installation on an system running IRIX. lsb, lsb-signed Generate RPM packages for LSB-conforming systems. The lsb-signed format uses the GPG private key you have defined in the ~/.rpmmacros file. native Generate an native distribution. This uses rpm for Linux, inst for IRIX, pkg for Solaris, swinstall for HP-UX, bsd for FreeBSD, Net- BSD, and OpenBSD, and osx for MacOS X. All other operating systems default to the portable format. osx Generate a MacOS X software package. pkg Generate an AT&T software package. These are used primarily under Solaris. portable Generate a portable distribution based on shell scripts and tar files. The resulting distribution is installed and removed the same way on all operating systems. [default] rpm, rpm-signed Generate a Red Hat Package Manager ("RPM") distribution suitable for installation on a Red Hat Linux system. The rpm-signed format uses the GPG private key you have defined in the ~/.rpmmacros file. setld Generate a Tru64 (setld) software distribution. slackware Generate a Slackware Linux software distribution. swinstall, depot Generate a HP-UX software distribution. Executable files in the distribution are normally stripped of debugging information when packaged. To disable this functionality use the -g option. Intermediate (spec, etc.) files used to create the distribution are normally removed after the distribution is created. The -k option keeps these files in the distribution directory. The -s and --setup-image options ("setup") include the ESP Software Wizard with the specified GIF or XPM image file with the distribution. This option is currently only supported by portable and RPM distributions. The --setup-program option specifies the setup executable to use with the distribution. This option is currently only supported by portable distributions. The --setup-types option specifies the setup.types file to include with the distribution. This option is currently only supported by porta- ble distributions. The --output-dir option specifies the directory to place output file into. The default directory is based on the operating system, version, and architecture. The -v option ("verbose") increases the amount of information that is reported. Use multiple v's for more verbose output. The --depend option lists the dependent (source) files for all files in the package. Distributions normally are named "product-version-system-release-machine.ext" and "product-version-system-release-machine-patch.ext" (for patch distributions.) The "system-release-machine" information can be customized or eliminated using the -n option with the appropriate trailing letters. Using -n by itself will remove the "system-release-machine" string from the filename entirely. The "system-release- machine" information can also be customized by using the -m option with an arbitrary string. Debian, IRIX, portable, and Red Hat distributions use the extensions ".deb", ".tardist", "tar.gz", and ".rpm" respectively. LIST FILES
The EPM list file format is now described in the epm.list(5) man page. KNOWN BUGS
EPM does not currently support generation of IRIX software patches. SEE ALSO
epminstall(1) - add a directory, file, or symlink to a list file mkepmlist(1) - make an epm list file from a directory epm.list(5) - epm list file format setup(1) - graphical setup program for the esp package manager COPYRIGHT
Copyright 1999-2008 by Easy Software Products, All Rights Reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER- CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. 26 August 2008 ESP Package Manager epm(1)