On Mon, Jan 27, 2014 at 3:15 PM, Anselm Lingnau wrote: > I still think it is unwise to do a major review of LPIC-1 just now, but if we > have to, »mostly systemd with awareness of SysV init« is probably a much more > future-proof approach than »mostly SysV init with an awareness of systemd«.
Last May (2013), regarding LPIC-2, I advised we at least introduce both Upstart and systemd with the lowest-level of Bloom Taxonomy, Knowledge (Weight 1), whether it be in LPIC-2 or in the next revision of LPIC-1. QUOTE: [bjs-13MayA] 'Might I suggest we start in this rev with Bloom's Knowledge (weight 1) [1] type questions. E.g., - Identify Upstart system init and event configuration (/etc/init, /etc/events.d) - Identify systemd reference and site local configuration (/lib/systemd, /etc/systemd) for services (.service files) I would also advise we include a topic on identification of the init. E.g., - systemd is almost always a symlink from /sbin/init to /lib/systemd/systemd - Upstart is a bit more difficult to identify without the package systems' solution (it replaces /sbin/init)' There is also room for additional Bloom's Understanding (Weight 2). QUOTE: [bjs-13MayA] 'BTW, because packages sometimes drop in files for different inits, whether they are in use or not, - Just because /etc/init and/or /etc/events exists, does not mean Upstart is in use, correspondingly. - Just because /sbin/systemd or /etc/systemd exists, it also does not mean systemd is in use Some of these might be more Understanding (weight 2). As more systems adopt both, we can expand the complexity and weight of the questions in future revisions. At that time, I would definitely like to see Objectives target differences between Upstart init/event files and .service files of systemd -- killing two birds with one stone (same questions, can be used to cover for both).' Regarding the "distro-specific" arguments, and SysV, let's not forget the SysV is still supported by both Upstart and systemd, and should _never_ be dropped. QUOTE: [bjs-13MayB] 'In reality, init and system management aspects should be rolled into one. Figuring out what is the init program, where are its configuration files for init, events, etc... for services, etc... I think that gets pretty non-specific. Especially the event-based stuff, that's not really Upstart-specific. I.e., I still have to go over this too many times with sysadmins, both RHEL6 and Ubuntu, with Upstart. We should have LPI professionals who understand these details. We're 3+ years in now. ;) ... SysV init concepts will _always_ be around. Both Upstart and systemd support SysV init scripts. Heck, systemd can even monitor SysV init forked processes by Socket dependencies (it automagically detects) without any configuration.' -- bjs Archives: [bjs-13MayA] http://list.lpi.org/cgi-bin/mailman/private/lpi-examdev/2013-May/002386.html [bjs-13MayB] http://list.lpi.org/cgi-bin/mailman/private/lpi-examdev/2013-May/002395.html -- Bryan J Smith - UCF '97 Engr - http://www.linkedin.com/in/bjsmith ----------------------------------------------------------------- "In a way, Bortles is the personification of the UCF football program. Each has many of the elements that everyone claims to want, and yet they are nobody's first choice. Coming out of high school, Bortles had the size and the arm to play at a more prestigious program. UCF likewise has the market size and the talent base to play in a more prestigious conference than the American Athletic. But timing and circumstances conspired to put both where they are now." -- Andy Staples, CNN-Sports Illustrated _______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
