Re: [gentoo-user] Succinct compilation of system info...

Re: [gentoo-user] Succinct compilation of system info...

[Scott Stoddard]

Harry Putnam wrote:
> What is the standard or common way to compile a detailed yet succinct
> listing of system info.  
> 
> Are there tools that do this?  Or maybe one of those 16 inch cmdlines
> with 2 dozen pipes... :)
> 

Well, if you're talking about all hardware then I tend to prefer 
sys-apps/lshw which can generate ascii/html output or run with a gui.

If you want more of a summary of things, you could consider lspci and 
lsusb (found in pciutils and usbutils respectively).

Scott.
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Succinct compilation of system info...

[Harry Putnam]

What is the standard or common way to compile a detailed yet succinct
listing of system info.  

Are there tools that do this?  Or maybe one of those 16 inch cmdlines
with 2 dozen pipes... :)

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: Succinct compilation of system info...

[Harry Putnam]

Scott Stoddard <scott@cs.ubishops.ca> writes:

> Harry Putnam wrote:
>> What is the standard or common way to compile a detailed yet succinct
>> listing of system info.  Are there tools that do this?  Or maybe one
>> of those 16 inch cmdlines
>> with 2 dozen pipes... :)
>> 
>
> Well, if you're talking about all hardware then I tend to prefer
> sys-apps/lshw which can generate ascii/html output or run with a gui.
>
> If you want more of a summary of things, you could consider lspci and
> lsusb (found in pciutils and usbutils respectively).

Thanks, I wasn't aware of lshw.   But I was thinking more along the
lines BelarcAdvisor in the windows world.

