LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-21-2018, 07:06 PM   #76
h2-1
Member
 
Registered: Mar 2018
Distribution: Debian Testing
Posts: 69

Original Poster
Rep: Reputation: Disabled

Quote:
Re: -p. Perhaps the filesystem info should be sourced from elsewhere then? After all, the partition's filesystem info can be obtained with lsblk -fs. In this case, I would think that the fact that a partition is ntfs is more useful information than it is fuseblk (a generic term that may not mean anything to those less-experienced users you talked about before).
Don't look for arguments from me when it comes to inxi being able to be better and more accurate, that's thee entire goal, after all. Sometimes it simply comes down to the simple fact that, well, it's always been that way, and I never rethought it or looked for other solutions.

now, with that said, basically what stuff like this adds is one entire more layer, and then I have to add lsblk to the inxi debugger data collector so I can start to verify what the actual values are from users who submit that data, which is enormously useful to me, it's one of my strongest dev tools, being able to look up that type of data readily.

so some of these are several steps, but I totally agree re lsblk -fs, that's a very good output. Easy to parse. Not on FreeBSD. Just checked, so basically, since really the label and uuid logic works fine as is, all I really need is the fs from that output, though I could make it the primary source for partition data once /dev xx is obtained.

Also keep in mind, there are many variants for partitions, remote, stuff like zfs, so it's not easy to change stuff, but I think in safe cases, it's not bad to start using lsblk as a backup or primary for fs. As you noted, it's obviously more useful to see it's NTFS than fusefs

If null data, or no match, well, nothing changes, fs stays the same. Sounds fine.

Last edited by h2-1; 03-21-2018 at 07:08 PM.
 
Old 03-21-2018, 07:10 PM   #77
h2-1
Member
 
Registered: Mar 2018
Distribution: Debian Testing
Posts: 69

Original Poster
Rep: Reputation: Disabled
Code:
-G
(old) GLX Version: 3.0 Mesa 17.2.8
(new) version: 4.2 Mesa 17.2.8
[glxinfo shows OpenGL version string: 3.0 Mesa 17.2.8; OpenGL core profile version string: 4.2 (Core Profile) Mesa 17.2.8]
Basically, there's a bug in there at one level, the compat version sometimes shows as a high number, > 3. I have that bug, was ignoring it.

Second, inxi was wrong, and pinxi is right, re the output, the 3.0 is the compat version, not the real version, and I'm not clear why about 99% of pinxi examples have it right, and 1% get it wrong. If you can pastebin: glxinfo

I may find the pattern as to why some systems are mixing those up.

Last edited by h2-1; 03-21-2018 at 07:13 PM.
 
Old 03-21-2018, 07:25 PM   #78
hydrurga
LQ Guru
 
Registered: Nov 2008
Location: Pictland
Distribution: Linux Mint 19 MATE
Posts: 5,290
Blog Entries: 2

Rep: Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707
Quote:
Originally Posted by h2-1 View Post
Don't look for arguments from me when it comes to inxi being able to be better and more accurate, that's thee entire goal, after all. Sometimes it simply comes down to the simple fact that, well, it's always been that way, and I never rethought it or looked for other solutions.

now, with that said, basically what stuff like this adds is one entire more layer, and then I have to add lsblk to the inxi debugger data collector so I can start to verify what the actual values are from users who submit that data, which is enormously useful to me, it's one of my strongest dev tools, being able to look up that type of data readily.

so some of these are several steps, but I totally agree re lsblk -fs, that's a very good output. Easy to parse. Not on FreeBSD. Just checked, so basically, since really the label and uuid logic works fine as is, all I really need is the fs from that output, though I could make it the primary source for partition data once /dev xx is obtained.

Also keep in mind, there are many variants for partitions, remote, stuff like zfs, so it's not easy to change stuff, but I think in safe cases, it's not bad to start using lsblk as a backup or primary for fs. As you noted, it's obviously more useful to see it's NTFS than fusefs

