2015/03/16

Change corrupt or incorrect UUID's in the fstab on Pisi Linux

Change UUID on Pisi Linux

You try a lot of Distributions next to Pisi Linux on your Hard Drive?
Also you make Distro hopping, on your HDD and not in the Virtualbox or an other Virtual Maschine.
And after you go back to Pisi Linux and you have lost you Swap partition.

No Problem here a little solution for it.

When you see in your System Monitor Swap 0,00GB/ and after no entrys have you lost your UUID (universally unique identifier) in the fstab.

The universally unique identifier
is an identifier standard used in software construction. A UUID is simply a 128-bit value. The meaning of each bit is defined by any of several variants.

For human-readable display, many systems use a canonical format using hexadecimal text with inserted hyphen characters. For example:

de305d54-75b4-431b-adb2-eb6b9e546013

Read more about the UUID here: Universally unique identifier

When this number is wrong you have lost your Swap Partition but no Panic you can restore it.

open a Terminal and give in the following command:

sudo blikd

The blkid  command print for you, many important information such as device file, identification number, name and file system on the volumes contained in the attached storage media show.


Now let your Terminal open, and after that command open >Dolphin>Root and there go to /etc/fstab,
open the fstab with Admin rights Important only with Admin rights can you write in the fstab.



Check the numbers for the swap partition, when they are not correct change it. the UUID from the blkid command are always the correct UUID.
Delete the UUID in the fstab carefully so as you see above on the Image, from the first Number 4 to the last letter c.
Do not delete the complete Line

Now copy the UUID for the fstab from the Terminal and paste it in the fstab where you have remove the incorrect UUID when you are ready save it.
Close all Windows and make a reboot, after the reboot can you see your Swap Partition so as it was before.



2015/03/07

Hardware and Systeminformation from Commandline in Pisi Linux Part 3 inxi

Hardware and Systeminformation from Commandline Part 3 inxi

inxi is a command line system information script built for for console and IRC. It is also used for forum technical support, as a debugging tool, to quickly ascertain user system configuration and hardware. inxi shows system hardware, CPU, drivers, Xorg, Desktop, Kernel, GCC version(s), Processes, RAM usage, and a wide variety of other useful information.


inxi output varies between CLI and IRC, with some default filters and color options applied to IRC use. Script colors can be turned off if desired with -c 0, or changed using the -c color options listed in the OPTIONS section below.


inxi is already installed in Pisi Linux and is a very great Commandline-Information Tool.

Here any Commands for inxi with images:

inxi -c 5 -b

- c is for color output and you can use number 


-c [0-32]
Available color schemes. Scheme number is required. Supported color schemes: 0-32

-c [94-99]
Color selectors run a color selector option prior to inxi starting which lets youset the config file value for the selection. Color selectors for each type display. (NOTE: irc and global only show safe color set):


- b is for basic info which has enough information about system to start




inxi -F

This command used to get Complete system information of CPU




inxi -S 

This command used to get information about your distribution along with the desktop environment used





inxi -r

This command used to check currently used repositories by your distribution





sudo inxi -U

this command used to update to the latest version of inxi




inxi -h

 For more help about inxi



PRIVACY AND SECURITY
In order to maintain basic privacy and security, inxi filters out automatically on IRC things like your network card mac address, WAN and LAN IP, your /home username directory in partitions, and a few other things. Because inxi is often used on forums for support, you can also trigger this filtering with the -z option (-Fz, for example). To override the IRC filter, you can use the -Z option. This can be useful to debug network connection issues online in a private chat, for example.


SUPPORTED IRC CLIENTS

BitchX, Gaim/Pidgin, ircII, Irssi, Konversation, Kopete, KSirc, KVIrc, Weechat, and Xchat. Plus any others that are capable of displaying either built in or external script output.

RUNNING IN IRC CLIENT

To trigger inxi output in your IRC client, pick the appropriate method from the list below: 

 Xchat, irssi (and many other IRC clients) /exec -o inxi [options] 
 If you leave off the -o, only you will see the output on your local IRC client. 

 Konversation /cmd inxi [options] To run inxi in konversation as a native script if your distribution or inxi package did not do this for you, create this symbolic link: ln -s /usr/local/bin/inxi /usr/share/kde4/apps/konversation/scripts/inxi If inxi is somewhere else, change the path /usr/local/bin to wherever it is located. Then you can start inxi directly, like this: /inxi [options] 

 WeeChat /shell -o inxi [options] 
 Before WeeChat can run external scripts like inxi, you need to install the weechat-plugins package. This is automatically installed for Debian users. Next, if you don't already have it, you need to install shell.py, which is a python script. In a web browser, 

