2 .\" This file and its contents are supplied under the terms of the
3 .\" Common Development and Distribution License ("CDDL"), version 1.0.
4 .\" You may only use this file in accordance with the terms of version
7 .\" A full copy of the text of the CDDL should have accompanied this
8 .\" source. A copy of the CDDL is also available via the Internet at
9 .\" http://www.illumos.org/license/CDDL.
12 .\" Copyright (c) 2014 Joyent, Inc. All rights reserved.
15 .TH BOOTFS 7FS "Nov 23, 2016"
17 bootfs \- boot-time module file system
23 file system is a read-only file system that provides access to any
24 boot-time modules that were passed in to the system loader which were
28 does not display any boot-time modules that were tagged as type
33 If modules with duplicate names and paths are specified, only the first
34 such entry will be present in the file system and a counter will be
35 incremented to indicate that a duplicate entry was found, but is not
36 present into the file system. If a module's name only consists of
37 invalid characters, such as '.', '..', or '/', then the module will not
38 be present in the file system and a counter will be incremented to
39 indicate that this has occurred. In both cases, diagnostic information
40 is available through the kstats facility.
48 The mount point for the
50 file system in the global zone.
55 Example 1 Determining if collisions or invalid names are present
58 To determine if any boot-time modules were not created due to collisions
59 or invalid names, enter the following command:
65 module: bootfs instance: 1
66 name: bootfs class: fs
67 crtime 236063.651324041
73 snaptime 236063.651324041
80 lists the number of boot-time modules that were discarded due to naming conflicts. The field
82 lists the number of duplicate entries that were found and therefore not displayed in the file system.
85 This information is provided for informational purposes only, it is not to be construed as a stable interface.