Alan McKinnon <alan.mckinnon <at> gmail.com> writes:
> In cases where a quick command to display something doesn't exist, it's > usually because it never occurred to the developer that there could be > another way I find in my own experience that I usually know what driver > is being used - I set the machines up after all - and if I do need to verify > the driver, I also want the error messages related to it. Which are sitting > in the log file If we followed that logic, why would we have things like 'lspci'....? After all, we could go grepping (egrep fgrep etc) who needs lspci anyway, certainly not an experienced admin.... I get it. parse the file. No big deal, just surprised me. James
