Originally posted by pgoetz
View Post
Announcement
Collapse
No announcement yet.
Systemd-Free Debian "Devuan" Planning Their First Developer Gathering This Spring
Collapse
X
-
Originally posted by starshipeleven View PostI have my doubts. Why you do stupid shit like mounting a ro overlay on /usr "to save space" when you don't even grasp the basics of the distro? You are asking for trouble.
Originally posted by starshipeleven View PostSeriously what the fuck.
I just told you that the library fuckup was done by the distro's package manager (or something else, more likely it was you doing stupid shit with /usr or other stuff you didn't tell), and you proceed to say you "don't care that it is systemd fault or not", then proceed to blame systemd for this issue again.
Are you seriously trying to channel debianxfce's spirit? Because that's right into his alley of mind-fuckery.
- Likes 1
Comment
-
Originally posted by debianxfce View PostUse systemd with the Amlogic S912 SOC and the android 3.19 kernel that has audio support. No go, systemd supports only newer kernels. No audio support in mainline kernels. http://linux-meson.com/doku.php
Systemd is developed for servers only and systemd developer idiots do not realize that Linux is used everywhere.
- Likes 4
Comment
-
Originally posted by Weasel View PostCan systemd just go fuck itself? I'm sick of it controlling everything and getting in my way. I've never had this kind of issues on any other VM without it. Just fuck off already.
Comment
-
Originally posted by Weasel View PostQ: "My system won't boot because systemd craps out, what do I do?"
A: "That's a problem with you, because you want to boot your PC, and systemd clearly doesn't want it, so it's your problem not systemd's, because it took control of your PC."
Comment
-
Originally posted by swagg_boi View PostI like systemd AND shell scripts.... I install my distro and then run my shell script to turn off the damn binary log files in /etc/systemd/journald.conf
Comment
-
Originally posted by Weasel View PostI'm not sure what this has to do with what I said. I did not want to even touch systemd or interact with it, but as I said, it keeps getting in my way.
Originally posted by Weasel View PostIn this case I just wanted to install some compilation components so I can test compile some stuff on latest Arch iso. Nothing really special. The package installation procedure gave me that conflict with systemd-libs and libsystemd so obviously it already got in my way. And then I opted to continue removing it because it was getting on my nerves and of course half the whole thing was bricked but not like I didn't mention this already.
To be specific: I had to remove it else I wouldn't have been able to install the damn packages I needed for compilation.
Comment
Comment