Click on the download button at: http://www.weechat.org/scripts/source/stable/shell.py.html/ Make the script executable by chmod +x shell.py Move it to your home folder: /.weechat/python/autoload/ then logout, and start WeeChat with weechat-curses Top of screen should say what pythons scripts have loaded, and should include shell. Then to run inxi, you would enter a command like this: /shell -o inxi -bx If you leave off the -o, only you will see the output on your local weechat. WeeChat users may also like to check out the weeget.py


More commands with inxi can you read here:




Hardware and Systeminformation from Commandline in Pisi Linux Part 2 the dmidecode

Hardware and Systeminformation from Commandline Part 2 the dmidecode


Dmidecode reports information about your system's hardware as described in your system BIOS according to theSMBIOS/DMI standard (see a sample output). This information typically includes system manufacturer, model name, serial number, BIOS version, asset tag as well as a lot of other details of varying level of interest and reliability depending on the manufacturer. This will often include usage status for the CPU sockets, expansion slots (e.g. AGP, PCI, ISA) and memory module slots, and the list of I/O ports (e.g. serial, parallel, USB).


DMI data can be used to enable or disable specific portions of kernel code depending on the specific hardware. Thus, one use of dmidecode is for kernel developers to detect system "signatures" and add them to the kernel source code when needed.

Beware that DMI data have proven to be too unreliable to be blindly trusted. Dmidecode does not scan your hardware, it only reports what the BIOS told it to.

Three additional tools come with dmidecode:
  • biosdecode prints all BIOS related information it can find.
  • ownership retrieves the "ownership tag" that can be set on Compaq computers;
  • vpddecode prints the "vital product data" information that can be found in almost all IBM computers.

Let us take a look at it with commands and Images:

sudo dmidecode -h

is the help command as seen here:


and so gives it much commands for dmidecode, i list here any more so that you can try it.

sudo dmidecode -s system-manufacturer

gives Info about the manufacturer from the System

sudo dmidecode -s system-product-name

Product Name output 

sudo dmidecode -s system-version

Model number from the System Version

sudo dmidecode -s bios-version

Version number of the BIOS

sudo dmidecode -s baseboard-manufacturer

Mainboard Manufacturer Name

sudo dmidecode -s baseboard-product-name

Product name of the Mainboard

sudo dmidecode -s baseboard-version

Version number of the Mainboard

sudo dmidecode

Output from all available Information's

sudo dmidecode -t x

Information about the DMI-Type x (0-41)

sudo dmidecode -t bios

All available Information's about the BIOS (Manufacturer, Version, Language ....)

sudo dmidecode -t processor

All Informations about the Processor

Thus, information about all available in the BIOS components can be learned.
The following command provides information on the characteristics of the main boards (BIOS), eg PCI, ACPI, UEFI ...

The following command provides information on the characteristics of the main boards (BIOS), eg PCI, ACPI, UEFI ...

sudo dmidecode -t 0 




The following command is an extended command sudo dmidecode -t 0, ie, He not only lists the type 0 on, but all types corresponding to:

sudo dmidecode -t bios



The following command provides detailed information about the processor:


sudo dmidecode -t processor




Other parameters are in the man pages.

Reading spec. Information using grep:

sudo dmidecode -t0 | grep EFI

to check whether the BIOS UEFI  capable is

sudo dmidecode | grep -A3 'BIOS Information'

BIOS information (3 lines)




sudo dmidecode | grep -A3 'Base Board Information'

Vendor and device information (3 lines)




sudo dmidecode | grep -A 16 "Memory Device" | egrep "(Type|Speed)"

RAM Speed Detect (16 lines)




Biosdecode

Biosdecode reads the / dev / mem device file and displays information and entry points about things that transmits the bios, if they are available. Currently it supports SMBIOS, DMI, SYSID, PNP, ACPI, BIOS32, PIR, 32OS, SNY, VPD, FJKEYINF.

Biosdecode has no command line parameters. Starting it simply:

sudo biosdecode