Proposal: Slightly tweaked version of inxi-gui

Forum Forums antiX-development Development Proposal: Slightly tweaked version of inxi-gui

  • This topic has 47 replies, 7 voices, and was last updated Feb 20-7:25 pm by h2.
Viewing 15 posts - 31 through 45 (of 48 total)
  • Author
    Posts
  • #129166
    Moderator
    Brian Masinick

      Which one are you referring to, still the second line? I don’t get how it works if you still think it works for my type of solid state drive.

      --
      Brian Masinick

      #129168
      Moderator
      Brian Masinick

        The entry for list partition layout shows both the ram drives and the SSD drive; the inxi -plu also shows what I’m looking for; the second entry we’re discussing is the one that gives NOTHING because of the /dev/sd, let me try it another way.

        Disk /dev/ram0: 16 MiB, 16777216 bytes, 32768 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 4096 bytes
        I/O size (minimum/optimal): 4096 bytes / 4096 bytes

        Disk /dev/ram1: 16 MiB, 16777216 bytes, 32768 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 4096 bytes
        I/O size (minimum/optimal): 4096 bytes / 4096 bytes

        Disk /dev/ram2: 16 MiB, 16777216 bytes, 32768 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 4096 bytes
        I/O size (minimum/optimal): 4096 bytes / 4096 bytes

        Disk /dev/ram3: 16 MiB, 16777216 bytes, 32768 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 4096 bytes
        I/O size (minimum/optimal): 4096 bytes / 4096 bytes

        Disk /dev/ram4: 16 MiB, 16777216 bytes, 32768 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 4096 bytes
        I/O size (minimum/optimal): 4096 bytes / 4096 bytes

        Disk /dev/ram5: 16 MiB, 16777216 bytes, 32768 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 4096 bytes
        I/O size (minimum/optimal): 4096 bytes / 4096 bytes

        Disk /dev/ram6: 16 MiB, 16777216 bytes, 32768 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 4096 bytes
        I/O size (minimum/optimal): 4096 bytes / 4096 bytes

        Disk /dev/ram7: 16 MiB, 16777216 bytes, 32768 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 4096 bytes
        I/O size (minimum/optimal): 4096 bytes / 4096 bytes

        Disk /dev/ram8: 16 MiB, 16777216 bytes, 32768 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 4096 bytes
        I/O size (minimum/optimal): 4096 bytes / 4096 bytes

        Disk /dev/ram9: 16 MiB, 16777216 bytes, 32768 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 4096 bytes
        I/O size (minimum/optimal): 4096 bytes / 4096 bytes

        Disk /dev/ram10: 16 MiB, 16777216 bytes, 32768 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 4096 bytes
        I/O size (minimum/optimal): 4096 bytes / 4096 bytes

        Disk /dev/ram11: 16 MiB, 16777216 bytes, 32768 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 4096 bytes
        I/O size (minimum/optimal): 4096 bytes / 4096 bytes

        Disk /dev/ram12: 16 MiB, 16777216 bytes, 32768 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 4096 bytes
        I/O size (minimum/optimal): 4096 bytes / 4096 bytes

        Disk /dev/ram13: 16 MiB, 16777216 bytes, 32768 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 4096 bytes
        I/O size (minimum/optimal): 4096 bytes / 4096 bytes

        Disk /dev/ram14: 16 MiB, 16777216 bytes, 32768 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 4096 bytes
        I/O size (minimum/optimal): 4096 bytes / 4096 bytes

        Disk /dev/ram15: 16 MiB, 16777216 bytes, 32768 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 4096 bytes
        I/O size (minimum/optimal): 4096 bytes / 4096 bytes

        Disk /dev/nvme0n1: 238.47 GiB, 256060514304 bytes, 500118192 sectors
        Disk model: KBG40ZNV256G KIOXIA
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes
        Disklabel type: gpt
        Disk identifier: 8C305B19-CCF4-4AE8-AA0D-F2D026B13884

        Device Start End Sectors Size Type
        /dev/nvme0n1p1 2580480 102934527 100354048 47.9G Linux filesystem
        /dev/nvme0n1p2 2048 2580479 2578432 1.2G EFI System
        /dev/nvme0n1p3 102934528 205334527 102400000 48.8G Linux root (x86)
        /dev/nvme0n1p4 205334528 307734527 102400000 48.8G Linux root (x86)
        /dev/nvme0n1p5 307734528 410134527 102400000 48.8G Linux root (x86)
        /dev/nvme0n1p6 410134528 426518527 16384000 7.8G Linux root (x86)
        /dev/nvme0n1p7 426518528 500118158 73599631 35.1G Linux filesystem

        Partition table entries are not in disk order.

        --
        Brian Masinick

        #129169
        Moderator
        Brian Masinick

          inxi-gui-updated-v14
          (null)
          xdg-open: file ‘(null)’ does not exist

          If I click the entry; otherwise if I do not click the entry it shows
          fs: ext4, type: 48GB, size: 9.6GB, used: 36GB, free: 22%, %used /, Mount:
          which indicates that the columns in the output are misaligned, at least for my nvme unit; they seem off by one column, as they get displayed they are very confusing to me, until I looked closely; now they make sense, they just don’t look right; that’s when I select the second button and press OK.

          --
          Brian Masinick

          #129171
          Member
          PPC

            it still doesn’t provide useful output on my system NOT show everything

            can you please post a screenshot of what the second inxi-gui entry windows displays in that system?

            What the system does, by order of complexity:
            – it runs “df -h -T”. It should display something like:

            Sistema de ficheiros Tipo     Tamanho   Uso Livre Uso% Montado em
            udev                 devtmpfs    1,9G     0  1,9G   0% /dev
            tmpfs                tmpfs       381M  792K  381M   1% /run
            /dev/sda3            ext4        115G   66G   43G  61% /
            tmpfs                tmpfs       5,0M  8,0K  5,0M   1% /run/lock
            tmpfs                tmpfs       762M     0  762M   0% /dev/shm

            – but it adds one extra pipe, running: “df -h -T| tail -n+2”, to cut down the title line (so the results can be displayed in columns, in a yad window). It should display something like:

            udev                 devtmpfs    1,9G     0  1,9G   0% /dev
            tmpfs                tmpfs       381M  792K  381M   1% /run
            /dev/sda3            ext4        115G   66G   43G  61% /
            tmpfs                tmpfs       5,0M  8,0K  5,0M   1% /run/lock
            tmpfs                tmpfs       762M     0  762M   0% /dev/shm

            – I added one final pipe, running: “df -h -T| tail -n+2 | grep -v “tmpfs””. It should display something like:
            /dev/sda3 ext4 115G 66G 43G 61% /
            … the df command should display data related to any drives detected, it does not matter if they are sdX, hdX, nvmeX, etc…

            In your case the yad window should display something like:

            /dev/nvme0n1p5 ext4 48G 9.6G 36G 21% /

            P.

            • This reply was modified 6 months, 1 week ago by PPC.
            #129177
            Member
            PPC

              Does this GUI work correctly in your computer (it’s used in FT10 to display disk info, but does not allow access to any partition)?

              eval exec yad --title="antiX-Disks" --image=drive-harddisk --text=" " --button="x" --width=650 --multi-progress $(df -hT $1 |sed '/tmpfs/d' | tail -n +2 | awk '{printf "--bar=\"<b>%s</b> (%s - %s) [%s/%s]\" %s ", $7, $1, $2, $4, $3, $6}')

              • This reply was modified 6 months, 1 week ago by PPC.
              #129180
              Moderator
              Brian Masinick

                screenshot of my “issue” attached.

                Attachments:

                --
                Brian Masinick

                #129183
                Moderator
                Brian Masinick

                  screenshot of your eval; that at least provides my device and only my device correctly; see latest attachment.

                  Attachments:

                  --
                  Brian Masinick

                  #129186
                  Moderator
                  Brian Masinick

                    With the latest expression, it provides what I perceive ought to be there, based on the description; I hope this is helpful @PPC.

                    --
                    Brian Masinick

                    #129190
                    Member
                    PPC

                      OK, folks, I hope this is the final proposal for the new inxi-gui

                      Change log:
                      -replaced the “disk info” function (function_disk_df) with a small, but fairly complex one that makes sure at least the disk space of all detected drives is correctly displayed, including am handy percentage graphic. The previous version of the function failed to work with NVME disks. Please note: this new version does not allow to access drives/partitions from the GUI, only displays information (but, at least, displays it well, I hope).
                      It also displays a user friendly title (the previous one just said “df”)

                      P.

                      • This reply was modified 6 months, 1 week ago by PPC.
                      • This reply was modified 6 months, 1 week ago by PPC.
                      #129202
                      Moderator
                      Brian Masinick

                        OK, folks, I hope this is the final proposal for the new inxi-gui

                        Change log:
                        -replaced the “disk info” function (function_disk_df) with a small but fairly complex one that makes sure at least the disk space of all detected drives is correctly displayed, including and handy percentage graphic. The previous version of the function failed to work with nvm disks. Please note: this new version does not allow to access drives/partitions from the GUI, only displays information (but, at least, displays it well, I hope).
                        It also displays a user friendly title (the previous one just said “df”)

                        P.

                        YES!

                        In my opinion, this now captures everything correctly for various different hardware configurations.
                        If anyone still wants to view their /dev/sda stuff the way you had it previously,

                        df -Th | grep /dev/sd will certainly provide it; I think the solution you have now is good because the other reports provide other details, such as all of the partitions and their devices, the partition table, block devices, etc. This is now both complete and general, and perhaps more than the casual user will even attempt to look at. The “medium” user is the perfect use case for this tool because the advanced user will either look in the /proc filesystem for details or will know the many different command line tools well anyway and probably will not seek the information in the tool, complete as it is!

                        Well done!

                        --
                        Brian Masinick

                        #129205
                        Member
                        Wallon

                          Dear Brian, Dear PPC,

                          For me, everything is working fine now.
                          Thank you both very much.

                          Kind regards,
                          Wallon

                          #129208
                          Moderator
                          Brian Masinick

                            Dear Brian, Dear PPC,

                            For me, everything is working fine now.
                            Thank you both very much.

                            Kind regards,
                            Wallon

                            Give @PPC the credit; I just gave him grief about picky details; he did the good job as always!

                            --
                            Brian Masinick

                            #129244
                            Moderator
                            Brian Masinick

                              I’m sorry @PPC; I went to TWO of my other systems, both of which I believe have SSD, but they are not non volatile memory (NVME) SSD, so guess what?
                              ALL of the others use sd notation, so for all the work you put into your tool, only people like me with NVME ( or some other convention that does not use /dev/sd* notat ion ) will require that work.

                              That said, I do know that BSD and other forms of UNIX-like systems do not use sd notation either, as if that matters (it doesn’t).

                              IF some other obscure device specs do arise, you have them covered, that is my “only” defense. [wink]

                              --
                              Brian Masinick

                              #129281
                              Member
                              PPC

                                I’m happy to report that, in antiX 21/22/23, inxi-gui was updated to include one of my latest proposals!
                                This makes it a bit easier to get new users (of recent versions of antiX) to get their system information without having to ask them to use the terminal… Also I think we just go a tool that works a bit better, looks a bit better and is more intuitive to use, without using any extra system resources, so that is always a plus!

                                EDIT: many thanks, @anticapitalista, for accepting my proposal.

                                P.

                                • This reply was modified 6 months ago by PPC.
                                • This reply was modified 6 months ago by PPC.
                                #129290
                                Member
                                Wallon

                                  Caro PPC,

                                  Here is the *.pot file for the translations.
                                  If you open the file, you’ll see that the lines for the buttons to be translated aren’t great!

                                  #: inxi-gui:13
                                  msgid "Save !/usr/share/icons/papirus-antix/48x48/actions/gtk-save.png"
                                  msgstr ""
                                  #: inxi-gui:14
                                  msgid "Close !/usr/share/icons/papirus-antix/48x48/actions/gtk-quit.png"
                                  msgstr ""
                                  #: inxi-gui:15
                                  msgid "OK!/usr/share/icons/papirus-antix/48x48/actions/gtk-ok.png"
                                  msgstr ""
                                  #: inxi-gui:204
                                  msgid " x "
                                  msgstr ""

                                  Would you please separate the text from the buttons and not show the icons?

                                  Would you please put some text (Exit or close window…) for the ” x ” button like I did in your “finder” program?

                                  We can’t transfer this *.pot file to Transifex.

                                  Com os melhores cumprimentos,
                                  Wallon

                                  Attachments:
                                Viewing 15 posts - 31 through 45 (of 48 total)
                                • You must be logged in to reply to this topic.