'\" te
.\" Copyright (c) 2007, 2015, Oracle and/or its affiliates. All rights reserved.
.TH contents 4 "29 Jan 2015" "SunOS 5.11" "File Formats"
.SH NAME
contents \- list of files and associated packages
.SH SYNOPSIS
.LP
.nf
\fB/var/sadm/install/contents\fR
.fi

.SH DESCRIPTION
.sp
.LP
The file \fB/var/sadm/install/contents\fR is a source of information about the packages installed via the SVR4 package system. This file must never be edited directly.
.sp
.LP
Each entry in the \fBcontents\fR file is a single line. Fields in each entry are separated by a single space character.
.sp
.LP
Two major styles of entries exist, old style and new style. The following is the format of an old-style entry:
.sp
.in +2
.nf
\fIftype\fR \fIclass\fR \fIpath\fR \fIpackage(s)\fR
.fi
.in -2

.sp
.LP
The following is the general format of a new-style entry:
.sp
.in +2
.nf
\fIpath\fR[=\fIrpath\fR] \fIftype\fR \fIclass\fR [\fIftype-optional-fields\fR] \fIpackage(s)\fR
.fi
.in -2

.sp
.LP
New-style entries differ for each \fBftype\fR. The \fBftype\fR designates the entry type, as specified in \fBpkgmap\fR(4). The format for new-style entries, for each \fBftype\fR, is as follows:
.sp
.in +2
.nf
ftype s: \fIpath\fR=\fIrpath\fR s \fIclass\fR \fIpackage\fR
ftype l: \fIpath\fR l \fIclass\fR \fIpackage\fR
ftype d: \fIpath\fR d \fIclass\fR \fImode\fR \fIowner\fR \fIgroup\fR \fIpackage(s)\fR
ftype b: \fIpath\fR b \fIclass\fR \fImajor\fR \fIminor\fR \fImode\fR \fIowner\fR \fIgroup\fR \fIpackage\fR
ftype c: \fIpath\fR c \fIclass\fR \fImajor\fR \fIminor\fR \fImode\fR \fIowner\fR \fIgroup\fR \fIpackage\fR
ftype f: \fIpath\fR f \fIclass\fR \fImode\fR \fIowner\fR \fIgroup\fR \fIsize\fR \fIcksum\fR \fImodtime\fR \fIpackage\fR
ftype x: \fIpath\fR x \fIclass\fR \fImode\fR \fIowner\fR \fIgroup\fR \fIpackage\fR
ftype v: \fIpath\fR v \fIclass\fR \fImode\fR \fIowner\fR \fIgroup\fR \fIsize\fR \fIcksum\fR \fImodtime\fR \fIpackage\fR
ftype e: \fIpath\fR e \fIclass\fR \fImode\fR \fIowner\fR \fIgroup\fR \fIsize\fR \fIcksum\fR \fImodtime\fR \fIpackage\fR
.fi
.in -2

.sp
.LP
A significant distinction between old- and new-style entries is that the former do not begin with a slash (/) character, while the latter (new-style) always do. For example, the following are old-style entries:
.sp
.in +2
.nf
d none /dev SUNWcsd
e passwd /etc/passwd SUNWcsr
.fi
.in -2

.sp
.LP
The following are new-style entries:
.sp
.in +2
.nf
/dev d none 0755 root sys SUNWcsr SUNWcsd
/etc/passwd e passwd 0644 root sys 580 48299 1077177419 SUNWcsr
.fi
.in -2

.sp
.LP
The following are the descriptions of the fields in both old- and new-style entries.
.sp
.ne 2
.mk
.na
\fB\fIpath\fR\fR
.ad
.RS 11n
.rt  
The absolute path of the node being described. For \fBftype\fR \fBs\fR (indicating a symbolic link) this is the indirect pointer (link) name.
.RE

.sp
.ne 2
.mk
.na
\fB\fIrpath\fR\fR
.ad
.RS 11n
.rt  
The relative path to the real file or linked-to directory name.
.RE

.sp
.ne 2
.mk
.na
\fB\fIftype\fR\fR
.ad
.RS 11n
.rt  
A one-character field that indicates the entry type (see \fBpkgmap\fR(4)).
.RE

.sp
.ne 2
.mk
.na
\fB\fIclass\fR\fR
.ad
.RS 11n
.rt  
The installation class to which the file belongs (see \fBpkgmap\fR(4)).
.RE

.sp
.ne 2
.mk
.na
\fB\fIpackage\fR\fR
.ad
.RS 11n
.rt  
The package associated with this entry. For \fBftype\fR \fBd\fR (directory) more than one package can be present.
.RE

.sp
.ne 2
.mk
.na
\fB\fImode\fR\fR
.ad
.RS 11n
.rt  
The octal mode of the file (see \fBpkgmap\fR(4)).
.RE

.sp
.ne 2
.mk
.na
\fB\fIowner\fR\fR
.ad
.RS 11n
.rt  
The owner of the file (see \fBpkgmap\fR(4)).
.RE

.sp
.ne 2
.mk
.na
\fB\fIgroup\fR\fR
.ad
.RS 11n
.rt  
The group to which the file belongs (see \fBpkgmap\fR(4)).
.RE

.sp
.ne 2
.mk
.na
\fB\fImajor\fR\fR
.ad
.RS 11n
.rt  
The major device number (see \fBpkgmap\fR(4)).
.RE

.sp
.ne 2
.mk
.na
\fB\fIminor\fR\fR
.ad
.RS 11n
.rt  
The minor device number (see \fBpkgmap\fR(4)).
.RE

.sp
.ne 2
.mk
.na
\fB\fIsize\fR\fR
.ad
.RS 11n
.rt  
The actual size of the file in bytes as reported by sum (see \fBpkgmap\fR(4)).
.RE

.sp
.ne 2
.mk
.na
\fB\fIcksum\fR\fR
.ad
.RS 11n
.rt  
The checksum of the file contents (see \fBpkgmap\fR(4)).
.RE

.sp
.ne 2
.mk
.na
\fB\fImodtime\fR\fR
.ad
.RS 11n
.rt  
The time of last modification (see \fBpkgmap\fR(4)).
.RE

.SH ATTRIBUTES
.sp
.LP
See \fBattributes\fR(5) for descriptions of the following attributes:
.sp

.sp
.TS
tab() box;
cw(2.75i) |cw(2.75i) 
lw(2.75i) |lw(2.75i) 
.
ATTRIBUTE TYPEATTRIBUTE VALUE
_
Availabilitysystem/core-os
_
Interface StabilityUncommitted
.TE

.SH SEE ALSO
.sp
.LP
\fBpkgadd\fR(1M), \fBpkgadm\fR(1M), \fBpkgchk\fR(1M), \fBpkgmap\fR(4), \fBattributes\fR(5)
.SH NOTES
.sp
.LP
As shown above, the interface stability of \fB/var/sadm/install/contents\fR is Uncommitted (see \fBattributes\fR(5)). It is common practice to use this file in a read-only manner to determine which files belong to which packages installed on a system. While this file has been present for many releases of the Solaris operating system, it might not be present in future releases. The fully supported way to obtain information from the installed package database is through \fBpkgchk\fR(1M). It is highly recommended that you use \fBpkgchk\fR rather than relying on the \fBcontents\fR file.
.sp
.LP
Note that only packages installed via SVR4 package commands are included in the \fBcontents\fR file. While \fBpkgchk\fR(1M) is the recommended way to query for packages, you need to use \fBpkg\fR(1) to query most of the packages on the system as they will be installed via IPS instead of SVR4.