> > the (updated) slides for monday's lecture are temporarily available at > > http://www.actcom.co.il/~choo/users-processes-files-and-permissions/ . > > > > the slides, in one 'tar.gz' file, are at: > > > > http://www.actcom.co.il/~choo/users-processes-files-and-permissions.tar.gz > > > > (hopefully, they will be placed on haifux's web site, by the kind little > > dwarves [hagamadim haktanim hatovim]). > > > > note that i added umask, fuser and lsof, and the sticky bit. i did not add > > hard links because there are already too many slides now ;) and i expect > > 'umask' to take a while to properly explain, with the octals, > > bit-operations, etc... > > > >
24: Only when the Process closes the File, the File will be actually deleted from disk -> Only when.... will the File be... (I don't know why. Just English) 25: fuser is not always in /sbin- On my Debian it is on /bin. I think it is more confusing than not, to list the specific path to a command which may not be there- better to insert both /sbin, /bin /usr/local/bin etc. into the path (or teach them that these are good thing to have in the path) but this is not the place. So the fact that you may not have /sbin in your path need not reflect on the slides. I just read slide 26. But I still think this is not necessarily the place to discuss the path, especially given the different location on various systems. 26: Nobody would know what mmap is. It is way beyond this lecture. I suggest to avoid the word mmap, and explain instead. The term adds nothing right now. 27 and 28: 28 is MIKRA for 27. I suggest shortening the output of lsof manually, in order to fit them on the same screen, according to Ron Artstein's principle of avoiding window switches. Otherwise, I epect you would find yourself explaining about the kinds of files when you either have the list and no examples, or doing it off by heart with the list- and no slide to aid the audiance. Or switch slides all the time. 37 When set for a File, it means that the File should be copied into the swap device, rather then loaded from its original location. This could make the File load faster. should be rather THAN. And the term SWAP might need explaining. Also, I do not get the purpose of loading a file by copying it from one part of the HD to another, even if it is called SWAP. how does it make the loading faster? 38: If we are in UNIX basics, should this be Unix? (in " Linux allows creating a File.." giving a program the impression ... should be with capital G Amaze your friends or bewilder them. should be "Amazing your friends or bewildering them" to support parallel structure (mivne makbili). 42 I suggest directing to slides of lecture 7 (by you) http://www.haifux.org/lectures/7/ hwich is about intro to sockets. I feel we should be covering grep and | (pipe), and the whole idea of "the Linux way" of building things from small units which do their job well. When I come to think of it, it is not the Linux way, but rather the hurd way, or the GNU way. Linux is actually monolithyc. :) These are very good slides, in my opinion. I think the repetitive motive is a good thing in such a lecture, and the previous one was at a good pace. But I think you should stress the commands you issue on the demos more. something like "We now issue ls -l", and not "and look- we see that...". Orna. -------------------------------------------------------------------------- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED]
