On Thu, Mar 9, 2017 at 3:02 AM, Kenneth Peiruza <kenn...@floss.cat> wrote: > Agreed on style, depth and order. > > LPIC 1 order isn't the most intuitive.
I totally agree with this statement with the caveat that LPIC-1 is a set of objectives describing what a candidate needs to know. It isn't a course or a book outline. In fact, I think that the more not like an outline it is, the better. That way authors have to figure out how they would like to present the material in a way that appeals to their sensibilities. > I generally begin with a bunch of 'survival' commands, LFHS and a bunch of > text processing exercises to start moving around. > > Hardware, installation and grub are taught on the last half of the course. Yep, that's how I did it when I was giving training. The last thing you want is to have your student mess up the entire machine on Monday morning and get all flustered trying to fix it so that he can get to the stuff that they use all day at work. > LPIC1 order doesn't looks like a path to follow to bring someone from near > no Linux knowledge to a self-sufficient technician. See above. I hope it never does :) Which is also why I'd voted for the BoK approach over making a book. We'll spend the entire weekend "deciding" on the structure and never get to any content...or a structure. Regards, --matt > > Regards, > > Kenneth > > > > Sent from my Mi phone > On Stephen Murphy <stephen.mur...@bcu.ac.uk>, Mar 9, 2017 8:33 AM wrote: > > Hi All, > > Have lurked in the background for a number of years, but this is something > that directly affected my students, so radio silence is broken! > > This sounds like an great idea - but thinking out loud at some of the issues > that would need to be dealt with in advance... > > I think the results would need quite a bit of editing to make it look > professional (different styles of writing, approaches etc.) unless (as Matt > says) this is really nailed down firmly in advance. A weekend is not a lot > of time to do this! > > As an alternative idea, how about a 'x chapters each' approach with a > deadline? That would work better for me, and possibly others with families > who expect to see them occasionally :-) Also how much would it cover > theory? Knowing what to put in what config file is one thing - the why are > you doing it is the important bit IMHO. > > I like the direct BOK approach in terms of clarity and linkage to the > objectives, but will it be usable by someone with limited experience? Often > things are taught in a certain order because they logically lead on from one > another and have pre-requisite knowledge. > > Best regards, > > Steve. > -- > Stephen Murphy - BA (Hons), MA (Oxon), MSc, PgDip (Ed), PgCert, MBCS, SFHEA > - Senior Lecturer > > Lead Academic - Technology Supported Learning - > https://icity.bcu.ac.uk/celt/learning-technology-support > Academic Lead - Linux Professional Institute Academy > > School of Computing and Digital Technology > Birmingham City University. > http://www.bcu.ac.uk > t: +44 (0)121 331 7515 > > ________________________________________ > From: lpi-examdev-boun...@lpi.org [lpi-examdev-boun...@lpi.org] on behalf of > Alessandro Selli [alessandrose...@linux.com] > Sent: 08 March 2017 23:37 > To: lpi-examdev@lpi.org > Subject: Re: [lpi-examdev] dealing with the dearth of LPIC training > materials > > Hello everybody, > Sorry for having not joined in any discussion for months, but it > looks like something was silently dropping incoming mail from lpi.org. > > On 08/03/2017 at 19:55, G. Matthew Rice wrote: >> On Mon, Feb 27, 2017 at 10:03 PM, Jeremy Hajek <ha...@hawk.iit.edu> wrote: >>> Thanks for all the hard work here - I admire this serious stepping up in >>> the >>> LPIC standards. Recently I found that the textbooks that matched the >>> LPIC >> Hey, guys, >> >> What do you think of the idea of a 'write a book in a weekend' idea? > > I'm afraid it'd take me longer than that! :-) > >> I've seen it work (almost) with other books. I think they just forgot >> to put more effort into planning the book upfront. >> >> We could also make it easier by focusing on creating the Body of >> Knowledge and forget the prose. Kind of like the start of the LPIC-2 >> BoK at: >> >> https://wiki.lpi.org/wiki/LPIC-2_BoK >> >> https://wiki.lpi.org/wiki/LPIC-2_BoK_Content_206.1_Make_and_install_programs_from_source > > I could drop a few lines here and there, sure. > >> FYI: https://en.wikipedia.org/wiki/Body_of_knowledge >> >> What do you guys think? A couple of us can work out the outline >> beforehand and then meet up online for a weekend (LPI will find a nice >> way to say thanks to the participants). > > "meet up online"? How do you intend to do it? > >> As well, I have at least one publisher that would be interested in >> publishing the results, too. No promises, they haven't seen what >> they're agreeing to yet ;) > > Let's shock them! :-) > >> The nice thing part of the BoK is that it provides more reference-able >> material for all authors; books, training material, etc. > > Useful indeed. > I'd like to help. Only, I am now busy on Saturdays, too (last Saturday > I delivered the fifth of a 20 sessions LPI online course) and will be > unavailable the month of May. Still, I'd really like dropping a few > lines here and there, I probably have many already there to contribute. > > > > -- > Alessandro Selli <alessandrose...@linux.com> > > _______________________________________________ > lpi-examdev mailing list > lpi-examdev@lpi.org > http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev > _______________________________________________ > lpi-examdev mailing list > lpi-examdev@lpi.org > http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev > > > _______________________________________________ > lpi-examdev mailing list > lpi-examdev@lpi.org > http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev -- G. Matthew Rice <m...@starnix.com> gpg id: 0x17CF9077 _______________________________________________ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