If null data, or no match, well, nothing changes, fs stays the same. Sounds fine.
Sorry for asking, as you may well have mentioned this elsewhere, but does this mean that you have a means by which a user can securely send you an "as full as you can get it" inxi output, anonymously, which you can add to a database, after further anonymisation if necessary, so that you can query it for outliers, unusual data, statistics etc.?
 
Old 03-21-2018, 09:16 PM   #79
h2-1
Member
 
Registered: Mar 2018
Distribution: Debian Testing
Posts: 69

Original Poster
Rep: Reputation: Disabled
Yes, one of the core development features of pinxi/inxi is to be able to generate a full dataset for debugging user issues. For example, one of the people I deal with on IRC just solved a bug/issue by such means, the issue in that case was that ps -p $PPID was returning gnome-terminal- [note the dash at the end, that's the bug] and I was trying to find the source of the error. The inxi log showed me that exact output, at which point I realized that the issue is a bug with either ps or gnome-terminal, since apparently it was not like that before. This would be essentially impossible to figure out without that big log file, which is part of the debugger dataset. Since people have every right to have trust concerns with people they may not know online, I did not ask for this during the beta testing process because I'd rather people showed ideas, errors, and feedback, than worry about the datasets I'd normally be requesting, but I can also tell you, I failed to solve some issues because users failed to provide the required data.

pinxi [options] --debug 10 - create full log file, usually in HOME/.local/share/pinxi/pinxi.log or /root/.local...

These do not take options because they run inxi internally and copy the log and output to file
pinxi --debug 20 - create a full debugger dataset, delete directory, leave gz, do not upload it, location, same as log

pinxi --debug 21 - create dataset, upload, delete directory, leave gz.

pinxi --debug 22 - create dataset, upload, delete directory, delete gz. A user asked for this early on, and I immediately realized how good it was as an option, its new, because that means I could run the debugger on a remote server, and not leave anything behind except the log file. Nothing to remember to clean up later. I had always left it so that users could look at it they wanted to, but I realized it's also fine to offer the full cleanup option so they can pick which they want.

These tools are so critical that the very first things I did in pinxi aside from the core initialization stuff was options, so I could trigger the debugger, then the debugger, and the down/upload tools, so I could use the self updater, those were the first parts of perl inxi that were written because they are actually the most important, then I did the color tools, the line generators, then I started on the actual data.

My formula is pretty basic re my time:

1. Direct access to the system. Re debug time, 10x-1000x faster than anything else. On practical terms, I have decided that I will no longer work on BSD stuff if I do not have access to the system via ssh. Otherwise it's a total waste of time, I was stubborn on this, but the example posted in another forum with openbsd output made me realize, either I get ssh access, or bsd doesn't get done. I have some remote bsd servers which is why inxi works very well on that FreeBSD variant.
2. debugger datasets, which is very complete, and allows me to inject the real data internally with some care. This has limits because practically speaking I can only inject 2 files max before it gets too confusing. Often when I'm debugging hard issues, I don't know which files I will need to see, so these datasets basically save me vast amounts of time, in fact, inxi would not exist if it did not have its debugger.
3. asking people for files one at a painful time, waiting to get it, then asking for the next one, etc. This process takes roughly 100x-10000x longer than the debugger dataset takes (which takes about 5 seconds to generate and auto upload), which already has all the data in it that I will need, except for rare cases that are very fringe.

On github, if someone posts an issue, and they don't provide the required data, I usually won't offer further support because it's too time consuming to guess, but in the beta process, I sacrificed this, which has worked out super well.

Nobody sees these except me, they aren't anonymized because they aren't public. I might put simple stuff like /proc/cpuinfo on public spaces, but not the other stuff. They go to my server, run by me, and are removed from it as soon as I download them. It's kind of the only part of pinxi/inxi that isn't truly 'open source', but it can't be, since users trust me with that data, and they aren't wrong to do that, since I only use it for debugging purposes and as a long term database I can refer to over years to figure out arcane issues.

for example, I just added several lsblk variants commands to the debugger data collector. I know why that was never used before, I checked an old Debian install I have, which has perl 5.08, to date it, and that command is not there, so I would not have used a command that was not available on systems that were some years old back when inxi started, and blkid for years has had no output issues on Debian, so that was never a viable candidate, but the lsblk is GREAT, the only downside is that column parsing is difficult, I'm going to look at the output options more because there are no white space null value holders for white space splits, but you can make the report use any columns you want, in any order, really great stuff. It uses the short and correct KMGT for MiB,GiB by the way, which was the other option I thought about for inxi.

the other advantage of using this direct to file or file copy method is that the data doesn't corrupt, which it always does if it's copied to irc or a forum, then copied by me to a file. In fact, I hit such a corruption just the other day, it was sensors output, and the degree symbols as copied were clearly visible on file, but perl refused to see them, and would not parse the file correctly until I told it look for 0 or more instances, not 1, which always works. That kind of corruption makes anything other than direct to file or copy of file output largely useless over time.

The actual reason I finally rewrote inxi into perl was that a core and utterly key debugger component, absolutely indispensible, I literally cannot solve most difficult issues without these, was the python based /sys file system parser tool and uploader, broke, and I could not fix it, and it had never, being python, worked on the slightly older version of python that were on systems slightly older than the python version, and it failed on new stuff, some changes in /sys with some data the kernel guys put in there, so I rewrote it to Perl 5.x, and it was faster, worked on every old and new system I had, all in all better, easier to debug, shorter, etc, and more pleasant in every way than the python it replaced, but that was why I actually realized perl 5 would really work for inxi itself, but it was needing that debugger tool to work that made me rewrite it into perl.

The beta test process also showed me a lot of places where the inxi logger itself was inadequate, and those were corrected as well, in fact, I just fixed two bugs, or found them, by realizing data that was being logged was not being used for output, I had just forgotten about it. Basically in the inxi logger, the amount of data you see in various sections is a direct indication in most cases of how hard debugging that part is without that full data, like the output of the ps -p $PPID command, full output, non touched.

Last edited by h2-1; 03-21-2018 at 10:14 PM.
 
1 members found this post helpful.
Old 03-21-2018, 11:53 PM   #80
h2-1
Member
 
Registered: Mar 2018
Distribution: Debian Testing
Posts: 69

Original Poster
Rep: Reputation: Disabled
inxi / pinxi v 2.9.03 now feature lsblk generated primary selection fs. df fs remains fallback for bsd, and machines without lsblk, which most modern ones will have. unmounted first choice lsblk fs, fallback file, as before, with same failure messages if no lsblk but file.

A very good suggestion, thanks.
 
Old 03-21-2018, 11:57 PM   #81
h2-1
Member
 
Registered: Mar 2018
Distribution: Debian Testing
Posts: 69

Original Poster
Rep: Reputation: Disabled
Core speeds (MHz):

That's the logical one, once you get over 4 cores or 8 with MT/HT, the output gets really messy
 
Old 03-22-2018, 01:02 AM   #82
h2-1
Member
 
Registered: Mar 2018
Distribution: Debian Testing
Posts: 69

Original Poster
Rep: Reputation: Disabled
I think you might be one of the best data output error proof readers I've ever come across, thanks very much.

-p - sort tried, see how it feels/looks. As noted, lsblk is already first choice for fs there now.

-C - Core Speeds (MHz): added, that avoids the visual clutter of putting the same thing after each core, which when you hit 96 core systems starts to get pretty extreme.

-G - inxi is wrong, and pinxi is right, re the gl version, As noted there is a glitch that makes a small subset of systems report the wrong compat-v: which I'll figure out at some point.

-o - fixed, now shows fs via lsblk, a really good and easy improvement to make. Long standing inxi weakness, thanks for bringing it up. I'd of course like the sort to be alpha then numeric, and may do that at a later point, but that perl sort is a bit harder to do than the simple one I used.

-t cm10 lol, that's the 3rd thing, re (..%) that I literally just forgot. The other two are fixed now, G compositor if one is found, I had the data internally but simply forgot to output it. A debugging log file showed me that.

I'll get to the % used tomorrow.

-w/-W are currently strings, not real values. I have the real values, and those will be implemented in the future, but since it's never been that way, I didn't view it as pressing. That would go along with hddtemp units, sensors temp units, and a few other things, so I'd do them all at once. That would also go with a new user config option, UNITS=... something simple that users will enter right, heh. That will trip the conversions when possible. New feature not coming in near future because I'm busy but it's in the plan.

-m is corrected.

-B double space, correct, I forgot to filter vendor and product name, which often means spaces, as you keenly observed, not a lot of people notice double spacing, I do too of course when I see it, it stands out to me. That's corrected.

All fixes contained in pinxi 2.9.03-04

Last edited by h2-1; 03-22-2018 at 01:04 AM.
 
Old 03-22-2018, 02:15 AM   #83
hydrurga
LQ Guru
 
Registered: Nov 2008
Location: Pictland
Distribution: Linux Mint 19 MATE
Posts: 5,290
Blog Entries: 2

Rep: Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707
You're definitely on the ball with all the quick changes, H2! Thank you also for your detailed explanations on the debugger and on the development process - I hope that they are illuminating for others too and not just me. It's my pleasure regarding the feedback - one of the hats I wear is as a copy editor and it's nice to help with the development of such a useful program. It's great that you're getting such good feedback from various sources, but I have no doubt that it is keeping you very (enjoyably, I hope) busy!

Anyway, I'll have a look at 2.09.03-04 today. I have no problem sending you debugging info if you ever require it.

Before I forget, I'll look over the output of -h in more detail at some point, and can do the same for the man file, but the following stand out (correct to the following):

-x -m and -xx -m: Manufacturer [note also that the same details are listed for both these levels]

-xx -R: algorithm

--alt 34: activities

--alt 44: as downloader options

Last edited by hydrurga; 03-22-2018 at 03:06 AM.
 
Old 03-22-2018, 03:05 AM   #84
hydrurga
LQ Guru
 
Registered: Nov 2008
Location: Pictland
Distribution: Linux Mint 19 MATE
Posts: 5,290
Blog Entries: 2

Rep: Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707
Re 2.09.03-04: still not seeing any obvious sort in -p, I've just realised that, according to -V, both wget and git are giving me 2.09.03-00. Should I be looking at an alternative branch?

Edit: Please ignore this. I now realise that I should be looking at the inxi-perl branch.

Last edited by hydrurga; 03-22-2018 at 03:23 AM.
 
Old 03-22-2018, 03:24 AM   #85
h2-1
Member
 
Registered: Mar 2018
Distribution: Debian Testing
Posts: 69

Original Poster
Rep: Reputation: Disabled
-tcm is corrected, that was just 2 mistakes, one, I made it extra when it was supposed to be regular, like the -I ram percents. Second mistake is it was using the wrong field for the value, heh.

man, --help, updated, corrected, those errors were because I changed slightly the order, put manu/partnu on -xx, and didn't update all the parts (updates require: updating help menu, man page, and 2 smxi.org doc pages, which are the help and man html versions. So I tend to forget one or more in the process).

-m reminds me of another reason data is moved to -xx or -xxx, it's when it's very often null, empty, but sometimes isn't. ram is like that, many systems show nothing for manufacturer, part nu, or serial, so those are pushed back. Other rows where that type of data is almost always there, like card rows, it's always shown.

These changes are in pinxi 2.09-05, not yet in inxi, I'm waiting to add some more fixes as I go along before the next real inxi commit.

I really lucked out, heh, I can tell you're very used to doing this level of editing proofing, inxi users, and my, good fortune, thanks.

Last edited by h2-1; 03-22-2018 at 03:26 AM.
 
Old 03-22-2018, 03:45 AM   #86
hydrurga
LQ Guru
 
Registered: Nov 2008
Location: Pictland
Distribution: Linux Mint 19 MATE
Posts: 5,290
Blog Entries: 2

Rep: Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707
Re 2.09.03-05:

-p: Ordering and fs look good. If you ever find a nice quick Perl sort that incorporates natural number ordering anywhere in the string, you could apply it to this mountpoint sort too (I'm an outlier again with my mountpoint directory names).

Out of interest, why does -p only show mounted partitions? Is there any option available which will show all visible partitions, whether mounted or not (in which case these would be more naturally ordered by /dev name)?

-t cm10: I'm getting what looks like debugging output ($VAR1 dump) before the normal output. You perhaps forgot to turn off the trace statement.

-V: Program Location still shows superfluous /./

All other mods looking good.
 
Old 03-22-2018, 04:20 AM   #87
hydrurga
LQ Guru
 
Registered: Nov 2008
Location: Pictland
Distribution: Linux Mint 19 MATE
Posts: 5,290
Blog Entries: 2

Rep: Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707
Further notes:

-A: -h indicates that -x shows the version, but I only see this appearing in -xx (as "v: kernel").

-C: min/max: 1200/3100 Mhz, but Speed: 1197 MHz (thought I should point it out although only 3 MHz difference).

-h indicates that -x shows microarchitecture revision, but I only see this appearing in -xx.

-h indicates that -xxx shows minimum CPU speed, but isn't this available in plain -C as min/max?

-Dx: might be worth indicating that temp may be available as root (similar to -m for RAM Report).

-G: interestingly, -G lists unloaded as "vesa,modesetting,fbdev", -Gx as "fbdev,modesetting,vesa", -Gxx as "vesa,fbdev,modesetting" and -Gxxx as "modesetting,vesa,fbdev".

-h indicates that -x shows direct rendering status, but this appears to be shown in vanilla -G as "direct render: Yes".

Last edited by hydrurga; 03-22-2018 at 04:22 AM.
 
Old 03-22-2018, 05:38 AM   #88
hydrurga
LQ Guru
 
Registered: Nov 2008
Location: Pictland
Distribution: Linux Mint 19 MATE
Posts: 5,290
Blog Entries: 2

Rep: Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707
Continuing on (but these are starting to get really picky so please feel free to completely ignore as much as you want):

-I: This is really petty of me, but I note that the capitalisation of your output fields follows the general rule of: Initial capitalism of all words for category (e.g. Drives); initial capitalisation of all words for sub-category (e.g. HDD Total Size); lower-case for elements within sub-categories (e.g. used). Anyway, "pinxi" breaks this convention (as does -N's IF element which is in addition placed on a new line - perhaps could be changed to a subcategory and renamed to e.g. Card-1-IF; also -C's "Core speeds"; I've ignored -r output because it looks great as it is).

-G: OpenGL has "version" element, whereas normally just "v" is used.

-p: As an outlier, my Veracrypt mount is showing up as fs: fuseblock. It's NTFS.

-o:

Code:
Unmounted: ID-1: /dev/dm-0 size: 400.00 GiB fs: root required label: N/A uuid: 12F150DD5AF55BE5 
           ID-2: /dev/sda1 size: 100.0 MiB fs: ntfs label: SYSTEM uuid: 3G2096E46096A307 
           ID-3: /dev/sda14 size: 400.00 GiB fs: 400G label: N/A uuid: N/A 
           ID-4: /dev/sda2 size: 50.00 GiB fs: ntfs label: Programs uuid: 01D25B81A5BF9600
I don't remember seeing /dev/sm-0 in the -o output before. Anyway, this is an outlier as it involves Veracrypt, but both ID-1 and ID-3 refer to the same partition which is in fact mounted and appears in -p.

Running as root gives:

Code:
Unmounted: ID-1: /dev/dm-0 size: 400.00 GiB fs: NTFS label: N/A uuid: 12F150DD5AF55BE5
           ID-2: /dev/sda1 size: 100.0 MiB fs: ntfs label: SYSTEM uuid: 3G2096E46096A307 
           ID-3: /dev/sda14 size: 400.00 GiB fs: 400G label: N/A uuid: N/A 
           ID-4: /dev/sda2 size: 50.00 GiB fs: ntfs label: Programs uuid: 01D25B81A5BF9600
Note the different capitalisation in NTFS and ntfs. Also the Veracrypt partition fs of "400g".
 
Old 03-22-2018, 12:35 PM   #89
hydrurga
LQ Guru
 
Registered: Nov 2008
Location: Pictland
Distribution: Linux Mint 19 MATE
Posts: 5,290
Blog Entries: 2

Rep: Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707Reputation: 1707
Some further thoughts on 2.9.03-5:

Is there any particular reason why the memory figures in the no-option output are in MiB while in -m etc. they are in GiB?

Incorrect parameters generate e.g. "Error 22: Unsupported option: -Q". Is there any need to generate the error number in normal operation i.e. would "Unsupported option: -Q" suffice for the normal user? The same goes for error 10.

-Sx: Is there any specific reason that the Desktop Toolkit info is only displayed for GNOME, KDE and Xfce? I would have thought that if the toolkit (I assume Gtk or Qt, primarily) is available for e.g. GNOME and Xfce, then it should be available for most GNOME-based distros such as MATE and Cinnamon.

-mx: It might be useful to add a "(requires root)" to the entry in -h. The same goes for all data in -h that requires root.

-s: "Fan Speeds (in RPM)" - The "in " is probably superfluous.

-h: -v: "Supported levels: 0-7" should read "Supported levels: 0-8".

-wxx: -h mentions humidity and pressure but these seem to be available with -x.

-wxxx: -h mentions dew point and wind chill but they seems to be available with -xx.

I think that might be me for the moment. If I notice anything else then I will flag it.
 
Old 03-22-2018, 01:10 PM   #90
rokytnji
LQ Veteran
 
Registered: Mar 2008
Location: Waaaaay out West Texas
Distribution: AntiX 17
Posts: 5,525
Blog Entries: 20

Rep: Reputation: 2626Reputation: 2626Reputation: 2626Reputation: 2626Reputation: 2626Reputation: 2626Reputation: 2626Reputation: 2626Reputation: 2626Reputation: 2626Reputation: 2626
Sorry to get back on this later. Rebuilding carburetors takes up computer time. I have seemed to have found out that my previous root owned pinxi folder on my chromebook seems to be a peculiar thing only defined by my chromebook. Because after updating pinxi on my Dell laptop. Same distro version install by the way.
Code:
harry@biker:~/.local/share/pinxi
$ ls -l
total 20
-rw-r--r-- 1 harry harry  255 Mar 22 12:42 location-main.txt
-rw-r--r-- 1 harry harry 1123 Mar 11 16:13 weather-31.9522-97.3459.txt
-rw-r--r-- 1 harry harry 1099 Mar 22 12:42 weather-32.4331-97.5390.txt
-rw-r--r-- 1 harry harry 1077 Mar 22 12:43 weather-79772.txt
-rw-r--r-- 1 harry harry 1077 Mar 22 12:43 weather-pecos-tx.txt
Thinking I misunderstood you h2. My root login statement was directed at another poster in this thread, < my neighbor from Round Rock Texas >. Not you. Forum posts can be hard to understand as I know. Harder than face to face.
This pinxi install < the steps taken > was done the same way as on the chromebook. Same distro version and kernel on the chromebook as this Dell readout below. Same Debian Stretch repos.

Code:
$ pinxi -v8
System:
  Host: biker Kernel: 4.15.9-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 6.3.0 
  Desktop: IceWM 1.4.2 dm: slim 
  Distro: antiX-17_x64-full Heather Heyer 24 October 2017 
Machine:
  Type: Laptop System: Dell product: Latitude E4310 v: 0001 serial: N/A Chassis: 
  type: 9 serial: N/A 
  Mobo: Dell model: 0T6M8G v: A01 serial: N/A BIOS: Dell v: A03 date: 07/08/2010 
Battery:
  BAT-0: charge: 48.8 Wh condition: 40.3/48.8 Wh (82%) volts: 12.5/11.1 
  model: Samsung SDI DELL RM6618A type: Li-ion serial: N/A status: Full 
Memory:
  RAM Report: permissions: Unable to run dmidecode. Are you root? 
PCI Slots:
  Permissions: Unable to run dmidecode. Are you root? 
CPU:
  Topology: Dual Core model: Intel Core i5 M 520 type: MT MCP arch: Nehalem rev: 5 
  L2 cache: 3072 KB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19151 
  Speed: 1463 MHz min/max: 1199/2400 MHz Core speeds (MHz): 1: 1266 2: 1244 3: 1377 
  4: 1217 
Graphics:
  Card-1: Intel Core Processor Integrated Graphics Controller driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:0046 
  Display Server: X.Org 1.19.2 driver: intel resolution: 1366x768~60Hz 
  OpenGL: renderer: Mesa DRI Intel Ironlake Mobile version: 2.1 Mesa 13.0.6 
  direct render: Yes 
Audio:
  Card-1: Intel 5 Series/3400 Series High Definition Audio driver: snd_hda_intel 
  v: kernel bus ID: 00:1b.0 chip ID: 8086:3b57 
  Sound Server: ALSA v: k4.15.9-antix.1-amd64-smp 
Network:
  Card-1: Intel 82577LM Gigabit Network Connection driver: e1000e v: 3.2.6-k 
  port: 6040 bus ID: 00:19 chip ID: 8086:10ea 
  IF: eth0 state: down mac: 5c:26:0a:06:32:15 
  Card-2: Intel Centrino Advanced-N 6200 driver: iwlwifi v: kernel bus ID: 02:00 
  chip ID: 8086:422c 
  IF: wlan0 state: up mac: 00:27:10:6a:ae:60 
  IP v4: 192.168.254.67/24 scope: global broadcast: 192.168.254.255 
  IP v6: fe80::227:10ff:fe6a:ae60/64 scope: link 
  WAN IP: 98.18.1.55 
Drives:
  HDD Total Size: 55.90 GiB used: 23.75 GiB (42.5%) 
  ID-1: /dev/sda model: KINGSTON_SV300S3 size: 55.90 GiB serial: 50026B7743028DAC 
  rev: BBF0 
  Optical-1: /dev/sr0 vendor: TSSTcorp model: DVD+-RW TS-U633F rev: D500 
  dev-links: cdrom 
  Features: speed: 24 multisession: yes audio: yes dvd: yes 
  rw: cd-r,cd-rw,dvd-r,dvd-ram state: running 
RAID:
  Message: No RAID data was found. 
Partition:
  ID-1: / size: 7.63 GiB used: 3.69 GiB (48.4%) fs: ext4 dev: /dev/sda2 
  label: rootantiX uuid: 78252287-6dbf-4719-9c7f-13d6bbc8143b 
  ID-2: /home size: 47.08 GiB used: 20.06 GiB (42.6%) fs: ext4 dev: /dev/sda1 
  label: homeantiX uuid: 62a4a2cd-066a-47d3-a366-f8059a89cbcb 
Unmounted:
  Message: No unmounted partitions found. 
USB:
  Hub: 1:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002 
  Hub: 1:2 usb: 2.00 type: Intel Integrated Rate Matching Hub chip ID: 8087:0020 
  Hub: 2:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002 
  Hub: 2:2 usb: 2.00 type: Intel Integrated Rate Matching Hub chip ID: 8087:0020 
  Device-1: Dell DW375 Bluetooth Module bus ID: 2:3 usb: 2.00 type: Bluetooth 
  chip ID: 413c:8187 
  Device-2: Broadcom BCM5880 Secure Applications Processor with fingerprint swipe 
  sensor 
  bus ID: 2:4 usb: 1.10 type: Application Specific Interface chip ID: 0a5c:5801 
here
Sensors:
  System Temperatures: cpu: 48.0 C mobo: N/A sodimm: 39.0 C 
  Fan Speeds (in RPM): cpu: 0 
Repos:
  Active apt repos in: /etc/apt/sources.list.d/antix.list 
  1: deb http://repo.antixlinux.com/stretch stretch main nosystemd
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
  1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list 
  1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
  2: deb http://security.debian.org/ stretch/updates main contrib non-free
  No active apt repos in: /etc/apt/sources.list.d/onion.list 
  No active apt repos in: /etc/apt/sources.list.d/various.list 
$VAR1 = [
          'harry     4782 16.5  5.3 2349616 429604 ?      sl   12:46   1:38 /usr/lib/firefox-esr/firefox-esr',
          'harry     2584  0.0  0.5 523680 41788 ?        sl   12:41   0:00 /usr/bin/python -o /usr/share/wicd/gtk/wicd-client.py -t',
          'root      2275  1.7  0.5 304268 41572 tty7     ssl+ 12:41   0:16 /usr/lib/xorg/xorg -nolisten tcp -auth /var/run/slim.auth vt07',
          'harry     2569  0.0  0.3 254112 28612 ?        s    12:41   0:00 volumeicon',
          'harry     6087  0.2  0.3 237240 25736 ?        s    12:52   0:00 rox-filer'
        ];
Processes:
  CPU  % used - Command - pid - Memory: MiB / % used - top: 5 
  1: cpu: 16.5% command: firefox-esr pid: 4782 mem: 419.5MiB (5.3%) 
  2: cpu: 1.7% command: xorg pid: 2275 mem: 40.6MiB (0.5%) 
  3: cpu: 1.1% command: lxterminal pid: 6954 mem: 24.7MiB (0.3%) 
  4: cpu: 0.5% command: bash pid: 6956 mem: 4.61MiB (0.0%) 
  5: cpu: 0.4% command: conky pid: 2643 mem: 10.2MiB (0.1%) 
  Memory MiB/% used - Command - pid - CPU: % used - top: 5 
  1: mem: 419.5 MiB (5.3%) command: firefox-esr pid: 4782 cpu: 5.3% 
  2: mem: 40.8 MiB (0.5%) command: python pid: 2584 cpu: 0.5% 
  3: mem: 40.6 MiB (0.5%) command: xorg pid: 2275 cpu: 0.5% 
  4: mem: 27.9 MiB (0.3%) command: volumeicon pid: 2569 cpu: 0.3% 
  5: mem: 25.1 MiB (0.3%) command: rox-filer pid: 6087 cpu: 0.3% 
Info:
  Processes: 157 Uptime: 15 min Memory: 7.72 GiB used: 597.1 MiB (7.6%) Init: SysVinit 
  v: 2.88 runlevel: 5 default: 5 Compilers: gcc: 6.3.0 alt: 6 Shell: bash 4.4.12 
  running in: lxterminal pinxi: 2.9.03-5
Chromebooks must reside in a different dimension is all I can figure. Because XDG should be the same on both laptops.

Code:
$ apt-cache policy xdg-utils
xdg-utils:
  Installed: 1.1.1-1
  Candidate: 1.1.1-1
  Version table:
 *** 1.1.1-1 500
        500 http://ftp.us.debian.org/debian stretch/main amd64 Packages
        500 http://ftp.us.debian.org/debian stretch/main i386 Packages
        100 /var/lib/dpkg/status
I am working outside mostly this week. Outside Temp here is going to up to 90F for the high. So please excuse my late responses.

Code:
$ pinxi -xxx -W pecos,tx
Weather:
  Conditions: 77 F (25 C) - Clear Wind: Calm Humidity: 22% 
  Pressure: 30.13 in (1020 mb) Dew Point: 35 F (2 C) Location: Pecos, Tx 
  Altitude: 787.3 m Time: Thu 22 Mar 2018 06:02:10 PM CDT 
  Observation Time: March 22, 12:35 PM CDT
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Firefox: are we its informal beta-testers? FeyFre Slackware 29 11-21-2011 02:15 AM
Beta Testers Needed msound General 18 07-28-2006 10:22 AM
looking for beta testers grizzly General 5 03-20-2004 11:24 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 10:22 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration