Repository question and eudev/libeudev/openrc

Forum Forums New users New Users and General Questions Repository question and eudev/libeudev/openrc

  • This topic has 12 replies, 4 voices, and was last updated Feb 18-1:31 pm by Anonymous.
Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • #6591
    Member
    fungalnet

      I’ve only been on antix for a few hours and I am already running on testing. I always think I owe it to the distribution to test and help the stabilization process. I am not sure I have the repos right.
      Pretty much I followed the scheme, disabled the stable/stretch repositories, enabled testing for antix and debian (2 main and security, right?). I did a complete dist-upgrade and added my stuff (openbox and tools). There are some things that are missing though and I can’t imagine they have systemd dependencies, so I am wondering if I am missing something. Simple pkgs like gksu/gksudo don’t exist.
      On antix repositories, must I enable antix/sid in addition to testing?

      Also it is telling me now that I can upgrade to libeudev, should I do eudev completely and throw out udev?

      Is openrc working out of the box or does it need manual configuration? What happens in the transition when sysv-rc is removed?

      #6592
      Member
      fungalnet
        Helpful
        Up
        0
        ::

        Also the intel-microcode 20180108 has been recalled by Intel and it is causing more damage than it is helping, in terms of the meltdown and/or spectre. Linus had a fit cursing out the intel engineers. Debian withdrew it and reverted to the older 20170711?? microcode. Is the one in the repository the later or the older one named as the newer one?

        #6597
        Moderator
        caprea
          Helpful
          Up
          0
          ::

          Indeed gksu doesnt exist in testing
          https://packages.debian.org/de/stretch/gksu
          But its the same version in stable and sid.

          You dont have to enable sid-repo for testing on antix.
          Maybe you could do it for one time to install gksu.
          On my installation gksu is installed by default.

          $ apt-cache policy gksu
          gksu:
            Installiert:           2.0.2-9+b1
            Installationskandidat: 2.0.2-9+b1
            Versionstabelle:
           *** 2.0.2-9+b1 100
                  100 /var/lib/dpkg/status
          

          This is my repo for testing, I think (hope) its correct

          $ inxi -r
          Repos:     Active apt sources in file: /etc/apt/sources.list.d/antix.list
                     deb http://repo.antixlinux.com/testing/ testing nosystemd main
                     Active apt sources in file: /etc/apt/sources.list.d/debian.list
                     deb http://ftp.de.debian.org/debian/ testing non-free contrib main
                     deb http://security.debian.org/ testing/updates non-free contrib main
          
          #6607
          Moderator
          caprea
            Helpful
            Up
            0
            ::

            intel-microcode testing

            https://packages.debian.org/buster/intel-microcode

            #6609
            Anonymous
              Helpful
              Up
              0
              ::

              Is openrc working out of the box or does it need manual configuration? What happens in the transition when sysv-rc is removed?
              Dear adventurous one, try it out and let it know how it goes, eh?

              =======================
              A repost, in case you haven’t returned to the topic page and noticed what “francesco” (not one of my pseudonyms, btw) replied

              I hope that the openrc movements shall be able to consolidate; the basis are all there. The only negative aspect that I see, is that there is a too high segmentation in the openrc movements while, in this moment, should be important to concentrate the efforts.
              Maybe that I’m wrong, the segmentation is one of the main advantage of Linux, I hope that it will be also for openrc.

              meh.
              Scritch, scritch… I haven’t noticed any “problems needing solved” regarding sysV.

              #6610
              Anonymous
                Helpful
                Up
                0
                ::

                Indeed gksu doesnt exist in testing
                https://packages.debian.org/de/stretch/gksu
                But its the same version in stable and sid.

                Well THIS is certainly a wake-up call for me.
                Although I realized “upstream” (guh-nome) had declared gksu as deprecated,
                until I checked just now, wasn’t aware that DebHat has deemed gksu: Unsuitable for release in buster

                antiX will need to host gksu from own repository.

                Also, in the near-term DebHat roadmap, consolekit will be on the chopping block.

                #6611
                Anonymous
                  Helpful
                  Up
                  0
                  ::

                  Also the intel-microcode 20180108 has been recalled by Intel and it is causing more damage than it is helping

                  You are dog-on-a-bone regarding the “microcode issue(s)”, eh?
                  artixlinux.org forum::Topic: Intel-microcode 01082018 WARNING
                  Yes! and have you yet seen this? —v
                  (Feb14,2018) “Hate to ruin your day, but… Boffins cook up fresh Meltdown, Spectre CPU design flaw exploits”

                  #6618
                  Member
                  fungalnet
                    Helpful
                    Up
                    0
                    ::

                    I like it 🙂 More patches for linux, no hope for other systems 🙂

                    WTF is wrong with Intel garbage patches? https://sysdfree.wordpress.com/173/

                    I wonder if the conditions are right for open-source free hw architecture to be financed and be mass produced. I thought there was at least one Berkeley group working on such a design.

                    Otherwise we can only expect such a miracle from Chiapas or Rojava.

                    #6621
                    Anonymous
                      Helpful
                      Up
                      0
                      ::

                      antiX will need to host gksu from own repository.

                      followup:

                      Behold the the Debian GNOME team “embrace, extend, extinguish” strategy at work.

                      https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887878
                      21 Jan, 2018

                      For the next major stable release of Debian (codenamed Buster), the Debian GNOME team plans to default to GNOME on Wayland where gksu does not even work.
                      gksu is unmaintained (last upload 2014) and is a security vulnerability.

                      Therefore, gksu has been removed from Debian Testing and will be removed from Unstable soon.

                      In earnest, I searched bug reports, but cannot find the reputed “security vulnerability”.
                      Sarcastically: the marked-as-Important bug “gksu: locking mouse/keyboard not enough to protect against keylogging” should be marked-as “Well, Duh!”

                      Related reading (sez me):
                      reddit topic (currently 52 comments): “Deb packages are not getting upstream to Debian”
                      and
                      Distribution packages considered insecure | Hacker News {——– statuscode.ch blogpost: “Distribution packages considered insecure”

                      #6622
                      Anonymous
                        Helpful
                        Up
                        0
                        ::

                        Hello Fungalnet,
                        I think it is because according to Boffins this dates all the way
                        back to design in the pipeline of the cpu. That means that
                        every cpu since the K5 and the Pentium 1 are vulnerable. I think a new
                        architecture with security in mind is the only sure cure, not just a
                        couple of software bandages.
                        Thx Skidoo for the link it was an eye opening on how deep the problem goes,
                        and how far back in design open-source hw would have go.
                        This also uses the parralel units (branch/dynamic/speculative) execution
                        in ways nobody gave much thought to or anticipated.

                        PS. should the cpu discussion be moved to a new topic somewhere else….
                        maybe meltdown/spectre or new one?

                        #6626
                        Anonymous
                          #6718
                          Member
                          fungalnet
                            Helpful
                            Up
                            0
                            ::

                            Novenna may be good, I didn’t know about it.
                            But consider this:
                            Let’s say we are in a cage, like in the zoo, and we are designing and building hangliders? What good are they?
                            You can’t built freedom tools in captivity. 🙂

                            #6720
                            Anonymous
                              Helpful
                              Up
                              0
                              ::

                              Let’s say we are in a cage, like in the zoo, and we are designing and building hangliders?

                              ???
                              figosdev with a shiny-new-for-2018 moniker, or what?

                              birdcage analogies and politics/idealism stuff should be posted in “Kafeino” subforum

                              (yeah, admittedly some of my posts within the long-running “Web Browsers” topic are edgy)

                            Viewing 13 posts - 1 through 13 (of 13 total)
                            • You must be logged in to reply to this topic.