Slashdot Mirror


Fedora To Get a New Partition Manager

sfcrazy writes Developer Vratislav Podzimek has announced the next-gen partition manager for Fedora, blivet-gui. It is eventually going to replace GParted, the most popular GUI based partition manager, found in all major distros. The new tool is named blivet-gui after the blivet python library (originally Anaconda's storage management and configuration tool). The need of a new partition manager stems from the fact that none of the existing GUI partitioning tools supports all modern storage technologies. Fedora's Anaconda base supports all, though, and is hence chosen as the back-end for this new tool. The application is only a few months old but is already looking nice and useful. Features like RAID and BTRFS support are being worked on. Vojtech Trefny is the other developer working with Vratislav on blivet-gui. Here's the announcement.

170 comments

  1. So.... by Anonymous Coward · · Score: 4, Insightful

    Fedora is going to replace GParted none of the existing GUI partitioning tools supports all modern storage technologies. Theyre replacing it with blivet-gui which doesnt support features like RAID and BTRFS.

    That hat too tight?

    1. Re:So.... by binaryhat · · Score: 1

      Fedora is going to replace GParted none of the existing GUI partitioning tools supports all modern storage technologies. Theyre replacing it with blivet-gui which doesnt support features like RAID and BTRFS.

      That hat too tight?

      The hat is cool!

    2. Re:So.... by Anonymous Coward · · Score: 0

      ... "eventually going to replace"... Sounds like it will take some time until it does.

    3. Re:So.... by Jeremiah+Cornelius · · Score: 2, Funny

      Are you the Judean People's Front?

      Listen. The only people we hate more than the Romans are the fucking Judean People's Front.

      P.F.J.: Yeah...

      JUDITH: Splitters.

      P.F.J.: Splitters...

      FRANCIS: And the Judean Popular People's Front.

      P.F.J.: Yeah. Oh, yeah. Splitters. Splitters...

      LORETTA: And the People's Front of Judea.

      P.F.J.: Yeah. Splitters. Splitters...

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
    4. Re:So.... by Anonymous Coward · · Score: 0

      What we really need is a tool that can work with all major filesystems, the ability to add modules for new filesystem or LVM systems, and can work both on the command line (so it can be used as part of a script), in a text window (ncurses/curses), and of course, as an X-windows client with as few library dependencies as possible.

      Even Windows has done this, although Storage Spaces is still separate from diskmgmt.exe and diskmgmt.msc.

      btrfs is a part of life. It finally is production-ready as of the last kernel, and only will get more stable after Facebook hammers the living fsck out of it. However, this doesn't mean that other LVMs and filesystems can be swept aside. Linux is used quite often in embedded components where space is everything, and SquashFS support can be important for a boot volume that might be measured in kilobytes or megabytes, not terabytes.

      What would be ideal is a GUI and curses tool similar to system-config-lvm, except with btrfs support. A filesystem may not be mainstream, but that is what modules are for.

    5. Re:So.... by Anonymous Coward · · Score: 0

      splitters

    6. Re:So.... by ysth · · Score: 3, Insightful

      No, we need such a command line tool or possibly library with a command line tool wrapped around it. The GUI is entirely optional and certainly shouldn't be bundled.

    7. Re: So.... by Guy+Smiley · · Score: 5, Interesting

      In typical open source fashion, their replacing a tool (GParted) that doesn't support a few features they want with a new one that (at least initially) didn't support _any_ features at all because it was written from scratch.

      Why not just fix GParted to add the few missing features instead of writing a completely new too? The new one will of course itself not support all the features GParted had, but instead be chok full of new bugs that will take years to find and fix...

      Why is it that everyone wants to reinvent the wheel instead of using and improving the tools we already have?

    8. Re: So.... by Anonymous Coward · · Score: 0

      Because you get credit for reinventing the wheel.

    9. Re: So.... by bored · · Score: 5, Insightful

      I considered moderating you, but I think this is really a case of <whine> "C++ is haaardddd, learning it enough to understand how to plug in a new module is going to take me months. Instead I'm going to rewrite it" </whine>

      Or similar bullshit by people who think "scripting" languages are appropriate for base system tools. Now you will have python dependency hell every-time you want to do something simple like repartition your disks. Oh, and is that project python 2 or python 3? On and on..

      Frankly, its fsking stupid and its another sign that redhat is jumping the shark.

      Plus, do you really want to depend on the skills of some "leet" hacker that thinks python is an appropriate tool for this?

    10. Re:So.... by Anonymous Coward · · Score: 0

      I strongly suspect the hand of Lennart Poettering somewhere in this mess. I mean, c'mon, blivet even literally means "ten pounds of shit in a five pound bag".

      Not to mention the whole "let's throw away perfectly good, proven tools" bit--for the sake of "it shouldn't wipe out your data if you don't want to" (emphasis mine). Is this really the right solution for a distribution? Let it get tested by outside usage first so it gains a history in the community, along with the accompany knowledge of "if this, do that", and THEN contemplate trusting your systems to it.

      I hope this doesn't infect Debian like PulseAudio and systemd.

    11. Re: So.... by Anonymous Coward · · Score: 1, Insightful

      This is a partition editor. It gets run O(1) times on each computer, within an environment that, if python is not supported, it should not be run.

    12. Re: So.... by Anonymous Coward · · Score: 1

      Q: Why not just fix GParted?
      A: NIH

      I wish this was a joke.

    13. Re:So.... by zdzichu · · Score: 1

      Fedora isn't. It just some guy choosen to announce his project on fedora-devel mailing list.

      --
      :wq
    14. Re:So.... by arglebargle_xiv · · Score: 1

      splitters

      You call that a splitter? This is a splitter.

    15. Re: So.... by Anonymous Coward · · Score: 1, Insightful

      Give it a rest. Someone pissy enough about not having python installed isn't a wuss using a GUI partition tool. You're the fscking stupid one.

    16. Re: So.... by Anonymous Coward · · Score: 0

      Well, I that is reasonably fine. I personally prefer to have a partitioning tool that can be used from minimal systems like an install disk or a rescue disk.
      Then again, I never really use GParted either.

    17. Re:So.... by Anonymous Coward · · Score: 0

      Quite likely this tool will be assimilated by systemd and become a hard dependency for X desktop..

    18. Re: So.... by thegarbz · · Score: 3, Insightful

      In typical open source fashion, their replacing a tool (GParted) that doesn't support a few features they want with a new one that (at least initially) didn't support _any_ features at all because it was written from scratch.

      Why not just fix GParted to add the few missing features instead of writing a completely new too? The new one will of course itself not support all the features GParted had, but instead be chok full of new bugs that will take years to find and fix...

      Why is it that everyone wants to reinvent the wheel instead of using and improving the tools we already have?

      In the typical open source fashion people thinking they're experts will blindly criticise someone's decision without understanding it. How about you start with blivet-gui is not a partition manager and then work onwards from there with your understanding.

      Blivet-gui is a standalone implementation of the storage manager used during the install process. Yes it can partition, and in the true open source fashion it uses another program to do so (parted), but that's a small subset of what they want to use it for which is more like be a one stop shop for all disk management, volume management, and RAID management.

      Please put the pitchfork away.

    19. Re: So.... by tshawkins · · Score: 1

      Fedora installs python as part of its base, pretty much all the command line system-* tools used to install and configure rh/fedora are written in python, hence there is a large community of devs who work in python at the system level, and a bunch of existing python libraries for touching just about every part of the system, including as pointed out in the article all the filesystems supported by the installer. While i am not a python programmer, and not a system level hacker, i can see how the approach makes absolute sense.

    20. Re: So.... by DrXym · · Score: 3, Informative

      Or similar bullshit by people who think "scripting" languages are appropriate for base system tools. Now you will have python dependency hell every-time you want to do something simple like repartition your disks. Oh, and is that project python 2 or python 3? On and on..

      gparted is a graphical tool for editing partitions and already has a raft of dependencies. One more won't make a difference especially since python is used increasingly in core distributions for scripting instead of bash.

      Secondly, perhaps the reason that gparted is considered a mess is precisely because it mixes up the graphical parts and the low level stuff in one package, a problem compounded because the installer also has its own partition editor. Fedora appears to have written a layer called blivet to abstract out partitioning from the installer GUI and therefore it makes sense that they use it in the desktop also.

    21. Re:So.... by CronoCloud · · Score: 1

      I hope this doesn't infect Debian like PulseAudio and systemd.

      Are you one of those bearded fellows who tugs at his suspenders as he pines for the days of pine over a serial line or 9600kbps phone line? Do you use TECO because EMACS is too newfangled for you?

      Now amittedly I'm a desktop user of Fedora so the change to systemd hasn't really affected me much (I still use the classic service commands which redirect to systemd), but... pulseaudio is better than what came before. Yes, it took time to polish the thing and iron out some issues, it didn't work by default with some HDMI audio till Fedora 18 (one would have to manually edit the default.pa in that case)... but now it works well and can do things that alsa, oss and esd can't easily do.

      on-the-fly per application audio control is the best thing ever. I have total control over where my audio goes. If I want one application to route audio to HDMI and another to route audio to analog headphone out, I can do that. I could even route audio over the network, just like X.

    22. Re: So.... by Anonymous Coward · · Score: 0

      Unless you're offering to do it, shut up and let them solve their problem.

    23. Re: So.... by gilboad · · Score: 1

      ... Have your bothered to read the release message instead of rushing to press the "save" button you'd notice the following [1]:

      "Why not use GParted you ask? The reason we came up with blivet-gui is that none of the existing storage management tools supports all storage technologies supported in modern Linux distributions. Anaconda does support them all so it's only logical to take Anaconda's storage backend, combine it with a nice, intuitive and in general user-friendly frontend and build a standalone application for storage management."

      So, I assume that Fedora should also throw out their Anaconda installer, and somehow write a new installer based on parted (the library behind gparted), just so they "won't reinvent the wheel"?
      Beyond that, what makes you so sure its even remotely possible to add iSCSI, BTRFS, LVM and Cryptofs support to gparted? As you are so quick to judge that Fedora is reinvent the wheel due to non-technical reasons, I assume you already know from personal experience that there are no design issues in adding the "missing features" to parted.

      [1] https://lists.fedoraproject.or...

    24. Re: So.... by gilboad · · Score: 2

      God knows why anyone moderated your comment as insightful.

      1. Fedora / RedHat is targeting, wait for it, Fedora / RedHat. End of story.
      As someone that maintains a fairly large DPI (kernel/user-land) software and a management software that uses PyGI, I can from attest from personal experience that both PyGI and PyGTK under both Fedora and RHEL are top-notch with zero dependencies issues.
      2. PyGI is *far* easier to use than Qt/C++. We wrote the original management code in Qt, but switched to PyGI as it increased that rate of the development by 3/1. We may switch back to Qt due to performance issues and lackluster mutli-threading support (Known python limitation) and problematic Windows support. (Both of which are non-issues when it comes to *Linux* storage management)
      3. I can agree that if you want to scan incoming packets at 150Gbps using software only, or write output at 1GB/s, you'd most likely need C++ or even C/asm combination. But what-exactly prevents python from calling a couple of syscalls to executing /sbin/cryptsetup / /sbin/lvm or /sbin/mkfs.ext4? What exactly makes Qt/C++ better at calling external binaries (such as the one mentioned above)?

      - Gilboa

    25. Re:So.... by Anonymous Coward · · Score: 0

      You call that a splitter? That's a bloody filter! This is a splitter... ;)

    26. Re: So.... by Anonymous Coward · · Score: 0

      God knows why anyone moderated your comment as insightful.

      Well because bored pretty much hit the nail on the head.

      1. Fedora / RedHat is targeting, wait for it, Fedora / RedHat. End of story.

      The "my way or the highway" method of programming didn't exactly help Gnome either. If Fedora / RedHat does it only because it suits them then they may have jumped the shark.

      2. PyGI is *far* easier to use than Qt/C++. We wrote the original management code in Qt, but switched to PyGI as it increased that rate of the development by 3/1.

      This is what bored was referring to. It doesn't matter how much faster you can develop in PyGl if you have to start completely over versus adding some code to an already existing piece of software. Basically you've just confirmed bored's hypothesis that you believe it would be easier to completely rewrite something than to find someone who understood how to program in something other than Python.

    27. Re:So.... by Anonymous Coward · · Score: 0

      The idea of pulseaudio is great. The execution is shit. If I mute it, it doesn't unmute without going down into alsamixer and unmuting it. Mute is one way. Isn't that shit enough?! This has been a fucking bug for over a year now.

      I'm not against new software and technology. I'm against rolling it out widely before it's been fucking tested and debugged.

    28. Re: So.... by Anonymous Coward · · Score: 0

      I'm thinking about starting my own distro tentatively named Clusterfuck Linux. The idea is to take all these forks that while proposed to fix things, typically break systems. Lets put all of them all in one place to spur development.

      Systemd, unity, wayland, pacman, pulse audio and now this partition manager. It will be the absolute bleeding edge of all things Linux. Contact me if you want to be involved.

    29. Re: So.... by RabidReindeer · · Score: 1

      I considered moderating you, but I think this is really a case of <whine> "C++ is haaardddd, learning it enough to understand how to plug in a new module is going to take me months. Instead I'm going to rewrite it" </whine>

      Or similar bullshit by people who think "scripting" languages are appropriate for base system tools. Now you will have python dependency hell every-time you want to do something simple like repartition your disks. Oh, and is that project python 2 or python 3? On and on..

      Frankly, its fsking stupid and its another sign that redhat is jumping the shark.

      Plus, do you really want to depend on the skills of some "leet" hacker that thinks python is an appropriate tool for this?

      Considering that Anaconda itself is written in python, that shark is about 15 years in the rear-view mirror. They didn't pick the name "Anaconda" for nothing.

      I guess that python was an appropriate tool after all.

    30. Re: So.... by RabidReindeer · · Score: 1

      Microsoft wasn't thoughtful enough to provide a port of Visual Basic for Linux. But there are lots of programs that deserve something between quick-and-dirty and full-on C or Java. Perl and Tcl were kind of filling that space, but one's write-only and the other isn't a complete system, but rather a way of stringing system tools together, one step up from raw shell scripts.

      Python is Linux's version of Visual Basic. It's easy to understand, has a rich set of system interface libraries (which install without the frustration I tend to get from CPAN), is easy to write in, and even has code optimization support.

      You could do worse.

    31. Re:So.... by m4rtink · · Score: 1

      Blivet GUI is a frontend to the Blivet storage management library, which already supports RAID and BTRFS just fine. It is just not yet supported in the GUI, but I suppose it should be added soon.

    32. Re:So.... by m4rtink · · Score: 1

      This is an email from Lennart Poettering to the Fedora Devel list dissing the Blivet GUI project due to implementation details:

      https://lists.fedoraproject.or...

      So Lennart Poettering actually really is involved, but in a rather different way than you would expect. :)

    33. Re: So.... by heson · · Score: 1

      No thats not the Fedora way. The Fedora way is replacing working feature filled software with buggy software that barely solves the mandatory features just because it has some cool new feature. Then they push a gazillion man hours into that crap until it becomes very good and then replaces it when users starts to love it.

    34. Re: So.... by bbsalem · · Score: 1

      Yeah, Mac OS X is sounding better and better all the time. Apple controls the platform but everything installs and the package management is stable, which is more than I can say for most Linux, and there isn't a zoo of filesystem types and partitions to deal with. To really upbrade Ubuntu I have to create space for a new partition to move /home to and then scrub the boot partition and reinstall. What if I have a 1 TB drive? Why should I have to partiton a 5 GB partition each time I want to use a different Linux? Why not use a simple filesystem and boot from any of a choice of images and don't let RedHat or Connonical control the filesystem?

    35. Re:So.... by Anonymous Coward · · Score: 0

      The one way mute was the final straw on the Pulseaudio that made me remove it from my machines. It was a bit embarassing to tell to my better half that if there is no audio on our machines, please open the audio controls and unmute all of the outputs PA had created until some of them will enable the audio. Without PA, the mute and unmute just work each time one presses the button for it in the keyboard. Perhaps PA needs a integration with systemd to make the unmute work again?-)

    36. Re: So.... by lsatenstein · · Score: 1

      Or similar bullshit by people who think "scripting" languages are appropriate for base system tools. Now you will have python dependency hell every-time you want to do something simple like repartition your disks. Oh, and is that project python 2 or python 3? On and on..

      gparted is a graphical tool for editing partitions and already has a raft of dependencies. One more won't make a difference especially since python is used increasingly in core distributions for scripting instead of bash.

      Secondly, perhaps the reason that gparted is considered a mess is precisely because it mixes up the graphical parts and the low level stuff in one package, a problem compounded because the installer also has its own partition editor. Fedora appears to have written a layer called blivet to abstract out partitioning from the installer GUI and therefore it makes sense that they use it in the desktop also.

      If you do not like the new tool, continue with Gparted. I am sure the Debian guys and SUSe will arrange for the RAID stuff to be included in Gparted.

      --
      Leslie Satenstein Montreal Quebec Canada
    37. Re: So.... by Anonymous Coward · · Score: 0

      Seeing as how Fedora was always intended as a bleeding edge developer distro to serve as a testbed for Redhat Enterprise Linux ..... looks like everything is working as designed.

    38. Re:So.... by CronoCloud · · Score: 1

      The execution is shit. If I mute it, it doesn't unmute without going down into alsamixer and unmuting it. Mute is one way. Isn't that shit enough?!

      I use Pulseaudio on Fedora 20. Mute/unmute works just fine.

    39. Re:So.... by CronoCloud · · Score: 1

      Without PA, the mute and unmute just work each time one presses the button for it in the keyboard.

      I run pulseaudio on Fedora 20, mute/unmute works fine every time I press the button on the keyboard.

  2. oh boy! by binaryhat · · Score: 1

    A new goodie tool.

  3. The origin of the term "blivet" by Nimey · · Score: 3, Informative

    Ten pounds of shit in a five-pound bag, i.e. a nasty, dirty situation. It seems to have originated around the 1940s as US military slang.

    --
    Hail Eris, full of mischief...

    E pluribus sanguinem
    1. Re:The origin of the term "blivet" by Anonymous Coward · · Score: 3, Funny

      Ten pounds of shit in a five-pound bag,

      A fantastic deal! if you're a dung beetle.

    2. Re:The origin of the term "blivet" by Anonymous Coward · · Score: 4, Informative

      http://en.wikipedia.org/wiki/Blivet

      It is a poiuyt, devil's fork or widget, is an undecipherable figure, an optical illusion and an impossible object. It appears to have three cylindrical prongs at one end which then mysteriously transform into two rectangular prongs at the other end.

    3. Re:The origin of the term "blivet" by RogueWarrior65 · · Score: 1

      I've always heard that it was six pounds. It's funnier because the bag might survive or it might break but you won't know when or where.

    4. Re:The origin of the term "blivet" by Anonymous Coward · · Score: 0

      ...as well as the unique Addo flightless dung beetle, found almost exclusively in Addo:
      http://sanparks.org/parks/addo/

    5. Re:The origin of the term "blivet" by m4rtink · · Score: 1

      Lets say that storage management is a rather interesting area to be involved in. ;-)

    6. Re:The origin of the term "blivet" by Anonymous Coward · · Score: 0

      I like the shitty definition better.

  4. Damn the GUI! by turbidostato · · Score: 2

    "The need of a new partition manager stems from the fact that none of the existing GUI partitioning tools supports all modern storage technologies"

    Does the backend -and kickstart, support all those "modern storage technologies"?

    That's the important part. For a GUI-based installation, the ability to format -and install into, a single root partition is good enough for me.

    1. Re:Damn the GUI! by phantomfive · · Score: 4, Interesting

      Yeah, another example of NIH coming from RedHat.

      --
      "First they came for the slanderers and i said nothing."
    2. Re:Damn the GUI! by Anonymous Coward · · Score: 1

      The emotional reaction to your statement is something that I had to remind myself shouldn't be said in public, so I won't repeat it here.

      Keep in mind that NIH at RedHat makes very little sense in the big scheme of things, when they fund at least 60% of all open source software development. Sure, they probably don't fund any geneology software or the latest MP3 player, but you'd have very few compilers, system software, etc without RedHat picking up the bill.

      So, not invented here rarely makes sense with RedHat, as a lot of the stuff that we take for granted was invented by RedHat. Today we might say, oh yeah, well there was X (and today X might be pretty good) but when RedHat started project Y, project Y was the compelling reason for X to get off it's laurels and actually (you know) develop again.

      Even then, odds are that RedHat's replacement is probably better, if you can avoid getting trapped in the hate. It's not like they write the stuff because existing projects already out-perform their customer's needs.

    3. Re:Damn the GUI! by Anonymous Coward · · Score: 0

      The problem is that even though the dual partition system (one for /, and one for swap) served us since 1991 quite well, a lot of needs have changed.

      One example is basic disk space utilization. Say I'm running an application, and it needs another 256 gigs of space. Yes, I could add a new partition, mount it, symlink files. I could also use unionfs to span two block devices on a filesystem level. Of course, I could tar off the filesystem and recreate the mount point on the new drive. However, the quickest solution (and this is completely ignoring fault tolerance) is to add a new hard disk [1], expanding the volume group onto the new drive, and expanding the filesystem for the application.

      Another reason why LVM use is needed is when one needs to move from one backend storage to another. Say the data is sitting on a relatively slow disk array. The company gets a decent SAN, and wants to consolidate backups using NDMP to a Data Domain appliance. With a LVM in place, one can create a mirror of all data, then once it is completely synchronized, break the mirror and all the data would be on the SAN. One can also just do a migratevg, and let the LVM code move every bit of data from the old disks to the new ones. Without a LVM in place, the machine would have to be shut down, backed up via an imaging utility and restored to the SAN... and in production, this almost certainly wouldn't be acceptable [2].

      Of course, software RAID can be useful. On some servers, they only offer RAID 1. So, I use that to protect the root filesystem, perhaps the OS if the mirror has drives big enough. The rest of the data goes on a software RAID 5 or 6 (the ideal is RAID-Z or RAID-Z2.) With ZFS or btrfs, a scrub can easily detect bit rot, and in RAID-Z2, can fix it.

      Even for a desktop machine, a LVM is useful for RAID ability.

      tl;dr, LVM and ZFS-like filesystems are here to stay, so a tool needs to work with them.

      [1]: Preferably via SATA, SAS, or a hard disk protocol. USB is designed for more dynamic storage, rather than storage that has to have the same ID and position day after day.

      [2]: Oftentimes VMs are being more and more used for production, so if you have an ESXi cluster, none of this stuff matters since the datastore is the critical part, not what the VM client thinks are its own drives. In reality, unless there is an actual reason something has to be bare metal (driving hardware devices, or requiring the full host performance), it should be tossed on a cluster. Plus, you can do backups by snapshot, kick them via NDMP to the backup appliance, and the client doesn't need any special software present.

    4. Re:Damn the GUI! by jafac · · Score: 1

      lol-ing at your comment, and your .sig :D

      --

      These are my friends, See how they glisten. See this one shine, how he smiles in the light.
    5. Re:Damn the GUI! by phantomfive · · Score: 1

      The emotional reaction to your statement is something that I had to remind myself shouldn't be said in public, so I won't repeat it here.

      Ulrich Drepper, is that you?

      --
      "First they came for the slanderers and i said nothing."
    6. Re:Damn the GUI! by phantomfive · · Score: 1

      Are they contradictory somehow?

      --
      "First they came for the slanderers and i said nothing."
    7. Re: Damn the GUI! by Anonymous Coward · · Score: 0

      Every "u hater"-type reaction to RH criticism is bound to sound more retrograde than the earlier one. It has gone beyond pathetic.

    8. Re:Damn the GUI! by OneAhead · · Score: 1

      So, not invented here rarely makes sense with RedHat

      NIH rarely makes sense anywhere, yet people are doing it everywhere. It's just that much more fun to create one's own code base and fix one's own bugs than to learn someone else's and do their homework for them. Own farts smell better...

    9. Re:Damn the GUI! by phantomfive · · Score: 1

      It's just that much more fun to create one's own code base and fix one's own bugs than to learn someone else's

      So true

      --
      "First they came for the slanderers and i said nothing."
    10. Re:Damn the GUI! by Anonymous Coward · · Score: 0

      The competition could be a good thing, as it could force the gparted to implement something new or fixing existing bugs. Besides that, it is nice to see a announcement of a thing with GUI that does not mention "experience" even once. Perhaps the UX-guys do not dare to touch a partition management software since they don't understand it? On the other hand, lack of understanding the problem area has never prevented them from breaking up a software before.

    11. Re:Damn the GUI! by m4rtink · · Score: 1

      "The need of a new partition manager stems from the fact that none of the existing GUI partitioning tools supports all modern storage technologies"

      Does the backend -and kickstart, support all those "modern storage technologies"?

      That's the important part. For a GUI-based installation, the ability to format -and install into, a single root partition is good enough for me.

      Yes - the blivet storage management library supports alsmost any existing data storage technology you can come up with and then some more. Thats the reason why Blivet GUI came to be - the functionality is already there, it just needs to be exposed by a graphical user interface.

  5. fuck up your disks with greater ease! by Anonymous Coward · · Score: 0

    Almost as eezee as windo'hs!

    1. Re:fuck up your disks with greater ease! by Anonymous Coward · · Score: 2, Informative

      And aimed at the same audience.

  6. Why not contribute to gparted? by sayfawa · · Score: 4, Insightful

    Instead of making another program, I wonder what was wrong with sharing the code with gparted so that they could incorporate support for more filesystems?

    TFA didn't say if that option had been explored.

    --
    Free the Quark 3 from asymptotic confinement! Bring your charm! Don't get down! All colours and flavours welcome!
    1. Re:Why not contribute to gparted? by Anonymous Coward · · Score: 0

      2004:
      "Instead of making another program, I wonder what was wrong with sharing the code with fdisk so that they could incorporate support for more filesystems?

      TFA didn't say if that option had been explored."

      What goes around comes around.

    2. Re:Why not contribute to gparted? by Anonymous Coward · · Score: 1

      blivet-gui is Gtk application written in Python, like all of redHat's tools. I don't know what gparted is written in, but it's probably not Python.

      RedHat is also known for having a bad case of Not-Invented-Here as well as wanting more control over a significant piece of their distro.

    3. Re:Why not contribute to gparted? by Anonymous Coward · · Score: 0

      gtkmm (c++).

    4. Re:Why not contribute to gparted? by Nimey · · Score: 1

      Besides that fdisk and gparted have totally different missions, you mean?

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    5. Re:Why not contribute to gparted? by Burdell · · Score: 5, Informative

      Because (as usual) the summary got it wrong. This is not a partition manager, it is a disk/filesystem manager. Partitions make up one part of that, but it is also intended to manage LVM, RAID, btrfs filesets, etc. I believe it uses the parted library on the backend for partitions.

      This is based on the years-of-development code used in the backend of anaconda, the Fedora/Red Hat installer. The code has been pulled out, split up into a library, and set up for stand-alone use (after install). I believe the intention is that anaconda keeps using the library, but now there will be the same interface during install and afterwards for managing disks and filesystems.

    6. Re: Why not contribute to gparted? by Anonymous Coward · · Score: 0

      What the fsck?

    7. Re:Why not contribute to gparted? by Blaskowicz · · Score: 1

      So blivet and parted have totally different missions, I guess?

      *I don't know the fuck what's so different between fdisk and parted, besides support for newer stuff like GTP partition tables.

    8. Re:Why not contribute to gparted? by guacamole · · Score: 1

      My guess the answer is that then there would be two separate code bases, one in gparted and another that anaconda uses. Considering so much Fedora/RedHat is built around anaconda, it makes sense to reuse some of anaconda code in places other than installer.

    9. Re:Why not contribute to gparted? by Anonymous Coward · · Score: 0

      Most likely it is not from Red Hat and therefore the "not invented here" syndrome kicks in. Alternatively, gparted could have a too degenerated code base. So instead fixing that which costs time, they build a new code base which will degenerate even more quickly, as they have to hack it together in short time.

    10. Re:Why not contribute to gparted? by Anonymous Coward · · Score: 0

      Why not take all blivet-gui's (python) code and incorporate it into gparted's (C++) code to give it support to more filesystems?

      I don't think blivet-gui has developed the backend code to support its filesystems, probably it uses existing LVM2 backend and other system utilities through an abstraction layer (a library). I'm just guessing here.

      Speaking of C++ code, in this case it's probably faster, but not noticeably faster, and certainly more difficult to manipulate than Python, to add frontend support to newer technology. Maybe it is easier to develop a whole new application than to add gui support to LVM VG, LV and filesystems inside LV, and raid, inside gparted's gui.

    11. Re:Why not contribute to gparted? by m4rtink · · Score: 1

      It is based on the blivet storage management library:

      https://github.com/dwlehman/bl...

      Which is also used by the Anaconda Fedore/Red Hat Enterprise Linux installer:

      https://fedoraproject.org/wiki...

      And Open LMI:

      https://fedorahosted.org/openl...

      But it might indeed use libparted to create the actual partitions.

  7. Uses Anaconda? by Anonymous Coward · · Score: 1

    If their liveCD installer is any indication, I'm not going to touch this with a ten foot pole. Its behavior is essentially random, whether it comes to partition numbering, free space reporting, and partition creation.

    1. Re:Uses Anaconda? by lippydude · · Score: 1

      If their liveCD installer is any indication, I'm not going to touch this with a ten foot pole. Its behavior is essentially random, whether it comes to partition numbering, free space reporting, and partition creation."

      Last time I tried, Fedora managed to install next to Ubuntu, without problems. The only distro that without fail, trashes dual-boot, is Windows ..

    2. Re:Uses Anaconda? by m4rtink · · Score: 1

      Talk is cheap - bugreports/logs or it din't happen. :P

  8. Why not add it to systemd? by Anonymous Coward · · Score: 0

    Maybe I shouldn't give those nutcases any ideas....

    1. Re:Why not add it to systemd? by gweihir · · Score: 1

      Indeed.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  9. Oblig. XKCD by NotInHere · · Score: 1, Redundant
    1. Re:Oblig. XKCD by Anonymous Coward · · Score: 0, Insightful

      Gee... we haven't seen that one over a thousand times already on Slashdot. Thanks for posting it again. Stay cool!

    2. Re:Oblig. XKCD by NotInHere · · Score: 1

      Technology repeats itself. Perhaps you see a message behind the surface? Do you know how often the letter "q" appears on slashdot? Do you complain about that one?

      On the internet things are cool only a very short time. If it were about cooless, this would have disappeared a long time ago.

    3. Re:Oblig. XKCD by reub2000 · · Score: 1

      An application is not a standard.

    4. Re:Oblig. XKCD by Anonymous Coward · · Score: 0, Troll

      You are so cool. May I suck your penis?

    5. Re:Oblig. XKCD by I'm+New+Around+Here · · Score: 1

      And you've read every one of them, just to verify your conjecture?

      --
      If you think I voted for Trump because of this post, you're wrong. I voted for Dr. Jill Stein of the Green Party. Again.
    6. Re:Oblig. XKCD by Anonymous Coward · · Score: 0

      Sure buddy! Are you at the Missouri Ren Faire too?

      I'm by the funnel cake and pewter shoppe, next to your fat wiccan wife and ugly kid.

  10. Who's designing the UI? by gun26 · · Score: 1

    I sure hope it won't be the geniuses who brought us the incomprehensible "new Anaconda" interface several Fedora releases ago.

    1. Re:Who's designing the UI? by CronoCloud · · Score: 1

      what do you mean several releases ago. It's still not as good as it could be in Fedora 20. IIRC it still doesn't let you individualize the packages installed, only letting you select "groups". One of my goals as a Fedora user is to NOT have to deal with the installer and I pray that "fedup" works properly so I don't have to.

  11. Idiots by Anonymous Coward · · Score: 2, Insightful

    I hate the FOSS mentality sometimes. So much unnecessary reinventing the wheel when all that's need is some enhancement of an existing tool. It seems like it'd make much more sense to take GParted, a very mature, well-supported and proven tool, and extend its feature set to incorporate the "modern technology" they require, rather than create a whole new tool almost from scratch and deal with an unproved base. They can either work with the GParted developers to incorporate these new features, or fork it and do the work themselves.

    Reusing existing tech is supposed to be the whole fucking POINT of FOSS - it's freely available code, take it and use what's already been developed and use it as a base to create something new/better. So many people though want to start from scratch because they believe that their implementation will be better. It's one of the reasons I see so many music players that do 90% of what Winamp can do for example, each player though doing a different 90% than the other. No-one seems to be able to collaborate in FOSS.

    1. Re:Idiots by kesuki · · Score: 1

      that worked great for openssl http://en.wikipedia.org/wiki/Heartbleed
      their solution? a fork to libssl without all the messy kludges for various vendors/platforms.

    2. Re:Idiots by Fwipp · · Score: 2

      Exactly - a fork, not a rewrite.

    3. Re:Idiots by StripedCow · · Score: 1

      take it and use what's already been developed and use it as a base to create something new/better,
      while letting the original developers take all the credit

      Fixed that for you.

      Also, making changes to somebody else's code involves the risk of introducing serious bugs. So essentially, what you are proposing is a lose/lose situation.

      --
      If Pandora's box is destined to be opened, *I* want to be the one to open it.
    4. Re:Idiots by m4rtink · · Score: 1

      Um, Blivet GUI is jut a GUI frontend to the existing Blivet storage library that has been there for years (many, many years if you include the time it was part of the Anaconda core). Adding the same functionality to GParted or making GParted use Blivet on the other hand would be one big useless rewrite.

  12. Don't let the systemd people know by Anonymous Coward · · Score: 1

    For surely they will want to integrate it.

  13. Still using /sbin/fdisk here.. by Anonymous Coward · · Score: 0

    Still using /sbin/fdisk here...

    1. Re:Still using /sbin/fdisk here.. by gweihir · · Score: 1

      Which means you actually understand partitioning and do not need some cretin "manager" to do it for you. Same here, although I use gparted for resizing and things like that.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    2. Re: Still using /sbin/fdisk here.. by Anonymous Coward · · Score: 1

      I agree with parent, and grand-parent. Now-a-days I use gdisk, though.

      When I switched to Gentoo 10 years ago (from SuSE), I /had/ to learn fdisk.

      Personally I feel anyone serious about learning Linux, should install and manage a Gentoo/Funtoo box for at least a year. I honestly find some of the stuff in RHEL/CentOS kind of cumbersome after having used Gentoo/Funtoo and all the handy tools that come with it for so long.

    3. Re: Still using /sbin/fdisk here.. by gweihir · · Score: 1

      Good point. One sign of the cretinization of Linux use (also called "entering the mainstream") is that there are more and more people that can just use specific tools, but have no idea what they are actually doing. There people are then also "locked in" to a specific distribution. No doubt that is the intent of the tool-makers.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  14. Pottard will have this in systemd before weeks end by musmax · · Score: 1

    mark my post.

  15. Uses Anaconda? by Anonymous Coward · · Score: 0

    At least we know it has good /dev/random support.

  16. We have a winner! by dbc · · Score: 4, Informative

    "RedHat is also known for having a bad case of Not-Invented-Here as well as wanting more control over a significant piece of their distro."

    1. Re:We have a winner! by Anonymous Coward · · Score: 0

      anyone else feel since rhel 7 redhat is going down hill? hope they get back on focus.

    2. Re:We have a winner! by Bacon+Bits · · Score: 1

      Which makes them not particularly different than Canonical. Or IBM. Or Microsoft, for that matter.

      --
      The road to tyranny has always been paved with claims of necessity.
  17. What does it support that others don't? by dbc · · Score: 3, Interesting

    Not flamage, this is data-seeking. The announcement only vaguely states that existing tools don't support all modern storage technologies. So, what are the technologies where blivit gets a "yes" and gparted gets a "no" in the "supports " column?

    1. Re:What does it support that others don't? by eulernet · · Score: 5, Funny

      slashdvertisement:

      Blivet: yes
      GParted: no

    2. Re:What does it support that others don't? by Anonymous Coward · · Score: 1

      The really big ones for me are LVM2 and encryption support. New enough version of GParted can see such containers, but won't touch them.

    3. Re:What does it support that others don't? by gilboad · · Score: 1

      No idea what will be included in blivit in the long run, but at least AFAIK, parted lacks the following:
      - lvm [1] [2].
      - cryptofs [3]
      - Complex software RAID setups (usually w/ lvm) [1].
      - Network based storage management (iSCSI, etc).

      - Gilboa
      [1] https://www.gnu.org/software/p...
      [2] AFAIK gparted *does* support LVM, but it requires the LVM to be inactive while being used. Which more or less makes it useless when trying to management the storage on a production server...
      [3] https://bugzilla.gnome.org/sho...

    4. Re:What does it support that others don't? by m4rtink · · Score: 1
      Basically anything more advanced than "plain partitions with a classicla filesystem (EXT3/4, XFS, FAT) on top":
      • LVM
      • BTRFS
      • RAID
      • iSCSI
      • multipath

      etc.

  18. Command line? by ToasterMonkey · · Score: 3, Interesting

    I'm completely fine seeing things move away from the older "GUI driving non-interactive commands in the background" model, to GUIs and CLIs that are built on shared libraries, because that potentially gives us THREE usable interfaces. However, is it normal for a CLI to lag behind the GUI now in Linuxland?

    I see that blivet comes from Anaconda, so I expect some integration there.
    It seems like a good CLI could be used to avoid the awkward practice of writing out a kickstart partition fragment from the pre section. We could just drive Anaconda's partitioning directly from %pre with shell logic instead of pooping out Anaconda-ese to be parsed later.

    So where's my damned anaconda partitioning CLI already, this would affect more [important] people than yet another partition GUI!!

    1. Re:Command line? by Anonymous Coward · · Score: 1

      Worst thing about anaconda partitioning tool is it decides what order your partitions should be on the drive. I always have to partition with gparted from an Ubuntu Live CD before installing RHEL/Fedora.

  19. A new partition manager. by Anonymous Coward · · Score: 0

    Yea, that's what Linux distros really need these days, can't have enough partition managers.

    1. Re:A new partition manager. by jones_supa · · Score: 1

      Linux and Linux distros have always taken the priority to ship cutting edge features over tried-and-true software.

  20. How to know if a component of Linux.. by Chryana · · Score: 1

    //How to know if an important back-end component of Linux will soon be replaced
    if (component.name=="linux-kernel*") { false; }
    else if (component.inventor=="Red Hat") { false; }
    else { true; }

    1. Re:How to know if a component of Linux.. by Nimey · · Score: 5, Funny

      Could be worse: it could have been written by Lennart Poettering.

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    2. Re:How to know if a component of Linux.. by Anonymous Coward · · Score: 2, Funny

      Could be worse: it could have been written by Lennart Poettering.

      Hey, you watch your tone! Lennart's arguably leading Linux development almost single-handedly now. Linus might be focused entirely on the kernel, but Lennart is doing all the work on system elements that are crucial to bring Linux into modern times. After Linus, Lennart's now the most prolific (and famous) Linux contributor of all time.

      Of course I'm just an AC, so there's no reason to listen to me. But I'm sure once Bennett Haselton write an article on systemd, you can be Slashdot will finally understand the genius of Lennart!

    3. Re:How to know if a component of Linux.. by readingprofile · · Score: 1

      It was a (poor) attempt a joke you stupid fucks. Clearly the mention of Bennett should have made it clear, as well as the suspiciously high praise of Lennart. But I suppose you're all idiots who can't grasp subtleties. Either that or you're just all stupid fucking americans.

  21. Can you specify the exact start cylinder for a... by Anonymous Coward · · Score: 0

    partition, or do you have to jump through hoops to get the partitions on an SSD properly aligned?

  22. KVPM? by Anonymous Coward · · Score: 0

    KVPM is by far the better GUI. Yeah, I know some of you have huge issues with KDE but KVPM handles partitions *and* LVM volumes and does so pretty smoothly.. I just discovered it a couple weeks ago when Gparted and LVM2 refused to start for some unknown reason and I needed something to get the job done.

    1. Re:KVPM? by Anonymous Coward · · Score: 0

      Does KVPM support LUKS? I'm installing it now, but it will take a while, 67MB to download (vs. 2MB for gparted).

  23. Except that it uses anaconda by Anonymous Coward · · Score: 0

    From harsh experience, "anaconda" blows goats as a pastime, and wipes the sputum into the partition blocks at the start of your disk. Really. It's fragile, confusion, underdocumented, and overall a *BAD TOOL*. The only way to make sure of consistent partitioning, especially with the 4096 byte block alignment requirement for disk images stored on NetApps for virtualizaiton, is to write a pre-deployment scripting tool to avoid anaconda partitioning like I'd avoid $20 hooker with open sores.

    Gparted is a GUI on top of parted and other tools, like LVM and the different flavors of mkfs. If it's incomplete, *compete it*. The API is clear and well documented. The API for anaconda is bad, bad Python spaghetti code that no one dares touch.

    1. Re: Except that it uses anaconda by Anonymous Coward · · Score: 0

      I call bs. It's written in python by ruby programmers, it's self documenting, easy to use, has built in new shiny. This isn't like all the tools before it, this one is for the kids that needs 128 colors in a IDE to write hello world.

  24. Anaconda too stupid to... by Anonymous Coward · · Score: 0

    Anaconda is too stupid to actually write the kickstart file it used to the operating system it installed. I'm not kidding.

    The associated tools such as "system-config-kicksteart" is too stupid to deal with a non-registered OS. I'm not kidding.

    Anaconda is too stupid to document, anywhere, that it can handle multiple '%pre' and "%post" scripts, and the associated GUI for it, system-config-kickstart, erases all but the one it can comprehend itself. And we trust these pinheads to write a GUI for disk management?

    FreeBSD, here I come!!!!!

  25. Anaconda's base supports all? by Antique+Geekmeister · · Score: 3, Insightful

    The only reason that "anaconda's base supports all" is because anaconda, and kickstart tools, have the ability to support '%pre" scripts that allow manual use of hte command line partitioning tools to tune the partitioning as desired, and completely skip anaconda partition. Anaconda has never, and from all signes will never, be able to support all disk management and partitioning tools.

    Since it's a Python based wrapper for the actual system tools used, features can be added. But there will be inevitable mismatches between configurations manageable through anaconda, and configurations manageable through command line tools for new disk and filesystem tools. And anaconda's use in system critical critical tools like kickstart mean that it _must_ be thoroughly tested before updates. This will slow feature addition in a way that gparted, or other tools, need not support.

  26. Do you Slashdoters really use Fedora? by NemoinSpace · · Score: 1

    It was DOA as far as I was concerned. Redhat basically told the world "we don't care about the desktop" and it shows. Now, I still rely on Centos but I prefer debian and my users get mint. Fedora gets to make the false insinuation that they are redhat till stuf blows up or changes in midstream. It's not redhat and it's not a standard linx desktop. Fedora is what's left over after a bunch of junior hacks get done dicking around for the day. You get to pick up the pieces. Nobody in their right mind uses Fedora. It's just Like working on the zune. Fedora is what a free edition of windows would be with a lot less polish. I wish Microsoft would just release their own version of linux and get it over with. You Linux guys are no disciplined enough to stick with a project and see it through.

    1. Re:Do you Slashdoters really use Fedora? by thule · · Score: 1

      Then I guess I'm not in my right mind.

      I like Fedora a lot. I like the desktop environment (Gnome3 has really grown on me). Fedora moves at a decent clip to track with the latest and greatest without a lot of hassle. I have always liked RedHat/Fedora's PXE/kickstart installer. I like the big projects RedHat/Fedora is working on like FreeIPA, OpenStack packaging, GFS2, KVM, OpenLMI, CloudForms, and oVirt. RedHat has spent a lot of money buying some of the companies that created some of that software and the turn around and open source all of it. FreeIPA is a big one. A seriously great project that took old code from Sun/Netscape and made it usable.

      I know the big gripe is systemd, but so far I like it. It makes writing start/stop/status configuration easy and reliable.

    2. Re:Do you Slashdoters really use Fedora? by guacamole · · Score: 1

      I have been using RedHat, Fedora, and CentOS as my personal desktop for a decade and CentOS is what I installed on desktop machines I managed. The meme that RedHat is no good for desktop is highly overblown. Just checked out CentOS 7 with Gnome, and thought the DE was still alright.

      One of my favorite things about RHEL/CentOS is a truly stable "enterprise grade" release cycle, meaning each version is supported for many years, but they give you updated installers with new drivers and such to be able to use the latest hardware. I guess that Debian gives you a similar kind of deal, although the loong time between Debian releases is due to project's pace rather than by design. Having switched to RedHat and its derivatives at around the time of RedHat Linux 6, when they finally got a working automatic updater, I never found a reason that's compelling enough to go back to Debian since then, although Debian or its derivative would be a good choice too. I guess today Debian is becoming more compelling to the purists who are sick of RHEL breaking some of well-established conventions.

    3. Re:Do you Slashdoters really use Fedora? by juanfgs · · Score: 0

      I'm a Fedora user for my workstation, I guess you have to be a person used to change. For desktop so far it has been a good experience, surprisingly worked better than Ubuntu has been on my machine (I'm not flaming Ubuntu, it works great for a lot of people that I know including my mom who can even install it on her own). The only real perceived fuck up is the new Anaconda GUI, I think it needs to be remade, they split from the step by step style of wizard and it doesn't really helps a lot. I really like some of the administrative tools like firewalld they are quite intuitive and useful, and the new stuff that I don't like... well I just don't use them. I still update from command line, and use the old tools which work fine. I think you are not really asking tho... just expressing your dislike for Red Hat and Fedora in the old Linux-er fashion of calling out a windows clone when it's not your distro of choice.

  27. Ridiculous by schmaustech · · Score: 0

    This is the reason why Linux will never make it to the desktop. The distro's spend far too time changing out tools for the new fan-boi based ones instead of maturing and refining the existing ones. Hey I have this new tool because nobody had the common sense to fix the bugs in the previous tools.

  28. Anaconda too stupid to... by Anonymous Coward · · Score: 0

    Your pain will increase.

    The view from slackware has always been much more pleasant and they don't have the self proclaimed BSD god-head in charge.

  29. Do you Slashdoters really use Fedora? by Anonymous Coward · · Score: 0

    You might have made a more believable case if you hadn't included the W* references. While your own preferences aren't inherently bad I would rarely trust a system admin with such a closed mindset.

    Seriously Zune? And the flame bait of a MS released linux. Why would anyone care if you ever made it to work? A trouble ticket that you dealt with would encourage many to find a different solution. A company without you in it would be a good start.

  30. It's wrong because NIH by Anonymous Coward · · Score: 0

    It's wrong because NIH. Sadly, it's the same curse that afflicts a lot of open-source projects.

  31. Slashdot: News for nerds, stuff that matters? by Anonymous Coward · · Score: 0

    And most of the comments here demonstrating yet again how slashdot has become totally irrelevant.

  32. Re:dbus interface? by Anonymous Coward · · Score: 0

    Will it have a dbus interface, and run as PID 1?

    That and more, PID 1 is essential for the interface to warn you about the TP being close to gone in the bathroom, and they're going to integrate a webserver into systemd as well so we don't need those other packages. I hear they're considering baking IE code into it as well, so it's part of the OS and non-removable.

  33. Shouldn't by Anonymous Coward · · Score: 0

    systemd handle this?

  34. Lie by Vlijmen+Fileer · · Score: 2

    "The need of a new partition manager stems from the fact that none of the existing GUI partitioning tools supports all modern storage technologies."
    That would be a lie. If that is all, just contribute to Parted already. As always more will be at stake, probable things like "not invented here" and "I wanna have the power". And as a result we get to have a partition editor that needs Python??

    1. Re:Lie by thatkid_2002 · · Score: 2

      It's not rewriting parted. Parted can't handle all modern storage technologies as it only deals with partitions which are only one part (pun intended) of the picture. In the [your favourite distro here] installer the UI calls out a *suite* of tools just like Blivet-GUI does. Previously in Fedora this was all piled into Anaconda - but now it is split out into this "Blivet-GUI" thing.

      If you bothered to read the articles or browse the source you'd know that it depended on Blivet and subprocess calls to normal system utilities. Blivet has been around for at least two years already and has matured through its use in Anaconda. Anaconda has been around for many years and has always (AFAIK) depended on Python. Nearly every Linux distro (and other Unixes, OSX and even Haiku) come with Python by default. Most installation environments can use whatever they please without impacting the resulting system so even if you didn't want to install Python (or the more concerning GTK, IMO) you don't have to. This person was not engaging in NIH - they were simply writing a new GUI to an existing tool to allow for better integration, easier modification and fewer dependencies... Shock horror! OMG WHAT AN IDIOT RITE???

      This mindless Red Hat bashing has really gone too far.

  35. hmm by PC_THE_GREAT · · Score: 1

    I hope whatever its coming up with allows disk partition creation based on partition form kickstart scripts itself.

  36. Blivet? by thePowerOfGrayskull · · Score: 1

    So we're stuck with either "impossible object" or "ten pounds of shit in a five pound bag".

    Naming is hard, but it's not *that* hard.

    1. Re:Blivet? by m4rtink · · Score: 1

      So we're stuck with either "impossible object" or "ten pounds of shit in a five pound bag".

      Naming is hard, but it's not *that* hard.

      You don't have much experience with data storage management, do you ? It makes much more sense in context. :)

    2. Re:Blivet? by thePowerOfGrayskull · · Score: 1

      Touché.

  37. Is it part of systemd? by Anonymous Coward · · Score: 0

    I can see the benefits, we can repartion our hard drives at startup much faster.

  38. blivet-gui? what a terrible, terrible name [NT] by Anonymous Coward · · Score: 0

    blivet-gui? what a terrible, terrible name.

  39. blivet-gui by Anonymous Coward · · Score: 0

    "blivet-gui" seriously?

    With all the "search" facilities in distros to launch programs, how the hell is anyone supposed to remember that name when they want to partition something?

    Makes me sad.

  40. New partitioner by Wowsers · · Score: 1

    I don't know about needing a completely new partition manager, but certainly needs to read GPT partitions. In GParted, there is one disk I have just for Windows7, Windows partitioned it, but GParted reads the drive as unpartitioned / available. I asked around and people were thinking it was partitioned wrong that's why invisible.... well if Windows partitioned it's own partitions wrong....

    And please pick a better name than the proposed one, at least make the name pronouncable.

    --
    Take Nobody's Word For It.
  41. The best thing about partition managers is by koinu · · Score: 1

    when you don't need them.

  42. Re:Can you specify the exact start cylinder for a. by jones_supa · · Score: 1

    I think SSD partition alignment "just works" for all modern partitioning tools. It should be fine.

  43. Tried it - hard dependency on Fedora? by Anonymous Coward · · Score: 0

    The subject interests me, so I tried installing it. Got the gui from git, the blivet itself, then pykickstart, but it still won't go. Possibly needs a different version of pykickstart?? Not well documented. But yes, we do need GPT capabilities, and LUKS + LVM2. For those interested in a capable tool:
    linstaller https://github.com/semplice/linstaller (doesn't yet handle GPT though...).

    1. Re:Tried it - hard dependency on Fedora? by Anonymous Coward · · Score: 0

      Although the code linked to suggests linstaller does support GPT!
      (Hint for Redhat: it uses python and is GPL'ed..!)

    2. Re:Tried it - hard dependency on Fedora? by m4rtink · · Score: 1

      Um yes - and the two people mentioned in the Announcement have @redhat.com addresses. ;-)

  44. Re:Can you specify the exact start cylinder for a. by Anonymous Coward · · Score: 0

    This is a important question. When the partition tools jumped the shark and started using those 10^x units instead of 2^x, one can not be sure what is the actual alignment anymore. After all, a calculator is needed to verify were the partitions on proper alignment or not.

  45. Re:Can you specify the exact start cylinder for a. by Anonymous Coward · · Score: 0

    Automatic partitioning doesn't necessarily guarantee alignment, and the only way to properly align it is with a manager that allows you the specify the exact start cylinder.

    Bring in uefi (some partition managers can do it, others can) into the picture, and you have a case of WTF!

    For me, Win7, and Centos aligned the partitions properly, but (*)ubuntu didn't. Gparted doesn't show cylinders, fdisk can do exact cylinders but complained about uefi, and ended up using gdisk!

    All of this because hdparm -t was reporting 5x less expected results for the SSD!

  46. Re:Can you specify the exact start cylinder for a. by jones_supa · · Score: 1

    fdisk can do exact cylinders but complained about uefi

    You probably mean GPT. There seems to a tool called gptfdisk that solves the problem.

  47. Re:Can you specify the exact start cylinder for a. by jones_supa · · Score: 1

    When the partition tools jumped the shark and started using those 10^x units instead of 2^x, one can not be sure what is the actual alignment anymore.

    Today it is practically always 1MB (1,048,576 bytes).

  48. Why not add what's missing to existing tools? by bloodhawk · · Score: 1

    I am no partition manager expert, but if the existing most popular one is missing some features then why not implement them rather than producing yet another piece of software to fragment and complicate things. Are the existing ones that bad that they can't be improved?

  49. That's really odd by kilodelta · · Score: 1

    Because I have a USB stick with GParted boot on it that does EVERYTHING and includes HFS, HFS+, NTFS, FAT32, ext2, ext3 and ext4. I think XFS is even in there.

    1. Re: That's really odd by Anonymous Coward · · Score: 0

      ISCSI SAN ?
      ZFS ?
      Ceph ?
      AWS local ?

      The things missing aren't for partitioning a disk, but things for working with storage.

    2. Re:That's really odd by m4rtink · · Score: 1

      Can it also do LVM2, BTRFS, advanced RAID, network storage and encryption ?

  50. Uses Anaconda? by Anonymous Coward · · Score: 0

    Yeah I also had a quite negative experience with Anaconda, Fedora's installer. Since it has been redesigned, I consider it to be one of the worst OS installers I have ever encountered. There are a lot of bugs, that make you lose the changes you just made. Also the partition manager is not really useable anymore. You don't really get the overview of available storage etc.
    Heck even good ol' Debian does better and makes it easier to install.

    The problems with Anaconda are a pity, since apart of that Fedora is IMHO a good distribution.

  51. Too much, too soon by Anonymous Coward · · Score: 0

    This, systemd, what's next? Red Hat really does, in my estimation, want to control the overall direction of Linux. There's a real reason why Slackware and Gentoo are becoming more and more popular as time goes on.

  52. Classic Red Hat by Anonymous Coward · · Score: 0

    nuff said

  53. Re:Pottard will have this in systemd before weeks by m4rtink · · Score: 1

    Um, I don't think that is very likely:

    https://lists.fedoraproject.or...

  54. This is rumour control, here are the facts by AdamWill · · Score: 2

    Unfortunately, Mukt completely mis-reported this and Slashdot picked up their errors for the summary, which is making for a lot of confusion.

    tl;dr:

    1. blivet-gui isn't supposed to (and in fact cannot) 'replace' gparted in any reasonable sense of that term.
    2. blivet-gui is a new application, but its backend is the Fedora installer's storage management code, which is a very old codebase. There is no new storage management backend being written here.
    3. Lennart and systemd have nothing at all to do with this.
    4. It wouldn't really be practical to 'contribute' this to gparted, as it would involve completely ripping and replacing gparted's backend and then very rapidly proposing significant changes to the GUI, and hence would be a project takeover by any other name.
    5. blivet uses standard underlying tools for performing operations, it's just a logic/configuration layer for them.

    1: what the original announcement says is that blivet-gui uses a gparted-like UI to make it instantly familiar for gparted users. It doesn't say anything at all about it 'replacing' gparted. That's a pure invention (likely based on a misunderstanding) in the Mukt article. See the original announcement at https://lists.fedoraproject.or... to verify this, if you like. There's no sense in which blivet-gui really *could* "replace" gparted, if you think about it. gparted is an independent project; Red Hat doesn't own or maintain it, so Red Hat can't stop it existing or being maintained. gparted isn't a significant component for either RHEL or Fedora: it's just a leaf package, an app like any other. It's not like anaconda uses gparted as its partitioning tool, or anything like that. So talking about blivet-gui 'replacing' gparted doesn't make any sense, not upstream, not downstream. So long as upstream gparted devs see a need to keep developing gparted, gparted will continue to exist upstream, and so long as a Fedora packager wants gparted to be in Fedora, it'll be in Fedora, whether or not blivet-gui or any *other* storage management GUI app is also in Fedora. We have lots of space in the repos.

    2: the backend for blivet-gui is blivet: https://git.fedorahosted.org/g... (packaged in Fedora as python-blivet). This codebase is simply the storage management backend of anaconda (the Fedora installer) split out into its own repository. The split happened back in 2012: http://www.redhat.com/archives... . The intent was to allow for exactly this kind of code re-use. So there really isn't some kind of new NIH effort going on here: the storage management code is not new, all that's new is the light wrapper around blivet to produce a standalone GUI app rather than using it as a part of the anaconda installer. The underlying codebase has existed basically as long as anaconda has existed, which is rather longer than gparted has existed. anaconda dates back to 1999 (https://fedoraproject.org/wiki/History_of_Red_Hat_Linux ), gparted AFAICT dates back to 2004 (http://gparted.org/news.php?item=180 ).

    3: Doesn't really need expanding on, but no, there is absolutely zero link to Lennart, systemd, or any other systemd developers.

    4: so the reason to do blivet-gui at all, and the reason anaconda doesn't just call gparted for "partitioning" like ubiquity does, is it doesn't cover anywhere near the functionality we actually need for the Fedora (and, more to the point, RHEL) installer. gparted really is a *partitioning* tool, and there's a reason I keep referring to blivet as "storage management". It handles things that aren't just partitions. The most obvious examples are mdraid, LVM, and btrfs (insofar as btrfs acts as a volume management and redundancy system, not just as a simple filesystem like ext), but blivet has all sorts of other interesting capabilities too, primarily of interest t

  55. Fedora's Partitioning UI by Dekonega · · Score: 1

    I sincerely feel that Fedora's Partitioning UI is ABSOLUTELY HORRIBLE. It was the biggest *huh* and *ugh* when I installed Fedora 19 and 20. It made no sense what so ever. I remember using Anaconda like in early 2000 to install Red Hat 9 and Fedora Core something and that UI worked just fine. The new UI in my opinion only confuses users and is clearly tuned towards formatting everything the HDD might already have such as Windows NT based OS.

    OpenSuse has a reasonably good partitioning UI. YAST isn't the best thing out there but gets the job done. Ubuntu had the best one last time I checked. It actually told you everything you needed to know and expressed that with smart well designed visual cues. Ubuntu's partitioning UI isn't imho perfect and it could use an "advanced mode" but so far Ubiquity is the best I've seen around in Linux world. The best "advanced mode" ships with the Debian-installer as it allows some really wicked and truly flexible partitioning schemes to be made.

    1. Re:Fedora's Partitioning UI by AdamWill · · Score: 1

      If you look at a screenshot of blivet-gui, you'll see it doesn't use the same UI as anaconda.

  56. Where did all these greedy dev's come from anyways by Anonymous Coward · · Score: 0

    THIS! Because they are greedy and selfish and the idea comes from the devs who were layed off from their old school MS gigs writing software for big bucks. It doesn't take half a brain to see how much they care about open source. Fedora is just a rolling beta testing system. I wouldn't use it on anyone's production system if they needed stability. Pure Debian or go home.