FAA - inxi - CLI information script for console and IRC
Posted: 20 Aug 2015, 18:23
inxi might be a neat thingy for Porteus coders, sysadmins and normal users alike:
It needs xdpyinfo and hddtemp, at least in the current XFCe version of x86-64:
inxi.1.gz and inxi.1 are the same, one randomly set executable, the other compressed.
Question:
When creating a module, could one leave out a file, in this case the huge inxi.changelog, replacing it with a small info text file that points the user to the online source of the original inxi_2.2.19.tar.gz that has inxi.changelog included?
And for now I will be nasty enough as to make one module that has inxi and both dependencies included, cause up to now I never had to load any of them for any other program...
Any objections against my approach this time? [Usually I only include the program itself and add needed deps as stand alones;
For myself I have always added to my GIMP module the needed gegl & babl but stripped all unneeded Locales. and with a complex program like GIMP stripping away all unneeded locales makes a huge difference, size-wise! See my other post about that.]
The highlighting is done by inxi$ /mnt/DL/inxi -tm
Processes: Memory - MB / % used - top 5 active
1: mem: 1202.67MB (35.4%) command: palemoon pid: 2078
2: mem: 571.75MB (16.8%) command: pale pid: 2154
3: mem: 105.62MB (3.1%) command: s (started by: viewnior) pid: 12220
4: mem: 101.64MB (2.9%) command: X pid: 1608
5: mem: 82.75MB (2.4%) command: s (started by: viewnior) pid: 12130
It needs xdpyinfo and hddtemp, at least in the current XFCe version of x86-64:
Code: Select all
L$ ls -o inxi* *xzm
-rw-r--r-- 1 root 45056 Aug 20 04:51 hddtemp-0.3beta15-x86_64-1_slack.xzm
-rwxr-xr-x 1 rava 488691 Feb 16 2015 inxi
-rwxr-xr-x 1 rava 25562 Feb 16 2015 inxi.1
-rw-r--r-- 1 rava 9979 Feb 16 2015 inxi.1.gz
-rwxr-xr-x 1 rava 101624 Feb 16 2015 inxi.changelog
-rw-r--r-- 1 rava 181796 Aug 20 04:42 inxi_2.2.19.tar.gz
-rw-r--r-- 1 root 28672 Aug 20 04:48 xdpyinfo-1.3.1-x86_64-1.xzm
Question:
When creating a module, could one leave out a file, in this case the huge inxi.changelog, replacing it with a small info text file that points the user to the online source of the original inxi_2.2.19.tar.gz that has inxi.changelog included?
And for now I will be nasty enough as to make one module that has inxi and both dependencies included, cause up to now I never had to load any of them for any other program...
Any objections against my approach this time? [Usually I only include the program itself and add needed deps as stand alones;
For myself I have always added to my GIMP module the needed gegl & babl but stripped all unneeded Locales. and with a complex program like GIMP stripping away all unneeded locales makes a huge difference, size-wise! See my other post about that.]