On 07/04/2013 23:22, Alessandro Selli wrote: > Anselm Lingnau wrote: >> Alessandro Selli wrote: >> >>> As far as I can tell, Ubuntu is still using upstart in it's current >>> stable release, 12.10. And I am not aware of any plan of theirs to >>> switch to systemd. I don't think that's a pool of users we can ignore, >>> even if RedHat didn't do us any "disservice". >> As a rule LPI doesn't cover technology that is used by one single >> distribution, even if that technology looks useful and the distribution >> seems >> popular. > > All right, so if RedHat didn't do us any disservice then we would be > free to disregard upstart any anyone still using it. But *SIGH!* with > Ubuntu we have two major players out there using upstart in some of > their maintained, stable, enterprise distros. I was not campaigning for > the sake of the Ubuntu field alone. And, even if it's not the default > init daemon, upstart is available also on other stable distributions as > an alternative one (e.g.: > http://www.debian.org/doc/manuals/debian-reference/ch03.en.html#_stage_4_the_normal_debian_system). > > [...] > >> It is interesting to note that even on the Ubuntu developer lists there is >> some movement in the direction of systemd. Apparently the reason why Ubuntu >> hasn't gone over to systemd is not that Ubuntu developers think Upstart is >> the >> better solution (which would be the sort of NIH syndrome one might expect >> from >> the original sponsors of Upstart development) but that they don't want to >> introduce a lot of churn just now. Ubuntu does seem to want to adopt certain >> parts of systemd such as systemd-logind (rather than ConsoleKit) even in the >> fairly short term, so I wouldn't be surprised if they decided to go with >> systemd instead of Upstart sooner or later. > > All right, but I don't think we can base our present decisions on the > changes that some distributions will go through in the future. We > should indeed be ready for them to arrive, but the present state of the > exams layout should not reflect those intentions. > >> Having said that, we have nearly two years until the next review of LPIC-1, >> and it would probably best to wait for the dust to settle before hurrying to >> include Upstart content in the exams RIGHT NOW. > > If there is any sense in including upstart is just now. I think > upstart will be o less relevance two years from now than it is today. > We either decide to include it now, or we'll leave it uncovered today as > it was in the past and will be in the (foreseeable) future. > >> It may well be the case that >> by that time all the systems that actually run Upstart are actually legacy >> ones. Certainly Red Hat is slated to replace Upstart with systemd for RHEL >> 7, >> which will probably come around earlier than the next exam review, and all >> the >> RHEL derivatives like CentOS and Scientific Linux will be following suit. >> That >> leaves (possibly, see above) Ubuntu as the last major Upstart-using >> distribution. Upstart is basically dead, it just hasn't fallen over yet. > > I agree on everything, including the very last word you wrote. :-) > I do agree upstart does not deserve too much coverage as it's a minority > system init daemon heading its way to extinction, yet I do believe that, > being it still here with a few of us, a LPI candidate should be aware of > it and at least be able to tell if a system he/she's logged in is using > a SysV or Upstart or Systemd init.
Let's be honest though - what is the weight attached to the objectives for the system start-up system? 1 or maybe 2? So the candidate would expect to get 1 or maybe 2 questions on it in an actual exam. And what form would those questions take: how to determine if a daemon is running how to start/stop/restart a daemon. What else could /really/ be asked? I would certainly expect an LPIC1 grad to know how to deal with these issues (or find out from Google in >5 minutes). I'd put these in the same category as cat, tac, head and tail - you are going to run into them quite early and you might as well devote half a page to each in a book. -- Alan McKinnon alan.mckin...@gmail.com _______________________________________________ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
