New answers tagged documentation
Source code is going to be your best bet. You can in a pinch use the command strings to get some basic ideas about a binary and text that it may contain. Example Here are the first 20 lines of the output. These are the lines that contain the string "error" in them. $ strings /usr/sbin/mkfs.ext3 | grep -i error | head -20 Syntax error in mke2fs config file ...
lspci is part of pciutils, which is portable to a variety of unix-like OS's and windows, so it presumably uses different methods depending on platform. You should be able to tell where it gets its info from in your case via strace lspci. After the preamble accessing libraries, etc, I (using fedora linux) get a lot of open() + pread() calls on stuff in ...
/proc I believe it was moved to /proc/bus/pci, so that all the buses could be kept in a single spot. $ pwd /proc/bus/pci Example lspci output: $ lspci | tail -10 03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 0d:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01) 0d:00.1 System peripheral: Ricoh Co Ltd Device e230 (rev ...
I've been using the RHEL6 docs instead. They're essentially the same. https://access.redhat.com/site/documentation/Red_Hat_Enterprise_Linux/ Here are the CentOS 6 Release Notes, if you're interested. The highlight the above link there as well.
Top 50 recent answers are included