Announcement

Collapse
No announcement yet.

Lennart Poettering Talks Up His New Linux Vision That Involves Btrfs

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

  • Lennart Poettering Talks Up His New Linux Vision That Involves Btrfs

    Phoronix: Lennart Poettering Talks Up His New Linux Vision That Involves Btrfs

    Lennart Poettering of systemd and PulseAudio fame has published a lengthy blog post that shares his vision for how he wishes to change how Linux software systems are put together to address a wide variety of issues. The Btrfs file-system and systemd play big roles with his new vision...

    http://www.phoronix.com/vr.php?view=MTc3NzU

  • #2
    In first!

    Lennart Poettering threads are always interesting spectacles to behold...........

    Comment


    • #3
      Originally posted by phoronix View Post
      Phoronix: Lennart Poettering Talks Up His New Linux Vision That Involves Btrfs

      Lennart Poettering of systemd and PulseAudio fame has published a lengthy blog post that shares his vision for how he wishes to change how Linux software systems are put together to address a wide variety of issues. The Btrfs file-system and systemd play big roles with his new vision...

      http://www.phoronix.com/vr.php?view=MTc3NzU
      Why doesn't Lennart just build his own distro? It's quite a serious question and would resolve a lot of the bad blood around his work being not-so-warmly-received by users of current distros.

      Comment


      • #4
        OMG, a proposal for higher-level Linux features that finally involves a modern file system.
        If there is one thing I dislike about Linux (having used BeOS way back, btw), it is that while Linux has many fancy file systems, the feature set is mostly unused by higher-level tools as they are apparently designed to run on file systems from the 1980s.

        BeOS implemented something similar to what many people today know as Spotlight, Baloo, etc. directly on the file system: No extra caches or indexes. Under BeOS it way easy to tell an individual file that a particular app has to open it it was saved as extended attribute.

        If that proposal would come true, finally a new base line for file systems under Linux would be set and then such BeOS-ish features get implemented as well.

        Comment


        • #5
          i'm guessing anti lennart comitee now hates btrfs and we're at brink of comment flood where ppl ask "why does btrfs needs to be in kernel?". my chips is ready

          Originally posted by halfmanhalfamazing View Post
          Lennart Poettering threads are always interesting spectacles to behold...........

          ohhh, dear... this image is so awesome, maybe michael should use this to tag lennart topics.

          Comment


          • #6
            Originally posted by Akdor 1154 View Post
            Why doesn't Lennart just build his own distro? It's quite a serious question and would resolve a lot of the bad blood around his work being not-so-warmly-received by users of current distros.
            You apparently don't know that he works for Red Hat and therefore already builds his own distro.
            Nobody from Debian, Arch, Mageia, etc. has ever been forced to accept code from Red Hat. It's just that those other distributors would then have to work on such technology on their own instead of freeloading Red Hat code which is far more work and probably less fun than flaming on mailing lists.

            Comment


            • #7
              Originally posted by Awesomeness View Post
              You apparently don't know that he works for Red Hat and therefore already builds his own distro.
              Nobody from Debian, Arch, Mageia, etc. has ever been forced to accept code from Red Hat. It's just that those other distributors would then have to work on such technology on their own instead of freeloading Red Hat code which is far more work and probably less fun than flaming on mailing lists.
              Debian does not contribute? Debian has shitload of contributors that do pretty awesome work. you probably mean Canonical?

              Comment


              • #8
                inb4 btrfs becomes the required linux filesystem.

                want dbus? you need btrfs!

                Comment


                • #9
                  Metastasis... the development of secondary malignant growths at a distance from a primary site of cancer...

                  Comment


                  • #10
                    Originally posted by justmy2cents View Post
                    Debian does not contribute? Debian has shitload of contributors that do pretty awesome work. you probably mean Canonical?
                    No, I meant Debian. Despite all the flaming during the systemd migration debate, NOBODY stood up and announced an alternative project, not even a prototype. Debian was discussing whether to migrate to Red Hat technology (systemd) or to Canonical technology (upstart).

                    The Gentoo devs are not afraid to tackle such tasks (hence OpenRC) but Debian is just a huge crowd of crybabies.

                    Comment


                    • #11
                      Haven't read the whole post yet but did a search for "atomic" and didn't get the hit I was looking for.
                      https://fedoraproject.org/wiki/Chang...ic_Cloud_Image

                      Amazed he's not aware of Colin's work in this area. This too is part of f.N, and is going to represent a massive leap forward in linux stability/usability.

                      Comment


                      • #12
                        Originally posted by johnc View Post
                        inb4 btrfs becomes the required linux filesystem.

                        want dbus? you need btrfs!

                        Disclaimer: I use and love btrfs and Lennart is my personal hero after Linus and Greg.

                        I can't wait for that to also follow into floods of support threads from casual users on 64gb ssds that cant seem free up space on their drive

                        Comment


                        • #13
                          [quote=Lennart and his fellow systemd core developers have been devising a new way to tackle these challenges to come up with an efficient way to allow vendors to package their software for end-users, allow end-users/administrators to install packages regardless of the distribution at play, a unified solution to cover everything, [/quote]

                          Good luck trying to unify all the differences between every single distribution on the planet.

                          Especially those like

                          - *-dev vs *-devel
                          - /lib32 + /lib (pre-multiarch Debian-based, Gentoo and Arch) vs /lib/<arch> (Debian-based multiarch) vs /lib + /lib64 (rpm-based)
                          - different distributions installing certain packages in different locations (at one point OpenSUSE installs KDE into /opt, not sure if they do this now)
                          - different naming conventions, especially for libraries (e.g.: Mageia / Mandriva uses libfoo and lib64foo, Fedora uses libfoo and libfoo.i686, OpenSUSE uses libfoo and libfoo-32bit)

                          Comment


                          • #14
                            This sounds interesting, worthwhile even. I don't trust that particular group of developers not to make it an overly complicated, incompatible mess though. We'll see.

                            Comment


                            • #15
                              Originally posted by Sonadow View Post
                              Good luck trying to unify all the differences between every single distribution on the planet.
                              Then they stop the madness and become Fedora and CentOS remixes.

                              Comment

                              Working...
                              X