On 2014-02-21 12:33 PM, thegeezer <thegee...@thegeezer.net> wrote:
On 02/20/2014 08:06 PM, Tanstaafl wrote:
Thinking about this more, since apparently using a separate profile
may just be 'overkill', how about something simpler, like, for
example, using eselect...
Something like:
# eselect init list
Available init systems:
[1] OpenRC *
[2] systemd
[3] runit
(whatever choices are supported).
+1 from here
Personally i'm most likely to stay with openRC, because the switch is
non-trivial and have no faith in the xinetd-style socket arbitrator.
but would eselect be able to script the following:
.. new kernel coptions
.. new grub2 command line
.. install dbus (use=-systemd)_then_ systemd
.. would be nice to use an import for localed and hostnamed and timedated
.. importing openrc services and runlevels to targets
.. pamd logind entires
.. syslogd changes to accomodate systemd
.. setting systemd to log to syslog to make transitions smoother (as
logs are lost on reboot by default)
and then the reverse for 'undo' ?
Well, there are two aspects to consider: new install (where most of the
above are not an issue), and switching back and forth.
Only a dev can answer your questions with respect to the latter.
Everything Canek and others were saying led me to believe it was more
trivial/less work than your questions suggest, so I'll just have to
leave the answers to those who know so much more than I...
