Im sorry.My english is not so good and i dont understend you correctly.Well it works,it boot faster but i cant enable dhcpcd.
systemctl enable dhcpcdt@eth0 doenst work for me

1 members found this post helpful.

tuxbg

dhcpcd has not been build against systemd yet.
you can just set your /etc/rc.d/rc.inet1.conf to use dhcp

this works.

So here's my version of the 60,000 dollar question.

How is systemd's configuration going to be easier to use than the BSD/SysVInit script set we use that keeps configuration methods, troubleshooting, and managing files written in plain text English, as well as the logging system that performs the same way?

Are you going to create documentation within the configuration files used by systemd to have internal hints, samples, and other documentation about switches and arguments made against the daemons being used?

Will systemd have the ability to support custom daemons not normally added such as is done with rc.local's method of add-on daemons?

2 members found this post helpful.

ReaperX7: please read post #27 from ruario if not already done.

Can't you see that you are off topic there?

1 members found this post helpful.

guess what reaperX7, rc.local works

you can add anything in rc.local to start.

also custom daemon are possible yes.

this I have built into systemd file to have the slackware motd work directly

you can have anything start in such a service file.

I can confirm that this SystemD build works, and works great.

I tested your SystemD build a virtual machine under Slackware 14.1 installed clean.

The first criticism of this build ...

The problem is not only that SystemD replaces the classic BSD-init of Slackware, but at the same time this build PAMify the innocent operating system.

And PAM is not a small toy ... His claws get everywhere, including up to Apache ... It's like an octopus.

Also, PAM is the first thing that is looked hatred by the Slackware community, even before The {Th,K}ing (the man also called Mister Arrogance).

I wonder if it's possible a replacement of PAM with ConsoleKit, which would make your project more acceptable and less invasive.

Hi Darth Vader, yes it is possible.
you can remove the pam options from the systemd build
and just build systemd and dbus.
optional openssh with pam config removed.

however the reason for including pam is for the systemd-logind session manager.

pam can be still optional for alot of packages, you dont have to enable it.
also a simple config that works for all programs that you want to use pam, without having much trouble

DISCLAIMER: I consider systemd an unwelcome intrusion on my peaceful and contented Slackware space. So no real open mindedness here, but...

I have been following this and thought I might give it a try as an easy way of getting some actual systemd exposure, which I lack.

But PAM is a deal breaker in itself, non-starter, enabled or not. So do I correctly understand that PAM is a hard dependency of systemd?

1 members found this post helpful.

pam is a hard dependency for the systemd-logind part
so if you want to use the session manager of logind than yes.

I did not test it without pam on version 207 and 208
before these versions it was possible to use it without, and as far as I know it still can be used without.

Then looks like that that systemd-logind needs a shadow slapping, how happened with the ConsoleKit...

on the side note, shadow will need to be rebuild to support group size of 32 characters.
you can just use consolekit as it is.

slackware provides as good as most up to date version. slack ships 0.4.5
and latest is 0.4.6
not many improvements there tho.

How am I off-topic when I'm asking a simple question about one of the more important aspects of this feet? Configuration!

Obviously, since you guys are so hostile against any questions against or for the topic, why is it even open as a topic? The purpose is to ask questions and get informed, right? Maybe I'm losing my hostility towards systemd with a proper implementation if one can exist, but unless I, or for the matter, anyone, can even ask questions, we have to ask them.

So Didier, pipe down yourself and maybe you should take Ruario's words to mind rather than me. YOU tone it down sir!

And bartgymnast, I'm in no way against you doing this IF it can be done simply, non-invasively, and properly in how Slackware's overall design is, with adequate documentation, samples, and reliability overall. You don't need to keep up the rhetoric with the sarcastic comments either. Either be serious about this, or don't bother. And yes, excising out PAM would be a good idea. PAM isn't very friendly to use, and should be optional entirely even if hard required by logind. Other avenues can exist that work far less intrusively.

If you pull this off correctly, you'll gladly have my respect. However, I do advise you that you are being watched heavily in this matter so leave the sarcasm out please.

1 members found this post helpful.

ReaperX7 - Leaving aside your systemd questions since I haven't ever used systemd and therefore cannot answer them, I'm pretty sure bartgymnast is serious about this. bartgymnast's first language may not be English (though it's pretty good and easily understood), so what you detect as sarcasm may just be down to language differences. On the other hand you do seem to be a native English speaker, and telling someone that they "are being watched heavily" in the manner that you have is not really a nice thing to say.

bartgymnast - Interesting work, I may try it on a VM if I have time, it'll be interesting for me to see how it works and to find out what's different.

3 members found this post helpful.

Okay, then I'll put it a better way... people are paying attention, but with skepticism.

While most seem to have performed some pretty good peer moderation I'd like to ensure this thread stays on topic from here on. That means posts should be helpful for the OP and truly constructive or else cease posting in this thread.
Thanks in advance for cooperating.