1. 19

This is a little thought I’m having about GNU/Linux actuality. Please, tell me I’m wrong.

  1.  

  2. 7

    I’m still annoyed because Void Linux seems to be the only one that jumped to LibreSSL.

    Alpine recently did as well.

    1. 4

      Indeed, that frustrates me too. I think this is one area where the 1 year support period is doing LibreSSL a major disservice - it makes it difficult for many distributions (and FreeBSD too) to adopt it.

      1. 3

        It is open source. Downstream projetcs can maintain it longer themselves if they want to. Long term maintenance is hard work no matter who is doing it.

        1. 2

          True. My perception (which may be wrong!) is that some downstream projects are wary of maintaining their own backports of security-related software patches after things like the infamous Debian OpenSSL RNG breakage.

          1. 2

            In that case they should simply track upstream versions or find trustworthy developers.

            1. 3

              Indeed, but tracking upstream LibreSSL alone is not really possible for 5 year-supported LTS releases (like FreeBSD major versions, Ubuntu LTS, RHEL, etc.).

              I’d be much more likely to trust upstream LibreSSL developers than other developers who are backporting patches to a multi-year old release…

      2. 3

        Great! Thanks for your comment. Will fix it.

        Also, it seems like Lunar Linux have the package in their repositories as an alternative

      3. 6

        For example, Slackware had some users just because it had BSD-style init scripts. But since they moved to systemd, they are like any other distribution but without dependencies handling.

        I was surprised to read that Slackware had moved to systemd, I had a quick google about and could see that 14.2 doesn’t have systemd and even up to the prerelease changelog do you have any more information about this at all?

        1. 7

          Oh! It seems I have a confusion about that. Sorry, it was my error. I’ll fix it.

          1. 2

            i guess they won’t be using systemd for a while, at least not for 14.2. i would be surprised if ever.

            what was introduced in 14.2 was pulseaudio as bluez decided to drop alsa support:

            Wed Jan 13 00:01:23 UTC 2016 Hey folks, happy new year! After upgrading to BlueZ 5 recently, everything seemed to be working great, but then it was pointed out that Bluetooth audio was no longer working. The reason was that the newer BlueZ branch had dropped ALSA support and now required PulseAudio. So with some trepidation, we began investigating adding PulseAudio to Slackware. Going back to BlueZ 4 wasn’t an option with various dependent projects either having dropped support for it, or considering doing so. After several iterations here refining the foundation packages and recompiling and tweaking other packages to use PulseAudio, it’s working well and you’ll likely not notice much of a change. But if you’re using Bluetooth audio, or needing to direct audio through HDMI, you’ll probably find it a lot easier to accomplish that. Best of all, we’re finally a modern, relevant Linux distro! ;-) Thanks to Mario Preksavec, Heinz Wiesinger, and Robby Workman for a lot of help and testing. Bug reports, complaints, and threats can go to me. Also, enjoy a shiny new LTS 4.4.0 kernel and consider this 14.2 beta 1.

            ftp://ftp.osuosl.org/pub/slackware/slackware64-14.2/ChangeLog.txt

          2. 4

            I wonder if you would find NixOS’s module system to be in support of your “system” goal. Simple changes like:

            {
              services.pcscd.enable = true; # turn on PC smart card daemon
              services.xserver.wacom.enable = true # turn on wacom tablet support for X
            }
            

            adjust your global system to support these features, meaning simply removing one of those lines from your configuration and rebuilding will completely and thoroughly undo the changes and remove them.

            EDIT 1: We do have a few packages which use LibreSSL instead of OpenSSL, but not many. However, with the way Nix does linking it is easy to slowly transition as packages add support, or even alter your local system to prefer libressl over openssl. In this way we don’t need to commit to such a sudden “jump” as you call it.

            EDIT 2: We aren’t a “flavor” of any other distro, NixOS has developed its own distro all on its own.

            1. 3

              Yeah! That’s a great thing! Will try it this weekend! Thanks for your response!

              1. 3

                Great! Come on by #nixos on Freenode, and we will help you get started.

                1. 2

                  Note that he didn’t say anything about systemd — NixOS does use systemd now, although it is good at not requiring you to touch systemd when you configure things.

              2. 5

                I’m guessing from your title that only the 3rd point matters, you say “the reason” and the other two don’t change anything. (On #1 you can ignore distros you don’t want and #2 you don’t care that it’s happening, you just don’t like bad decision-making.)

                I can’t tell you you’re wrong. Linux distros aren’t an integrated whole like the BSDs are and probably never will be. I would recommend looking at Ubuntu and Slackware because they are probably the closest to that idea, but it’s clear you already have and don’t want them.

                But I don’t know why you’d want to be told that you’re wrong. The BSDs are great, and if they fit the way you think about a system and want to work, it’s great that you’ve found the right tool for your job. Enjoy FreeBSD and don’t worry about Linux.

                1. 3

                  Hi! Thanks for your answer! You are kind of right with the first and second point, since I wrote them as a preparation for the third, which is my priority. Those points are just the things that started the change in my mind.

                  The first distribution I used was Ubuntu 10.04 and I liked it at that point. I’m not using *buntus / Debian-based mostly because I don’t like .deb packages.

                  About FreeBSD, I’m enjoying it! Except using wi-fi connection. Is not the first time I’m using it, but the first time using it as my only OS. Sorry for my english!

                2. 3

                  A peripheral commentary, not all distros are the same package manager. When I was new to Linux I installed a lot of distros just to see what they were about. It is true that even among fringe distros there are ones that are basically the same, eg. Sorcerer Linux and SourceMage. But there are more than enough different Distros. A particular standout case is GoboLinux, which eschews FHS for a every app in its own directory style. Also I agree that distributions feel mostly a kernel + some apps glued together because that is what they are. The only one I’ve tried that came close to feeling like an integrated product was Pardus.

                  I too don’t like the systemd direction. I should migrate to *BSD.

                  1. 1

                    What about Solus ? I don’t think I ever seen discussed here before.

                    I would say that Ikey is good benevolent dictator and develops and steers the project well. Also the advantage of having someone that cares so much and has very strong opinions (where have I seen this before? ;-) is that stuff gets done not by hype :-)