Yes, it's back in the news on /. and probably elsewhere. Is it too early to worry about whether Pat and the gang will be forced to migrate to it or not? I'm not trying to init flamebait, I'm just worried...

One dweeb was opining that "Let's just wait a year or two. By then all the hotheads that are running for the BSDs now will be back, everybody will be using systemd (including gentoo and slackware) since it clearly is the best approach available right now."

Which is why I never read effing slashdot.

4 members found this post helpful.

You mentioned systemd. You just initialized flamebait.

I don't worry about what software will be added to Slackware. I've used Slackware for 10 years and Mr. Volkerding has never failed to deliver an outstanding release.
Things are good, mate.

13 members found this post helpful.

I'm 100% sure that Pat doesn't know yet.

1 members found this post helpful.

Without disagreeing with that vote of confidence, I still see good reason to worry. This thing is (deliberately?) written so that people developing software on machines that use it will, barring special awareness and effort on their part, naturally start assuming and requiring it. Software that once worked fine on any *nix suddenly becomes only usable on selected (deviant) linuces. It's step 2 of the classic Microsoft business plan.

It's similar to PAM. It's a steaming pile I for one want nothing to do with. The only time I care about it is when I need to use something that requires it. But when that happens, it's a very big deal. Compromise your own system? Set up another machine just for this one task, and compromise it?

Sure all you have to do for now is be smart enough to use Slack, but what happens down the road after enough critical upstreams become compromised?

7 members found this post helpful.

You just don't know anymore what is an opinion of a single person and what is a paid PR campaign camouflaged as "user generated content". Sometimes you see the same statements copied and pasted to different sites under different accounts, then it is obvious. But in general you should not trust social media.

3 members found this post helpful.

Out of curiosity (and because I wasn't in a mood of making anything useful at that time) just yesterday I made a package for Slackware-14.0 of eudev-1.6, the dirtiest and laziest way you can think of, i.e. replacing the udev-182 tarball with the eudev-1.6 one inside a copy of the /source/a/udev directory, making a few edits so that the SlackBuild can run without errors (commenting out the patches, mostly), and running upgradepkg to install the new package. As first reboot NetworkManager and X complained of a missing shared object, so I made a symlink to fake them (I should be granted of my consistency in making things the dirty way :-).

I'm sure not everything works (I saw some missing files in /dev and got back the audible bell, for instance), but so far I had no major issue in starting the system and using it with Fluxbox.

Still just out of curiosity I 'll have a closer look to the differences with udev-182 in the coming days, as at least that could help Gentoo developers in case they didn't receive reports from someone trying it with Slackware's init system yet.

6 members found this post helpful.

This project has been accepted into GSoC 2014:

https://www.google-melange.com/gsoc/...39274879778816
http://www.openbsdfoundation.org/gsoc2014.html#systemd

Could be interesting for unix-like non-CoreOS Linux, too...

4 members found this post helpful.

No GNU/Linux is forced to use systemd. There are plenty of options like eudev for udev purposes and alternative init solutions like Runit, s6, OpenRC, etc, and there's even the rough choice of using DevFS rather than udev.

Systemd is a choice only because it's a mainstream, funded, and big brand project, but it's not the ONLY choice as many would have you believe.

Eudev and Runit are being heavily experimented with on LFS and the Runit work is currently WIP status, but the results in the long term are going to be fully portable to any system. Eudev is complete and fully port ready to any Linux distribution.

Both of these projects are non-funded small resource projects being ported by users who have made a choice to take back our systems and promote choice. Our code and published porting hint guides are free and available to all.

1 members found this post helpful.

Well I'm just in a happy mood today, don't take any offense. But..

-- picture deleted ---

regards.

3 members found this post helpful.

I don't know systemd like some of you guys appears to but I've a little question about systemd :

From what I've found on the Internet, systemd is also relevant because it's the only thing that offers a "proper" replacement for deprecated tools like PolKit.

You are free to correct me if I'm wrong.

I'm just a student trying to figure out what's happening therefore I'm not an expert of any kind.

I'm running Arch on a VM to see what's systemd like from an regular end user point of view.

So far, my only complain is that systemd renames your network interfaces into some weird and unintuitive names.

polkit/consolekit and the like are only needed for the freedesktop.org based desktop environments. Stick with a traditional UNIX/X11 environment and you don't need them either.

Sadly, the modern linux desktop is going "full retard", and everyone knows one should "never go full retard!"


Anyway, lets cross this bridge when we get to it.

1 members found this post helpful.

why do people believe that making something like an init system or udev or whatever is hard ?

To those tired of following the success or failure of systemd, Don't then. I have posted numerous times with negative things to note about it and I have to admit that for some reason I feel if I met Poettering I'd have to keep my hands in my pockets (or risk saying something like "ur taes oot") but I am not prejudiced against the system. If it is made to work well, even for some applications, so be it. It does seem that partly because of systemd CoreOS is capable of very rapid massive deployment and that is a big plus for Enterprise systems. So, I think continued discussion is a good thing. We don't have to use it, but we should stay informed.