Announcement

Collapse
No announcement yet.

Systemd-Free Debian "Devuan" Planning Their First Developer Gathering This Spring

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

  • Originally posted by arokh View Post
    You've deleted, modified or added something under /usr (which you said yourself, downloaded compiled and installed something manually).
    I said no such thing. I simply confirmed "Yes" when it asked me to remove libsystemd because it conflicted with systemd-libs. If I didn't, then the VM would be worthless anyway. Unless you refer to the first part, which I've simply overlaid squashfs + tmpfs on /usr and that worked fine until I had to unmount it, but that didn't brick anything though. Still systemd annoyance.

    Originally posted by arokh View Post
    You gave me the "fucking command" yes but you didn't give me the fucking result you got that you claim is because of systemd. It just shows that you understand completely nothing you mentally challenged chimp. Like I said, the command you gave works great on an Arch system that haven't been tampered with by monkeys.
    Like I said the command I gave leads to that conflict and I don't give a single fuck of what you say.

    I don't know the exact output because I don't want to redownload the iso just to satisfy a piece of shit like you. If you want it so much then YOU do it yourself and find out exactly what it is.

    Because clearly the fact I said about what happened (the libsystemd conflict) is not enough and you need copy-pasta, and I'm simply not going to waste my time on this because of you since clearly you'll just claim I "made it up" anyway, don't make me laugh.

    Originally posted by arokh View Post
    You certainly did something to cause the conflict, systemd has no such functions to mess with system files. Learn how to read and process information in your brain please.
    It's obviously a packager's problem. But it is with systemd. He messed up due to systemd. If there was no systemd, there would be no packaging problem. Really simple.

    Originally posted by arokh View Post
    I understand that you don't understand a single goddamn thing about how these things work and absolutely refuse to learn.

    You're forgetting that you're the noob that can't solve or identify the cause to a simple conflict. My Arch systems are all running great, I can install packages without issue.
    Omg just stfu with your stupid anecdotes, you think this is the first time I used such a VM? Are you fucking stupid? I've used them at least 10 times by now, the squashfs thing was like a year ago if not more.

    Sometimes I encounter such problems in the VM, doing the exact same things. In these cases, sometimes, IT IS ALWAYS A SYSTEMD-RELATED PROBLEM. Even if it's not the fault of systemd directly, it's still related to it.

    I don't believe in such coincidences.

    Originally posted by arokh View Post
    You mean you know that you would look like a complete fucking tool when I prove you wrong. You haven't provided any proof to your bullshit statement, there's not a single person on this planet gonna take your word for it that systemd caused a conflict in your filesystem.
    You haven't provided a single proof you fucking moron, all you provided ae anecdotes nobody gives a shit about.

    I told you already what conflict I got. I told you how to reproduce it exactly with which live iso as well. What kind of proof do you want? A copy pasted log? I can easily make that up just as well and I know you'll whine like a bitch if I did, claiming I made it up after I wasted time redownloading the thing again. Because that's how kids work, I'm all too familiar with it.

    Frankly I'm done with you since I simply don't give a shit of your opinion anymore. Bury your head in the sand some more.

    Comment


    • Originally posted by Weasel View Post
      I said no such thing. I simply confirmed "Yes" when it asked me to remove libsystemd because it conflicted with systemd-libs. If I didn't, then the VM would be worthless anyway.
      and that's the point - this was *not* a proper solution and pointed out a packaging problem you was not able to solve beause of no expierience with Arch - frankly, i wouldn't have known out of my mind on Arch too BUT as i understand package management in generel THAT would not happened

      IT WAS NOT A SYSTEMD ISSUE - PERIOD
      IT WAS A DISTRIBUTION ERROR HANDELED WRONG BY YOU

      Comment


      • Originally posted by Weasel View Post
        It's obviously a packager's problem. But it is with systemd. He messed up due to systemd. If there was no systemd, there would be no packaging problem. Really simple.
        shithead the same packager problem can be with every single important library and is not related to systemd at all
        when you are too dumb to operate a Linux system it's not systemd - it's the shit in your head

        Comment


        • Originally posted by Weasel View Post
          I told you already what conflict I got. I told you how to reproduce it exactly with which live iso as well. What kind of proof do you want?
          it's already proven that you did shit, it's that simple

          dealing with local packages is not always straight forwarded, dnf on fedora has similar issues with obsoletes/provides and "dnf upgrade *" from a local folder while having the same packages in a repo solves it pretty fine, on fedora iw ould either have used the online repos or installed "createrepo-c", run it against the folder with my local packages and use that local repo, problem solved, done hundrets of times

          but nobody right in his mind removes libsystemd, nss, openssl or something else half of the system is linked against

          Comment


          • For all the religious pro-systemd nutcases here:
            Free software, free choice. Some people decided not to embrace software they do not like. It's their free choice to make. Unless you like something forced down your throats same way, learn to cope with it.
            They are putting out efforts of their own to have and use software they like. Not forcing YOU to neither develop for their Devuan nor forcing you to use Devuan.
            Not your business to critizise, mock, or insult about - unless you dearly love to see somebody else abusing you in a similar way. What goes around, eventually comes around. In this thread, you are aggressing because some people decided to something you idelogically disagree with? What are you? Religious police?

            Now creep back into systemd threads and run amok there. This ain't systemd thread.

            Comment


            • Originally posted by Weasel View Post
              Sometimes I encounter such problems in the VM, doing the exact same things. In these cases, sometimes, IT IS ALWAYS A SYSTEMD-RELATED PROBLEM.
              "in this cases sometimes is always" - idiot :-)

              Comment


              • Originally posted by aht0 View Post
                For all the religious pro-systemd nutcases here:

                They are putting out efforts of their own to have and use software they like. Not forcing YOU to neither develop for their Devuan nor forcing you to use Devuan.
                Not your business to critizise, mock, or insult about - unless you dearly love to see somebody else abusing you in a similar way. What goes around, eventually comes around. In this thread, you are aggressing because some people decided to something you idelogically disagree with? What are you? Religious police?

                Now creep back into systemd threads and run amok there. This ain't systemd thread.
                problem is that you shitheads argue idelogically with "unix principles" from 30 years ago not realizing that following this logic we still would sit on tress, the "unix principles" are not some holy grail but was the best available 30 years (and more) ago - not more and not less

                i don't give a fuck about Devuan and it#s uses as long as they are not talking technical bullshit what you do all the time

                Comment


                • Part of the confusion with Arch Linux may be that /sbin, /bin, /lib are SYMLINKS (arrrgh!) to /usr/bin, lib etc. So if someone goes in /usr/lib thinking it's safe to delete libraries and fix it later (e.g. with a make install of something) they might delete something critical that used to be in /lib, for example.

                  With Arch, you have to behave yourself a little or you'll break it (it's also a rolling release etc.)

                  Comment


                  • Originally posted by Weasel View Post
                    I said no such thing. I simply confirmed "Yes" when it asked me to remove libsystemd because it conflicted with systemd-libs. If I didn't, then the VM would be worthless anyway. Unless you refer to the first part, which I've simply overlaid squashfs + tmpfs on /usr and that worked fine until I had to unmount it, but that didn't brick anything though. Still systemd annoyance.
                    AHAHAHAHA you attempted to remove systemd and it bricked your system? You must be the dumbest guy on the planet actually. Your parents should be fined.

                    Like I said the command I gave leads to that conflict and I don't give a single fuck of what you say.
                    Yes, you don't give a single fuck that you look like a total noob. Your command is similar to deltree c:\windows\system you monkey.

                    I don't know the exact output because I don't want to redownload the iso just to satisfy a piece of shit like you. If you want it so much then YOU do it yourself and find out exactly what it is.
                    Satisfy me? Don't get me wrong here my sweet fucknoob, I couldn't care less if you fix your problem. I'm not the one blasting systemd because I'm clueless and broke my OS.

                    I simply asked for the complete command and output, so we can all laugh at you when we see exactly what you did. But anyway you have explained it well enough, we have enough to laugh now

                    Because clearly the fact I said about what happened (the libsystemd conflict) is not enough and you need copy-pasta, and I'm simply not going to waste my time on this because of you since clearly you'll just claim I "made it up" anyway, don't make me laugh.
                    Don't worry, I got it and it's enough. You're a raging noob that much is obvious. Why are you acting like you aren't?

                    It's obviously a packager's problem. But it is with systemd. He messed up due to systemd. If there was no systemd, there would be no packaging problem. Really simple.
                    Removing systemd components and bricking your system is your problem and nobody elses. You're an idiot.

                    Omg just stfu with your stupid anecdotes, you think this is the first time I used such a VM? Are you fucking stupid? I've used them at least 10 times by now, the squashfs thing was like a year ago if not more.
                    I think this is your first time on a computer. Or you're a baboon.

                    Sometimes I encounter such problems in the VM, doing the exact same things. In these cases, sometimes, IT IS ALWAYS A SYSTEMD-RELATED PROBLEM. Even if it's not the fault of systemd directly, it's still related to it.
                    It's related to you having no fucking idea what you're doing and you are hellbent on not learning lmfao.

                    I don't believe in such coincidences.
                    Facts are hard to deal with when you're a complete retard.

                    You haven't provided a single proof you fucking moron, all you provided ae anecdotes nobody gives a shit about.
                    You're withholding the proof you idiot, I asked for it but you refused to give it. The proof of burden is on you fucktard.

                    I told you already what conflict I got. I told you how to reproduce it exactly with which live iso as well. What kind of proof do you want? A copy pasted log? I can easily make that up just as well and I know you'll whine like a bitch if I did, claiming I made it up after I wasted time redownloading the thing again. Because that's how kids work, I'm all too familiar with it.
                    See above, if it's removing systemd then you're still a retard.

                    Frankly I'm done with you since I simply don't give a shit of your opinion anymore. Bury your head in the sand some more.
                    Actually, it's not about my opinion. It's a fact that what you attempted to do makes you an idiot noob. Burying in sand is exactly what you're doing how does it feel to embarass yourself in front of the entire phoronix forum?

                    Comment


                    • Originally posted by Grogan View Post
                      Part of the confusion with Arch Linux may be that /sbin, /bin, /lib are SYMLINKS (arrrgh!) to /usr/bin, lib etc. So if someone goes in /usr/lib thinking it's safe to delete libraries and fix it later (e.g. with a make install of something) they might delete something critical that used to be in /lib, for example.
                      the opposite is true given that /bin/bash and /usr//bin/bash as example are both equal valid
                      Last edited by hreindl; 03-05-2019, 05:08 PM.

                      Comment

                      Working...
                      X