The steps are easy but long, take your time.

1) Install needed toolsi:
# sudo apt-get install kernel-package libncurses5-dev fakeroot wget bzip2

2) Download kernel source of the version you like (I’m using Jaunty Jackalope one):
# sudo apt-get install linux-source-2.6.28
It’s better takes the source code of the running kernel version on your machine. Change the numbers with that of you version.

3)Now locate in the directory of the downloaded archive and extract the files:
# cd /usr/src
# bzip2 -d linux-source-2.6.28.tar.bz2
# tar xvf linux-source-2.6.28.tar


As result there’s a directory named as the archive, ex. linux-source-2.6.28

4) create a symbolic link to this directory and name it linux. Now enter it:
# ln -s linux-source-2.6.28 linux
# cd linux


5) Now, to save time on the determination of your hardware configuration, you can copy the configuration file of the kernel you are using to run the penguin:
# cp /boot/config-`uname -r` ./.config

6) Now go here and download the patch file that supports DMI (browse the posts and you will find it).

7) After downloading the patch, apply the change to the file fixup.c in the directory content arch/x86/pci/ copying the text from the patch file and pasting it at the end of fixup.c and save it:

If you are under GUI
gedit arch/x86/pci/fixup.c

If you are under cli
vi arch/x86/pci/fixup.c

I’m using Ubu 32-bit on intel so I changed the file in the directory fixup.c belonging pci x86 architecture. If you have other types of laptops in this series with other features, and you have the same bug, you can edit the same file in a directory other than x86. For example for 64-bit version you have to access the file arch/ia64/pci/fixup.c and paste the contents of the file to patch.

8)We can dedicate ourselves to the specific change in the configuration file according to our preferences if we want something optimized for our machine, otherwise you can leave as is (both are already the choice of configuration files that are currently used to boot linux ) and skip to step 9. For perfectionists, however this is the command to access the configuration menu
# make menuconfig

9)Now we carry out thorough cleaning of the code (useful if you happen to have to start over from scratch even if errors occur during compilation)
# make-kpkg clean

10) Now is the most annoying: the compilation itself. on my machine has made us almost an hour
# CONCURRENCY_LEVEL=2 fakeroot make-kpkg --initrd --append-to-version=-asus kernel_image kernel_headers

After –append-to-version= you have to write a string that will serve to distinguish the customized version of the kernel. This string must begin with dash “-” and must not contain white spaces. I wrote down “-asus” then do as you like, you choose a name what you like.

11) Now go and make a turn. Go to the gym, go to crush a nap, do whatever you want so we can see in an hour

12) At the end of compilation in the directory can find the newly created deb packages. All that remains is to install

# sudo dpkg -i linux-image-2.6.28.9-asus_2.6.28.9-asus-10.00.Custom_i386
# sudo dpkg -i linux-headers-2.6.28.9-asus_2.6.28.9-asus-10.00.Custom_i386

Et voilà. Now you have to do is restart and select the kernel you have just completed to start ubuntu without having to change the line in the grub with the usual restriction of memory: the three are all jig! After that you can use the proprietary fglrx driver of the ATC. I put the 9.5. Happy to have been of help ;D

BL - President


Configure linux-image-2.6.28.9-m51se (2.6.28.9-m51se-10.00.Custom) …
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
initrd.img(/boot/initrd.img-2.6.28.9-m51se
) points to /boot/initrd.img-2.6.28.9-m51se
(/boot/initrd.img-2.6.28.9-m51se) — doing nothing at /var/lib/dpkg/info/linux-image-2.6.28.9-m51se.postinst line 588.
vmlinuz(/boot/vmlinuz-2.6.28.9-m51se
) points to /boot/vmlinuz-2.6.28.9-m51se
(/boot/vmlinuz-2.6.28.9-m51se) — doing nothing at /var/lib/dpkg/info/linux-image-2.6.28.9-m51se.postinst line 588.
Running postinst hook script update-grub.
Searching for GRUB installation directory … found: /boot/grub
Searching for default file … found: /boot/grub/default
Testing for an existing GRUB menu.lst file … found: /boot/grub/menu.lst
Searching for splash image … none found, skipping …
Found kernel: /boot/vmlinuz-2.6.28.9-m51se
Found kernel: /boot/vmlinuz-2.6.28-11-generic
Found kernel: /boot/vmlinuz-2.6.24-24-generic
Found kernel: /boot/memtest86+.bin
Updating /boot/grub/menu.lst … done

To resolve I had to do the following:

sudo chmod -x /etc/kernel/postinst.d/nvidia-common
sudo apt-get remove nvidia-common

This completes the installation of the custom kernel. However, the /etc/kernel/postinst.d/nvidia-common is still there. So, I, reinstalled it and then purged:

