[Haifux] Suggestions for part 2 of SiL#1
Hi, Now that the SiL#1 lecture was split into two, we can add more material to the lecture. Here are my suggestions. I think the following things should be added to the lecture: - umask - sTicky bit - a bit more on symbolic links (what happens when you delete the link target, etc.) If there is time: - hard links - device files - chroot Alon -- This message was sent by Alon Altman ([EMAIL PROTECTED]) ICQ:1366540 GPG public key at http://alon.wox.org/pubkey.txt Key fingerprint = A670 6C81 19D3 3773 3627 DE14 B44A 50A3 FE06 7F24 -- -=[ Random Fortune ]=- The only real argument for marriage is that it remains the best method for getting acquainted. -- Heywood Broun -- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED]
Re: [Haifux] Suggestions for part 2 of SiL#1
On Tue, 23 Dec 2003, Alon Altman wrote: Hi, Now that the SiL#1 lecture was split into two, we can add more material to the lecture. Here are my suggestions. I think the following things should be added to the lecture: - umask - sTicky bit - a bit more on symbolic links (what happens when you delete the link target, etc.) Alos, whar are the meanings of the colors ls produces- a link to such a table or soemthing (we don't need to study colors by heart, except for red=don't walk :) ) And I think the left slides plus what alon wrote upto this point would fill a lecture completely. plus, anyone who has not heard the Hanukah story guy told us lost :) If there is time: - hard links - device files - chroot Alon -- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED]
Re: [Haifux] Suggestions for part 2 of SiL#1
On Tue, 23 Dec 2003, Alon Altman wrote: Hi, Now that the SiL#1 lecture was split into two, we can add more material to the lecture. Here are my suggestions. I think the following things should be added to the lecture: - umask as i shouted at the end of the first lecture - i'll talk about umask. - sTicky bit *shrug* you _do_ want to confuse the listeners completely? as if umask is not confusing enough... oh, well. i'll try to find a simple way to explain that. - a bit more on symbolic links (what happens when you delete the link target, etc.) i'll add that to the slides. If there is time: - hard links - device files device files will be covered during the 'installing a device driver' lecture - i don't want to bring into this lecture, which will make it look like so what?. - chroot no, no, no. definately not. this is where i draw the line. there will be no chroots in my slides! ;) i mean that. i'll have to think about a very good example for umask... wait a minute... i think i got it. (to be continued...). dot dot dot. -- 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]
[Haifux] Re: Suggestions for part 2 of SiL#1
On Tue, 23 Dec 2003, Orna Agmon wrote: On Tue, 23 Dec 2003, Alon Altman wrote: Hi, Now that the SiL#1 lecture was split into two, we can add more material to the lecture. Here are my suggestions. I think the following things should be added to the lecture: - umask - sTicky bit - a bit more on symbolic links (what happens when you delete the link target, etc.) Alos, whar are the meanings of the colors ls produces- a link to such a table or soemthing (we don't need to study colors by heart, except for red=don't walk :) ) Well, three notes are in order: 1. The exact colors are user configurable (via the LS_COLORS env var or otherwise) and may vary from distribution to distribution or from system to system. 2. ls can color files which match a certain glob in different colors, like *.zip or *.gz. This is a coloring that is only a convenience and does not indicate that the file is special in any way. (it may also not belong to its correct type). 3. colors can be misleading. For example, on my Mandrake system, all files ending with .sh are colored green (which is the same color for exacutables) even if they are not executable. I remember trying to execute a shell script I prepared because I saw its color was green (./upload.sh) only to discover it was not executable as far as its permissions were concerned. Regards, Shlomi Fish And I think the left slides plus what alon wrote upto this point would fill a lecture completely. plus, anyone who has not heard the Hanukah story guy told us lost :) If there is time: - hard links - device files - chroot Alon -- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED] -- Shlomi Fish[EMAIL PROTECTED] Home Page: http://t2.technion.ac.il/~shlomif/ An apple a day will keep a doctor away. Two apples a day will keep two doctors away. Falk Fish -- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED]