But different in the sense that it isn't gui.  With Belarc you have to
start and run the gui, which generates an html page.  To get a text
file you can `save as' from the gui.

I want straight command line so redirect is possible, but a thorough
summary.  Not just hdw or pci or usb.  I want that but also what
filesystems, which users, all installed software. How much data on
which partitions, all devices broken down into their uses such as
ethernet, disk controller etc etc.

In general a full scope summary.  It seems this would have been
invented long ago, for the treasure trove it would supply to
developers. 

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: Succinct compilation of system info...

[Bob Sanders]

On Mon, 28 Nov 2005 22:31:28 -0600
Harry Putnam <reader@newsguy.com> wrote:


> I want straight command line so redirect is possible, but a thorough
> summary.  Not just hdw or pci or usb.  I want that but also what
> filesystems,

	df -h
	cat /etc/fstab

> which users, 

	cat /etc/passwd
	cat /etc/group

> all installed software.

	emerge -evt world

> How much data on
> which partitions, 

	du -hSx /
	du -hSx /home
	...for each partition of interest.  Probably need to do some sorting and summaries
		with grep, sed, and awk.

> all devices broken down into their uses such as
> ethernet, disk controller etc etc.
>

	lshw 
	-or- 
	lshw -short
	lshw -businfo
	lshw -html
	etc.

> In general a full scope summary.  It seems this would have been
> invented long ago, for the treasure trove it would supply to
> developers. 
>

It was never hidden and has always been available.  The commands, excepting
lshw, have been available since the 1970s.  And lots of system inventory scripts
are in existance.  Many written obscurely in Perl and other languages.

Bob
-  
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: Succinct compilation of system info...

[Harry Putnam]

Bob Sanders <rmsand@concentric.net> writes:

> It was never hidden and has always been available.  

Not sure I understand that comment.  Or rather I am sure I do not.

>                        The commands, excepting lshw, have been
> available since the 1970s.  And lots of system inventory scripts are
> in existance.  Many written obscurely in Perl and other languages.

Thanks for the handy list.  I know all those tools of course but
assumed someone would have had enough time during those 35 yrs to have
assembled a nifty script that I could just edit for my own needs.

I've never subscribed to the fool notion that I must do it myself from
the ground up, mainly so that I could smugly stroke my grey guru
beard.  I'd happily save a good bit of time instead.

I'm sure many such scripts have been written in the past 35yrs.  I
hoped a few would have become famous and available by name that I
could simply edit.

You mentioned possibly obscure system inventory scripts in perl.  
So apparently you already know it can be a time consuming undertaking
to dig one up with google, test it, etc etc.

Do you know of one off the top of your head? Hopefully not too
obscure. 


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: Succinct compilation of system info...

[Bob Sanders]

On Tue, 29 Nov 2005 08:36:38 -0600
Harry Putnam <reader@newsguy.com> wrote:

> 
> You mentioned possibly obscure system inventory scripts in perl.  
> So apparently you already know it can be a time consuming undertaking
> to dig one up with google, test it, etc etc.
> 
> Do you know of one off the top of your head? Hopefully not too
> obscure. 
>

Sorry.  The last one I worked with was -
		- dependant upon some obscure layer on top of perl, no longer maintained.
		- used tricks to avoid typing clean code.
		- written by people no longer around when I tried to make it work.
		- broken by updates to both the system, perl, various CPAN modules and
		  relied on the web server being Netscape Enterprise.
		- Dedicated to IRIX systems.

I could really rant about this, but I'll just let it go.

Bob
-  
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: Succinct compilation of system info...

[darren kirby]

[-- Attachment #1: Type: text/plain, Size: 2285 bytes --]

quoth the Harry Putnam:

> I'm sure many such scripts have been written in the past 35yrs.  I
> hoped a few would have become famous and available by name that I
> could simply edit.

Perhaps so, but I decided to write one anyway. Just 'stroking the beard' I 
guess. It is in python, as I cannot stand Perl.

I have only spent a few hours on this, so it is still rough around the edges 
(ie: there is virtually no error checking so far), but good enough to post 
now I think. I will spend the next few days polishing it up.

Problems with it:
1. For now, it only works properly on single cpu systems. If you have 2+ cpu's 
it will just print "Couldn't get cpu info"
2. Hardware is just a dump of 'lspci'; user and group is just a dump 
of /etc/passwd and /etc/group. I will fix this so that it actually displays a 
useful report in the next few days...
3. May not work on systems with hardware I don't have ;) That is, I have not 
tested with devices such as tape drives, raid arrays etc...so the script 
might break with this sort of input (or perhaps just ignore it)
4. No package/software listing yet. I want to do this in a distro neutral way.

What it does so far:
1. print meta info: hostname, distro, architecture (ie i686)
2. cpu details: model, speed, cache, bogomips
3. memory and memory usage details (including swap)
4. kernel information: version, uptime, cmdline, loaded modules, supported 
filesystems etc...
5. hardware (lspci for now...)
6. network info: interfaces, ip address, broadcast, netmask, MAC, default GW, 
nameservers
7. mounted devices: net mounts, pseudo mounts, disk usage
8. Users, groups 

I would like to do this thing right, so if you (anybody!) has ideas, advice, 
requests etc  please try it out and let's talk. Am I missing anything that 
should be printed?

As mentioned, I have tomorrow free, so I will plug away at it more then...

You can download at:
http://badcomputer.org/unix/code/sysinfo.py.gz

or just view and cut/paste the code from:
http://badcomputer.org/unix/code/sysinfo.bot

-d
-- 
darren kirby :: Part of the problem since 1976 :: http://badcomputer.org
"...the number of UNIX installations has grown to 10, with more expected..."
- Dennis Ritchie and Ken Thompson, June 1972

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: Succinct compilation of system info...

[Harry Putnam]

darren kirby <bulliver@badcomputer.org> writes:

> I would like to do this thing right, so if you (anybody!) has ideas, advice, 
> requests etc  please try it out and let's talk. Am I missing anything that 
> should be printed?

Thanks for the effort.  It looks promising.  I've downloaded but not
tried yet.  I'm not likely to be much help since I know nothing of
python but may be able to test it on at least one different system and
report.

I don't have any tricky hardware though... just normal stuff.

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: Succinct compilation of system info...

[Harry Putnam]

Bob Sanders <rmsand@concentric.net> writes:

> Sorry.  The last one I worked with was -

Thanks... I guess thats probably about par for the course.. hehe

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] [OT] Re: Succinct compilation of system info...

[darren kirby]

[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]

I have put up an update.

Now user/groups are presented more usefully (including heuristics to separate 
human from system users). Also, it now lists packages for Gentoo, Arch Linux, 
and RPM based distros. (debian based on the way...)

On Gentoo systems, first it checks for epm, and if found uses that. epm's 
output is much more friendly programmatically, and response is near instant.

If there is no epm, it uses "equery list" which takes a while on my system, 
and breaks the columned output. Are there any other commands to print nice 
output of all installed packages?

Still working on hardware output, and in this department I could really use 
the output from 'lspci' on an array of different systems to help detect the 
largest spread of possible hardware. Especially useful would be lspci output 
from SCSI and SATA systems. If you feel up to it, please feel free to email 
me this info off-list. 

You can download at:
 http://badcomputer.org/unix/code/sysinfo.py.gz

or just view and cut/paste the code from:
http://badcomputer.org/unix/code/sysinfo.bot

 -d

-- 
darren kirby :: Part of the problem since 1976 :: http://badcomputer.org
"...the number of UNIX installations has grown to 10, with more expected..."
- Dennis Ritchie and Ken Thompson, June 1972

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Re: Succinct compilation of system info...

[michael]

This seems to have tremendous potential. Having all this information in
one standard form allows you to take snapshots of your system, and then
if things break you can compare snapshots before and after to possibly
get a hint of where to focus. This will be especially true when you add
the ability to list packages and software installed.

It could also be useful when trying to help solve a problem, especially
remotely.

Why not set this up as a sourceforge project?

M


On Tue, 29 Nov 2005, darren kirby wrote:

> quoth the Harry Putnam:
>
>> I'm sure many such scripts have been written in the past 35yrs.  I
>> hoped a few would have become famous and available by name that I
>> could simply edit.
>
> Perhaps so, but I decided to write one anyway. Just 'stroking the beard' I
> guess. It is in python, as I cannot stand Perl.
>
> I have only spent a few hours on this, so it is still rough around the edges
> (ie: there is virtually no error checking so far), but good enough to post
> now I think. I will spend the next few days polishing it up.
>
> Problems with it:
> 1. For now, it only works properly on single cpu systems. If you have 2+ cpu's
> it will just print "Couldn't get cpu info"
> 2. Hardware is just a dump of 'lspci'; user and group is just a dump
> of /etc/passwd and /etc/group. I will fix this so that it actually displays a
> useful report in the next few days...
> 3. May not work on systems with hardware I don't have ;) That is, I have not
> tested with devices such as tape drives, raid arrays etc...so the script
> might break with this sort of input (or perhaps just ignore it)
> 4. No package/software listing yet. I want to do this in a distro neutral way.
>
> What it does so far:
> 1. print meta info: hostname, distro, architecture (ie i686)
> 2. cpu details: model, speed, cache, bogomips
> 3. memory and memory usage details (including swap)
> 4. kernel information: version, uptime, cmdline, loaded modules, supported
> filesystems etc...
> 5. hardware (lspci for now...)
> 6. network info: interfaces, ip address, broadcast, netmask, MAC, default GW,
> nameservers
> 7. mounted devices: net mounts, pseudo mounts, disk usage
> 8. Users, groups
>
> I would like to do this thing right, so if you (anybody!) has ideas, advice,
> requests etc  please try it out and let's talk. Am I missing anything that
> should be printed?
>
> As mentioned, I have tomorrow free, so I will plug away at it more then...
>
> You can download at:
> http://badcomputer.org/unix/code/sysinfo.py.gz
>
> or just view and cut/paste the code from:
> http://badcomputer.org/unix/code/sysinfo.bot
>
> -d
> -- 
> darren kirby :: Part of the problem since 1976 :: http://badcomputer.org
> "...the number of UNIX installations has grown to 10, with more expected..."
> - Dennis Ritchie and Ken Thompson, June 1972
>
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: Succinct compilation of system info...

[darren kirby]

[-- Attachment #1: Type: text/plain, Size: 1531 bytes --]

quoth the michael@michaelshiloh.com:
> This seems to have tremendous potential. Having all this information in
> one standard form allows you to take snapshots of your system, and then
> if things break you can compare snapshots before and after to possibly
> get a hint of where to focus. 

Yup. I was thinking it would be good for a weekly (or daily) cron report 
delivered to your mailbox. Maybe an option to only send a diff from the 
previous run...

> This will be especially true when you add 
> the ability to list packages and software installed.

Which is done (for Gentoo, Arch, Fedora, RHEL, SuSe).

> It could also be useful when trying to help solve a problem, especially
> remotely.

 Also, put it on your favorite live/rescue cd and have instant info on 
unfamiliar systems...

> Why not set this up as a sourceforge project?

I am not sure that a project of this scope really needs full blown sourceforge 
project page...a bug tracker, forums, and three pages just to download the 
thing seem a bit extreme...I think I can host from my site, at least for now.

This isn't to say I don't appreciate testers and bug reports...

I am still plugging away, and will try to have a real, polished tarball 
release with a man page etc up before the weekend is done.

> M

Thanks,
-d
-- 
darren kirby :: Part of the problem since 1976 :: http://badcomputer.org
"...the number of UNIX installations has grown to 10, with more expected..."
- Dennis Ritchie and Ken Thompson, June 1972

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Re: Succinct compilation of system info...

[luis jure]

el 2005-12-01 darren kirby escribió:

> This isn't to say I don't appreciate testers and bug reports...

if this is of any use...

Filesystems supported:
        udf | ntfs | iso9660 | vfat | msdos | ext2 | 
        ext3 | 
Other possible supported filesystems (unloaded modules):
Traceback (most recent call last):
  File "/home/lj/sysinfo.py", line 492, in ?
    main()
  File "/home/lj/sysinfo.py", line 467, in main
    getKernelInfo()
  File "/home/lj/sysinfo.py", line 174, in getKernelInfo
    opfs_l = os.listdir("/lib/modules/" + kernv[:-1] + "/kernel/fs")
OSError: [Errno 2] No such file or directory:
'/lib/modules/2.6.13-rt14/kernel/fs'

i have all support for filesystems compiled in the kernel and none as
modules. i didn't have a fs/ directory under /lib/modules/$KERNEL/kernel.
creating by hand such directory made the script work.


nice script by the way, thanks.

best,

lj

-- 
gentoo-user@gentoo.org mailing list