The init could show promise but having mdev could be something worth investing time in if we can get it working for complete systems. Research is research, and knowing that mdev can be used does unlock a few doors for Linux. If the case ever comes down where udev becomes useless due to kdbus, having a fallback plan that could get picked up and ran with, could prove highly useful.

I plan on building a BusyBox mdev and Runit init system for research purposes soon anyway.

I'll let you know when I get to the point of needing mdev.

I have been messing around with busybox init and mdev trying to get it working under arch linux. Based my efforts on the work on Neales runit-init (post links soon). Running from console do not have any real problems but X is another story. If I use systemd-udev then it works fine.

Hotplug scripts is interesting as arch does not ship with hot plug support any more.

Hope you do not mind me jumping in on your post.

I gather this is one of the main problems with systemd it tries to make itself a dependency of software which should in all honesty know nothing about the type of init system being used, so if your X system has been built with systemd support it probably is not going to run on anything else, check out the blfs book on building X with/without systemd, personally I wouldn't touch it with a ten foot battle lance!

Although arch is a source based distro similar to lfs/blfs I'm not shure how compatible the two systems are to mix'n'match, why not just go the whole hog and switch to lfs ( go on you know you want to really ).

Yes, once systemd is in a system, basically all the packages that can build against it, must be rebuilt to use it. Then they become hardlocked to systemd's library.

systemd isn't just an init system. It's a service management host controller (basically a GNU/Linux version of svchost, SMF, and launchd) that serves as the core hypervisor of the system.

If you wanted to run a systemd system without systemd, you'd basically have to rebuild EVERYTHING from the ground up to remove the depedency upon systemd, and that is not an easy task.

Do not really have a problem with systemd just want freedom of choice. You are of course right I would have to rebuild everything. Alternatively run Void which is runit based.

Sorry for hijacking thread ;-)