Practically every part of systemd has been modularized or supplemented out. Some of which aren't needed at all.
systemd-init - uselessd cloned the entire init and service supervisor. Other init programs of a similar nature include sysvinit/sinit+perp/runit/s6/daemontools-encore, runit (standalone), monit, and several other advanced init systems. In part, systemd-init was unnecessary to begin with. systemd-udev - eudev already segregated the entire udev part. vdev aims to replace it entirely. mdev replaces it in part but lacks the automated rule handler relying on kernel hotplugging instead. systemd-logind - loginkit and consolekit2 work together to replace logind in part and in whole minus a few specific functions. systemd-journald - was unneeded and completely unnecessary. Work was already done by sysklogd, rsyslog, and syslog-ng. systemd-networkd - was unneeded and unnecessary. Netplug, NetworkManager, inetd, xinetd, dhcpcd, and dhcp(client) to name a few already did the same work. Netplug is possibly the lightest weight of them all and provides connectivity device management as well as net connectivity service. Yes there are others but really what do they do new that isn't done already? To be truthful, the only real contribution systemd has offered has been logind which was nothing more than an advanced ConsoleKit client for DBus. That contribution has been miniscule and really unwarranted because all it is doing is doing things the wrong way by creating a huge monolithic project outside the scope of it's own parameters that has very little quality control and no real purpose other than creating another Busybox and monolithic hypervisor. Not to say it as something negative, but if Lennart and the Cabal had any real talent, they would focus their talents to improving existing systems rather than reinventing a wheel just for the sake of reinventing it to forcibly deprecate software and create a huge schism within GNU/Linux that has done more harm than good not just to GNU/Linux, but UNIX on the whole. -Jim > Date: Thu, 7 May 2015 11:27:10 +0100 > From: l...@diamand.org > To: jud...@gmail.com > CC: dng@lists.dyne.org > Subject: Re: [Dng] Which source version fo systemd are you stripping code > from? > > You might want to take a look at uselessd, which I think is an attempt > to do something similar. > > http://uselessd.darknedgy.net/ > > I think even if it turns out to be impossible, it will still be > instructive! Good luck! > > On 7 May 2015 at 08:24, Jude Nelson <jud...@gmail.com> wrote: > > > >> Since I have time on my hands, I would like to give a try stripping > >> the bare minimum of necessary functions from systemd. I know the task > >> is complex. If I fail, it will not be the end of the universe. > >> > >> Which systemd source version are you using? I am assuming it should be > >> version: 215-17 from Debian Jessie. > >> > > > > I'm basing libudev-compat on libudev 219. Also, some of vdev's helper > > programs (i.e. the ones that begin with "stat_") are derived from code in > > udev 219. > > > > It probably doesn't matter what version you go with unless you need a > > specific feature or want to avoid a specific bug. Why not just go with the > > latest? Stable releases of systemd are pretty frequent. > > > > -Jude > > > > > > _______________________________________________ > > Dng mailing list > > Dng@lists.dyne.org > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > > _______________________________________________ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
_______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
