| 1 |
This seems to have tremendous potential. Having all this information in |
| 2 |
one standard form allows you to take snapshots of your system, and then |
| 3 |
if things break you can compare snapshots before and after to possibly |
| 4 |
get a hint of where to focus. This will be especially true when you add |
| 5 |
the ability to list packages and software installed. |
| 6 |
|
| 7 |
It could also be useful when trying to help solve a problem, especially |
| 8 |
remotely. |
| 9 |
|
| 10 |
Why not set this up as a sourceforge project? |
| 11 |
|
| 12 |
M |
| 13 |
|
| 14 |
|
| 15 |
On Tue, 29 Nov 2005, darren kirby wrote: |
| 16 |
|
| 17 |
> quoth the Harry Putnam: |
| 18 |
> |
| 19 |
>> I'm sure many such scripts have been written in the past 35yrs. I |
| 20 |
>> hoped a few would have become famous and available by name that I |
| 21 |
>> could simply edit. |
| 22 |
> |
| 23 |
> Perhaps so, but I decided to write one anyway. Just 'stroking the beard' I |
| 24 |
> guess. It is in python, as I cannot stand Perl. |
| 25 |
> |
| 26 |
> I have only spent a few hours on this, so it is still rough around the edges |
| 27 |
> (ie: there is virtually no error checking so far), but good enough to post |
| 28 |
> now I think. I will spend the next few days polishing it up. |
| 29 |
> |
| 30 |
> Problems with it: |
| 31 |
> 1. For now, it only works properly on single cpu systems. If you have 2+ cpu's |
| 32 |
> it will just print "Couldn't get cpu info" |
| 33 |
> 2. Hardware is just a dump of 'lspci'; user and group is just a dump |
| 34 |
> of /etc/passwd and /etc/group. I will fix this so that it actually displays a |
| 35 |
> useful report in the next few days... |
| 36 |
> 3. May not work on systems with hardware I don't have ;) That is, I have not |
| 37 |
> tested with devices such as tape drives, raid arrays etc...so the script |
| 38 |
> might break with this sort of input (or perhaps just ignore it) |
| 39 |
> 4. No package/software listing yet. I want to do this in a distro neutral way. |
| 40 |
> |
| 41 |
> What it does so far: |
| 42 |
> 1. print meta info: hostname, distro, architecture (ie i686) |
| 43 |
> 2. cpu details: model, speed, cache, bogomips |
| 44 |
> 3. memory and memory usage details (including swap) |
| 45 |
> 4. kernel information: version, uptime, cmdline, loaded modules, supported |
| 46 |
> filesystems etc... |
| 47 |
> 5. hardware (lspci for now...) |
| 48 |
> 6. network info: interfaces, ip address, broadcast, netmask, MAC, default GW, |
| 49 |
> nameservers |
| 50 |
> 7. mounted devices: net mounts, pseudo mounts, disk usage |
| 51 |
> 8. Users, groups |
| 52 |
> |
| 53 |
> I would like to do this thing right, so if you (anybody!) has ideas, advice, |
| 54 |
> requests etc please try it out and let's talk. Am I missing anything that |
| 55 |
> should be printed? |
| 56 |
> |
| 57 |
> As mentioned, I have tomorrow free, so I will plug away at it more then... |
| 58 |
> |
| 59 |
> You can download at: |
| 60 |
> http://badcomputer.org/unix/code/sysinfo.py.gz |
| 61 |
> |
| 62 |
> or just view and cut/paste the code from: |
| 63 |
> http://badcomputer.org/unix/code/sysinfo.bot |
| 64 |
> |
| 65 |
> -d |
| 66 |
> -- |
| 67 |
> darren kirby :: Part of the problem since 1976 :: http://badcomputer.org |
| 68 |
> "...the number of UNIX installations has grown to 10, with more expected..." |
| 69 |
> - Dennis Ritchie and Ken Thompson, June 1972 |
| 70 |
> |
| 71 |
-- |
| 72 |
gentoo-user@g.o mailing list |
Archives