1.

A. The instance name represents the kernel’s abbreviation name for every possible device on the system. For more information, see the “Device Drivers” section.

2.

D. Physical device files are found in the /devices directory. For more information, see the “Physical Device Name” section.

3.

D. The sysdef command displays device configuration information, including system hardware, pseudo devices, loadable modules, and selected kernel parameters. For more information, see the “Physical Device Name” section.

4.

C. When you see the driver not attached message, it means no driver is currently attached to the device instance because there is no device at this node or the device is not in use. For more information, see the “Physical Device Name” section.

5.

A. The .conf files reside in the /kernel/drv directories. For more information, see the “Device Autoconfiguration” section.

6.

B. Instance names are mapped to a physical device name in the /etc/path_to_inst file. For more information, see the “Instance Names” section.

7.

A, B. You can determine the mapping of an instance name to a physical device name by looking at the dmesg output and by viewing the /var/adm/messages file. For more information, see the “Instance Names” section.

8.

A, B. The system relies on information found in both the /etc/vfstab file and the /etc/path_to_inst file to find the root, usr, and swap device. For more information, see the “Instance Names” section.

9.

C. The devfsadm command a creates logical links to device nodes in /dev and /devices and loads the device policy. For more information, see the “Instance Names” section.

10.

D. The devfsadm command is used to inform the system about newly installed device drivers. For more information, see the “Instance Names” section.

11.

A. The devfsadmd daemon is the daemon responsible for handling both reconfiguration boot processing and updating /dev and /devices in response to dynamic reconfiguration event notifications from the kernel. For more information, see the “Instance Names” section.

12.

C. An example of when to use the devfsadm command would be if the system has been started, but the power to the CD-ROM or tape drive was not turned on. During startup, the system did not detect the device; therefore, its drivers were not installed. The devfsadm command will perform these tasks. For more information, see the “Instance Names” section.

13.

B. The major device number indicates the general device driver for devices such as disk, tape, or serial line. For more information, see the “Major and Minor Device Numbers” section.

14.

B. The minor device number indicates the specific member within a driver. For more information, see the “Major and Minor Device Numbers” section.

15.

D. The logical device name is a link from the /dev directory to the physical device name located in the /devices directory. For more information, see the “Logical Device Name” section.

16.

C. The logical device name is a link from the /dev directory to the physical device name located in the /devices directory. For more information, see the “Logical Device Name” section.

17.

A. The logical device name is a link from the /dev directory to the physical device name located in the /devices directory. The following is an example of a logical device name: /dev/dsk/c0t0d0s7. For more information, see the “Logical Device Name” section.

18.

A. The devfsadm command can be used to create entries in the /dev directory for disk drives attached to the system. For more information, see the “Instance Names” section.

19.

D. The /dev/dsk directory contains the disk entries for the block device nodes in /devices. For more information, see the “Block and Raw Devices” section.

20.

A. A physical device name represents the full device pathname of the device. Physical device files are found in the /devices directory and have the following naming convention:

For more information, see the “Physical Device Name” section.

21.

B. The fields of the logical device name cXtYdZ are as follows:

For more information, see the “Logical Device Name” section.

22.

B. In the character device name /dev/rdsk/c0t3d0s0, the /rdsk directory refers to the character or raw device file. The r in rdsk stands for raw. For more information, see the “Block and Raw Devices” section.

23.

A. The instance name represents the kernel’s abbreviated name for every possible device on the system. For example, sd0 and sd1 represent the instance names of two SCSI disk devices. For more information, see the “Instance Names” section.

24.

A. Logical device names are used with most Solaris file system commands to refer to devices. Logical device files in the /dev directory are symbolically linked to physical device files in the /devices directory. For more information, see the “Logical Device Name” section.

25.

A. Logical device files in the /dev directory are symbolically linked to physical device files in the /devices directory. For more information, see the “Logical Device Name” section.

26.

D. On a standard Solaris file system, a file system cannot span multiple disks or slices. It’s only possible when using virtual file systems (that is, Solaris Volume Manager). For more information, see the “Disk Slices” section.

27.

A. Disk configuration information is stored on the disk label. For more information, see the “Displaying Disk Configuration Information” section.

28.

A. The boot block stores the procedures used in booting the system. Without a boot block, the system does not boot. For more information, see the “Components of the UFS” section.

29.

A. The slice information for a particular disk can be viewed by using the prtvtoc command. For more information, see the “Disk Slices” section.

30.

