1contents(4) File Formats contents(4)
2
3
4
6 contents - list of files and associated packages
7
9 /var/sadm/install/contents
10
11
13 The file /var/sadm/install/contents is a source of information about
14 the packages installed on the system. This file must never be edited
15 directly. Always use the package and patch commands (see SEE ALSO) to
16 make changes to the contents file.
17
18
19 Each entry in the contents file is a single line. Fields in each entry
20 are separated by a single space character.
21
22
23 Two major styles of entries exist, old style and new style. The follow‐
24 ing is the format of an old-style entry:
25
26 ftype class path package(s)
27
28
29
30 The following is the general format of a new-style entry:
31
32 path[=rpath] ftype class [ftype-optional-fields] package(s)
33
34
35
36 New-style entries differ for each ftype. The ftype designates the entry
37 type, as specified in pkgmap(4). The format for new-style entries, for
38 each ftype, is as follows:
39
40 ftype s: path=rpath s class package
41 ftype l: path l class package
42 ftype d: path d class mode owner group package(s)
43 ftype b: path b class major minor mode owner group package
44 ftype c: path c class major minor mode owner group package
45 ftype f: path f class mode owner group size cksum modtime package
46 ftype x: path x class mode owner group package
47 ftype v: path v class mode owner group size cksum modtime package
48 ftype e: path e class mode owner group size cksum modtime package
49
50
51
52 A significant distinction between old- and new-style entries is that
53 the former do not begin with a slash (/) character, while the latter
54 (new-style) always do. For example, the following are old-style
55 entries:
56
57 d none /dev SUNWcsd
58 e passwd /etc/passwd SUNWcsr
59
60
61
62 The following are new-style entries:
63
64 /dev d none 0755 root sys SUNWcsr SUNWcsd
65 /etc/passwd e passwd 0644 root sys 580 48299 1077177419 SUNWcsr
66
67
68
69 The following are the descriptions of the fields in both old- and new-
70 style entries.
71
72 path The absolute path of the node being described. For ftype s
73 (indicating a symbolic link) this is the indirect pointer
74 (link) name.
75
76
77 rpath The relative path to the real file or linked-to directory
78 name.
79
80
81 ftype A one-character field that indicates the entry type (see
82 pkgmap(4)).
83
84
85 class The installation class to which the file belongs (see
86 pkgmap(4)).
87
88
89 package The package associated with this entry. For ftype d (direc‐
90 tory) more than one package can be present.
91
92
93 mode The octal mode of the file (see pkgmap(4)).
94
95
96 owner The owner of the file (see pkgmap(4)).
97
98
99 group The group to which the file belongs (see pkgmap(4)).
100
101
102 major The major device number (see pkgmap(4)).
103
104
105 minor The minor device number (see pkgmap(4)).
106
107
108 size The actual size of the file in bytes as reported by sum (see
109 pkgmap(4)).
110
111
112 cksum The checksum of the file contents (see pkgmap(4)).
113
114
115 modtime The time of last modification (see pkgmap(4)).
116
117
119 See attributes(5) for descriptions of the following attributes:
120
121
122
123
124 ┌─────────────────────────────┬─────────────────────────────┐
125 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
126 ├─────────────────────────────┼─────────────────────────────┤
127 │Availability │SUNWcsr │
128 ├─────────────────────────────┼─────────────────────────────┤
129 │Interface Stability │Unstable │
130 └─────────────────────────────┴─────────────────────────────┘
131
133 patchadd(1M), pkgadd(1M), pkgadm(1M), pkgchk(1M), pkgmap(4),
134 attributes(5)
135
137 As shown above, the interface stability of /var/sadm/install/contents
138 is Unstable (see attributes(5)). It is common practice to use this file
139 in a read-only manner to determine which files belong to which packages
140 installed on a system. While this file has been present for many
141 releases of the Solaris operating system, it might not be present in
142 future releases. The fully supported way to obtain information from the
143 installed package database is through pkgchk(1M). It is highly recom‐
144 mended that you use pkgchk rather than relying on the contents file.
145
146
147
148SunOS 5.11 20 Dec 2007 contents(4)