Monday, June 23, 2008

Various installations for Week 5

My installations went really well. Installing a gui desktop in my Ubuntu server went perfectly. I pinged a known host and it worked. I installed the desktop. I connected to the internet and when I typed in the URL http://localhost/, a window opened saying "It Works!" I was really happy.

I installed Ubuntu Desktop in a virtual machine by following the YouTube videos. They made it really easy. When I checked the disk, it said I had no errors. That was great, because whenever I copied the ISO image to a disk it came up with errors.

I installed Webmin and it was a piece of cake! These installations went really well for me, which makes up for all of my struggling with the Ubuntu Desktop boot disk. It's really easy when you have step by step instructions.

Sunday, June 22, 2008

Server gone

I went back to open my server and my virtual machine was gone. I started to panic. I thought I would have to do everything all over. But then I did a file search in my start menu for .vmx files and I found it. What a relief!

Monday, June 16, 2008

Some commands I tried in the Linux server

My exercises all went fine. Nothing went wrong when configuring the two files using nano.

When in the server, I tried many commands. The following are some of them.

ls showed me my home files.

ls /bin showed me a screen full of files.

ls –l showed me the home files in long form.

ls -1 /etc /bin showed a couple pages of files.

ls –la .. showed four lines, the first line said “total 12.” The next three were
drwxr-xr-x 3 root root 4096 2008-06-09 19:35 .
drwxr-xr-x 21 root root 4096 2008-06-09 19:27 ..
drwxr-xr-x 2 megan megan 4096 2008-06-15 20:15 megan

cd /etc and then ls to see files. One file was named magic.

less magic went into something and I wasn’t sure what it was. I couldn’t get out. I finally just pressed a bunch of buttons and a screen called “Summary of Less Commands” came up. I scrolled down and it gave more instructions on how to search, jump, change files, miscellaneous commands, options, and line editing. When I got to the bottom, I pressed q to get out. But then I was in the same stuck place. Finally I typed :q and got back to the command line.

ls –lt head got the same results as ls –la.

du sort –nr got the results:
44 .
40 ./megan

grep stop\)* and nothing came up. Then I didn’t know how to get the command line back again. I tried :q, but it didn’t work.

Vim Text Editor

I installed the vim text editor tutorial and the installation went fine. I went through the tutorial and I thought that it was ok. It was pretty different from any text editor I have ever used because it is modal. It was weird pressing escape to get back to the normal mode. The directional letters took a little while to get used to, but it was not bad since they are in a line on the keyboard. There were a lot of commands that I like and that seemed to save a lot of time using over other text editors. An example is the d command to delete. It is especially useful being able to add a number to delete several words in a row (d5w) or typing dd to delete a whole line. I also like the replace command (r). I did get confused a little in the substitution section. It's cool that you can also do outside commands within the text editor. At one point accidentally hit v before I got to the part about what v does and had a hard time getting out of it.


Monday, June 9, 2008

Tutorials

The tutorials from UA CBT were fairly easy to understand. I did not get everything that he said, but it will make more sense once I try out the commands he talked about. I liked that the videos weren't too long. Plus, he sounded really nice. I watched these tutorials before reading any of the other print tutorials. I liked how he talked about what was in each directory. I also liked how he explained the way files are displayed and what it means. I also liked the find and grep utilities. Those were interesting. I didn't really understand the linking part.

The Learning the Shell lessons were easy to understand. I really like how things are broken down into small lessons. It made me wonder if I should try using a mouse.