A. The following are virtual file systems: swapfs, procfs, lofs, cachefs, tmpfs, and mntfs. For more information, see the “Virtual File Systems” section.

31.

D. The format utility is used to retrieve corrupted disk labels, repair defective sectors, format and analyze disks, partition disks, and label disks. For more information, see the “Using the format Utility to Create Slices” section.

32.

D. Here are a few of the more important things contained in a superblock:

For more information, see the “The Superblock” section.

33.

A, C. An inode contains all of the information about a file except its name, which is kept in a directory. The inode information is kept in the cylinder information block and contains the following:

For more information, see the “The inode” section.

34.

D. As a general rule, a larger logical block size increases efficiency for file systems in which most of the files are large. Use a smaller logical block size for file systems in which most of the files are small. For more information, see the “Logical Block Size” section.

35.

A. The number of inodes depends on the amount of disk space that is allocated for each inode and the total size of the file system. For more information, see the “The inode” section.

36.

A. The file system fragment size is the smallest allocable unit of disk space, which by default is 1024 bytes. For more information, see the “Information on File Systems” section.

37.

A. Swap space plus the total amount of physical memory is also referred to as virtual memory. For more information, see the “Virtual File Systems” section.

38.

A, B, C. fsck should be run after a power outage, when a file system is unmounted improperly, or whenever a file system cannot be mounted. For more information, see the “Repairing File Systems” section.

39.

B. Normally, fsck is run noninteractively at bootup to preen the file systems after an abrupt system halt. Preening automatically fixes any basic file system inconsistencies and does not try to repair more serious errors. While preening a file system, fsck fixes the inconsistencies it expects from such an abrupt halt. For more serious conditions, the command reports the error and terminates. For more information, see the “Repairing File Systems” section.

40.

C. The /etc/vfstab file contains a list of file systems to be automatically mounted when the system is booted to the multiuser state. For more information, see the “Creating an Entry in the /etc/vfstab File to Mount File Systems” section.

41.

B. The mountall command mounts all file systems specified in the file system table (vfstab). For more information, see the “Mounting File Systems” section.

42.

E. The following commands can be used to display disk space usage: du, df, quota, repquota. For more information, see the “Displaying a File System’s Disk Space Usage” section.

43.

A. The largefiles mount option lets users mount a file system containing files larger than 2GB. For more information, see the “Mounting File Systems” section.

44.

A. Use the -o nologging option of the mount command to disable UFS logging on a file system. Logging is the default. For more information, see the “Mounting File Systems” section.

45.

A. The correct format for the /etc/vfstab file is as follows:

device to mount, device to fsck, mount point, FS type, fsck pass, mount at boot, mount options.

For more information, see the “Creating an Entry in the /etc/vfstab File to Mount File Systems” section.

46.

A. Use the du (directory usage) command to report the number of free disk blocks and files. For more information, see the “Displaying a File System’s Disk Space Usage” section.

47.

A. The df command with no options lists all mounted file systems and their device names. It also lists the total number of 512-byte blocks used and the number of files. For more information, see the “Displaying a File System’s Disk Space Usage” section.

48.

A. Typically, creating large numbers of small files causes high fragmentation. The solution is to either create a larger file system or to decrease the block size (finer granularity). For more information, see the “Displaying a File System’s Disk Space Usage” section.

49.

B. The df -k command does not display the percentage of fragmentation. For more information, see the “Displaying a File System’s Disk Space Usage” section.

50.

D. newfs is the friendly front end to the mkfs command. The newfs command automatically determines all the necessary parameters to pass to mkfs to construct new file systems. newfs was added in Solaris to make the creation of new file systems easier. It’s highly recommended that the newfs command be used to create file systems. For more information, see the “Creating a UFS” section.

51.

D. After you create the file system with newfs, you can use the labelit utility to write or display labels on unmounted disk file systems. For more information, see the “Creating a UFS” section.

52.

A. Use the fstyp command to determine a file system type. For example, use it to check whether a file system is a UFS. For more information, see the “The fstyp Command” section.

53.

B. Use the tunefs command to change the minfree value of a file system. For more information, see the “Tuning File Systems” section.

54.

A. Use the fstyp command to view file system parameters. Use the -v option to obtain a full listing of a file system’s parameters. For more information, see the “The fstyp Command” section.

55.

D. A large file is a regular file whose size is greater than or equal to 2GB. For more information, see the “Mounting a File System with Large Files” section.

56.

