Page 3 of 3

Re: Options for Salix if Slackware is forced to switch init

Posted: 1. Jan 2017, 13:53
by colebaas
http://ewontfix.com/14/

In the same - above -, ~ comments section; Our Minix3-style OS + init.
1] Written in Assembly;
2] Full OS == 722kB (That's Kilobytes)

Boot timings - in fractions of a (1) second
--------------------------------------------------------
udev 0.17| * Starting udev ...
udev 0.18| [ ok ]
udev 0.18| * create a /dev/root symlink ...
udev 0.18| [ ok ]
udev 0.19| * Pop /dev with existing devices ...
udev 0.22| [ ok ]
udev 0.23| * Wait for uevents ...
udev 0.24| [ ok ]
hostname 0.30| * Set hostname to localhost ...
sysctl 0.30| * Configuring kernel parameters ...
loopback 0.30| * Bringing up network interface lo ...
hostname 0.31| [ ok ]
loopback 0.31|ip: either "lo" is duplicate
sysctl 0.31| [ ok ]
loopback 0.32| [ ok ]
fsck 0.32| * Checking local filesystems ...
fsck 0.32|/sbin/fsck.xfs ... file system.
fsck 0.33| [ ok ]
root 0.35| * Remount root filesystem read/write ...
root 0.36| [ ok ]
TOTAL boot time (into full featured, graphical DE!) == 0.39 seconds.

You wanted fast, right?!...
Happy New Year!

Re: Options for Salix if Slackware is forced to switch init

Posted: 1. Jan 2017, 20:14
by DidierSpaier
Some of us have read this article long ago and it seems me that we are beating a dead horse posting again in this thread. Considering that:
  • Whether Slackware will adopt systemd in (one of the) next stable versions(s) is entirely up to Patrick J. Volkerding
  • Whether Slint(1) will follow suit is entirely up to gapan
  • Nothing like that will probably occur this year anyway
My personal conclusion is...

Happy New Year Everybody

(1) PS: I meant Salix

Re: Options for Salix if Slackware is forced to switch init

Posted: 1. Jan 2017, 21:15
by colebaas
Some of us have read this article long ago
That's nice. Yet, still here we are....

The point being that, if one sees the problem with systemd then there are quite a few things one can (and should!) do about it. Roll your own, pick a different, existing one, and so on. (We did.)
Perhaps providing suggestions to PV or to gapan is also not entirely without merit, especially since they get to pick-and-chose.

Re: Options for Salix if Slackware is forced to switch init

Posted: 1. Jan 2017, 22:03
by laprjns
DidierSpaier wrote:Whether Slint will follow suit is entirely up to gapan
Did you mean Salix....

Re: Options for Salix if Slackware is forced to switch init

Posted: 1. Jan 2017, 22:04
by DidierSpaier
colebaas wrote:Perhaps providing suggestions to PV or to gapan is also not entirely without merit, especially since they get to pick-and-chose.
See this post and especially its last line.

Re: Options for Salix if Slackware is forced to switch init

Posted: 1. Jan 2017, 22:06
by DidierSpaier
laprjns wrote:
DidierSpaier wrote:Whether Slint will follow suit is entirely up to gapan
Did you mean Salix....
Of course! Thanks for the heads-up. But that somehow stands for Slint too :lol:

Re: Options for Salix if Slackware is forced to switch init

Posted: 2. Jan 2017, 04:35
by colebaas
See this post and especially its last line.
... and while PV has been an exceptional guide all along, that alone does not make Faith a strategy nor Hope a destination.
It is one thing to construct clever structures but it is yet an other to defend Freedom.

Re: Options for Salix if Slackware is forced to switch init

Posted: 13. Mar 2018, 08:54
by globetrotterdk
I voted SysV. This is what Debian used to use and Devuan continues to use. I have been extremely happy with using SysV on my Devuan system. It is a lot quicker than systemd and doesn't have any of the inherent problems of systemd:
https://youtu.be/lDXsw2ijRkw

Re: Options for Salix if Slackware is forced to switch init

Posted: 25. Mar 2018, 13:18
by Kingpin
systemd would be a trap that Salix couldn't escape from, since it seems everything becomes dependent on it. So anything but that, I guess.

Re: Options for Salix if Slackware is forced to switch init

Posted: 28. Mar 2018, 15:55
by globetrotterdk
Kingpin wrote:
25. Mar 2018, 13:18
systemd would be a trap that Salix couldn't escape from, since it seems everything becomes dependent on it. So anything but that, I guess.
Rather disturbingly, I have noted that there is a "Dlackware" Slackware Live Edition that has Gnome3, PAM and systemd on top of Slackware. Talk about the dark side of the force :twisted: