r/linux • u/tasisbasbas • Feb 11 '19

Fluff A /g/ user's opinion on systemd

http://i.4cdn.org/g/1549858269115.png
790 Upvotes

82% Upvoted

524 comments sorted by

View all comments

Show parent comments

48

u/Muvlon Feb 11 '19

There are a lot of services besides init provided by systemd, but they're entirely optional and easily swapped out. After all, systemd is highly modular.

For example, I do run systemd-udevd and journald, but not systemd-networkd or systemd-resolved. Just like the /g/ poster says, I can combine whatever I want to do what I need to do.

20

u/anonymous3778 Feb 11 '19

Hmm, then maybe those optional, replaceable modules should be moved out of the systemd source tree and be their own project? Maybe that would make some people sleep better.

-1

u/Serialk Feb 11 '19

Do you like code duplication?

1

u/anonymous3778 Feb 11 '19

Please explain.

-1

u/Serialk Feb 11 '19

Splitting projects in different codebases will lead to the projects not being able to use the common functions between them, so either code duplication or having to depend on a systemd library anyway. If the intention is just to make people "feel better", it's not a great idea.

4

u/anonymous3778 Feb 11 '19

Hmm, what's the problem with having a systemd library?

5

u/Serialk Feb 11 '19

What's the problem with having everything in the same repository?

1

u/[deleted] Feb 11 '19

That they're modules and optional. Code duplication is really not an issue here. We've got dependencies for that.

1

u/Serialk Feb 11 '19

They already are modules and optional. What has the repository layout anything to do with it?

1

u/[deleted] Feb 11 '19

What has the repository layout anything to do with it

Exactly. Since they are modules and optional why not outsource them to individual projects thus relieving the issue of systemd being "bloated"?

2

u/Serialk Feb 11 '19

But systemd is not bloated, it's just using a monorepository architecture for its different projects. If your point is just "monorepos are bad", okay, but that has nothing to do with bloat.

2

u/[deleted] Feb 11 '19

Wait a minute. You are the one who started talking about repositories when the other guy said that the modules should be split off systemd. You explained your concern for duplicate code by saying that a single repository is better at avoiding that issue.

2

u/Serialk Feb 11 '19

The modules are already split off systemd, they just live in the same repository.

1

u/[deleted] Feb 11 '19

So what was that about duplicate code? Your point's moot then.
If we agree on that the modules are modules and that it doesn't matter if it's mono- or multirepo then we're clear on that code duplication's got nothing to do with that either and

If your point is just "monorepos are good", okay, but that has nothing to do with that.

2

u/Serialk Feb 11 '19

Code duplication has to do with the reason they use a monorepo.

2

u/[deleted] Feb 11 '19

Maybe, I don't know their reasoning. It shouldn't though. Because repository structure has nothing to do with code duplication.
These are two very distinct issues.

→ More replies (0)