B. A utility is called large file–aware if it can process large files in the same manner that it does small files. A large file—aware utility can handle large files as input and can generate large files as output. The vi command is not large file–aware. For more information, see the “Mounting a File System with Large Files” section.

57.

C. As stated in the previous question and answer, a utility is called large file–aware if it can process large files in the same manner that it does small files. A large file–aware utility can handle large files as input and can generate large files as output. For more information, see the “Mounting a File System with Large Files” section.

58.

D. The -o nolargefiles option of the mount command provides total compatibility with previous file system behavior, enforcing the 2GB maximum file size limit. For more information, see the “Mounting a File System with Large Files” section.

59.

A. Type the mount command with the -p option to display a list of mounted file systems in /etc/vfstab format. For more information, see the “Creating an Entry in the /etc/vfstab File to Mount File Systems” section.

60.

B. The following command uses the mount command to map a directory to a file system as read/writeable, disallow setuid execution, and enable the creation of large files (more than 2GB in size):

For more information, see the “Mounting a File System with Large Files” section.

61.

A. When a file system is mounted, an entry is maintained in the mounted file system table called /etc/mnttab. This file is actually a read-only file system and contains information about devices that are currently mounted. For more information, see the “Mounting File Systems” section.

62.

C. D. Do not use the following commands on a mounted file system: fsck, and labelit. newfs cannot be run on a mounted file system—it generates an error. For more information, see the “Unmounting a File System” section.

63.

A. If something is causing the file system to be busy, you can use the fuser command to list all of the processes accessing the file system and to stop them if necessary. For more information, see the “The fuser Command” section.

64.

A. The following command stops all processes that are using the /home2 file system by sending a SIGKILL to each one: fuser -c -k /home2. For more information, see the “The fuser Command” section.

65.

C. The vold daemon is the mechanism that manages removable media, such as the CD-ROM and floppy disk drives. For more information, see the “Volume Management” section.

66.

D. vold does not automatically mount a file system located on another system when that file system is accessed. The facility responsible for that task is AutoFS. For more information, see the “Volume Management” section.

67.

B. /dev/rdiskette and /vol/dev/rdiskette0 are the directories providing character device access for the medium in the primary floppy drive, usually drive 0. For more information, see the “Volume Management” section.

68.

C. vold reads the /etc/vold.conf configuration file at startup. The vold.conf file contains the Volume Manager configuration information used by vold. For more information, see the “Volume Management” section.

69.

A. The “Actions” section of the vold.conf file specifies which program should be called if a particular event (action) occurs such as eject or insert. For more information, see the “Volume Management” section.

70.

C. The volmissing action in the vold.conf file notifies the user if an attempt is made to access a CD or diskette that is no longer in the drive. For more information, see the “Volume Management” section.

71.

D. Use the fdformat command to format a floppy disk, and then add a volume label. For more information, see the “Troubleshooting Volume Manager” section.

72.

B. Run the following run control script to stop the volume management daemon: /etc/init.d/volmgt stop. For more information, see the “Troubleshooting Volume Manager” section.

73.

D. The df command gives you capacity information on each mounted file system. For more information, see the “Displaying a File System’s Disk Space Usage” section.

74.

A. The volcheck command instructs vold to look at each device and determine if new media has been inserted into the drive. The system administrator issues this command to check the drive for installed media. By default, it checks the drive to which /dev/diskette points. For more information, see the “Volume Management” section.

75.

C. You can type mount /opt on the command line and not get an error message if /opt is listed in the /etc/vfstab file. For more information, see the “Creating an Entry in the /etc/vfstab File to Mount File Systems” section.

76.

A. Volume Manager provides access to the floppy disk and CD-ROM devices through the /vol/dev directory. For more information, see the “Volume Management” section.

77.

D. Volume management does not automatically fsck file systems at bootup. It does, however, automatically mount CD-ROM and file systems when removable media containing recognizable file systems are inserted into the devices. For more information, see the “Volume Management” section.

78.

C. The /etc directory contains configuration files that define a system’s identity. For more information, see the “The Root (/) File System” section.

79.

B. A hard link cannot span file systems, but a symbolic link can. For more information, see the “Hard Links” section.

80.

A. An advantage of a symbolic link over a hard link is that you can create a symbolic link to a file that does not yet exist. For more information, see the “Soft (Symbolic) Links” section.

81.

B. Remove a link using the rm command. For more information, see the “Soft (Symbolic) Links” section.

82.

B. The SMC Disks Tool cannot be used to format a disk. For more information, see the “Using the Solaris Management Console Disks Tool” section.