Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Administration: Common Tasks Oracle Solaris 11 Information Library |
1. Locating Information About Oracle Solaris Commands
2. Managing User Accounts and Groups (Overview)
3. Managing User Accounts and Groups (Tasks)
4. Booting and Shutting Down an Oracle Solaris System
5. Working With Oracle Configuration Manager
6. Managing Services (Overview)
9. Managing System Information (Tasks)
Displaying System Information (Task Map)
How to Display a System's Release Information
How to Display a System's Host ID Number
How to Display a System's Product Name
How to Display a System's Installed Memory
How to Display Default and Customized Property Values for a Device
How to Display the Date and Time
Identifying Information About Chip Multithreading Features
How to Display a System's Physical Processor Type
How to Display a System's Logical Processor Type
Changing System Information (Task Map)
How to Manually Set a System's Date and Time
How to Set Up a Message-Of-The-Day
How to Change a System's Identity (nodename)
10. Managing System Processes (Tasks)
11. Monitoring System Performance (Tasks)
12. Managing Software Packages (Tasks)
14. Scheduling System Tasks (Tasks)
15. Setting Up and Administering Printers by Using CUPS (Tasks)
16. Managing the System Console, Terminal Devices, and Power Services (Tasks)
17. Managing System Crash Information (Tasks)
18. Managing Core Files (Tasks)
19. Troubleshooting System and Software Problems (Tasks)
20. Troubleshooting Miscellaneous System and Software Problems (Tasks)
System-provided driver.conf files can be supplemented with administratively provided driver.conf files. Vendor-provided (system-provided) driver data is preserved in the root file system, while administratively provided driver configuration is stored separately in a new /etc/driver/drv directory. The format of an administratively provided driver.conf file is identical to a system-provided driver.conf file.
At boot time, and whenever a driver.conf file for a driver is searched for and loaded, the system will also check for the driver in the driver.conf file within the /etc/driver/drv directory. If found, the system automatically merges the vendor-provider driver.conf files with the local, administratively provided driver.conf files. The driver's view of the system properties consists of these merged properties. Therefore, no driver changes are necessary.
Note that vendor-provided driver.conf files that are in the /kernel and /platform directories can no longer be edited. If you need to supplement a driver's configuration, instead of editing the vendor-provided driver.conf file, add a corresponding driver.conf file to the local /etc/driver/drv directory, then customize that file.
To display the merged properties, use the prtconf command. Note that the prtconf command has a new -u option. This option enables you to display both the original and updated property values for a driver. For instructions, see How to Display Default and Customized Property Values for a Device.
For more information, see the driver(4) and driver.conf(4) man pages.