| *** shmohamud has quit (Ping timeout: 480 seconds) | 01:08 | |
| *** shmohamud has quit (Ping timeout: 480 seconds) | 03:24 | |
| *** sysadmin_ has quit (Quit: Leaving) | 09:34 | |
| *** scooper has quit (Ping timeout: 480 seconds) | 09:34 | |
| jelkner | Good morning fkoikoi! | 10:25 |
|---|---|---|
| jelkner | and scooper and tboimah | 10:25 |
| scooper | good morning Jeff | 10:25 |
| tboimah | Good morning Jeff | 10:25 |
| jelkner | is fkoikoi nearby? | 10:26 |
| scooper | before we continue please view this git link at your less busy time today | 10:26 |
| scooper | yes | 10:26 |
| scooper | https://git.mcssliberia.org/python-team/PythonStudy/src/branch/main/Article-Of-Incorp.md | 10:26 |
| fkoikoi | I'm here Jeff | 10:26 |
| jelkner | excellent start, scooper! | 10:27 |
| jelkner | now i don't see anything about it being a worker cooperative | 10:27 |
| jelkner | which is why it is good to start early | 10:28 |
| jelkner | worker coops are a recognized form of business in some places | 10:28 |
| jelkner | and in others they are not | 10:28 |
| jelkner | for example, in DC, they are | 10:28 |
| jelkner | in Virginia, they are not | 10:28 |
| jelkner | so NOVA Web Development had to use another form, LLC | 10:28 |
| jelkner | Limited Liability Corporation | 10:29 |
| jelkner | and use its Operating Agreement to make it a coop | 10:29 |
| scooper | This will not be a sole proprietorship but rather a partnership in liberia. | 10:30 |
| scooper | I m sure of that but will do research properly on that | 10:30 |
| scooper | Mean while I was advice strongly by a legal person to get a legal advice as it relate to crafting the Article of Incorp for Jetro Web | 10:32 |
| jelkner | Have you seen the operating agreement for NOVA Web Development, scooper? | 10:32 |
| scooper | -1 | 10:32 |
| jelkner | Ah, we should change that | 10:32 |
| jelkner | i am looking for the URL for it | 10:32 |
| jelkner | i can't find it, so i'm calling stefan | 10:35 |
| jelkner | brb | 10:35 |
| scooper | ok | 10:36 |
| jelkner | https://novawebdevelopment.org/public/documents/NOVAWebDevelopmentOperatingAgreementRevised_2023-05-01.pdf | 10:41 |
| jelkner | right now, adrian and i are the only worker / owners | 10:43 |
| jelkner | but the plan is to have Antonio and Kei added next May | 10:44 |
| jelkner | and to try to grow from there | 10:44 |
| jelkner | we had 4 worker / owners last year | 10:44 |
| jelkner | but 3 of them are now gone, and i had to be added back to keep the coop running | 10:44 |
| jelkner | we have not figured out yet how to successfully run a small web development business, but we have learned a lot of lessons | 10:45 |
| jelkner | that will help us going forward | 10:45 |
| jelkner | which we can share with Jetro Web Development as it gets going | 10:45 |
| jelkner | this will be a long journey, scooper and fkoikoi | 10:46 |
| jelkner | that's why i want to start talking about it now | 10:46 |
| jelkner | it will take a long time to learn the concepts of what a worker coop is | 10:46 |
| jelkner | what a web development business does | 10:46 |
| jelkner | to develop a business plan | 10:47 |
| jelkner | etc. | 10:47 |
| jelkner | we will by necessity do a lot of "learning by doing" | 10:47 |
| jelkner | the good news is that we already have a lot of customers | 10:48 |
| jelkner | by "a lot" i mean about a dozen | 10:48 |
| jelkner | the problem has been that it is difficult to support most of them | 10:48 |
| jelkner | they are small non-profit or community organizations that do not have deep pockets | 10:49 |
| jelkner | scooper, fkoikoi are you still here? | 10:49 |
| scooper | +1 | 10:49 |
| jelkner | i guess i should stop for now | 10:49 |
| scooper | following keenly | 10:50 |
| fkoikoi | +1 | 10:50 |
| jelkner | scooper, i am looking forward to the day when you two have more and more questions | 10:50 |
| jelkner | since that will mean you are beginning to understand the problem | 10:50 |
| jelkner | and to think about the solution | 10:50 |
| scooper | concerning Python??? | 10:50 |
| jelkner | LOL | 10:50 |
| jelkner | concerning the business, now | 10:51 |
| scooper | ooh | 10:51 |
| scooper | ok | 10:51 |
| jelkner | what have i been writing about? | 10:51 |
| jelkner | anyway, we need to take small steps | 10:51 |
| scooper | I will place my questions in a markdown file and publish it to you since the time we have here i short | 10:51 |
| jelkner | but we need to start now | 10:52 |
| jelkner | that's what i hope to do with fkoikoi in our 10 minute meetings | 10:52 |
| jelkner | fkoikoi, are you here? | 10:52 |
| fkoikoi | +1 | 10:52 |
| jelkner | let's have our stand-up meeting now | 10:52 |
| jelkner | i saw that you have begun to investigate the ICA | 10:53 |
| jelkner | next step will be to find a contact person there whom you can email with questions | 10:53 |
| jelkner | we need to reach out to them for help | 10:53 |
| jelkner | since they will be able to provide us with guidance about how to form a worker cooperative in a place that doesn't have them yet | 10:54 |
| jelkner | fkoikoi, also keep asking around | 10:55 |
| jelkner | because maybe there are already worker cooperatives in Liberia, and we don't know about them yet | 10:55 |
| scooper | ok now we are on a little break I will embark on this journey with fkoikoi | 10:55 |
| jelkner | excellent | 10:55 |
| scooper | To help gather all necessary information | 10:55 |
| jelkner | super! | 10:55 |
| jelkner | ok, that's all i have for today | 10:56 |
| jelkner | i'll be here again at 11 am your time tomorrow | 10:56 |
| scooper | ok thank for the time | 10:56 |
| scooper | we are awaiting Shmun | 10:56 |
| jelkner | thank you, scooper and fkoikoi | 10:56 |
| jelkner | yes | 10:56 |
| jelkner | i'll look at the logs tomorrow morning to see how that goes | 10:57 |
| jelkner | ACTION signs off for today | 10:57 |
| scooper | He promised to be here Monday, Wednesday and Friday | 10:57 |
| *** jelkner has quit (Quit: Leaving) | 10:57 | |
| *** svaye has quit (Remote host closed the connection) | 12:25 | |
| *** svaye has quit (None) | 12:39 | |
| *** tboimah has quit (Remote host closed the connection) | 12:45 | |
| ubuntourist | tboimah, mulbah Hi! | 13:00 |
| mulbah | Hello Mr. Cole | 13:01 |
| tboimah | Good morning ubuntourist | 13:01 |
| ubuntourist | So, any questions? Progress? Anything you'd like to talk about before we dive into somethng? | 13:02 |
| mulbah | well I don't have question now | 13:03 |
| tboimah | -1 | 13:03 |
| ubuntourist | I will be honest: I had originally planned to look more at the book and decide what to do next, but I never got around to it. | 13:03 |
| mulbah | Mr. Cole did you take a look at the python program that I e-mail you | 13:04 |
| ubuntourist | So, very briefly (I hope), we'll talk about some of the Chapter 10 topics and them move on. | 13:04 |
| ubuntourist | mulbah, I sent a response to you in e-mail. | 13:04 |
| ubuntourist | mulbah, a few days ago. | 13:04 |
| mulbah | alright let me check it | 13:05 |
| ubuntourist | So... Let's crank up tmate. | 13:06 |
| tboimah | ssh sChP8VAkwPmNdWJxXqENvBUUv@sfo2.tmate.io | 13:07 |
| mulbah | ssh LkThfE3z3eBwGVzkTJkqsR7a3@lon1.tmate.io | 13:08 |
| ubuntourist | We'll be looking at a little more about processes. | 13:10 |
| ubuntourist | Some things I won't be able to see in tmate, because I want you to start up a second terminal and I don't want to ssh into four terminal windows. | 13:11 |
| ubuntourist | But, before we do that, just type | 13:11 |
| ubuntourist | top | 13:11 |
| ubuntourist | "top" is like those medical displays you see next to a hospital bed: It is monitoring the "heartbeat and respiration" of your computer. | 13:13 |
| ubuntourist | It is showing you the "top" of the "ps" process status: It is deciding which processes are the most active, and | 13:14 |
| ubuntourist | showing you a bunch of "vital statistics" -- updating every second. | 13:14 |
| ubuntourist | So, for example, I see that on mulbah's computer, firefox is chewing up significant resources, staying near the top of the list. | 13:15 |
| ubuntourist | On tboimah's computer I see that there's not too much happening. The main activvity was hexchat, but I see firefox is also running. | 13:16 |
| ubuntourist | My guess: mulbah has more tabs open in firefox, or is on a web site that is constantly sending information -- like a news site or social media site. | 13:17 |
| ubuntourist | Something is keeping mulbah's firefox a little bit busier than tboimah's firefox. | 13:17 |
| ubuntourist | You can get "top" to sort the information by different criteria -- You can ask "top" to show you which processes are using up | 13:18 |
| ubuntourist | the most CPU processing power, which ones are getting more attention / using up more "time" and which ones are using the most | 13:19 |
| ubuntourist | memory. | 13:19 |
| ubuntourist | "top" is "case-sensitive" so, upper-case means something different from lower-case. | 13:20 |
| ubuntourist | type "P" (no quotes. | 13:20 |
| ubuntourist | P shows you which processes are using the most CPU processing power. | 13:21 |
| ubuntourist | (the CPU% column is what to pay attention to with the P sorting order.) | 13:21 |
| ubuntourist | T will show you who's chewing up the most TIME and that's the column to pay attention to. | 13:22 |
| ubuntourist | and M will sort by memory (%MEM) | 13:22 |
| ubuntourist | "q" to quit. | 13:23 |
| ubuntourist | ps and top are often useful for answering questions like "Why is my computer suddenly very slow?" | 13:25 |
| ubuntourist | or "Why did this application freeze?" | 13:25 |
| ubuntourist | For example, with "top" and "P" if you see a process with a very large %CPU then it usually means that the application | 13:26 |
| ubuntourist | is trying to do some mathematical operation that is very difficult or it is stuck doing something very repetitios. | 13:27 |
| ubuntourist | Unless you know that you are trying to do complex mathematics, it usually means something's wrong: The application | 13:28 |
| ubuntourist | is trying to solve a problem that it cannot solve and it is devoting all of its "brainpower" to the problem. | 13:28 |
| ubuntourist | A very high %MEM suggests that an application is loading a lot of data from some file, or downloading a lot into memory. | 13:29 |
| ubuntourist | That might be a problem if you are not expecting that -- for example if you go to a web site and suddenly your %MEM spikes high | 13:30 |
| ubuntourist | it coud indicate malware or a virus trying to take control by flooding your computer with too much data. | 13:31 |
| *** fkoikoi has quit (Ping timeout: 480 seconds) | 13:31 | |
| *** tboimah has quit (Ping timeout: 480 seconds) | 13:31 | |
| *** scooper has quit (Ping timeout: 480 seconds) | 13:31 | |
| ubuntourist | Usually you want to watch "top" for several seconds to see if the list changes. If you're only having momentary spikes, | 13:32 |
| ubuntourist | it's usually not something to worry about. firefox might "go high" with %CPU or %MEM for a second or two, but | 13:32 |
| ubuntourist | if it drops down in the list again, it's probably nothing to be conerned about. | 13:33 |
| ubuntourist | I don't use a lot of the informaton from "top" -- So I cannot explain it all. | 13:34 |
| ubuntourist | But, PID we've seen before from "ps" -- it's the Process ID which will become important in a minute. | 13:34 |
| ubuntourist | "user" is pretty self-explanatory: Who started this program? Is it "root" or "systemd+" which usually mean | 13:35 |
| ubuntourist | a normal user didn't start it and it's part of the operating system running in the background? | 13:36 |
| ubuntourist | Or is it a "normal user" like mulbah07 or "tboimah" which means it's probably something that you started? | 13:37 |
| ubuntourist | "PR" and "NI" are related: If you subtract NI from 20, you get PR... | 13:38 |
| ubuntourist | PRiority and NIceness. | 13:38 |
| tboimah_ | ACTION going to use the bath room please | 13:39 |
| ubuntourist | Priority is "how imortant" is this process? How much attention and love from the CPU should it receeive? | 13:40 |
| ubuntourist | Niceness is funny word: It refers to an adjustment to the priority. Easier to explain with an example. | 13:41 |
| ubuntourist | mulbah, (I killed it because it was making me crazy watching the screen move while I was typing in chat.) | 13:42 |
| mulbah | okay | 13:42 |
| ubuntourist | Suppose you WANT to do something complicated on the server. Something that will chew up a lot of CPU and memory. | 13:43 |
| ubuntourist | But it's a server. You are not the only one using it. | 13:43 |
| ubuntourist | If you start up your busy program, it may suck up all the CPU power and memory, and | 13:44 |
| ubuntourist | make the computer unusable for other people. It will ignore everyone in favor of your task. | 13:44 |
| ubuntourist | Well, there is a command... "nice" which you use to tell your application to "play nicely with the other children 😉" | 13:45 |
| ubuntourist | You can set the "niceness level" to say "Even if this application would normally eat up all the resources, slow it down, hold it back, | 13:46 |
| tboimah_ | ACTION back | 13:46 |
| ubuntourist | lower the priority." | 13:47 |
| ubuntourist | tboimah_, I'll give you a second to catch up with the reading here. | 13:47 |
| tboimah_ | ACTION done | 13:49 |
| ubuntourist | (I don't know anything really about VIRT RES and SHR -- I'm guessing virtual, reserved and shared memory, | 13:49 |
| ubuntourist | but I never pay much attention to those values. I should probably learn, but I'd rather make music. 😉) | 13:50 |
| ubuntourist | "S" is status. status can be "sleeping", "reading", "writing". and others. It is "what, exactly, is the application doing at this | 13:51 |
| ubuntourist | second?" | 13:51 |
| ubuntourist | It's a long list, and Chapter 10, plus "man ps" will tell you more. | 13:51 |
| ubuntourist | ("man top" too.) | 13:52 |
| mulbah | alright | 13:52 |
| ubuntourist | OK... Start a separate terminal, and in that terminal type | 13:53 |
| ubuntourist | find / -iname "*" | 13:53 |
| ubuntourist | then, come back to the firstt terminal that you are sharing with me, and type "top" | 13:54 |
| ubuntourist | mulbah, no. | 13:54 |
| ubuntourist | In a separate terminal type the find command. | 13:54 |
| mulbah | okay | 13:55 |
| ubuntourist | tboimah_, do you have the find command running in a separate terminal? | 13:55 |
| tboimah_ | yeah | 13:55 |
| ubuntourist | tboimah_, I see it now. | 13:55 |
| *** mulbah has quit (Remote host closed the connection) | 13:56 | |
| ubuntourist | tboimah_, try P in the top terminal. | 13:56 |
| tboimah_ | okay | 13:57 |
| ubuntourist | And after a few seconds try M | 13:57 |
| ubuntourist | and then after a few seconds, try T | 13:57 |
| ubuntourist | tboimah_, Is find still working hard in the other terminal? | 13:57 |
| tboimah_ | yes | 13:58 |
| ubuntourist | Hmmm... I must have done something wrrong. I was trying to create a "spike" in the top list... | 13:58 |
| ubuntourist | The "find" command should be trying to find all files and directories on the computer, which I thought would make it very busy... | 13:59 |
| ubuntourist | Anyway, we can still work with it. | 14:00 |
| ubuntourist | mulbah, do you have find command running in a separate window? | 14:00 |
| mulbah | It was running | 14:01 |
| mulbah | but it stop | 14:01 |
| mulbah | cause it find all the files | 14:01 |
| ubuntourist | mulbah, start it again and we'll try to work faster. I want it running while we do something to it. | 14:01 |
| ubuntourist | tboimah_, if yours stops, restart it too. | 14:01 |
| tboimah_ | okay | 14:02 |
| ubuntourist | tboimah_, mulbah in your "top" terminal type q to stop top and then type -- while find is still running: | 14:02 |
| ubuntourist | ps auxwww | grep find | 14:02 |
| ubuntourist | ps. not pa. and three w's. not two. | 14:03 |
| ubuntourist | mulbah, find stopped again by itself... | 14:04 |
| ubuntourist | you typed --- find / -iname "*" | 14:04 |
| ubuntourist | right? | 14:04 |
| ubuntourist | tboimah_, now type: | 14:04 |
| mulbah | done | 14:05 |
| ubuntourist | kill -9 127844 | 14:05 |
| ubuntourist | mulbah, yours will be different | 14:05 |
| ubuntourist | Pooh. we're not fast enough.... | 14:05 |
| ubuntourist | OK... I have another idea... | 14:05 |
| ubuntourist | in the window where you typed "find", | 14:06 |
| ubuntourist | type "nano qwert" | 14:06 |
| ubuntourist | (We're creating a file with a stupid file name.) | 14:06 |
| ubuntourist | mulbah, No. in the other window. | 14:07 |
| tboimah_ | done | 14:07 |
| mulbah | done | 14:07 |
| ubuntourist | now, in the "ps" window, type "ps auxwww | grep nano" | 14:07 |
| mulbah | done | 14:08 |
| ubuntourist | tboimah_, good. Waiting to see the same on mulbah computer before continuing. | 14:08 |
| tboimah_ | okay | 14:09 |
| ubuntourist | mulbah, I' not seeing it. One window should be running nano, and the window you are sharing I should see | 14:10 |
| ubuntourist | ps auxwww | grep nano | 14:10 |
| ubuntourist | mulbah, good. | 14:10 |
| ubuntourist | Now I can explain: | 14:10 |
| ubuntourist | we used "ps" to see if any programs were active that have "nano" in the command. | 14:11 |
| ubuntourist | There are two programs: One was the "grep" command itself. (We asked grep to search the "ps" list to display any line | 14:12 |
| ubuntourist | containing nano and it found itself.) | 14:12 |
| ubuntourist | but we're interested in the other line. The first line that it returned "nano qwert" | 14:13 |
| ubuntourist | It tells us that for tboimah_ it is running in a terminal named "pts/2" and has a PID = 129681 | 14:14 |
| ubuntourist | It tells us that for tboimah_ it is running in a terminal named "pts/2" and has a PID = 129681 | 14:15 |
| ubuntourist | for mulbah it's running in "pts/5" (do you have several terminal windows open? more than two?) and a PID = 27236 | 14:15 |
| ubuntourist | So, now, in the same window, type the following and watch the nano window. (DON'T type in the nano window) | 14:16 |
| ubuntourist | THESE WILL BE DIFFERENT: DON'T TYPE THE SAME THING: | 14:16 |
| ubuntourist | tboimah_, YOU type: kill -9 129681 | 14:17 |
| tboimah_ | yeah | 14:17 |
| ubuntourist | mulbah, YOU type kill -9 27236 | 14:17 |
| ubuntourist | right. | 14:17 |
| mulbah | enter? | 14:17 |
| ubuntourist | And notice what happened in the other window. | 14:17 |
| ubuntourist | Yes enter. | 14:17 |
| mulbah | it stop nano | 14:18 |
| ubuntourist | (I wanted to do it with find because I thought find would go crazy for a long time listing lots and lots of files.) | 14:18 |
| tboimah_ | The process was kill and this tboimah@tboimah-successful:~$ show up in the nano file | 14:19 |
| ubuntourist | As a systems administrator, maybe one of your users will do something that they do not know how to stop. | 14:19 |
| tboimah_ | Mr. Cole can i ask a question? | 14:20 |
| ubuntourist | And you will have to stop it for them. But you are not near their computer. So, you ssh and look for whatever has gone wrong | 14:20 |
| ubuntourist | and then "kill" it. | 14:20 |
| ubuntourist | tboimah_, yes. ask. | 14:20 |
| tboimah_ | In the command we just type what is the function of the -9 in the command. | 14:21 |
| ubuntourist | Good question: I was just getting to that. | 14:21 |
| tboimah_ | Okay now i get it | 14:22 |
| ubuntourist | There when you "kill" a process you are sending a "signal" to it that says "STOP! INTERRUPT! WAIT!" | 14:22 |
| ubuntourist | the signal type tells the process why you asked it to interrupt what it was doing. | 14:23 |
| ubuntourist | "kill" is a bad choice for a command name: It doesn't always kill the process. It sometimes just interrupts. | 14:24 |
| ubuntourist | the two most common kill signals are "kill -15" and "kill -9" (SIGTERM and SIGKILL) | 14:25 |
| ubuntourist | You should always try -15 first: It says "Please try to stop the program in a way that preserves any work that is being done" TERMinate the program normally. | 14:26 |
| ubuntourist | Sometimes -15 doesn't work: The running process ignores the polite request. | 14:27 |
| ubuntourist | -9 is the atom bomb and says "Screw it. You wouldn't surrender quietly and nicely. Die. I don't care if you lose all the work. Just die." | 14:28 |
| tboimah_ | hahaha | 14:29 |
| ubuntourist | Some of the others are used for stopping only part of what the process is doing. Some are more of a "tap on the shoulder" | 14:29 |
| ubuntourist | that say "excuse me. could you briefly pause and then continue?" Or "could you quickly stop and restart without losing anything?" | 14:30 |
| ubuntourist | Like with "ps" status codes, there are too many kill signals for me to remember what each one does. I don't ever need | 14:31 |
| ubuntourist | most of them. -15 and -9 get used a lot. Once in a while -1 "SIGHUP" but usually, you only use SIGHUP because | 14:32 |
| ubuntourist | some documentation that you are reading says "for this application, use SIGHUP". | 14:33 |
| ubuntourist | We should all read Chapter 10 which I think will talk a lot about "ps", "top", "kill" and maybe "killall" wihich is similar to kill. | 14:34 |
| mulbah | okay the best sysadmin teacher in the whole world | 14:35 |
| ubuntourist | ACTION is skimming ahead in the book for a sseccond. | 14:35 |
| ubuntourist | The book includes "a gentle introduction to vi" later.. I suspect Jeff has already covered a lot of that. | 14:37 |
| ubuntourist | Editors are a very personal choice, and I personally don't like vi or vim. But a lot of smart people do. | 14:38 |
| ubuntourist | A lot of smart people also like emacs as their editor. I like emacs because I learned it a long, long time ago, on a computer | 14:38 |
| ubuntourist | that did not have vi or vim. | 14:39 |
| ubuntourist | nano is a good "beginner" editor, because it always provides help at the bottom of the screen, telling you which | 14:39 |
| ubuntourist | commands are available. So, I prefer it for instruction. I can say "Type Ctrl-X" and you can look at the bottom of your screen to | 14:40 |
| ubuntourist | see that Ctrl-X is for "eXit". | 14:40 |
| ubuntourist | But, eventually, you will want a better editor, and you should make every effort to learn as much as | 14:41 |
| ubuntourist | you can about your editor. Like with the keyboard shortcuts that were in Chapter 8, and the expansions in Chapter 7, | 14:42 |
| ubuntourist | Being able to edit well will save you a LOT of time. | 14:42 |
| *** mulbah has quit (Remote host closed the connection) | 14:44 | |
| ubuntourist | Suppose you have a file that is a 200-page book when printed. And maybe the original author has misspelled the same word | 14:44 |
| ubuntourist | thousands of times. You need to be able to use your ediitor to correct all of the mistakes quickly. You do not want | 14:45 |
| ubuntourist | to use your eyes to read every line of the book searching for mistakes. | 14:45 |
| ubuntourist | Or maybe you want to create a file and automatically number each line. Doing it manually will take too much | 14:46 |
| ubuntourist | time. | 14:46 |
| ubuntourist | So, practice keyboard shortcuts and whatever editor you choose so that you can quickly jump to the end of the file, the | 14:47 |
| ubuntourist | beginning of the file, the next paragraph, the previous paragraph, jump to a specific line (line 200 or something like that), | 14:47 |
| ubuntourist | advance 10 lines,, go backwards 20 lines, search for a specific string, jump to the end of the current line, jump to the beginning of the currrent line, | 14:48 |
| ubuntourist | find and replace text, etc. | 14:48 |
| ubuntourist | I'm going to leave the Gentie Introduction to VI (Chapter 12) and the Keyboard Shortcuts (Chapter 8) for you to practice a lot. | 14:50 |
| tboimah_ | Okay | 14:50 |
| mulbah | okay Mr. Cole | 14:51 |
| ubuntourist | But the next section of the book Chapter 11, and Chapter 13, talk about some of the stuff we've already done: | 14:51 |
| ubuntourist | Environment variables, and configuring our environment. | 14:51 |
| ubuntourist | for example, we have created an environment variable $PAGER and set the value to "most" | 14:52 |
| ubuntourist | using "export PAGER=most" | 14:52 |
| ubuntourist | and we made it permanent by putting it into the file ".profile" | 14:52 |
| ubuntourist | Chapter 11 will be a "deeper dive" into that, covering the same material but looking at what else is like that. | 14:53 |
| ubuntourist | (We also did some other stuff with environment variables before we played with $PAGER. We looked at $HOME and | 14:54 |
| mulbah | sure | 14:54 |
| ubuntourist | created a few silly environment variables to show how they worked. I know you're both taking notes like I suggested, | 14:55 |
| ubuntourist | so if you need to, go back and review your notes. | 14:55 |
| mulbah | Thanks for the teaching today Mr. Cole | 14:55 |
| ubuntourist | So, next time, we'll start fooling with the material in chapter 11. | 14:55 |
| ubuntourist | I'll try to read chapter 10 to see if there's anything super-useful there that we need to talk about, but | 14:56 |
| ubuntourist | the basics are "ps", "top" and "kill". with details about each one. | 14:57 |
| ubuntourist | OK. See you Friday. | 14:57 |
| mulbah | Mr. Cole | 14:57 |
| tboimah_ | Okay thank for today | 14:57 |
| ubuntourist | mulbah, question? | 14:57 |
| tboimah_ | Have a nice day | 14:57 |
| ubuntourist | tboimah_, you too. | 14:57 |
| mulbah | I and tboimah was thinking to ask you if you will be having chance in the night at your time because we meet Monday and Friday only and you can really teach us in these two days of the week but we relly want to finish the book soon and have all the necessary skills that a sysadmin should have | 14:57 |
| ubuntourist | Well, I'm volunteering. It's already 4 hours a week... Night my time would be REALLY late night your time. | 14:59 |
| mulbah | we are available any our | 14:59 |
| ubuntourist | I think we are getting to a stage where we should start using e-mail more. | 15:00 |
| mulbah | we just want to learn faster | 15:00 |
| ubuntourist | Read the book, try the examples and send me clear e-mail messages with questions and progress. | 15:01 |
| ubuntourist | I will think about trying to make an additional time free for continuing. | 15:01 |
| tboimah_ | Okay | 15:01 |
| ubuntourist | (We're already moving through the book pretty quickly. But when I watch you type in the terminal, | 15:01 |
| mulbah | Thanks so much Mr. Cole 😉 😉 😉 😉 | 15:02 |
| ubuntourist | I can see you need more practice to get your speed up. And those shortcuts and editing will make it much faster to | 15:02 |
| ubuntourist | communicate too. So, do practice those. A lot.) | 15:02 |
| mulbah | My computer keyboard is giving problem | 15:03 |
| mulbah | mostly the shift key | 15:03 |
| mulbah | so that why I take time to type | 15:03 |
| ubuntourist | mulbah, Ah. That's going to slow things down a bit. | 15:03 |
| ubuntourist | Still, knowing when to use TAB, double-TAB, Ctrl-R, Esc-<, Esc-> and stuff... Watch in your tierminal... | 15:04 |
| ubuntourist | Most of that was me just using Ctrl-something to jump to the beginning, jump to the end, delete a word, search for words, etc. | 15:07 |
| ubuntourist | I did not type left-arrow, left-arrow, left-arrow, backspace, backspace, backspace, up arrow, up arrow up arrow. | 15:07 |
| ubuntourist | That is a very slow way to do things. | 15:07 |
| ubuntourist | tboimah_, I just did the same sort of thing in your terminal window. | 15:09 |
| tboimah_ | yeah i saw it | 15:10 |
| mulbah | Thanks for today Mr. Cole | 15:11 |
| ubuntourist | Bye~~ | 15:11 |
| *** ubuntourist has quit (Quit: Leaving) | 15:11 | |
| mulbah | we really do appreciate all of your effort to was us | 15:12 |
| *** tboimah_ has quit (Quit: Leaving) | 15:12 | |
| *** mulbah has quit (Ping timeout: 480 seconds) | 15:48 | |
| *** mulbah07_ has quit (Quit: Leaving) | 15:50 | |
| *** shmohamud has quit (Remote host closed the connection) | 23:25 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!