Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

osinfo-query(1) [centos man page]

OSINFO-QUERY.C(1)					      Virtualization Support						 OSINFO-QUERY.C(1)

NAME
osinfo-query - Query information in the database SYNOPSIS
osinfo-query [OPTIONS...] TYPE [CONDITION-1 [CONDITION-2 ...]] DESCRIPTION
The "osinfo-query" command allows extraction of information from the database. TYPE can be one of "os", "platform", "device", or "deployment". With no conditions specified, all entities of the given type will be listed. # List all operating systems $ osinfo-query os Short ID | Name ... ----------------------+----------- centos-6.0 | CentOS 6.0 ... centos-6.1 | CentOS 6.1 ... ... Conditions allow filtering based on specific properties of an entity. For example, to filter only distros from the Fedora Project, use # List all operating systems $ osinfo-query os vendor="Fedora Project" Short ID | Name ... ----------------------+-------------- fedora1 | Fedora Core 1 ... fedora2 | Fedora Core 2 ... ... The set of fields which are printed can be controlled using the "--fields" command line argument: # List all operating systems $ osinfo-query --fields=short-id,version os vendor="Fedora Project" Short ID | Version ----------------------+---------- fedora1 | 1 fedora2 | 2 ... OPTIONS
-s PROPERTY, --sort-key PROPERTY Set the data sorting key. Defaults sorting the first column -f PROPERTY1,PROPERTY2,..., --fields PROPERTY1,PROPERTY2,... Set the visibility of properties in output PROPERTY NAMES
OS Valid property names for the "os" type are: short-id The short OS identifier name The long OS name version The OS version string family The OS kernel family vendor The OS vendor release-date The OS release date eol-date The OS end-of-life date codename The OS code name id The OS identifier PLATFORM Valid property names for the "platform" type are: short-id The short platform identifier name The long platform name version The platform version string vendor The platform vendor release-date The platform release date eol-date The platform end-of-life date codename The platform code name id The platform identifier DEVICE Valid property names for the "device" type are: name The device name product The device product name product-id The device product ID string vendor The device vendor name vendor-id The device vendor ID string class The device type class bus The device bus type id The device identifier DEPLOYMENT Valid property names for the "deployment" type are: id The deployment identifier EXIT STATUS
The exit status will be 0 if matching entries were found, or 1 if not matches were found SEE ALSO
"osinfo-db-validate(1)", "osinfo-detect(1)" AUTHORS
Daniel P. Berrange <berrange@redhat.com> COPYRIGHT
Copyright (C) 2012 Red Hat, Inc. LICENSE
"osinfo-query" is distributed under the termsof the GNU LGPL v2+ license. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE libosinfo-0.2.7 2013-02-06 OSINFO-QUERY.C(1)

Check Out this Related Man Page

EMVENDOR(1)						User Contributed Perl Documentation					       EMVENDOR(1)

Name
       emvendor - retrieve vendor-specific package configuration strings

Synopsis
	emvendor -V|--vendor VENDOR -p|--package PACKAGE -k|--key KEY
	emvendor -?|-h|--help|--version

Commands
	-v|--vendor VENDOR:    the vendor name from dpkg-vendor
	-p|--package PACKAGE:  the package name (usually source)
	-k|--key KEY:	       arbitrary string for the key of the data

       All commands must be specified every time.

       On success, the string is printed and emvendor exits with zero.

       In the case of error, emvendor dies with an empty string on STDERR and exits with a non-zero return value.

Description
       emvendor provides a way for debian/rules to call in a string for a particular package that fits into the rules for that package and
       conforms to the requirements of the vendor.

       http://wiki.debian.org/EmdebianAuditDetail#Vendor

       It is fairly obvious that specifying each vendor in the debian/rules file of each package is not going to be particularly flexible.

	DEB_VENDOR=$(shell dpkg-vendor --query vendor)
	ifeq (Debian,$(DEB_VENDOR))
	 # Debian build
	 EXCONFARGS=--disable-mono --disable-monodoc
	else
	 # any-vendor build
	 EXCONFARGS=$(shell emvendor --vendor $(DEB_VENDOR) --package avahi --key EXCONFARGS)
	endif

       or use the short options:

	EXCONFARGS=$(shell foo-bar -V $(DEB_VENDOR) -p avahi -k EXCONFARGS)

       The values themselves are in a vendor-specific conf file in /etc/emvendor.d/

	$ cat /etc/foo-bar.d/emdebian-crush
	[avahi]
	EXCONFARGS=--disable-mono --disable-monodoc --disable-python
	--disable-doxygen-doc --disable-pygtk --disable-python-dbus
	--disable-core-docs --disable-qt3 --disable-qt4 --disable-gobject
	--with-distro debian

	[busybox]
	foo=

       (Note that the value has to be all on one line which is a little awkward - also note that values are not able to include the equals sign
       which could be more of an issue.)

       Packages that need two strings can do so - the key string is entirely arbitrary as long as it fits in the style of a typical ini file.

       Therefore, the key can be matched to the needs of the relevant package.

       "emdebian-buildsupport" provides /etc/emvendor.d/emdebian-crush with all the content for all packages that need such details.

emvendor and dpkg-vendor
       dpkg-vendor supports vendor functionality but emvendor adds an extra hierarchy, organised by Debian source package name. It would be
       possible to include the relevant strings in /etc/dpkg/origins/vendor but each identifier string would need to be unique across all packages
       for each vendor, which is an unrealistic limitation.

perl v5.14.2							    2012-09-26							       EMVENDOR(1)
Man Page

Featured Tech Videos