Job Description of A Programmer Analyst
---------------------------------------
1. Plans, develops, tests, and documents computer programs, applying knowledge
of programming techniques and computer systems.
2. Evaluates user request for new or modified program. Consults with user to
identify current operating procedures and clarify program objectives.
3. Formulates plan outlining steps required to develop program, using
methodologies such as structured analysis and design or object-oriented
development.
4. Captures requirements using industry standard development frameworks and
tools.
5. Designs reports, forms and letters along with computer terminal screen
displays to accomplish goals of user request.
6. Reviews screens, reports, forms and letters designs with users.
7. Converts project specifications, using industry standard tools, such as
object-oriented tools, into sequence of detailed instructions and logical
steps for coding into language processable by computer, applying knowledge
of computer programming techniques and computer languages.
8. Enters program codes into computer system.
9. Enters commands into computer to run and test program.
10. Reads computer printouts or observes display screen to detect syntax or
logic errors during program test, or uses diagnostic software to detect
errors.
11. Replaces, deletes, or modifies codes to correct errors.
12. Analyzes, reviews and alters program to increase operating efficiency or
adapt to new requirements.
13. Writes documentation to describe program development, logic, coding, and
corrections. Writes manual for users to describe installation and operating
procedures.
14. Assists users to solve operating problems.
Thursday, March 5, 2009
Programmer Analyst
Monday, March 2, 2009
Spyware Removal guide
Spyware Removal guide
For those that don't know, spyware is bad, spyware is really bad. It also has many different names. Like adware, malware, badware, trojans, worms, downloaders, junkware, etc. Whatever you call it it's bad and you need to know how to get rid of it. The most common method people use to remove spyware is to download some software from Download.com and run that to remove the spyware. This method works ok most of the time but it usually takes much longer than I would ever want to spend on a computer. This spyware removal guide presents a much faster more effective way.
To understand how to deal with spyware you first have to understand how it works. It gets on a computer by attaching itself to, or disguising itself as, some useful piece of software. Kazaa is the classic example of that It is a useful piece of Peer to Peer software but it is packed full of spyware. The first thing that spyware does when it is on a computer is add itself to various parts window's registry so that it will be loaded when windows starts up. So the first thing you need to do is removed these various registry entries so that you can then remove the spyware.
To do this you will need to use some cool software. The first cool software you should use is called msconfig. It is installed standard on Windows XP, Windows ME and Windows 98. It is not included with Windows 2000. Don't ask me why. I always run this right off before I do anything else. To access it all you have to do is click the Start button. Then click on Run and type in "msconfig" and click "ok". You are greeted with the System Configuration Utility. You can disable most start up items by clicking on "Selective Startup" and uncheck "Load Startup Items". If you do this most of the stuff that normally starts up will not start up when you reboot your computer. Then go to the Services tab and Disable all non-Microsoft services. Don't be timid in disabling anything in this utility. There is nothing you can do that will permanently damage Windows because you can always come back to this utility and undo your changes.
After you have ran msconfig I would reboot the computer into safe mode. You can do this by pressing "F8" while windows is starting up. Sometimes it hard to know when to do this. It's after your computer goes out of the bios and boots off the hard drive you should press F8. If in doubt repeatedly press F8 while the computer is starting up. The advantage of being in safe mode is that none but the cleverest Spyware is loaded in Safe Mode. In safe mode it is time to try the powerful program known as HiJackThis.exe. HiJackThis functions like msconfig but it is much more thorough at finding possible spyware problems. The rule to follow when using HiJackthis is, "If you don't know what it is get rid of it." When you run a scan with HiJackThis you will be presented with a list of possible spyware found in the registry. Keep in mid that it is possible spyware, just because it is there it doesn't mean it is bad. Most of the stuff listed here will be extensions to Internet explorer and stuff like that. Everything listed is optional. Your computer will work perfectly fine even if you removed everything listed. Once you check those things that you want to remove and you click "Fix Checked", restart your computer in normal mode and you should have about 90% of your spyware removed.
To find out if you have successfully removed all the spyware, start HiJackThis again and do a scan. If you find anything listed that you had previously removed that means that the spyware is still on your computer somewhere and has come back to plague your existence. At this point it is hard to give you an exact procedure on how to remove the remaining spyware. Probably the easiest thing to do is download a good spyware scanner and run that. You can see a list of the ones I recommend at the Spyware Scanners page. If the spyware scanners still fail to remove the spyware than you'll have to find a more involved procedure. A sure fire method of removing a known spyware file is by booting into an entirely different operating system and manually deleting it.
When you ran HiJackThis you probably noticed a file name associated with. This is most likely the file that is run when windows starts up that activates the evil spyware process. If you thought, "I'll just delete this file." It would be a great idea but if you tried to do so you probably came across the error, "Access Denied, file may be in use" or something like that. Don't ask me why but Windows is unable to delete a file if it is in use. There is absolutely no reason why this has to be the case. I have no problems deleting executables of running processes in Linux. Anyway, to delete this file you need to boot the computer from a different medium, the most convenient is probably a CD. The best type of bootable CD for spyware removal purposes is probably Bart's PE. You can find information on how to build a bootable CD with windows XP and spyware removal tools here.
If you took a look at that you probably noticed that it was a rather complicated procedure. It is quite possible that you already have a boot CD that will do what you need to do. If you have a windows Installation CD you could boot from it and then press 'r' to enter the recovery console. Sometimes it will ask you for your administrator password. If you don't know it try just pressing enter. If that doesn't work see Windows Password Recovery Guide for information on how to reset administrator passwords. Once you are presented with a prompt you can issue DOS commands like, "del /Path/to/file/filename.exe" to remove the offending file that you found with HiJackThis.exe (you did wright that file name down, right?).
Hopefully this spyware removal guide has helped you get your computer working as good as the day you purchased it. Of course this all would have been avoided if you had just used Linux. Don't forget to check out Spyware prevention once you get all the spyware removed.
Copyright © 2007–2009 by NNU Computer Whiz. All rights reserved.
For those that don't know, spyware is bad, spyware is really bad. It also has many different names. Like adware, malware, badware, trojans, worms, downloaders, junkware, etc. Whatever you call it it's bad and you need to know how to get rid of it. The most common method people use to remove spyware is to download some software from Download.com and run that to remove the spyware. This method works ok most of the time but it usually takes much longer than I would ever want to spend on a computer. This spyware removal guide presents a much faster more effective way.
To understand how to deal with spyware you first have to understand how it works. It gets on a computer by attaching itself to, or disguising itself as, some useful piece of software. Kazaa is the classic example of that It is a useful piece of Peer to Peer software but it is packed full of spyware. The first thing that spyware does when it is on a computer is add itself to various parts window's registry so that it will be loaded when windows starts up. So the first thing you need to do is removed these various registry entries so that you can then remove the spyware.
To do this you will need to use some cool software. The first cool software you should use is called msconfig. It is installed standard on Windows XP, Windows ME and Windows 98. It is not included with Windows 2000. Don't ask me why. I always run this right off before I do anything else. To access it all you have to do is click the Start button. Then click on Run and type in "msconfig" and click "ok". You are greeted with the System Configuration Utility. You can disable most start up items by clicking on "Selective Startup" and uncheck "Load Startup Items". If you do this most of the stuff that normally starts up will not start up when you reboot your computer. Then go to the Services tab and Disable all non-Microsoft services. Don't be timid in disabling anything in this utility. There is nothing you can do that will permanently damage Windows because you can always come back to this utility and undo your changes.
After you have ran msconfig I would reboot the computer into safe mode. You can do this by pressing "F8" while windows is starting up. Sometimes it hard to know when to do this. It's after your computer goes out of the bios and boots off the hard drive you should press F8. If in doubt repeatedly press F8 while the computer is starting up. The advantage of being in safe mode is that none but the cleverest Spyware is loaded in Safe Mode. In safe mode it is time to try the powerful program known as HiJackThis.exe. HiJackThis functions like msconfig but it is much more thorough at finding possible spyware problems. The rule to follow when using HiJackthis is, "If you don't know what it is get rid of it." When you run a scan with HiJackThis you will be presented with a list of possible spyware found in the registry. Keep in mid that it is possible spyware, just because it is there it doesn't mean it is bad. Most of the stuff listed here will be extensions to Internet explorer and stuff like that. Everything listed is optional. Your computer will work perfectly fine even if you removed everything listed. Once you check those things that you want to remove and you click "Fix Checked", restart your computer in normal mode and you should have about 90% of your spyware removed.
To find out if you have successfully removed all the spyware, start HiJackThis again and do a scan. If you find anything listed that you had previously removed that means that the spyware is still on your computer somewhere and has come back to plague your existence. At this point it is hard to give you an exact procedure on how to remove the remaining spyware. Probably the easiest thing to do is download a good spyware scanner and run that. You can see a list of the ones I recommend at the Spyware Scanners page. If the spyware scanners still fail to remove the spyware than you'll have to find a more involved procedure. A sure fire method of removing a known spyware file is by booting into an entirely different operating system and manually deleting it.
When you ran HiJackThis you probably noticed a file name associated with. This is most likely the file that is run when windows starts up that activates the evil spyware process. If you thought, "I'll just delete this file." It would be a great idea but if you tried to do so you probably came across the error, "Access Denied, file may be in use" or something like that. Don't ask me why but Windows is unable to delete a file if it is in use. There is absolutely no reason why this has to be the case. I have no problems deleting executables of running processes in Linux. Anyway, to delete this file you need to boot the computer from a different medium, the most convenient is probably a CD. The best type of bootable CD for spyware removal purposes is probably Bart's PE. You can find information on how to build a bootable CD with windows XP and spyware removal tools here.
If you took a look at that you probably noticed that it was a rather complicated procedure. It is quite possible that you already have a boot CD that will do what you need to do. If you have a windows Installation CD you could boot from it and then press 'r' to enter the recovery console. Sometimes it will ask you for your administrator password. If you don't know it try just pressing enter. If that doesn't work see Windows Password Recovery Guide for information on how to reset administrator passwords. Once you are presented with a prompt you can issue DOS commands like, "del /Path/to/file/filename.exe" to remove the offending file that you found with HiJackThis.exe (you did wright that file name down, right?).
Hopefully this spyware removal guide has helped you get your computer working as good as the day you purchased it. Of course this all would have been avoided if you had just used Linux. Don't forget to check out Spyware prevention once you get all the spyware removed.
Copyright © 2007–2009 by NNU Computer Whiz. All rights reserved.
Friday, February 27, 2009
Convert UIF to ISO
Convert UIF to ISO
The fastest way to convert an UIF image to ISO image is UIF2ISO. It is a speedy command line tool, that will save you the hassle of installing wine and MagicISO.
This is how I downloaded and installed UIF2ISO, written by Luigi Auriemma.
1. We first need to install zlib and OpenSSL with apt-get.
sudo apt-get install zlib1g zlib1g-dev libssl-dev build-essential
2. Now we can download UIF2ISO with wget from a terminal, or from the author’s site here.
wget http://aluigi.altervista.org/mytoolz/uif2iso.zip
3. Once you have the file downloaded, unzip it and cd into the directory.
unzip uif2iso.zip
cd src
4. Finally compile the source, and create the executable.
make
sudo make install
5. Now you can convert the .uif file to an .iso with the following command:
uif2iso example.uif output.iso
Mounting an ISO
You don't necessarily need to burn a cd in order to access the files within the ISO. You can mount it with some simple commands.
Here is how to mount the ISO from command line.
sudo modprobe loop
sudo mkdir ISO_directory
sudo mount /media/file.iso /media/ISOPoint/ -t iso9660 -o loop
Tuesday, February 24, 2009
Get UUID info
[root@localhost alex]# blkid /dev/sda1
/dev/sda1: UUID="0E3CCDE13CCDC445" LABEL="HP_PAVILION" TYPE="ntfs"
[root@localhost alex]# ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 2009-02-24 10:07 0E3CCDE13CCDC445 -> ../../sda1
lrwxrwxrwx 1 root root 10 2009-02-24 10:07 3864DD9564DD566A -> ../../sda3
lrwxrwxrwx 1 root root 10 2009-02-24 10:07 3f480ba3-8683-452e-b355-cba2480b2a0a -> ../../sda9
lrwxrwxrwx 1 root root 10 2009-02-24 10:07 51d4ad6a-673a-44c4-884c-fcbf14a8ea28 -> ../../sda5
lrwxrwxrwx 1 root root 10 2009-02-24 10:07 6dd1961e-dc7c-4bf7-9fb2-70ff72eabecc -> ../../sda8
lrwxrwxrwx 1 root root 10 2009-02-24 10:07 d94a3fcf-5b25-4320-8510-c21ce9691586 -> ../../sda7
lrwxrwxrwx 1 root root 10 2009-02-24 10:07 dbaa1464-8820-4965-b9e8-c7f13dc9784b -> ../../sda6
lrwxrwxrwx 1 root root 10 2009-02-24 10:07 e17520dd-565c-4e2e-b594-f9a0da78fbc8 -> ../../sda2
Downloading Oracle 9i
Oracle9i Database Release 2 (9.2.0.4) Enterprise/Standard Edition
for Linux x86-64
Oracle9i Database Release 2 (9.2.0.4.0) for Linux x86-64
Download the Complete Files
amd64_db_9204_Disk1.cpio.gz (423,559,952 bytes) (cksum - 2519016497)
amd64_db_9204_Disk2.cpio.gz (578,948,873 bytes) (cksum -721603952)
amd64_db_9204_Disk3.cpio.gz (334,834,987 bytes) (cksum - 1896810138)
Directions
1. Uncompress the file using "gunzip".
[root]# gunzip amd64_db_9204_Disk1.cpio.gz
2. Extract the file resulting from the step above using "cpio"
[root]# cpio -idcmv < amd64_db_9204_Disk1.cpio
Tuesday, February 17, 2009
Harnessing Hibernate by Elliott,O'brien & Fowler
Harnessing Hibernate
by Elliott,O'brien & Fowler
CHAPTER 1: Installation and Setup
---------------------------------
1.Getting and Installing an Ant Distribution
1.1.[root]# cd /opt
1.2.[root]# wget http://www.ibiblio.org/pub/mirrors/apache/ant/binaries/apache-ant-1.7.1-bin.tar.gz
1.3.[root]# tar xvfz apache-ant-1.7.1-bin.tar.gz
1.4.[root]# ln -s /opt/apache-ant-1.7.1 /usr/local/ant
1.5.[root]# vi /etc/profile.d/ant.sh
----------------------------------
View the ant.sh file
----------------------------------
1.6.[root]# chmod a+x /etc/profile.d/ant.sh
1.7.[root]# source /etc/profile.d/ant.sh
2. Check Your Java Version
2.1.[root]# java -version
3. Check Ant version
3.1.[root]# ant -version
4. Getting and Installing the Maven Tasks for Ant
4.1.[root]# wget http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-ant-tasks-2.0.9.jar
4.2.[root]# mv maven-ant-tasks-2.0.9.jar %ANT_HOME/lib/.
4.3.[root]# ant -diagnostics | grep maven | grep bytes
5. Using the HSQLDB Database Engine
5.1 Download the hsqldb jars from their website
6. Using and Installing Hibernate Core
6.1.Download the hibernate-distribution-3.3.1.GA-dist.tar.gz
6.2.[root]# mv hibernate-distribution-3.3.1.GA-dist.tar.gz /opt/.
6.3.[root]# cd /opt
6.4.[root]# tar xvfz hibernate-distribution-3.3.1.GA-dist.tar.gz
6.6.[root]# ln -s /opt/hibernate-distribution-3.3.1.GA /usr/local/hibernate
7. Setting Up a Project Hierarchy
7.1.[root]# mkdir /home/alex/HibernateProjects
7.2.[root]# cd /home/alex/HibernateProjects
7.3.[root]# mkdir data
7.4.[root]# mkdir src
7.5.[root]# mkdir -p src/com/oreilly/hh/data
7.5.[root]# vi src/build.xml
----------------------------------
View the build.xml file
----------------------------------
7.6.[root]# ant db
7.7.[root]# ant print-classpath
Thursday, February 12, 2009
Updating Fedora 15 to the Linux kernel version 3.0.3
Modified: 08/24/2011
Check the http://www.kernel.org/ website for the correct URL of the tarballs.
1.[root]# mkdir /usr/builds/src/
2.[root]# cd /usr/builds/src/
3.[root]# yum install wget
4.[root]# wget http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.0.3.tar.bz2
5.[root]# tar xvjf linux-3.0.3.tar.bz2
6.[root]# ln -sfn /usr/builds/src/linux-3.0.3 /usr/src/kernels/linux
7.[root]# cd /usr/src/kernels/linux
8.[root]# wget http://www.kernel.org/pub/linux/kernel/v3.0/patch-3.0.3.bz2
9.[root]# bzip2 -dc patch-3.0.3.bz2 | patch -p1 -R
10.[root]# yum install kernel-devel kernel-headers gcc ncurses-devel
Note: Necessary only if previously not installed
11.[root]# make mrproper
Note: If there is no /boot/config-$(uname -r), perform a manual copy first.
12.[root]# cp /boot/config-2.6.35.11-83.fc14.i686 /boot/config-$(uname -r)
13.[root]# cp /boot/config-$(uname -r) ./.config
14.[root]# make menuconfig
(a) Load Alternative Configuration File
(b) .config
(c) Exit
(d) Yes
15.[root]# make clean
16.[root]# make all
17.[root]# make modules_install
18.[root]# make install
Check the http://www.kernel.org/ website for the correct URL of the tarballs.
1.[root]# mkdir /usr/builds/src/
2.[root]# cd /usr/builds/src/
3.[root]# yum install wget
4.[root]# wget http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.0.3.tar.bz2
5.[root]# tar xvjf linux-3.0.3.tar.bz2
6.[root]# ln -sfn /usr/builds/src/linux-3.0.3 /usr/src/kernels/linux
7.[root]# cd /usr/src/kernels/linux
8.[root]# wget http://www.kernel.org/pub/linux/kernel/v3.0/patch-3.0.3.bz2
9.[root]# bzip2 -dc patch-3.0.3.bz2 | patch -p1 -R
10.[root]# yum install kernel-devel kernel-headers gcc ncurses-devel
Note: Necessary only if previously not installed
11.[root]# make mrproper
Note: If there is no /boot/config-$(uname -r), perform a manual copy first.
12.[root]# cp /boot/config-2.6.35.11-83.fc14.i686 /boot/config-$(uname -r)
13.[root]# cp /boot/config-$(uname -r) ./.config
14.[root]# make menuconfig
(a) Load Alternative Configuration File
(b) .config
(c) Exit
(d) Yes
15.[root]# make clean
16.[root]# make all
17.[root]# make modules_install
18.[root]# make install
Sunday, February 1, 2009
Updating your ndiswrapper module
UPDATING THE ndiswrapper module WHEN YOU UPDATE THE FEDORA KERNEL
---------------------------------------------------------------------
1. Clean the yum database
-------------------------
[root@localhost alex]# yum clean all
Loaded plugins: refresh-packagekit
Cleaning up Everything
2. Update the packages based on the updates from database
----------------------------------------------------------
[root@localhost alex]# yum update
Loaded plugins: refresh-packagekit
fedora | 2.8 kB 00:00
fedora/primary_db | 8.1 MB 02:44
rpmfusion-free-updates | 2.7 kB 00:00
rpmfusion-free-updates/primary_db | 130 kB 00:00
rpmfusion-nonfree-updates | 2.7 kB 00:00
rpmfusion-nonfree-updates/primary_db | 56 kB 00:00
rpmfusion-free | 2.7 kB 00:00
rpmfusion-free/primary_db | 259 kB 00:01
adobe-linux-i386 | 951 B 00:00
adobe-linux-i386/primary | 10 kB 00:00
adobe-linux-i386 17/17
rpmfusion-nonfree | 2.7 kB 00:00
rpmfusion-nonfree/primary_db | 66 kB 00:00
http://mirrors.kernel.org/fedora/updates/10/x86_64/repodata/repomd.xml: [Errno 12] Timeout:
Trying other mirror.
updates | 2.3 kB 00:00
updates/primary_db | 2.4 MB 00:12
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package selinux-policy-targeted.noarch 0:3.5.13-40.fc10 set to be updated
---> Package kernel.x86_64 0:2.6.27.12-170.2.5.fc10 set to be installed
---> Package PackageKit-udev-helper.x86_64 0:0.3.13-1.fc10 set to be updated
---> Package PackageKit-yum-plugin.x86_64 0:0.3.13-1.fc10 set to be updated
---> Package gnome-packagekit.x86_64 0:0.3.13-1.fc10 set to be updated
---> Package selinux-policy.noarch 0:3.5.13-40.fc10 set to be updated
---> Package kernel-firmware.noarch 0:2.6.27.12-170.2.5.fc10 set to be updated
---> Package PackageKit-yum.x86_64 0:0.3.13-1.fc10 set to be updated
---> Package kernel-doc.noarch 0:2.6.27.12-170.2.5.fc10 set to be updated
---> Package xine-lib-pulseaudio.x86_64 0:1.1.16.1-1.fc10 set to be updated
---> Package kernel-headers.x86_64 0:2.6.27.12-170.2.5.fc10 set to be updated
---> Package PackageKit.x86_64 0:0.3.13-1.fc10 set to be updated
---> Package libpurple.x86_64 0:2.5.4-1.fc10 set to be updated
---> Package xine-lib.x86_64 0:1.1.16.1-1.fc10 set to be updated
---> Package pidgin.x86_64 0:2.5.4-1.fc10 set to be updated
---> Package PackageKit-glib.x86_64 0:0.3.13-1.fc10 set to be updated
---> Package kernel-devel.x86_64 0:2.6.27.12-170.2.5.fc10 set to be installed
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository
Size
================================================================================
Installing:
kernel x86_64 2.6.27.12-170.2.5.fc10 updates 20 M
kernel-devel x86_64 2.6.27.12-170.2.5.fc10 updates 5.5 M
Updating:
PackageKit x86_64 0.3.13-1.fc10 updates 361 k
PackageKit-glib x86_64 0.3.13-1.fc10 updates 124 k
PackageKit-udev-helper x86_64 0.3.13-1.fc10 updates 54 k
PackageKit-yum x86_64 0.3.13-1.fc10 updates 112 k
PackageKit-yum-plugin x86_64 0.3.13-1.fc10 updates 55 k
gnome-packagekit x86_64 0.3.13-1.fc10 updates 2.4 M
kernel-doc noarch 2.6.27.12-170.2.5.fc10 updates 9.3 M
kernel-firmware noarch 2.6.27.12-170.2.5.fc10 updates 361 k
kernel-headers x86_64 2.6.27.12-170.2.5.fc10 updates 755 k
libpurple x86_64 2.5.4-1.fc10 updates 7.4 M
pidgin x86_64 2.5.4-1.fc10 updates 1.3 M
selinux-policy noarch 3.5.13-40.fc10 updates 616 k
selinux-policy-targeted noarch 3.5.13-40.fc10 updates 2.0 M
xine-lib x86_64 1.1.16.1-1.fc10 updates 2.4 M
xine-lib-pulseaudio x86_64 1.1.16.1-1.fc10 updates 16 k
Transaction Summary
================================================================================
Install 2 Package(s)
Update 15 Package(s)
Remove 0 Package(s)
Total download size: 52 M
Is this ok [y/N]: y
Downloading Packages:
(1/17): xine-lib-pulseaudio-1.1.16.1-1.fc10.x86_64.rpm | 16 kB 00:00
(2/17): PackageKit-udev-helper-0.3.13-1.fc10.x86_64.rpm | 54 kB 00:00
(3/17): PackageKit-yum-plugin-0.3.13-1.fc10.x86_64.rpm | 55 kB 00:00
(4/17): PackageKit-yum-0.3.13-1.fc10.x86_64.rpm | 112 kB 00:00
(5/17): PackageKit-glib-0.3.13-1.fc10.x86_64.rpm | 124 kB 00:00
(6/17): kernel-firmware-2.6.27.12-170.2.5.fc10.noarch.rp | 361 kB 00:01
(7/17): PackageKit-0.3.13-1.fc10.x86_64.rpm | 361 kB 00:02
(8/17): selinux-policy-3.5.13-40.fc10.noarch.rpm | 616 kB 00:03
(9/17): kernel-headers-2.6.27.12-170.2.5.fc10.x86_64.rpm | 755 kB 00:04
(10/17): pidgin-2.5.4-1.fc10.x86_64.rpm | 1.3 MB 00:06
(11/17): selinux-policy-targeted-3.5.13-40.fc10.noarch.r | 2.0 MB 00:10
(12/17): xine-lib-1.1.16.1-1.fc10.x86_64.rpm | 2.4 MB 00:12
(13/17): gnome-packagekit-0.3.13-1.fc10.x86_64.rpm | 2.4 MB 00:12
(14/17): kernel-devel-2.6.27.12-170.2.5.fc10.x86_64.rpm | 5.5 MB 00:28
(15/17): libpurple-2.5.4-1.fc10.x86_64.rpm | 7.4 MB 00:38
(16/17): kernel-doc-2.6.27.12-170.2.5.fc10.noarch.rpm | 9.3 MB 00:49
(17/17): kernel-2.6.27.12-170.2.5.fc10.x86_64.rpm | 20 MB 01:40
--------------------------------------------------------------------------------
Total 196 kB/s | 52 MB 04:34
============================== Entering rpm code ===============================
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Updating : xine-lib 1/32
Updating : libpurple 2/32
Updating : pidgin 3/32
Updating : xine-lib-pulseaudio 4/32
Updating : kernel-firmware 5/32
Updating : selinux-policy 6/32
Updating : selinux-policy-targeted 7/32
Installing : kernel-devel 8/32
Updating : kernel-headers 9/32
Updating : kernel-doc 10/32
Installing : kernel 11/32
Updating : PackageKit-yum 12/32
Updating : PackageKit-yum-plugin 13/32
Updating : PackageKit-glib 14/32
Updating : PackageKit 15/32
Updating : gnome-packagekit 16/32
Updating : PackageKit-udev-helper 17/32
Cleanup : libpurple 18/32
Cleanup : PackageKit-yum 19/32
Cleanup : kernel-doc 20/32
Cleanup : PackageKit-yum-plugin 21/32
Cleanup : gnome-packagekit 22/32
Cleanup : PackageKit 23/32
Cleanup : selinux-policy 24/32
Cleanup : pidgin 25/32
Cleanup : PackageKit-udev-helper 26/32
Cleanup : xine-lib 27/32
Cleanup : kernel-headers 28/32
Cleanup : kernel-firmware 29/32
Cleanup : xine-lib-pulseaudio 30/32
Cleanup : PackageKit-glib 31/32
Cleanup : selinux-policy-targeted 32/32
=============================== Leaving rpm code ===============================
Installed:
kernel.x86_64 0:2.6.27.12-170.2.5.fc10
kernel-devel.x86_64 0:2.6.27.12-170.2.5.fc10
Updated:
PackageKit.x86_64 0:0.3.13-1.fc10
PackageKit-glib.x86_64 0:0.3.13-1.fc10
PackageKit-udev-helper.x86_64 0:0.3.13-1.fc10
PackageKit-yum.x86_64 0:0.3.13-1.fc10
PackageKit-yum-plugin.x86_64 0:0.3.13-1.fc10
gnome-packagekit.x86_64 0:0.3.13-1.fc10
kernel-doc.noarch 0:2.6.27.12-170.2.5.fc10
kernel-firmware.noarch 0:2.6.27.12-170.2.5.fc10
kernel-headers.x86_64 0:2.6.27.12-170.2.5.fc10
libpurple.x86_64 0:2.5.4-1.fc10
pidgin.x86_64 0:2.5.4-1.fc10
selinux-policy.noarch 0:3.5.13-40.fc10
selinux-policy-targeted.noarch 0:3.5.13-40.fc10
xine-lib.x86_64 0:1.1.16.1-1.fc10
xine-lib-pulseaudio.x86_64 0:1.1.16.1-1.fc10
Complete!
[root@localhost alex]#
3. Uninstall the old ndiswrapper module compiled using the old kernel
---------------------------------------------------------------------
[root@localhost ndiswrapper-1.54]# make uninstall
NOTE: Not all installed files are removed, as different distributions install ndiswrapper files at different places.
Run uninstall as many times as necessary until no "removing" messages appear below.
removing /sbin/loadndisdriver
removing /usr/sbin/ndiswrapper
removing /usr/sbin/ndiswrapper-buginfo
4. Compile a new version of ndiswrapper module using the new kernel
-------------------------------------------------------------------
[root@localhost ndiswrapper-1.54]# make
make -C driver
make[1]: Entering directory `/home/alex/Download/ndiswrapper-1.54/driver'
make -C /usr/src/kernels/2.6.27.12-170.2.5.fc10.x86_64 M=/home/alex/Download/ndiswrapper-1.54/driver
make[2]: Entering directory `/usr/src/kernels/2.6.27.12-170.2.5.fc10.x86_64'
MKEXPORT /home/alex/Download/ndiswrapper-1.54/driver/crt_exports.h
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/crt.o
MKEXPORT /home/alex/Download/ndiswrapper-1.54/driver/hal_exports.h
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/hal.o
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/iw_ndis.o
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/loader.o
MKEXPORT /home/alex/Download/ndiswrapper-1.54/driver/ndis_exports.h
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/ndis.o
MKEXPORT /home/alex/Download/ndiswrapper-1.54/driver/ntoskernel_exports.h
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/ntoskernel.o
MKEXPORT /home/alex/Download/ndiswrapper-1.54/driver/ntoskernel_io_exports.h
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/ntoskernel_io.o
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/pe_linker.o
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/pnp.o
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/proc.o
MKEXPORT /home/alex/Download/ndiswrapper-1.54/driver/rtl_exports.h
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/rtl.o
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/wrapmem.o
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/wrapndis.o
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/wrapper.o
MKEXPORT /home/alex/Download/ndiswrapper-1.54/driver/usb_exports.h
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/usb.o
MKSTUBS /home/alex/Download/ndiswrapper-1.54/driver/win2lin_stubs.h
AS [M] /home/alex/Download/ndiswrapper-1.54/driver/win2lin_stubs.o
LD [M] /home/alex/Download/ndiswrapper-1.54/driver/ndiswrapper.o
Building modules, stage 2.
MODPOST 1 modules
CC /home/alex/Download/ndiswrapper-1.54/driver/ndiswrapper.mod.o
LD [M] /home/alex/Download/ndiswrapper-1.54/driver/ndiswrapper.ko
make[2]: Leaving directory `/usr/src/kernels/2.6.27.12-170.2.5.fc10.x86_64'
make[1]: Leaving directory `/home/alex/Download/ndiswrapper-1.54/driver'
make -C utils
make[1]: Entering directory `/home/alex/Download/ndiswrapper-1.54/utils'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/alex/Download/ndiswrapper-1.54/utils'
5. Install the new ndiswrapper module
-------------------------------------
[root@localhost ndiswrapper-1.54]# make install
make -C driver install
make[1]: Entering directory `/home/alex/Download/ndiswrapper-1.54/driver'
make -C /usr/src/kernels/2.6.27.12-170.2.5.fc10.x86_64 M=/home/alex/Download/ndiswrapper-1.54/driver
make[2]: Entering directory `/usr/src/kernels/2.6.27.12-170.2.5.fc10.x86_64'
MKEXPORT /home/alex/Download/ndiswrapper-1.54/driver/crt_exports.h
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/crt.o
MKEXPORT /home/alex/Download/ndiswrapper-1.54/driver/hal_exports.h
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/hal.o
MKEXPORT /home/alex/Download/ndiswrapper-1.54/driver/ndis_exports.h
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/ndis.o
MKEXPORT /home/alex/Download/ndiswrapper-1.54/driver/ntoskernel_exports.h
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/ntoskernel.o
MKEXPORT /home/alex/Download/ndiswrapper-1.54/driver/ntoskernel_io_exports.h
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/ntoskernel_io.o
MKEXPORT /home/alex/Download/ndiswrapper-1.54/driver/rtl_exports.h
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/rtl.o
MKEXPORT /home/alex/Download/ndiswrapper-1.54/driver/usb_exports.h
CC [M] /home/alex/Download/ndiswrapper-1.54/driver/usb.o
MKSTUBS /home/alex/Download/ndiswrapper-1.54/driver/win2lin_stubs.h
AS [M] /home/alex/Download/ndiswrapper-1.54/driver/win2lin_stubs.o
LD [M] /home/alex/Download/ndiswrapper-1.54/driver/ndiswrapper.o
Building modules, stage 2.
MODPOST 1 modules
LD [M] /home/alex/Download/ndiswrapper-1.54/driver/ndiswrapper.ko
make[2]: Leaving directory `/usr/src/kernels/2.6.27.12-170.2.5.fc10.x86_64'
echo /lib/modules/2.6.27.12-170.2.5.fc10.x86_64/misc
/lib/modules/2.6.27.12-170.2.5.fc10.x86_64/misc
mkdir -p /lib/modules/2.6.27.12-170.2.5.fc10.x86_64/misc
install -m 0644 ndiswrapper.ko /lib/modules/2.6.27.12-170.2.5.fc10.x86_64/misc
/sbin/depmod -a 2.6.27.12-170.2.5.fc10.x86_64 -b /
make[1]: Leaving directory `/home/alex/Download/ndiswrapper-1.54/driver'
make -C utils install
make[1]: Entering directory `/home/alex/Download/ndiswrapper-1.54/utils'
install -D -m 755 loadndisdriver /sbin/loadndisdriver
install -D -m 755 ndiswrapper /usr/sbin/ndiswrapper
install -D -m 755 ndiswrapper-buginfo /usr/sbin/ndiswrapper-buginfo
NOTE: Windows driver configuration file format has changed since 1.5. You must re-install Windows drivers if they were installed before.
make[1]: Leaving directory `/home/alex/Download/ndiswrapper-1.54/utils'
mkdir -p -m 0755 /usr/share/man/man8
install -m 644 ndiswrapper.8 /usr/share/man/man8
install -m 644 loadndisdriver.8 /usr/share/man/man8
6. Load the new ndiswrapper module using modprobe
--------------------------------------------------
[root@localhost ndiswrapper-1.54]# modprobe ndiswrapper
[root@localhost ndiswrapper-1.54]# modprobe ndiswrapper
[root@localhost ndiswrapper-1.54]# modprobe ndiswrapper
7. Check is ndiswrapper module is successfully loaded
-----------------------------------------------------
[root@localhost ndiswrapper-1.54]# modinfo ndiswrapper
filename: /lib/modules/2.6.27.12-170.2.5.fc10.x86_64/misc/ndiswrapper.ko
license: GPL
version: 1.54
description: NDIS wrapper driver
author: ndiswrapper team
srcversion: FB4F5DE146139E5A7B80324
depends:
vermagic: 2.6.27.12-170.2.5.fc10.x86_64 SMP mod_unload
parm: if_name:Network interface name or template (default: wlan%d) (charp)
parm: proc_uid:The uid of the files created in /proc (default: 0). (int)
parm: proc_gid:The gid of the files created in /proc (default: 0). (int)
parm: debug:debug level (int)
parm: hangcheck_interval:The interval, in seconds, for checking if driver is hung. (default: 0) (int)
parm: utils_version:Compatible version of utils (read only: 1.9) (charp)
[root@localhost ndiswrapper-1.54]#
Subscribe to:
Posts (Atom)