SoylentNews is people
SoylentNews
A developer affiliated with boycottsystemd.org has announced and released a fork of systemd, sardonically named uselessd.
The gist of it:
uselessd (the useless daemon, or the daemon that uses less... depending on your viewpoint) is a project which aims to reduce systemd to a base initd, process supervisor and transactional dependency system, while minimizing intrusiveness and isolationism. Basically, it’s systemd with the superfluous stuff cut out, a (relatively) coherent idea of what it wants to be, support for non-glibc platforms and an approach that aims to minimize complicated design.
uselessd is still in its early stages and it is not recommended for regular use or system integration, but nonetheless, below is what we have thus far.
They then go on to tout being able to compile on libc implementations besides glibc, stripping out unnecessary daemons and unit classes, working without udev or the journal, replacing systemd-fsck with a service file, and early work on a FreeBSD port (though not yet running).
Responses from the wider Linux community are yet to be heard.
(Score: 0) by Anonymous Coward on Sunday September 21 2014, @08:37AM
"there isnt a single, coherent, provable point that there is a problem with systemd"
Really? That's just the biggest load of bullshit. Even if systemd was the god you are potraying it to be, there for sure are problems with it. Even if i don't know too much about it, in my view systemd seems like emacs, an OS on it's own stuffed in one package, or EU. When you say things like the quote above, or never or always, i don't even care to really read the rest.
(Score: 1) by chris.alex.thomas on Sunday September 21 2014, @10:44AM
just because you pedantically took the meaning of "problem" and ran off with it doesn't change the point I was trying to make, which is, that all the so called problems that people have said systemd has, are just bullshit, they arent true and they are just whingebags who don't like change, probably they hate wayland as well.....
you knew exactly what I meant and if you didn't, perhaps you should think a little harder about what people are saying before you "prematurely optimise" your understanding of a conversation.
(Score: 3, Funny) by VLM on Sunday September 21 2014, @01:04PM
"probably they hate wayland as well."
Accusing them of having good taste does not exactly help your argument.
(Score: 2) by digitalaudiorock on Sunday September 21 2014, @01:39PM
"probably they hate Windows as well."
...fixed that for him. ;)
(Score: 0) by Anonymous Coward on Sunday September 21 2014, @04:29PM
Well with problem i mean design problems, concept problems, not some bugs, and i personally am not so sure that there aren't bad ones with systemd, unlike you seem to be.
"probably they hate wayland as well....."
Nice one. What is your problem? Do you think this somehow helps making your points? You seem to be very, very emotional about this. I like wayland, but am leaning towards not liking systemd due to the complexity of it. Same reason i like wayland over all that stuff that X has gathered over the years, including problems, which can't really be fixed due to the complexity of it all.
(Score: 1) by gcrumb on Monday September 22 2014, @03:23AM
[A]ll the so called problems that people have said systemd has, are just bullshit, they arent true and they are just whingebags who don't like change....
What the fuckety fuck fuck?!?
If 99.992% of all the complaints about systemd weren't valid, if everything everyone ever said was exaggeration, if systemd was the greatest thing ever committed to ones and zeros, if systemd solved the halting problem, filled knapsacks perfectly everytime, set every traveling salesman's itinerary ever, turned P into NP in an instant....
... We would still be right to bitch about the fact that it's usurping its place in Linux, that it should never have been moved into place until it had achieved years of exposure to real-world conditions and consensus among the technical community, that there is not, and never has been, a compelling argument for designing it in such a way as to make it unavoidable if you use Linux.
Ignoring the compendious technical arguments against the design and its implementation, ignoring the arrogance of youth that thinks it knows better than us fucking 'whingebags' who were admining systems while you were still (literally, in some cases) in fucking diapers... ignoring all of that, systemd's developers still have no right to tromp all over a usable system the way they have.
The whole line of argument that begins, '... but the kernel ...' deserves the same response another sycophantic little shit got back when he thought he was smarter than his opponent: Systemd, I know the kernel. I work with the kernel. You're not the fucking kernel. You're nothing like as useful or important. So get off your high fucking horse and listen to us fucking whingebags who know when change is a Good Thing, and when it's an exercise in folly.
Crumb's Corollary: Never bring a knife to a bunfight
(Score: 3, Insightful) by digitalaudiorock on Sunday September 21 2014, @01:24PM
Bingo. systemd's core swiss-army-knife-do-everything-whether-you-want-it-or-not design, where none of it's bloated features are modular is the problem. I'd say that's provable.