From b96ed769fbf915ac9050b9c5df7bdbc2b3d6fd89 Mon Sep 17 00:00:00 2001 From: Papoteur Date: Tue, 2 Jul 2019 16:04:11 +0200 Subject: Adding or refreshing mcc in it --- mcc/7/it/content/otherMageiaTools.html | 63 ++++++++++++++++++++++++++++++++++ 1 file changed, 63 insertions(+) create mode 100644 mcc/7/it/content/otherMageiaTools.html (limited to 'mcc/7/it/content/otherMageiaTools.html') diff --git a/mcc/7/it/content/otherMageiaTools.html b/mcc/7/it/content/otherMageiaTools.html new file mode 100644 index 00000000..2a84fc2c --- /dev/null +++ b/mcc/7/it/content/otherMageiaTools.html @@ -0,0 +1,63 @@ + + + + + Altri strumenti di Mageia

Altri strumenti di Mageia

There are more Mageia tools than those that can be started in the Mageia +Control Center. Click on a link below to learn more, or continue reading the +next pages.

  1. la sezione chiamata «Strumento per la segnalazione di bug di Mageia»drakbug +

  2. la sezione chiamata «Collect Logs and System Information for Bug Reports»drakbug_report

  3. la sezione chiamata «Display Available NFS And SMB Shares»TO BE WRITTEN

  4. la sezione chiamata «Mostra le informazioni riguardo PCI, USB e PCMCIA»

  5. E altri strumenti?

Strumento per la segnalazione di bug di Mageia

drakbug

Usually, this tool[50] starts automatically +when a Mageia tool crashes. However, it is also possible that, after filing +a bug report, you are asked to start this tool to check some of the +information it gives, and then provide that in that existing bug report.

If a new bug report needs to be filed and you are not used to doing that, +then please read How to +report a bug report properly before clicking on the "Report" button.

In case the bug has already been filed by someone else (the error message +that drakbug gave will be the same, then), it is useful to add a comment to +that existing report that you saw the bug, too.

Collect Logs and System Information for Bug Reports

drakbug_report

This tool[51] can only be started and used +on the command line.

It is advised to write the output of this command to a file, for instance by +doing drakbug_report > drakbugreport.txt, +but make sure you have enough disk space first: the file can easily be +several GBs large.

Nota

L'output è troppo grande per essere allegato a un bug report senza +cancellare le parti non necessarie.

Questo comando raccoglie le seguenti informazioni sul tuo sistema:

  • lspci

  • pci_devices

  • dmidecode

  • fdisk

  • scsi

  • /sys/bus/scsi/devices

  • lsmod

  • cmdline

  • pcmcia: stab

  • usb

  • partizioni

  • cpuinfo

  • syslog

  • Xorg.log

  • monitor_full_edid

  • stage1.log

  • ddebug.log

  • install.log

  • fstab

  • modprobe.conf

  • lilo.conf

  • grub: menu.lst

  • grub: install.sh

  • grub: device.map

  • xorg.conf

  • urpmi.cfg

  • modprobe.preload

  • sysconfig/i18n

  • /proc/iomem

  • /proc/ioport

  • Versione di Mageia

  • rpm -qa

  • df

Nota

At the time this help page was written, the "syslog" part of this command's +output was empty, because this tool had not yet been adjusted to our switch +to systemd. If it is still empty, you can retrieve the "syslog" by doing (as +root) journalctl -a > journalctl.txt. If +you don't have a lot of diskspace, you can, for instance, take the last 5000 +lines of the log instead with: journalctl -a | tail +-n5000 > journalctl5000.txt.

Display Available NFS And SMB Shares

lsnetdrake

This tool [52] can only be started and used +on the command line.

This page hasn't been written yet for lack of resources. If you think you +can write this help, please contact the Documentation +team. Thanking you in advance.

Mostra le informazioni riguardo PCI, USB e PCMCIA

lspcidrake

This tool [53] can only be started and used +on the command line. It will give some more information if used under root.

lspcidrake gives the list of all the connected devices to the computer (USB, +PCI and PCMCIA) and the used drivers. It needs the ldetect and ldetect-lst +packages to work.

With the -v option, lspcidrake adds the vendor and device identifications.

lspcidrake often generates very long lists, so, to find an information, it +is often used in a pipeline with the grep command, like in these examples:

Informazioni sulla scheda grafica;

lspcidrake | grep VGA

Informazioni sul network

lspcidrake | grep -i network

-i per ignorare la distinzione di maiuscolo e minuscolo.

In this screenshot below, you can see the action of the -v option for +lspcidrake and the -i option for grep.

There is another tool that gives information about the hardware, it is +called dmidecode (under root)


[50] You can start this tool from the command line, by typing drakbug.

[51] You can start this tool from the command line, by typing drakbug_report as root.

[52] You can start this tool from the command line, by typing lsnetdrake. +

[53] You can start this tool from the command line, by typing lspcidrake.

© Mageia
CC BY-SA 3.0
Uploaded on 02/07/2019
Indietro   
 Partenza 
loading table of contents...
-- cgit v1.2.1