Do you really compare this to the Devuan endeavor???

Seriously, that page is disgusting, the colors, the fonts, everything is so wrong. A plain white-and-black with Comic-Sans! would look 10 times better. The time it took them to make that web-page, they definitely had the time to at least make one with a look that at least do not wish you to pop up your eyes with a fork.

Devuan, seriously...

Hehe, no, unlike Mao, I actually mean it.

They probably could fork the core of Debian and then use build scripts to import more packages for Devuan, but that would effectively reduce the Devuan project to the size of Slackware, LFS, etc. smaller distributions, and then it would just be Debian derived.

Yes and no... Surely not something that requires "tons of deps"... As the init system must be "built" at early stage of a system bootstrap.

So we requires "early stages tools" which are mostly the C cross-compiler and some system libs (binutils and such)...

It ALWAYS A BAD IDEA to take something too high level for a bootstrap, this is the same kind of problem with systemd's goal: taking the admin for a grand-ma... The init system is NEVER for the grandma, so why willing it to be "userfriendly, integrated, unmmodular" (as you point it) ?

That we have some high level GUI tool to do the grandma config is alright.... Believing grandma will "bootstrap a system" is an insult to all dev/devops/sysadmins.

To get back to your point, so C is not a bad choice. A "high level language" is good, but that's what SHELL (CLI+script) are done for, to have "high level glue to processes"...

For my a good init system rely on SHELL and some 'modular' deamons/processes/whatever that might or might not be native binaries built, but relying on very few dependencies in it's "vanilla" setup, the rest being up to the admin - and if AFTER that, some daemons/tools/script are in higher level or domain specific language, that's ok, the system has been bootstrapped.

Cheers

Garry.

1 members found this post helpful.

I was about to write "Maintaining a distribution involves a series of skills like communication and marketing, good knowledge in webdesign, etc." but then I suddenly had to think about this and decided to shut up in the future.

3 members found this post helpful.

This is great.

Someone writing something like this is either: 1) incredibly naive, or, 2) a very experienced internet troll.

I must admit that, in terms of design, the Slackware website is my favourite distribution website. Simple, functional and computerish. Everyone else could, and should, learn from it.

6 members found this post helpful.

Well, they're not having to replicate all that work. Those thousands of developers' efforts are directly applicable to Devuan. Most packages and tools should just trivially port over. They didn't have to rewrite DAK, for instance; they're simply using it as-is to create/manage the base repo.

We'd better hope the Devuan effort is successful. The more demand generated for keeping packages' systemd dependencies optional, the better for Slackware too (assuming it remains systemd-unburdened). I do not pretend to know, but strongly suspect, that if Slackware ever adopts systemd, it will be because of the maintenance burden imposed by the need to remove hard systemd dependencies from must-have packages.

4 members found this post helpful.

I must be 1/9 veteran:

1 members found this post helpful.

Exactly.
They've just released pinning config for apt package manager and all their job can shrink to upload on packages.devuan.org systemd-affected packages only. If optional packages for sysvinit would exist in Jessie, they would only need take care for default metapackges to pick nonsystemd dependencies and that's it.

No extra meta package required, it already exists in Jessie.
Basically, they're asking money for a different wallpaper.

What annoys me most, is the involvement of two DD's (hello you back-stabbing ********).
I still call this elite-debian-fork-thingy a fraud, it will not add anything.

1 members found this post helpful.

It seemed ok to me, more readable than black on white, but im no expert, maybe you have better taste than i do.
I think they were more concerned with content than beauty. Geez i guess the medium really is the message.

1 members found this post helpful.

I'm sorry but you are simply wrong and underestimate things a bit. After a few minutes found hard dependency in gnome metapackage for systemd based gnome-logs for journald, instead of alternative gnome-system-log for syslog.
EDIT: or dbus, or policykit (I'd appreciate if anybody with current Jessie default install could list reverse dependencies for systemd and libsystemd packages. As fair as I know packages.debian.org does not have this feature.)

Its one of my favorite web pages