======Part 1====== =====Entries===== ====Entry 1: January 24, 2012==== Today I experienced some trouble with the Class Chat. The ctrl + a release both tap d wasn't working on my original chat so i made a new one. With the new chat up I first tested that i could detatch from the chat with ctrl + a release both tap d and it worked so i was happy. But sadly, when i reattched to the chat i realized i couldn't type anything. So after again making a new one that works correctly now i still can't get rid of the one that i can't type /quit in. Hopefully the answer will dawn upon me sooner than later but having to take the long way into talking to my class mates is well worth it for their help. ====Entry 2: January 25, 2012==== Today Wedge helped me learn a new command "the 'kill' command". A little bit about the "kill" command: kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]. What the kill command does is that it your having trouble with a bash (like i was with the screen) you issue this command to terminate the process. The reason why it was related to the course is because that I was having trouble with my screen that i couldn't do anything in. After wedge issued the kill command on the process I didn't have to use screen -r 23478 to re-attatch myself to the classroom chat screen that worked. Maybe the kill command can help you guys out if you have a troublesome bash. ====Entry 3: February 5, 2012==== This is my attempt to make an ASCII tree of my home directory. {{:opus:spring2012:mfaucet2:unix_ascii_chart.xlsx|}} ====Entry 4: Feburary 29, 2012==== Lately the labs and case studies have been easier to understand. I don't really know why but I think it's because the way I have been thinking lately (more out of the box) has really helped in figuring out the "puzzles" in the labs. I don't really know much of languages but I have been learning on how to write in pseudocode (<--sp?) and if it doesn't make any sense to anybody let me know and i will try and make it more clear to them. =====Keywords===== {{page>unixpart1&nofooter}} =====Experiments===== ====Experiment 1==== ===Question=== Can I remove more than 1 file while using the "rm" command? ===Resources=== None used ===Hypothesis=== I believe that I can remove more than 1 file at a time using the "rm" command because with the "touch" command I can create more files with 1 command. ===Experiment=== I have already created files using the touch command and I will use the rm command to see if i can remove them all at once. ===Data=== lab46:~/messaround$ ls example.txt example1.txt example2.txt example3.txt lab46:~/messaround$ rm example.txt example1.txt example2.txt example3.txt rm: remove regular empty file `example.txt'? yes rm: remove regular empty file `example1.txt'? yes rm: remove regular empty file `example2.txt'? yes rm: remove regular empty file `example3.txt'? yes lab46:~/messaround$ ls lab46:~/messaround$ ===Analysis=== My hypothesis was correct and through typing the file names after the first I was prompted to delete them all, but it was still prompting me one at a time for each file. ===Conclusions=== I have discovered that the touch command along with the rm command have some similarities with each other in that they can both manipulate multiple files at once. ====Experiment 2==== ===Question=== Am I able to remove a directory while it still has files in it? ===Resources=== None used ===Hypothesis=== I believe I will be able to remove the directory that has files in it because it would be like removing a folder in a GUI environment, where if it has files in it the user would just be prompted if he/she would want to remove the folder or in a CLI enviroment a directory. ===Experiment=== I have a mess around directory that has nothing important in it and have four files that are blank. After using the rmdir command on /messaround hopefully the directory will be removed. ===Data=== lab46:~/messaround$ ls example.txt example1.txt example2.txt example3.txt lab46:~/messaround$ cd .. lab46:~$ rmdir messaround rmdir: failed to remove `messaround': Directory not empty lab46:~$ ===Analysis=== My hypothesis was incorrect. The directories in a cli are different than folders in a gui environment; tho they have the same purpose. ===Conclusions=== I have found that in order to remove a directory, whatever is in it must also be removed in order to remove the directory. ====Experiment 3==== ===Question=== Can I attach to an active screen? ===Resources=== None used ===Hypothesis=== I don't believe I can attach to an active screen, because I'm technically already on it. i would have to detach myself then reattach myself to the screen. ===Experiment=== I'm going to exit out of the screen by exiting my virtual machine and seeing if the screen is attached. If it is I can further go the experiment by using screen -r to reattach myself to the screen, if not I will have to use screen -d then screen -r to reattach myself to the screen. ===Data=== lab46:~$ screen -ls There is a screen on: 23478.pts-5.lab46 (01/24/2012 12:43:26 PM) 1 Socket in /var/run/screen/S-mfaucet2. lab46:~$ screen -r There is a screen on: 23478.pts-5.lab46 (01/24/2012 12:43:26 PM) (Attached) There is no screen to be resumed. lab46:~$ screen -d [23478.pts-5.lab46 detached.] lab46:~$ screen -ls There is a screen on: 23478.pts-5.lab46 (01/24/2012 12:43:26 PM) (Detached) 1 Socket in /var/run/screen/S-mfaucet2. lab46:~$ screen -r [detached from 23478.pts-5.lab46] lab46:~$ ===Analysis=== Based on the data collected: My hypothesis was correct as shown above. I could not attach to a attached screen because it was already on. After detaching the screen i was then able to attach myself to the detached screen. ===Conclusions=== I have learned that screens are like different sections of the server. If they are accessed when somebody is already on their screen they will either have to: make another screen, detach from the active screen and reattach themselves to it, or use screen -x to override the attached screen error.