Is there any information, other than the documentation at Gentoo's website, I can get into creating an LFS build with OpenRC as a choice of INIT?

I normally don't ask why when such things arise because of the beauty of the LFS approach is that you can do whatever you want and there need not be a reason other than curiosity and to learn more. That said, above and beyond gaining more experience with an alternative init approach (certainly not systemd), what advantages are there in an LFS context with openrc as opposed to sysvinit?

And you're right, aside from the Gentoo documentation, there's very little elsewhere about openrc. It does look intriguing and as a sometimes Gentoo user, it's semi-familiar but admittedly, I take it for granted since it "just works" (TM) and I've never probed how it works. It's a shame that Roy Marples' site is no longer maintained since the entries there did show promise in revealing the under the hood aspects of openrc.

I presume you've seen this?

http://forums.freebsd.org/showthread.php?t=35770 (Replacement of Init System)

Yeah, I found this link posted:

https://wiki.freebsd.org/launchd

It's about FreeBSD attempting a port of Launchd from OSX which would be somewhat interesting if they can as Launchd is a very interesting INIT system, though the page seems somewhat abandoned.

My only concern was how difficult it was to build, install, and setup OpenRC from Scratch (no pun intended), any dependencies, and if there were any sample scripts I'd need to utilize to craft up a native script for my system.

Plus, the reason I chose OpenRC was simply the fact that OpenRC seems to supplement and enhance sysvinit rather than outright replace it, and it already has a usage on Gentoo which seems fairly stable, and was actually pushed out by Gentoo to be freely open to importing into other systems.

One thing your posting did was to put a little fire in my belly on far more modest task, one I had contemplated for years but only started working on a few hours ago. I'm in the process of redoing all of init scripts (both those from LFS/BLFS and my own) to use /bin/dash rather than /bin/bash. I ran the checkbashims Perl script over the whole directory and there are a large number of bash-specific constructs that I'm now shedding.

So this is my first small step toward trying something a wee bit different in the init process. Why? Well, not to make it boot any faster since that's a low priority of mine but just to scratch another itch of curiosity.

Take a look at the PKGBUILDs for Arch. There you can see dependencies and how they build it.

Thank for the info Lennie.

My delving into OpenRC is merely but starting at about how sysvinit can be extended rather than just simply replaced as init and management software like systemd wants to do and how with the right extensions, support vectors, and native programs and libraries. Plus, I'd rather do things the right way, rather than the wrong way. This is Linux, not Lennix.

I had been deciding between OpenRC, RUnit, and a variant of Slackware's BSD-like SysV scripts, and OpenRC seemed more a logical choice to not have to completely abandon sysvinit, but supplement, extend, and enhance it in various ways and means while holding true to the LSB, POSIX, and SUS philosophies, and keeping compatible scripting.