On Sun, 21 Dec 2003, Orna Agmon wrote: > On Sun, 21 Dec 2003, guy keren wrote: > > > > > I think also a very important thing to teach is to check after yourself when > > > you change permissions, at least in the first few times, to see you did > > > what you intended. And only that. > > > > this is something i will mention during the lecture. how would you put it > > in the slides, and where? > > I would show an example of a chmod, and then ls -l of this file, and read > with them (slowly) the interpretation of all those x's and r's and -'s and > w's. also for a directory, to see the d. Better, I would ask any of the > listeners to interpret that for us.
i asked - how would you put it _in the slides_? i still cnnot ask for people's participation in a statically written slide ;) > > > 29: I personally find the summary line :"Google for them all on your spare > > > time.." > > > improper. > > > > improper in what manner? i am trying to say "you'll need to learn about > > these issues on your own, because we are not showing them here". they are > > bound to stumble on these issues sooner or later - so i just make them > > known by name. > > the google direction scares people. you can say it oraly, but it loks bad > written. they come to us in order not to be on their own. they want to > know what they have leaned, not that there is a google out there. and a > summary slide is important- it gives the sense of achievement. > it differes from table of ocntents, in that people are supposed to know > what you are talking about by then. so you'd rather i don't mention these issues at all? i mentioned them for one reason - the next time people will encounter them, they could tell themselves "hey, i heard about these beasts before", which should (in my opinion) reduce the puzzlement factor. > "Tell them what you are goingto tell them, then tell them, then tell them > what you told them". ok. i'll think of how to add such a slide without it looing silly _as a slide_. i know i'm supposed to summarize everything in the end of the lecture (i went to "teaching methods 1(01) a decade ago). i'm arguing about whether this should be reflected in the slides, or only be done verbally. > regarding the octal chmod: I do not think it is good to use it, but I > think they should learn it exists, and the difference between octal chmod > and umask. could get very confusing. the intention of _this_ lecture is two-fold: 1. show peple how to do something. in this case, if there are two ways to do something, i prefer showing the simple one. 2. explain what is going on. from this point of view, i should explain the _permissions_ themselves and how they work. note that i am not even mentioning 'umask', and it did not come up until now. there is just so much that can be covered in a 2-hour lecture. i would consider lengthening this series into 4 lectures after i see the reactions to the first lecture. attendance, for one thing. of course, since this series does not get he same publicity as the 'welcome to linux' series did, i don't expect that many people to show up. but then again - i might be surprised... -- guy "For world domination - press 1, or dial 0, and please hold, for the creator." -- nob o. dy -------------------------------------------------------------------------- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED]
