Systemd 227 Released: "Lots Of New Awesomeness"

[SystemCrasher]

Could you respond again in practice explaining how to do an #ifdef for features not available on other platforms?

Then such platforms either have to implement missing features or enjoy by crippled features of software, obviously. Or program author could just refuse to support platforms which are unable to meet minimum requirements. Any other sane options I miss?

Systemd developers should be portable, because.. why? *BSD isn't going to use something so low level while it is licensed as BSD. Also, it would be nice to get an actual response

If I remember, someone was even trying to port systemd to FreeBSD. But whatever, since BSDs were never giving a fuck to compatibility of their inits with anything else, it would be terminally wrong for them to complain about anything. And if they lack anything comparable to cgroups and namespaces, so they can't expose same api or "gate" expected API to comparable API they have, its not Linux fault either. They can implement either compatible interfaces or whatever they think is cool and try to patch stuff like they see it fits to get it on wheels. That's how it works. Yelling about "should" and "must" is futile and just not going to work at all. And systemd haters who failed to get this idea are nuts.

And yeah, whatever, but I enjoy, say, process watchdog API of systemd. It really useful in embedded Linux systems. Those dumass nuts who yell its not needed "should" go to hell, where they belong.

[unixfan2001]

Then such platforms either have to implement missing features or enjoy by crippled features of software, obviously. Or program author could just refuse to support platforms which are unable to meet minimum requirements. Any other sane options I miss?


If I remember, someone was even trying to port systemd to FreeBSD. But whatever, since BSDs were never giving a fuck to compatibility of their inits with anything else, it would be terminally wrong for them to complain about anything. And if they lack anything comparable to cgroups and namespaces, so they can't expose same api or "gate" expected API to comparable API they have, its not Linux fault either. They can implement either compatible interfaces or whatever they think is cool and try to patch stuff like they see it fits to get it on wheels. That's how it works. Yelling about "should" and "must" is futile and just not going to work at all. And systemd haters who failed to get this idea are nuts.

And yeah, whatever, but I enjoy, say, process watchdog API of systemd. It really useful in embedded Linux systems. Those dumass nuts who yell its not needed "should" go to hell, where they belong.

If they're using Sysvinit, there's no reason to go there. They already are in hell.

[pal666]

You'd be surprised how many programs have #ifdefs in their header files and in some low-level routines.

to be surprised by huge amount of shitty software one has to not use software at all. and of course not to look at sources. or at least not meet dumbasses like you everywhere.
some low-level routines below to low-level libraries. but that requires working brain to grasp

[nirvanix]

*uses ArchLinux, complains about editing configuration*

As the primary user (and probably the one who installed the OS), you are a system admin, whether you like it or not. If you aren't the admin, let the admin handle it.

As far as disabling it, see the man pages for systemd-journald.service, journald.conf, and the ArchLinux wiki for systemd. I'm pretty sure it's as simple as:
systemctl disable systemd-journald.service
systemctl stop systemd-journald.service
systemctl start <yourloggerhere>.service
systemctl enable <yourloggerhere>.service
(Edit: you may have to disable the associated socket files, too. method is the same)

systemd and company has lots of documentation, all of it in man pages and online. Use it.

So if you had an intellect you might surmise that I would attempt to read documentation and configure journald since I am an arch linux user. journald as it was delivered to my arch system 3 years ago overwhelmed the capabilities of my system, which should never have happened in the first place. Secondly, the documentation about config and the config parameters then were very different than now. I was unable to config journald to my liking back then and subsequently worked around it. You remind me so much of one of those blowhard "I know what's best for you and if you don't like it then it's your fault" types that are the poison of the linux community. That's why linux never gained wide acceptance over the fifteen years I've been using it until Google created android to give the users what they actually wanted and not what you thought was good for them.

[timtas]

to be surprised by huge amount of shitty software one has to not use software at all. and of course not to look at sources. or at least not meet dumbasses like you everywhere.
some low-level routines below to low-level libraries. but that requires working brain to grasp

Why don't you just fuck off?

[timtas]

Could you respond again in practice explaining how to do an #ifdef for features not available on other platforms? And what's the point exactly? Systemd developers should be portable, because.. why? *BSD isn't going to use something so low level while it is licensed as BSD. Also, it would be nice to get an actual response!

Well, sometimes features are not available and somtimes they work slightly different. I give you an easy example: Windows has no sleep(int seconds), but instead a Sleep(int milliseconds). So my header files defines:
#ifdef _WINDOWS_
#define sleep(x) Sleep(x*1000)
#endif

So now, in the main program I can always call sleep(int seconds).

If features are not available, you either have to implement them or simulate something. Now, I can't tell if that would be possible in systemd regarding cgroups, maybe not. But generally: write wrapper functions, call the cgroups stuff on linux in there and something appropriate on other platforms. I'd have to look at the actual source code of systemd to tell you how exactly i would do it, maybe it will prove quite tricky. And yes, there would be some performance penalty.
Does that answer your question.

I think one problem was that gnome started to depend unconditionally on systemd-logind, to which there was no alternative available, thus making Gnome unusable on non-systemd platforms. This has changed, as far as I know.

[timtas]

Now I know #ifdefs can't be avoided completely in the development of complex software and are generally preferred in cases of small platform differences. However, have you ever considered laying your code out more modularly?
Generally, it's considered good practice to put the platform specific stuff in separate headers.

Yes, that's what I do. The wrapped-up stuff is usually in one file.

[Ericg]

Why don't you just fuck off?

Cool it, timtas, quick and easy way to get yourself banned from the forums.

That also goes to anyone else who's lashing out in this thread, this one just caught my eye cause it was on the page I loaded to.

[Nobu]

Post in mod queue... long story short, I gave you a solution, which you asked for. If you don't like it, fine, that's not my problem.
Edit: Honestly, I don't feel I was that rude about it either (aside from the quip at the beginning). Could have just said RTFM. :/

[Luke_Wolf]

Cool it, timtas, quick and easy way to get yourself banned from the forums.

That also goes to anyone else who's lashing out in this thread, this one just caught my eye cause it was on the page I loaded to.

Dude... you've been around here long enough to know that's not how things work around here, otherwise pal666 and others would have been banned long ago for being aggressive and abrasive.

You can only get banned if you do one of the following things:
1). You post spam (and even that can take a long long time, see the guy who was posting "it's Qt")
2). You post porn or something otherwise NSFW
3). Someone pisses the community off enough that they pull out the pitchforks and petition Michael for several months to get him to ban them. (See Q, Funkstar, etc...)

Otherwise Michael doesn't care as more flamewars means longer threads which means more ad-views which means more money for him.