Announcement

Collapse
No announcement yet.

Libstorage-NG Landing Soon In openSUSE Tumbleweed For Improving The Installer

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

  • Libstorage-NG Landing Soon In openSUSE Tumbleweed For Improving The Installer

    Phoronix: Libstorage-NG Landing Soon In openSUSE Tumbleweed For Improving The Installer

    Users of the openSUSE rolling-release Linux distribution will soon find an improved installer thanks to Libstorage-NG landing soon and improvements to YaST...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Can't believe this bug is still not fixed: https://bugzilla.opensuse.org/show_bug.cgi?id=966870
    On every other user-friendly distribution the installer uses the maximun size for home as default size
    Maybe libstorage-ng will fix this.

    Comment


    • #3
      Originally posted by theghost View Post
      Can't believe this bug is still not fixed: https://bugzilla.opensuse.org/show_bug.cgi?id=966870
      On every other user-friendly distribution the installer uses the maximun size for home as default size
      Maybe libstorage-ng will fix this.
      why not add a comment to the bug and ask if libstorage-ng will fix it.

      Comment


      • #4
        Btrfs multi-device support, BCache SSD/HDD caching
        yissss!!!

        Comment


        • #5
          Originally posted by theghost View Post
          Can't believe this bug is still not fixed: https://bugzilla.opensuse.org/show_bug.cgi?id=966870
          On every other user-friendly distribution the installer uses the maximun size for home as default size
          Maybe libstorage-ng will fix this.
          It normaly does , this is just a spcific issue when you are running LUKS encrypted volumes. I have never run into it

          Comment


          • #6
            Reinventing the wheel as usual... Fedora already has blivet (https://github.com/storaged-project/blivet)

            Comment


            • #7
              Originally posted by theghost View Post
              Can't believe this bug is still not fixed: https://bugzilla.opensuse.org/show_bug.cgi?id=966870
              On every other user-friendly distribution the installer uses the maximun size for home as default size
              Maybe libstorage-ng will fix this.
              Default settings are not bugs. They are just default settings, and can obviously be changed quite easily by the user. If you set the default root partition size at 50GB for LUKS+LVM encrypted, then you would have bug reports claiming that the default was too large.

              Comment


              • #8
                why bother with btrfs?

                Comment


                • #9
                  Originally posted by szymon_g View Post
                  why bother with btrfs?
                  because it's cool.

                  Comment


                  • #10
                    Originally posted by andyprough View Post

                    Default settings are not bugs. They are just default settings, and can obviously be changed quite easily by the user. If you set the default root partition size at 50GB for LUKS+LVM encrypted, then you would have bug reports claiming that the default was too large.
                    Depends. I don't know if you used OpenSuse's installer before.
                    In this case it's a bug.
                    The installer offers an option where the installer automatically setups the partioning and an option where the user manually determines the partition layout.
                    As the first option is clearly for inexperienced users, that don't want to mess with manual partioninig, it would be good if /home uses the maximun available size of the hdd.
                    At the moment only a few gbs are used and the rest stays free. Yes, it only happens with LUKS but nevertheless it's a usability bug, as no one, who uses the automatic install option wants to resize /home after installation.
                    But what do I know. Maybe people like bad usability.

                    Comment

                    Working...
                    X