as an old slacker i agree with those that dont want systemd, you cant just build a drop-in replacement of the init system, its like the launch codes on an ICBM multi-warhead nuclear missile = not something to be meddling with if you want it to all work properly

4 members found this post helpful.

I just want to test it.Why so much hate ?

5 members found this post helpful.

As far as I know, the separate /usr issue exists right now, even with the glorious and so orthodox udev. This is the price payed to have a super-cool auto-configuration, but having apps or libraries as dependencies in /usr...

That's why most of us we need a properly initrd to boot our super nice auto-configured (and so encrypted?) operating system.

To be honest, even I believe too that the page author is a rare piece of arrogance, still I do not see nothing wrong in that page...

tuxbg,

the error after using your login name is because of the file /etc/login.defs
you will need the one supplied with the package.

most likely it is still /etc/login.defs.new

I updated the build script to make sure it is not .new, people can change the options later as needed.

i think that would work better with an other linux than slackware at the moment..

You are funny guy

Yes it was my mistake.I override /etc/login.defs and now all things works

Then, you do not have now any "separate /usr" problems?

No i dont have "any" login problems

good to hear tuxbg,

the next package on my list to do this weekend is util-linux.
this package is linked against libudev.so.0, but systemd/udev since v187 (if not mistaken) is using libudev.so.1

As you see in the systemd.slackbuild it uses currently the ugly hack of linking libudev.so.0 to libudev.so.1
That should at the end not be needed anymore.

If you came across things that might seem to be a problem, do not hesitate to write it here. or send to my mail

1 members found this post helpful.

Long story short, the SystemD works in your system as expected and you consider that, as replacement (now!) of the orthodox BSD-like init of Slackware, it works equal or even better?

Now, see, most days I don't mind systemd too much, but then they have things like this:

And I think - why not just mount the stuff on fstab first? And who wants to run this stuff before filesystems come up? hplip? Really? Is it a problem that their core init program is linked to all this stuff, and this stuff is on /usr? How about not making the init linked to all this and, after processing fstab, start the bigger part of systemd? Seems easier than changing a 40-something-year-old concept.

But then I read this, and I get it. The word 'Solaris' appears 12 times. Compatibility to other Unixes/Linuxes translates to Solaris. Upstream is Solaris. Despite our closer cousins in BSD, they don't get mentioned once. It's an enterprise move so that Oracle doesn't need to try so hard to port our software.

In the end, if the technical reasons don't make sense, it's because they're made after the fact - it's really about the politics.

But now I'm being mean. I still want to see good stuff come out of these SlackBuilds!

EDIT: Heh, we were still on page 2 when I started that... whoops...

I just wont to test it.What's the problem?Why everybody judge me?

tux, darth-vader wanted to have your opinion.

he wants to know if it works better, the same or worse than before

I do not judge you, my friend! I just ask you if SystemD works fine as replacement of Slackware BSD-Init, which is really it, in our case...