#!/bin/bash
#sicusys-about
Encoding=UTF-8
#
export TEXTDOMAIN=sicusys
export TEXTDOMAINDIR="/usr/share/locale"
dirname="$(dirname "$(readlink -e "$0")")"
{
#
SICUSYS_ABOUT='
<window window_position="1" icon-name="sicusys" maximize_initially="true" resizable="true" title="'$"About"'">	
		<notebook labels="'$"About|coreutils|lsmod|lsusb|lspci|lscpu|dmidecode|iwconfig|ifconfig|glxinfo|xdpinfo|fdisk|fsck|hdparm|acpi|vmstat|nvme-cli|nano|History"'" scrollable="true">
			<vbox scrollable="true" space-expand="true" space-fill="true" homogeneous="true">
				<text use-markup="True" width-chars="10">
					<label>"<span color='"'red'"'><b><big><big><big>SiCuSys</big></big></big></b></span>"</label>
				</text>
				
				##<text use-markup="True">
				##	<label>"'$"<b>Version "$VERSION"</b>"'"</label>
				##</text>
   
				<text  use-markup="True">
					<label>"'$"<b>Author:</b> D.M-Wilhelm [leiche]"'"</label>
				</text>
				
				<text>
					<label>"'$"A simple way to get some info about your system!

You can connect pcc (PCLinuxOS Control Center), too."'" </label>
				</text>
				
				<text>
					<input>gtkdialog -v | grep gtkdialog</input>
				</text>
				
				<text>
					<label>"'$"The Crystal Clear icon set was created by 
Everaldo Coelho, http://www.everaldo.com/

Big thanks to our testers
ghostbunny, angel02_de, and Neal."'"</label>
				</text>
				
				<text use-markup="True">
					<label>"'$"<b>Released</b> 2011-2025"'"</label>
				</text>
				
				<text use-markup="True">
					<label>"<b>'$"Under GPLv2 License"'</b>"</label>
				</text>
			</vbox>
			
			<vbox>  
				<text use-markup="true" xalign="0">
					<label>"'$"The GNU Core Utilities or <b>coreutils</b> is a package of GNU software containing reimplementations for 
many of the basic tools, such as <b>cat</b>, <b>ls</b>, and <b>rm</b>, used on Unix-like operating systems.
<b>Maintainers</b>
Coreutils is currently being maintained by 
Jim Meyering jim@meyering.net, 
Pádraig Brady P@draigBrady.com, 
Bernhard Voelker mail@bernhard-voelker.de, 
Eric Blake ebb9@byu.net, 
Paul Eggert eggert@cs.ucla.edu and 
Assaf Gordon assafgordon@gmail.com."'"</label>
				</text>
				<text use-markup="true" xalign="0">
					<label>"<b>'$"Installed package"'</b>"</label>
				</text>	
				<text xalign="0">
					<input>rpm -q coreutils</input>
				</text>
			</vbox>
		
			<vbox>  
				<text use-markup="true" xalign="0">
					<label>"'$"<b>lsmod</b> is a command on Linux systems which prints the contents of the <b>/proc/modules</b> file. 
It shows which <b>loadable kernel modules</b> are <b>currently</b> loaded. 

lsmod is a part of <b>module-init-tools</b>.					
<b>Authors</b>: 
Alan Jenkins
Jon Masters
Adam J. Richter
Rusty Russell"'"</label>
				</text>
				<text use-markup="true" xalign="0">
					<label>"<b>'$"Installed package"'</b>"</label>
				</text>	
				<text xalign="0">
					<input>rpm -q kmod</input>
				</text>
			</vbox>
  
			<vbox>
				<text use-markup="True" xalign="0">
					<label>"'$"The <b>lsusb</b> command allows you to display information about USB buses and devices that are attached to them. 
Default list all USB devices that are in the system.
					
<b>Author</b>: Thomas Sailer"'"</label>
				</text>
				<text use-markup="true" xalign="0">
					<label>"<b>'$"Installed package"'</b>"</label>
				</text>
				<text xalign="0">
					<input>rpm -q usbutils</input>
				</text>
			</vbox> 
  
			<vbox>
				<text use-markup="True" xalign="0">
					<label>"'$"<b>lspci</b> is a utility for displaying information about <b>PCI buses</b> in the system and devices connected to them.

By default, it shows a brief list of devices.

<b>Author</b>: The PCI Utilities are maintained by Martin Mares"'"</label>
				</text>
				<text use-markup="true" xalign="0">
					<label>"<b>'$"Installed package"'</b>"</label>
				</text>
				<text xalign="0">
					<input>rpm -q pciutils</input>
				</text>
			</vbox> 
			
			<vbox>
				<text use-markup="True" xalign="0">
					<label>"'$"<b>lscpu</b> gathers CPU architecture information from sysfs and /proc/cpuinfo. The command output can be optimized 
for parsing or for easy readability by humans. The information includes, for example, 
the number of CPUs, threads, cores, sockets, and Non-Uniform Memory Access (NUMA) nodes. 
There is also information about the CPU caches and cache sharing, family, model, bogoMIPS, 
byte order, and stepping.
					
<b>AUTHOR</b>: Cai Qian
		     Karel Zak
		     Heiko Carstens "'"
					</label>
				</text>	
				<text use-markup="true" xalign="0">
					<label>"<b>'$"Installed package"'</b>"</label>
				</text>
				<text xalign="0">
					<input>rpm -q util-linux-ng</input>
				</text>
			</vbox>
			<vbox>
				<text use-markup="True" xalign="0">
					<label>"'$"<b>dmidecode</b>  is  a tool for dumping a computer's DMI (some say SMBIOS) table contents in a human-readable format. 
This table contains a description of the system's hardware components, as well as other useful 
pieces of information such as  serial  numbers and  BIOS  revision.  Thanks  to this table, 
you can retrieve this information without having to probe for the actual hardware. While this 
is a good point in terms of report speed and safeness, this also makes the presented  information  
possibly  unreliable.

The  DMI  table doesn't only describe what the system is currently made of, it also can report 
the possible evolutions (such as the fastest supported CPU or the maximal amount of memory supported).

SMBIOS stands for System Management BIOS, while DMI stands for Desktop Management Interface. 
Both standards are tightly related and developed by the DMTF (Desktop Management Task Force).

<b>Author</b>: Alan Cox, Jean Delvare"'"</label>
				</text>
				<text use-markup="true" xalign="0">
					<label>"<b>'$"Installed package"'</b>"</label>
				</text>
				<text xalign="0">
					<input>rpm -q dmidecode</input>
				</text>
			</vbox>
  
			<vbox>
				<text use-markup="True" xalign="0">
					<label>"'$"<b>Iwconfig</b>  is  similar to <b>ifconfig</b>, but is dedicated to the wireless interfaces. 
It is used to set the parameters of the network interface which are specific to the wireless 
operation (for example : the frequency).  
Iwconfig may also be used  to  display those parameters, and the wireless statistics 
(extracted from /proc/net/wireless).

All these parameters and statistics are device dependent. Each driver will provide 
only some of them depending on hardware support, and the range of values may change. 
Please refer to the man page of each device for details.

<b>Author</b>: Jean Tourrilhes"'"</label>
				</text>
				<text use-markup="true" xalign="0">
					<label>"<b>'$"Installed package"'</b>"</label>
				</text>
				<text xalign="0">
					<input>rpm -q wireless-tools</input>
				</text>
			</vbox>
			
			<vbox>
				<text use-markup="True" xalign="0">
					<label>"'$"<b>Ifconfig</b> is used to configure the kernel-resident network interfaces. It is used at boot time to 
set up interfaces as necessary. After that, it is usually only needed when debugging or 
when system tuning is needed.

If no arguments are given, ifconfig displays the status of the currently active interfaces. 
If a single interface argument is given, it displays the status of the given interface only; 
if a single -a argument is given, it displays the status of all interfaces, even those that 
are down. Otherwise, it configures an interface. 

lease refer to the man page of each device for details.

<b>Author</b>:
Fred N. van Kempen
Alan Cox
Phil Blundell
Andi Kleen"'"</label>
				</text>
				<text use-markup="true" xalign="0">
					<label>"<b>'$"Installed package"'</b>"</label>
				</text>
				<text xalign="0">
					<input>rpm -q net-tools</input>
				</text>
			</vbox>
			
			<vbox>
				<text use-markup="True" xalign="0">
					<label>"'$"<b>glxinfo</b> lists information about the GLX extension, OpenGL capable visuals, and the OpenGL 
renderer on an X server. The GLX and renderer info includes the version and extension 
attributes. The visual info lists the GLX visual attributes available for each OpenGL 
capable visual (e.g. whether the visual is double buffered, the component sizes, 
Z-buffering depth, etc). 
					
<b>Author</b>: Brian Paul"'"</label>
				</text>
				<text use-markup="true" xalign="0">
					<label>"<b>'$"Installed package"'</b>"</label>
				</text>
				<text xalign="0">
					<input>rpm -q glxinfo</input>
				</text>
			</vbox> 
			
			<vbox>
				<text use-markup="True" xalign="0">
					<label>"'$"<b>Xdpyinfo</b> is a utility for displaying information about an X server. It is used to examine 
the capabilities of a server, the predefined values for various parameters used in 
communicating between clients and the server, and the different types of screens 
and visuals that are available.

By default, numeric information (opcode, base event, base error) about protocol 
extensions is not displayed. This information can be obtained with the -queryExtensions 
option. Use of this option on servers that dynamically load extensions will likely 
cause all possible extensions to be loaded, which can be slow and can consume 
significant server resources.

Detailed information about a particular extension is displayed with the -ext 
extensionName option. If extensionName is all, information about all extensions 
supported by both xdpyinfo and the server is displayed. 
					
<b>Author</b>: Jim Fulton, MIT X Consortium"'"</label>
				</text>
				<text use-markup="true" xalign="0">
					<label>"<b>'$"Installed package"'</b>"</label>
				</text>
				<text xalign="0">
					<input>rpm -q xdpyinfo</input>
				</text>
			</vbox> 
			
			<vbox scrollable="true">
				<text use-markup="True" xalign="0">
					<label>"'$" Hard disks can be divided into one or more logical disks called partitions. This division 
is described in the partition table found in sector 0 of the disk.

In the BSD world one talks about 'disk slices' and a 'disklabel'.

Linux needs at least one partition, namely for its root file system. 
It can use swap files and/or swap partitions, but the latter are more 
efficient. So, usually one will want a second Linux partition dedicated 
as swap partition. On Intel compatible hardware, the BIOS that boots 
the system can often only access the first 1024 cylinders of the disk. 
For this reason people with large disks often create a third partition, 
just a few MB large, typically mounted on /boot, to store the kernel 
image and a few auxiliary files needed at boot time, so as to make sure 
that this stuff is accessible to the BIOS. There may be reasons of 
security, ease of administration and backup, or testing, to use more 
than the minimum number of partitions.

fdisk (in the first form of invocation) is a menu driven program for 
creation and manipulation of partition tables. It understands DOS 
type partition tables and BSD or SUN type disklabels.

<b>fdisk</b> doesn't understand GUID Partition Table (GPT) and it is 
not designed for large partitions. In particular case use more 
advanced GNU parted(8).

The device is usually /dev/sda, /dev/sdb or so. A device name refers 
to the entire disk. The old systems without libata (a library used 
inside the Linux kernel to support ATA host controllers and devices) 
make a difference between IDE and SCSI disks. In such a case the 
device name will be /dev/hd* (IDE) or /dev/sd* (SCSI). 

The <b>fdisk</b> command is part of the <b>util-linux-ng</b> package.				
<b>Author</b>: "'"</label>
				</text>
				<text use-markup="true" xalign="0">
					<label>"<b>'$"Installed package"'</b>"</label>
				</text>
				<text xalign="0">
					<input>rpm -q util-linux-ng</input>
				</text>
			</vbox> 
			
			<vbox scrollable="True">
				<text use-markup="True" xalign="0"> 
					<label>"'$"<b>fsck</b> is used to check and optionally repair one or more Linux file systems. 
filesys can be a device name (e.g. /dev/hdc1, /dev/sdb2), a mount 
point (e.g. /, /usr, /home), or an ext2 label or UUID specifier 
(e.g. UUID=8868abf6-88c5-4a83-98b8-bfc24057f7bd or LABEL=root). 
Normally, the fsck program will try to handle filesystems on 
different physical disk drives in parallel to reduce the total 
amount of time needed to check all of the filesystems.

If no filesystems are specified on the command line, and the -A 
option is not specified, fsck will default to checking filesystems 
in /etc/fstab serially. This is equivalent to the -As options.

The exit code returned by fsck is the sum of the following conditions:
   0 - No errors
   1 - File system errors corrected
   2 - System should be rebooted
   4 - File system errors left uncorrected
   8 - Operational error
  16 - Usage or syntax error
  32 - Fsck canceled by user request
 128 - Shared library error
The exit code returned when multiple file systems are checked is the 
bit-wise OR of the exit codes for each file system that is checked. 

<b>-a</b> Automatically repair the file system without any questions 
(use this option with caution). Note that e2fsck(8) supports -a for 
backwards compatibility only. This option is mapped to e2fsck's -p 
option which is safe to use, unlike the -a option that some file 
system checkers support. 

The <b>fdisk</b> command is part of the <b>util-linux-ng</b> package.
					
<b>Author</b>:"'"</label>
				</text>
				<text use-markup="true" xalign="0">
					<label>"<b>'$"Installed package"'</b>"</label>
				</text>
				<text xalign="0">
					<input>rpm -q util-linux-ng</input>
				</text>
			</vbox> 
			
			<vbox scrollable="True">
				<text use-markup="True" xalign="0">
					<label>"'$"The <b>hdparm</b> provides a command line interface to various kernel interfaces 
supported by the Linux SATA/PATA/SAS "libata" subsystem and the older 
IDE driver subsystem. Many newer (2008 and later) USB drive enclosures 
now also support "SAT" (SCSI-ATA Command Translation) and therefore may 
also work with hdparm. Eg. recent WD "Passport" models and recent 
NexStar-3 enclosures. Some options may work correctly only with the 
latest kernels. 
					
<b>-t</b> Perform timings of device reads for benchmark and comparison 
purposes. For meaningful results, this operation should be repeated 2-3 
times on an otherwise inactive system (no other active processes) with 
at least a couple of megabytes of free memory. This displays the speed 
of reading through the buffer cache to the disk without any prior 
caching of data. This measurement is an indication of how fast the 
drive can sustain sequential data reads under Linux, without any 
filesystem overhead. To ensure accurate measurements, the buffer cache 
is flushed during the processing of -t using the BLKFLSBUF ioctl					
					
<b>Author</b>: Mark Lord, the original primary developer and maintainer 
of the (E)IDE driver for Linux, and current contributer to the libata 
subsystem, along with suggestions and patches from many netfolk."'"</label>
				</text>
				<text use-markup="true" xalign="0">
					<label>"<b>'$"Installed package"'</b>"</label>
				</text>
				<text xalign="0">
					<input>rpm -q hdparm</input>
				</text>
			</vbox>
			
			<vbox>
				<text use-markup="True" xalign="0">
					<label>"'$"The <b>acpi</b> - Shows battery status and other ACPI information.
Get information from the <b>/proc</b> or the <b>/sys filesystem</b>, 
such as battery status or thermal information.
					
					
<b>Author</b>: The  original  version  of this manual page was written 
by Paul Telford for the Debian system. Newer additions
were done by Michael Meskes. Permission is granted to copy, 
distribute and/or modify  this  document  under
       the terms of the GNU GPL"'"</label>
				</text>
				<text use-markup="true" xalign="0">
					<label>"<b>'$"Installed package"'</b>"</label>
				</text>
				<text xalign="0">
					<input>rpm -q acpi</input>
				</text>
			</vbox> 
			
			<vbox>
				<text use-markup="True" xalign="0">
					<label>"'$"The <b>vmstat</b> reports information about processes, memory, paging, block IO, traps, and cpu activity.

The first report produced gives averages since the last reboot.	
Additional reports give information on a sampling period of length delay.
The process and memory reports are instantaneous in either case.

The <b>vmstat</b> command is part of the <b>procps</b> package.
					
<b>Author</b>: 
Henry Ware.
Fabian Frederick"'"</label>
				</text>
				<text use-markup="true" xalign="0">
					<label>"<b>'$"Installed package"'</b>"</label>
				</text>
				<text xalign="0">
					<input>rpm -q procps</input>
				</text>
			</vbox> 
			
			<vbox scrollable="true">
				<text use-markup="True" xalign="0">
					<label>"'$"
NVM-Express is a fast, scalable host controller interface designed 
to address the needs for not only PCI Express based solid state 
drives, but also NVMe-oF(over fabrics).

This nvme program is a user space utility to provide standards 
compliant tooling for NVM-Express drives. It was made specifically 
for Linux as it relies on the IOCTLs defined by the mainline kernel 
driver.

The utility has sub-commands for all admin and io commands defined 
in the specification and for displaying controller registers. There is
also an option to submit completely arbitrary commands. 
For a list of commands available, run (nvme help).
"'"</label>
				</text>
				<text use-markup="true" xalign="0">
					<label>"<b>'$"Installed package"'</b>"</label>
				</text>
				<text xalign="0">
					<input>rpm -q nvme-cli</input>
				</text>
			</vbox> 
  
			<vbox scrollable="true" space-expand="true" space-fill="true">
				<text  xalign="0">
					<input>nano --version</input>
				</text>	
				<text  xalign="0">
					<input>nano --help</input>
				</text>	
				<text use-markup="true" xalign="0">
					<label>"<b>'$"Installed package"'</b>"</label>
				</text>
				<text xalign="0">
					<input>rpm -q nano</input>
				</text>
			</vbox>
				
			<vbox scrollable="true" space-expand="true" space-fill="true">
				<text>
					<input file>'$dirname'/HISTORY.txt</input>
				</text>	
			</vbox>
		</notebook>		
</window>
'
export GUI="`echo "$SICUSYS_ABOUT" | sed -e 's/##.*//'`" 
gtkdialog -p GUI #> /dev/null 2>&1
}