The YouTube videos (Part 1: http://youtube.com/watch?v=S30OUYsu2Qo, Part 2: http://youtube.com/watch?v=jEcAD1cMWIY, Part 3: http://youtube.com/watch?v=sNL512ScRfs) for installing the Ubuntu Server were really helpful and easy. The only thing is that in the beginning, it starts with VMware server and I was using VMware Workstation, but that was no big deal. And I didn't have the problem in the end with the kernel issue. Mine restarted fine after the install. It was nice having it playing while I was doing it. It was reassuring to be able to see the same thing happening on my screen as in the videos.

Installing Ubuntu Server in VMware Workstation

This went a lot better for me that Ubuntu Desktop. I followed the YouTube video instructions and it was pretty easy. In the beginning it mentioned something about the VM Workstation clocking my CPU speed to be so many MHz but Windows reports that it is a different number of Mhz and this will make the clock lag or something. I should have written it down. I clicked ok and then I got another message saying that it couldn't connect to a virtual device floppy and asked if I wanted it to attempt to connect to this drive every time I powered on, and I said no. After that, every thing went smoothly. I chose to install the LAMP and OpenSSH servers. I then tried out some commands at the end wehen it rebooted and I logged on for the first time. From my home directory, if I enter "ls", I only get one file (named "megan" - my username). I wonder if this is right.

Ubuntu Desktop Part 2

I tried to burn another cd, because my first one didn't work. The first cd I burned said there was an error before it finished burning. The second cd burned, but wouldn't boot. The third cd I burned would boot, but when I selected check cd, it said, "Error reading boot cd."

So, I downloaded Ubuntu Desktop again. I did the MD5 check and it was fine. I burned a cd again, and it got an error again before finishing. The second cd wouldn't boot, and when I checked it in My Computer, it said it was blank. I reinstalled the ISO Recorder. I then burned another cd, it booted, I selected check cd, and it said it had 9 file errors!! I then selected "Try Ubuntu without any change to your computer," and the Desktop did come up after several minutes. So I played around for a little while. I checked out all of the games and applications. I messed around with OpenOffice, which is pretty much like MS Office 2003 (Word, Excel, and PowerPoint). I went to the Terminal and played around with the commands.

Next, I am going to try burning Desktop on a different computer because mine is obviously having a lot of issues with it.

Sunday, June 8, 2008

Trying to boot Ubuntu Desktop

First I put in the Desktop boot disk and restarted by computer. The Ubuntu screen came up and I was asked to pick a language. Then I scrolled down to check the cd. It said it was loading the Linux kernel. I thought it might be stuck at first, but after a couple of minutes it said it was checking the integrity. This took about 5 minutes, at which point it said that it found errors in 6 files. It asked me to press any key to reboot, which I did. It then asked me to pick a language again. Then I selected "Try Ubuntu without any change to you computer." It said it was loading the Linux kernel again. It said it was 100%, but then it just sat there. After about 20 minutes, I pressed F1 for help. It then thought for a while and then started rapidly repeating a couple of lines over and over. I tried to write them down, but they were going so fast it was hard to read. I think that it said:

SQUASHFS error-
unable to read page block 29f9fc73
sb_bread failed reading block Oxa7e8d

I wonder if I should just download Ubuntu again and create a new cd?

By the way, I booted the cd on the computer I burned it on. I did the MD5 check and it was correct.

Saturday, June 7, 2008

Ubuntu Forums

I was reading in the Ubuntu forums and came across a post from someone who who having trouble booting Ubuntu for the first time. Everyone who responded was really nice to him and patient. He had downloaded Ubuntu, checked winMD5Sum to make sure it was ok, and burned a boot cd. But when he runs the cd to boot Ubunt, it freezes. Several people tried to help him. Some of their help was hard for me to understand, and I wondered how he understood it if he was new to Ubuntu. One of the replies looked like this:

"HI there, ive got the same laptop as you, to get it working under 8.04 you need to do the following.
download the ubuntu alt CDat the cd boot prompt press F6 and type in noapic.
once installed to your liking and you have rebooted, let the os load up, once its stoped at loading local scripts press alt F2 and login.
you need to install and configure the xorg-driver-fglrx via envyng.Type (each line individually separated by return)
Code:sudo bash *//..and then enter your password, this logs you in as root.
update-pciids
apt-get update
apt-get install build-essential
apt-get install envyng-core *// Installs Video Driver Install system.
envyng-t
Select option 3 to install the ATI Preparatory video driver.
shutdown now *// shuts down the computer, reboot and let it load.The xserver should load up.

To get the wirless working with your card, if its the same as mine, Atheros AR5007EG you need to download and patch the madwifi kernel modual.
Loadup the terminal (applications > accessory's > terminal) and type..
Code:sudo bash *//Same as before.
apt-get install build-essential *//Installs a build inviroment.
wget http://snapshots.madwifi.org/special/madwifi-ng-r2756+ar5007.tar.gz
tar zxvf madwifi-ng-r2756+ar5007.tar.gz
cd madwifi-ng-r2756+ar5007
sudo make uninstall
sudo make clean
sudo make
sudo make install
sudo modprobe ath_pci *//loads the patched ath_pci module....and then reboot."

Wow! That seems pretty crazy to me. And intimidating. And this post was for someone who hadn't even gotten it installed or running yet. I thought that was pretty interesting. It was cool that so many people took the time to help and he did get it running in the end.