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