sudo apt-get install nvidia-common
sudo apt-get purge nvidia-common

After that, the file is gone and the problem is solved.
Bye!!!

Free IP Switcher is the perfect tool for this situation. It offers a one click change of the network settings that require no reboot. Probably the fastest solution if you connect to different networks regularly.
What I really like is the feature to import the current network settings which spares you from the hassle to add them to the IP Changer as well. Different IP settings are available in tabs in the program and it only takes two clicks to activate another configuration.

The program offers several additional settings that can be added if needed besides the obvious ones like IP, DNS and Proxy. The computer name and the Workgroup can be changed as well as the default printer of the system. Last but not least it is possible to set the DNS Domain and a Wins server.

by President

Enjoy!

Where can I get free interactive access to HP-UX or Linux distro or UNIX shell access? Here!

You can simply grab and try out any Linux / BSD / Solaris Live CD. However, some time you cannot install and use particular UNIX like os. So, if you want to try the latest technologies over the Internet? Try HP TestDrive program:

This program allows you to testdrive some of the hottest hardware and operating systems available today. Have you ever wanted to try out HP’s exciting 64-bit Integrity and PA-RISC technology? Get time on SMP x86 and Opteron ProLiant servers? Try out a Blade server. Try different Open Source operating systems such as FreeBSD, Suse, Redhat, Debian and other Linux distributions.

This program is perfect for students and new users to try out and learn basis of UNIX. You can also try and test your C/C++ programs using latest Intel compilers. It is intended for those users who want to sample the 32- and 64-bit servers running a variety of HP, UNIX, Linux and third-party operating systems and applications.

Type in a site’s URL or feed address, then your mobile phone number, and you’re on your way to mobile updates. You can also preview your feed messages and have only updates with certain keywords sent along.

Bye and Thanks to all for your attention!
Continue to read US!

You will need the following tools and libraries that are distributed free of charge:

1. Ant tool.
2. NSIS: a scriptable win32 installer/uninstaller system.
3. ProGuard: java shrinker, optimizer, and obfuscator.
4. Launch4j: Cross-platform Java executable wrapper for creating lightweight Windows native EXEs.
5. NSIS Ant task: to compile NSIS scripts.

The goal is to create a single build.xml file that will compile (JAVAC), obfuscate, shrink, optimize (ProGuard) our code, create an EXE file (Launch4j) and pack it all including other files (like license text file) to an installer package (NSIS).

The ant build file consists of a number of targets that can depend upon other targets in the same build file. That means before the target does something useful it will run the targets it depends upon:

Now download build.xml file and we’ll comment it together…

Initialization Target

First, let’s define a number of properties:

XML

You may want to justify the paths according to your system.

The target init will depend upon target ‘clean’ – we want to clean everything before the build starts:

XML

After it is over, the target ‘init’ will run.

XML

We create a number of folders, copy source code, libraries, html, and image files.

Compile Target

Compile the classes and copy the required files, such as Velocity templates and property files to the folder with the freshly compiled classes.

XML

JAR Target

Next step is to create a JAR file and feed it to ProGuard that will “obfuscate, shrink, optimize” our code. ProGuard task has a number of limitations and requirements, so while my example is pretty clear you may want to read the ProGuard documentation. In a few words you name the libraries that are used by your application, specify you jar file name, and the name of the jar that will be the result of ProGuard’s work. ProGuard modifies the names of classes, so you need to keep the name of your Main-Class untouched. Anyway, consult the docs or you may run into some issues here.

XML

EXE Target

After the JAR target, we have a jar file that needs to be wrapped to become a native Windows executable file. We use Launch4j tool here. Launch4j needs an xml file with the settings:

XML, proggy.xml

You may want to get an ICO & BMP images for your application. The icon file is the image to be rendered at the left top corner of every Windows application. The BMP file will be displayed as a splash file when the proggy starts. Java 1.6 has built-in splash functionality, so you may want to use it along with some nice PNG image with shadows and other alpha tricks, and not the Launch4J’s ugly bmp file.

XML

Distibution Target

NSIS comes with a number of templates, samples, some nice graphics and GUI application. Therefore, you will definitely want to see its samples. my_proggy.nsi is the name of the script that will guide you installation and deinstallation processes: create folders, copy files, create menu group, create desktop icons etc.

NSIS script:

XML

NSIS script And the appropriate target.

It is really convenient. After you make some changes in the code, you run a single file and have an installer package ready.

By the way, it also makes sense to check for the required system paths before the build process. Create a .BAT file:

DOS:

1.
@echo off
2.
if “%ANT_HOME%”==”" goto noAntHome
3.
if “%JAVA_HOME%”==”" goto noJavaHome
4.

15.
:end


Good luck @ all, especially to my friend “The King of All”!