Announcement

Collapse
No announcement yet.

Red Hat Developers Introduce New Tool For Linux Storage Management

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #11
    Originally posted by tessio View Post
    I wonder why Red Hat keeps insisting with GTK..
    They're a few reasons. The best one being, IMHO, that gtk, by focusing on Linux as systemd does, can take advantage of Linux only features both more simply (less abstraction because multiplatform support isn't the main concern, but best effort) and quickly. Considering the relative inaudible insignificance of the desktop within redhat a movement to a new tk might just make management say fuck it.

    Comment


    • #12
      Originally posted by BubuXP View Post
      'Reinventing the wheel' and/or 'not invented here' syndrome?
      If "layout is inspired by GParted" why they didn't simply improve GParted?
      1. This tool replaces the deprecated system-config-lvm storage management tool.
      2. A a design decision, Parted (the tool behind gparted) doesn't support any type of advanced features beyond basic partition management - be that LVM, software RAID and/or btrfs.

      I would retract the "NIH" comment.
      oVirt-HV1: Intel S2600C0, 2xE5-2658V2, 128GB, 8x2TB, 4x480GB SSD, GTX1080 (to-VM), Dell U3219Q, U2415, U2412M.
      oVirt-HV2: Intel S2400GP2, 2xE5-2448L, 120GB, 8x2TB, 4x480GB SSD, GTX730 (to-VM).
      oVirt-HV3: Gigabyte B85M-HD3, E3-1245V3, 32GB, 4x1TB, 2x480GB SSD, GTX980 (to-VM).
      Devel-2: Asus H110M-K, i5-6500, 16GB, 3x1TB + 128GB-SSD, F33.

      Comment


      • #13
        Originally posted by pali View Post
        Another tool which does not support UDF FS?
        Poor RedHat developers wrote a tool to cater for the million of RHEL and Fedora users, but left pali out.
        Guess they'll have to rewrite the troll from scratch just for you.
        oVirt-HV1: Intel S2600C0, 2xE5-2658V2, 128GB, 8x2TB, 4x480GB SSD, GTX1080 (to-VM), Dell U3219Q, U2415, U2412M.
        oVirt-HV2: Intel S2400GP2, 2xE5-2448L, 120GB, 8x2TB, 4x480GB SSD, GTX730 (to-VM).
        oVirt-HV3: Gigabyte B85M-HD3, E3-1245V3, 32GB, 4x1TB, 2x480GB SSD, GTX980 (to-VM).
        Devel-2: Asus H110M-K, i5-6500, 16GB, 3x1TB + 128GB-SSD, F33.

        Comment


        • #14
          Originally posted by gilboa View Post
          Poor RedHat developers wrote a tool to cater for the million of RHEL and Fedora users, but left pali out.
          Guess they'll have to rewrite the troll from scratch just for you.
          Before writing you should read source code and see that there is no NTFS and exFAT support too. Also if you do not know exFAT is standardized FS for modern SDXC cards... And if you do not want tot use NTFS and exFAT then there UDF (read at least wiki: http://en.wikipedia.org/wiki/Universal_Disk_Format).

          So that new tool does not support no modern FS which is supported by more major & minor OS. Which means that tool is useless for formating removable disks.

          Comment


          • #15
            python and gui. i doubt that i like this.

            Comment


            • #16
              Originally posted by pali View Post
              Before writing you should read source code and see that there is no NTFS and exFAT support too. Also if you do not know exFAT is standardized FS for modern SDXC cards... And if you do not want tot use NTFS and exFAT then there UDF (read at least wiki: http://en.wikipedia.org/wiki/Universal_Disk_Format).

              So that new tool does not support no modern FS which is supported by more major & minor OS. Which means that tool is useless for formating removable disks.
              I would imagine they made a design decision not to support it - at least not initially.
              I'd venture and guess that least of which is due to the obvious fact that NTFS support is limited to compatibility w/ Windows and exFAT support is experimental at best making both FS unsuitable for a production use.
              Don't like it, write your own.

              - Gilboa
              oVirt-HV1: Intel S2600C0, 2xE5-2658V2, 128GB, 8x2TB, 4x480GB SSD, GTX1080 (to-VM), Dell U3219Q, U2415, U2412M.
              oVirt-HV2: Intel S2400GP2, 2xE5-2448L, 120GB, 8x2TB, 4x480GB SSD, GTX730 (to-VM).
              oVirt-HV3: Gigabyte B85M-HD3, E3-1245V3, 32GB, 4x1TB, 2x480GB SSD, GTX980 (to-VM).
              Devel-2: Asus H110M-K, i5-6500, 16GB, 3x1TB + 128GB-SSD, F33.

              Comment


              • #17
                Originally posted by Nille View Post
                python and gui. i doubt that i like this.
                Fedora uses Python + GUI for the past decade +.
                I personally use it write the management UI front-ends to in-kernel modules.
                I fail to see what's wrong with this combination. (PyQT is no better, and writing C++/Qt will take for more effort).
                oVirt-HV1: Intel S2600C0, 2xE5-2658V2, 128GB, 8x2TB, 4x480GB SSD, GTX1080 (to-VM), Dell U3219Q, U2415, U2412M.
                oVirt-HV2: Intel S2400GP2, 2xE5-2448L, 120GB, 8x2TB, 4x480GB SSD, GTX730 (to-VM).
                oVirt-HV3: Gigabyte B85M-HD3, E3-1245V3, 32GB, 4x1TB, 2x480GB SSD, GTX980 (to-VM).
                Devel-2: Asus H110M-K, i5-6500, 16GB, 3x1TB + 128GB-SSD, F33.

                Comment


                • #18
                  Originally posted by pali View Post
                  They are stupid or what?? There is hardcoded install path in launch script blivet-gui (/usr/lib/python2.7/site-packages/blivetgui/main.py). This is some new restriction from Lennart or what?
                  Few messages down the thread you can find his thoughts on the blivet-gui

                  Comment


                  • #19
                    Originally posted by gilboa View Post
                    I fail to see what's wrong with this combination.
                    Its very slow.

                    Comment


                    • #20
                      Originally posted by Nille View Post
                      Its very slow.
                      it is only slow if complete solution is written in python. and even then solution needs to consist of long standing cpu reliant jobs. try using PiTiVi and then ask your self if you ever had a feeling you run like you say slow python application.

                      Comment

                      Working...
                      X