Originally posted by L_A_G
View Post
Announcement
Collapse
No announcement yet.
Systemd-Free Debian "Devuan" Planning Their First Developer Gathering This Spring
Collapse
X
-
Originally posted by Weasel View PostDelete what?
I gave you the fucking command which packages to install.
I didn't delete anything until systemd had a piece of shit conflict, you fucking retard. I don't care what happened after the conflict, THE CONFLICT ITSELF WAS DUE TO SYSTEMD.
You understand the simple fact that if I did not install those packages, I might as well just nuke the entire VM as it would be completely worthless, right? As if bricking it would be any worse. The entire PURPOSE of that VM with the live Arch iso was to install those packages and bricking it wouldn't be any worse than not installing them at all. Dumb fuck.
And of course you don't even know that, since you're a noob trash at Arch.
I'm not going to redownload the iso just to satisfy a retard who can't do it by himself.
Actually it shows you know how to mumbo jumbo techno babble just like hreindl and don't even know how to do offline installation of packages. Lol.
Comment
-
Originally posted by pal666 View PostA little bit of advice: by spelling something else you are barking at something else
Originally posted by lucrus View PostNot only I'm perfectly fine with it, I'm even happy they meet in Amsterdam. In fact, if they didn't, I couldn't laugh out loud to the level I do now.
I'm not moaning, I just notice that they are not quiet like you pretend they are.Last edited by L_A_G; 05 March 2019, 07:35 AM.
Comment
-
Originally posted by arokh View PostYou've deleted, modified or added something under /usr (which you said yourself, downloaded compiled and installed something manually).
Originally posted by arokh View PostYou 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.
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 PostYou 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.
Originally posted by arokh View PostI 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.
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 PostYou 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.
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
-
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.
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.
- Likes 2
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.)
- Likes 1
Comment
-
Originally posted by Weasel View PostI 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.
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.
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.
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.
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.
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.
- Likes 1
Comment
Comment