Func Module ‘Yumcmd’ Enhancement Project

I have just created a Project page on Wiki for my project work . Project work is enhancement of Func based module named ‘Yumcmd’. Its Just a beginning. Here is link to my project page.

Yumcmd Enhancement Project Wiki Page

Suggestions & help would be really appreciated.

LPT 730 lab#06 (Unit Conversion Calculator) Java Script

Hi Everybody

Here is link to my lab work for LPT#730 Unit Conversion calculator.It works well for Weight & length conversion.

length:
Meters to Feet
feet to meters
Weight
Kilograms to pound
pound to kilograms

Unit Conversion Calculator XHTML/Java Script

it needs some more work to be do print logs history.

Review Questions for SYA710 test1

Hi LUX guys, here is link to review questions for LUX SYA-710 test.I hope it may help.

Installing from source & packaging

To do the practice for lab work of ‘Installation from source’ &  Packaging I have down loaded the source tar ball for supertuxkart, a linux game.

I have went through the experience of how to install the software from source & how to packaging it as well. i have done this in two phases. step are given below. Hope fully my blog post for this experience will help.

Installation from source:

1. Down loaded the tar file from sourceforge.net

2. Extract the source file with #tar xvf <tar.gz file.name>

3 ./configure (this step require some addition dependencies.including the free-glut-devel at the time of “make’ .

4. make

5. make install

its running well

Screen short from Supertuxkart Linux game

Second phase

Packaging:

1:  rpmdev-setup tree

2. copy the source tarball in to ~/rpmbuild/SOURCES dir

3. cd ~/rpmbulid/SPECS

4. rpmdev-newspecs supertuxkart-0.4

5. vi supertuxkart-0.4.spec edit spec file (name & version column are very important should be same as original source tar ball)

6. rpmbuild -ba supertuxkart-0.4.spec (this step give an error message )

RPM build errors:
    Installed (but unpackaged) file(s) found:
   /usr/bin/supertuxkart
   /usr/share/applications/supertuxkart.desktop

this problem get solved by making entry for each directory in the spec file under %files section e.g.

for error for "/usr/share/applications/supertuxkart.desktop"
i made an entry in "spec" file under %files 

/usr/share/applications

then aagin "rpmbuild -ba supertuxkart-0.4.spec"

every thing went fine & successful

 supertuxkart-RPMS and -SRPMS   


References:

1. Class notes SPR720 (prof Chris Tyler)
2. On line help on IRC #seneca by prof. Chris Tyler
3. Thanks to prof. Chris Tyler for his time for me to help even at weekend.

Fedora 9 Booting from another harddisk

it is all about yesterday’s (oct 2nd, 2008)  SYA710 lab we all had newly installed fedora 9 on /dev/sdb. Due to some reason we have to change parameters at grub prompt. Here is explanation what i know..

So first of all we have to tell the grub actually where the kernel (vmlinuz &  initrd) is residing. it is represented by hard disk number + partition number. steps are given below.

step 1. grub>find /grub/stage1 (we can skip this step for our lab because we know that where the linux kernel is). so we can start from step 2.

it will gave us output (hd1,0).

Then we have to set root with command. But in our lab’s case we know that we have installed the linux on harddisk, which is ‘/dev/sdb’. so the command would be root(hd1,0). please note that it is hd1 not sd1.it is grub language.

step 2.: grub> root (hd1,0)

Now we have to tell the kernel which hard disk + partition has the ‘/’. (please note it not root’s home dir.), rather it is  the ‘/’ (root (top) of the file system

we can find that with

step 3: grub> find /etc/passwd (this command sometime dont work if the file system contains logical volumes. then we have to use linux boot disk to find the ‘/’ partiton.)

so if the  out put of above command is

(hd1,1)

then we will invoke the command..

step 4:grub> kernel /vmlinuz-<pressing tab will comlete the command automatically>  ro root=/dev/sdb2

This command tells the kernel on which hard disk’s which partition the ‘/’ of the file system is . In our case we had given /dev/sdb2 in response to (hd1,1). The thing is simple grub starts numbering   the hdds from zero (0) (NOT 1) i.e. hd0,hd1,hd2 & partitions with 0, 1, 2…..3.

But the kernel starts form 1 (not form zero)

kernel          hard disk & partition number          GRUB

sda1 hard disk 1, partition 1                           hd0,0

sda2 hard disk 1, partition 2                           hd0,1

sdb1 hard disk 2, partiton1.                            hd1,0

sdb2 hard disk 2 partition 2                            hd1,1

step 5:grub> initrd  /initrd…. < pressing tab wil complete the command>

step 6:grub> boot

This is how it works.

I hope you all would find it helpful.