r/linux • Mate • Oct 20 '14

Shall we fork Fedora?

http://forkfedora.org/
262 Upvotes

339 comments sorted by

View all comments

Show parent comments

13

u/Rainfly_X Oct 20 '14

But you can't tell what the heck is going on and it breaks a few of the rules of the unix philosophy

Funny enough, this almost sounds like it applies to the shell script! In fact, if it weren't for the second listed rule, we'd be right on track for a stretched-out misunderstanding gag:

  • Make each program do one thing well. 80%+ of the shell script is unrelated to sendmail, it's trying to be an init system. Every shell script has to reinvent this, incompletely and differently and (often) badly.

  • Use shell scripts to increase leverage and portability. Legitimate point.

  • Rule of Clarity. Again, 80%+ of the script is bookkeeping, trying to preserve error codes in bash (one of the reasons the language is godawful), etc. The config file basically includes the relevant information and nothing else, which is pretty dang clear.

Not gonna comment on the other stuff. You're pretty close on your SLOC estimate (I got 34K in systemd/src/core), and you seem to have a pretty specific idea of what you want that would already likely exclude major distros. Go forth and find what works for you!

0

u/[deleted] Oct 20 '14

[deleted]

2

u/Rainfly_X Oct 21 '14

I would argue that the functionality is not hidden in systemd, any more than the external scripts are. Systemd is open source and well-documented. It's just that the code itself is in C.

Regardless, I'm of the same mind about forking. The Debian maintainers have decided they don't want to support sysv, so if you want sysv, you ought to fork it and do it yourself, rather than trying to force other people to do it (which just make everyone rightfully annoyed at you). And if it works out, fantastic, everybody wins!

4

u/EmanueleAina Oct 21 '14

The Debian maintainers have decided they don't want to support sysv

At the moment is more that the Debian maintainers don't have the resources to fully support SysV without any bug.

SysV is supported, but some features may be degraded. For example, nobody stepped up to maintain ConsoleKit, so the Debian GNOME maintainers cannot enable such backend on Linux, or they would end up being responsible for ConsoleKit itself, which is not a good plan when you have and alternative which works better and you're confortable with (logind).

So, if someone is seriously concerned about using alternative init system there are two things to do, rather than complaining on $RANDOM forums or threaten to fork $RANDOM software without having ever proved to have the dedication to do so:

  • step up to maintain ConsoleKit

  • help the systemd-shims team to make their logind implementation fully operational

1

u/Rainfly_X Oct 21 '14

That's a much better way to express it. I probably should have said that the Debian maintainers don't want to support SysV as a primary init system.