-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 26/05/13 08:59 AM, J. Roeleveld wrote: > On Sat, May 25, 2013 21:55, Tom Wijsman wrote: >> On Sat, 25 May 2013 21:09:47 +0200 "J. Roeleveld" >> <jo...@antarean.org> wrote: >> >>> How will the stop/start part of services/init-scripts/... be >>> done? >> >> Not sure what you mean here; if you keep init function the same >> as the init you boot with, this should continue to work. > > As an example. Lets say I want to test a new init-system. To do > this, I follow the (still to be written) guide on "eselect init" > and boot into new-and-shiny-init-system. > > I am still used to stopping/starting services using > "/etc/init.d/<service> start/stop" And using the "rc" command to > add/remove services from the runlevel(s). > > If I then, accidentally, type "/etc/init.d/xyz start" when "xyz" > hasn't been started by any means yet. What will happen? I would > assume that openrc will try to start "xyz"? This is, I believe, > something that could cause issues as dependencies might also try to > start and I then have a service running not managed by the > "new-and-shiny-init-system" that I was testing.
Point #1 - openrc isn't init -- 'eselect init' or w/e is not necessarily going to be the same as 'eselect rc-system'. It's unlikely that you'll want to use another rc system if using systemd for your init, but that doesn't mean you can't. Point #2 - yes, this can be an issue and I believe it's already being worked on separately; WilliamH has mentioned issues like this more than once on irc, at least, although I don't know if he's implemented any solution(s). This bit should go into a separate thread or bug, and not be considered part of the overall 'eselect init' solution imo. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlGiIiQACgkQ2ugaI38ACPA7dwD/Y6IJo+/j2Ho4p1bM8mGMt7E8 ZglL7SvNS7g/90K6n1gA/37F0u5v2gzIoSTVi6uEmyhcPMW/2I2vr+YRv0rALO8S =PuVY -----END PGP SIGNATURE-----
