Linux Days 2-4

We have spent the last few days installing and messing around in SUSE linux. We chose the gnome desktop option, because that was the one we were most familiar with. One main issue we had was that the networking abilities of our computer were limited, but we managed to finally get the drivers and get access to the internet. Unfortunately, we can not figure out how to assign a static IP address, and continue to connect to the internet, so we have resorted to staying on DHCP. Hopefully tomorrow we will install Sabayon, and our homework tonight is to download a version of it. But as for class today, we just looked around, explored, poked, and prodded all the information that we could out of SUSE. We worked on our packets and explored the disk setup of linux. We also experimented with the terminal, and figured out how to give our account root privileges. sudo -l and your root password ftw. Now, I'm off to download a sabayon .iso. So long reader/s

Linux Day 1

We started our linux unit today, on top of making our bartpe disk, we also installed suse on our group computer. At first, we got errors because it couldn't resize our partitions properly, and would stop installing, so we had to restart the installation. On our bartpe disk, we are changing the background, and I made a super awesome background and Jose shopped it. It is a triforce that's made of triforces, which are made out of triforces, which are made out of alt code triangles. Its pro.

DOS and stuff continued

To elaborate, GPartED is the Gnu Partition Editor. What it does is boot from a cd and gives you an environment to partition your hard drives in whatever format you like. Partitioning is basically, making multiple virtual hard drives on one real, physical hard drive. As I said earlier, our group formatted our one hard drive in a 50%/25%/25% set up with the 50% for Windows, and 25% for ubuntu, and 25% for other, that I don't know about yet. http://lmgtfy.com/?q=Gparted


To explain what we did in DOS, one must start at the beginning. We learned how to navigate to the root directory, the syntax of which is cd\
When we were there, we made our own folders with the mkdir command.
We then copied many crucial system files to our folders, and used the attrib command to change our viewing properties. We learned the syntax to address all files, and all files of a certain type.
We then used basic FTP to upload and download files from a server. We learned how to stop a shutdown, and to control-c out of dumb batch files.
http://lmgtfy.com/?q=MS+Dos+commands

Then we took a DOS test, and I got a 95, because my slashes were wrong :(. But all in all, the last two weeks were cool, because I'm in T's class.

CRAZY FOOL DOS

First of all, we GPartED our hard drives and made three partitions, 50%, 25%, and 25%.
So, we did some basic DOS navigation and manipulation. DOS stands for Disk Operating System. We moved around through directories and drives, copied files from one folder to another. One of our problems was to copy NTLDR off a windows XP cd. We learned how to put and get files off of a FTP, and learned how to stop a computer shutting down with shutdown -a. And we learned to ctrl-C out of stupid batch files. I already knew most of this stuff, but there was some that I didn't, so all in all, I'm glad that we did basic DOS skill building.

Se-cuh-ri-dee

Well, on our computer, we installed deepfreeze, and created an image of our computer, to be rebooted whenever the computer shut down. Unfortunately, this conflicted with our use of GPEDIT.MSC . Because deepfreeze resets the computer, gpedit settings could not be saved. If you tried to do GPEDIT, the you could not deepfreeze, because you didn't have the permission to save and access/install the package. Through an interesting amalgam of both, although I'm not sure of the specifics, we limited computer rights and created a deepfreeze on our hard drive. So our computer was relatively secure. When we went to hack the SuperTrooper's computer, we used OPHcrack to try and find out their admin password. Unfortunately, booting to this cd, or something else we did early on in the competition messed up their computer. We used ERD commander to edit the registry from a live CD, and changed to path of the wallpaper to get it from the C:\ drive, where we saved our logo. It didn't work that way. We booted up and the background didn't change. Then the computer froze again. So we decided the only way to fix this problem was to do a repair install of XP. We did this, waited for 20 minutes, only to have the installation freeze. We assumed that the only logical path of action would be to reformat, which was against the rules. So near the end, we sat for a while, then we told T the situation, and he ended the contest, because it was really supposed to be over anyway. So we tied with the superlosers, and the now 4 stooges.

Overclocking

The week before last, we over clocked our computer. Our processor was up to 4.11ghz, and we left our RAM and video card alone. We topped the class in raw processor power and calculations, but overall, our computers performance was average.

PIMP MY 7

Today we are presenting our windows 7 tweaks to the entire class. We changed the theme, added programs, used fences and cube desktop etc... its pretty boss.