How to build a kernel

First of all I built a virtual machine on my desktop using vmware server. I then installed Debian 5 on it using the net install ISO to make a minimal install. I didn’t set it up with any roles i.e. desktop.
Once booted install SSH. Logging on as root and enter:

apt-get install ssh

After this point you can access the vm with putty and copy files to and from the vm with Winscp. You could install a samba server of ftp but I am not going to cover this here.

Now we need to install all the software needed to allow us to compile kernel sources. This is done using the following command:

apt-get install gcc-4.3 make wget bzip2 build-essential

These tools are as follows:

• gcc-4.3 the GNU C Compiler
• make the tool that runs the compile script
• wget a tool to download files from http servers
• bzip2 a compression tool
• build-essentials tools and libraries used to compile

Once this is complete you have a system that is setup to compile kernels and driver modules.
We now need to get some files from the altiris system.
First we need the config file from the altiris Linux boot environment. The config file holds all the settings that were used to build the kernel that is used in the current build and is a good starting place for a new kernel.
To get it we need to send a job down to a machine to boot the Linux environment and run the following script:

cp /proc/config.gz /mnt/ds
gzip -d /mnt/ds/config.gz

This will copy the config file from the boot environment and put it into the root of your deployment share.

Now we also need the rootfs file. This file is like a virtual disk that holds the file system for the Linux been environment we may need to add some files to this or delete as needed. This file is located at \bootwiz\platforms\linux\x86\base\rootfs.

Now you have these files copy them over to the vm using Winscp and place them in the /root directory.

Now we need to get hold of the source code for the kernel that we want to use. If you just want to make new driver modules you need the same version as is used in your existing build (currently 2.6.18.8).
you can download the kernel from here you need a kernel that follows the name linux-2.6.**.*.tar.bz2 it should be about 40mb + in size. I have had good results with 2.6.24.7. Once you have selected the kernel you need right click on it and copy the link location. Then go to your putty and enter the following commands:

cd /usr/src
wget http://url to file

Instead of having the type “http://url to file your can right click and your copied location will be pasted in saving your figures. press enter and your kernel will be downloaded.
Once finished you need to extract the kernel from the archive as bellow:

tar -jxf linux-2.6.**.*.tar.bz2

This will extract the source to a folder of the same name.
To make life easier I would delete the archive now but its up to you.
Now we need to move the kernel source to a folder called linux this is for compatibility with making new drivers.

mv linux-2.6.**.*/ linux/

Now we copy the config file into the kernel source folder and make it hidden (this is how the compiler likes it).

cp /root/config /usr/src/linux/.config

Dont forget the . in .config.

Ok you now have the same conditions that the altiris developers had before they made there kernel. But we want more in our kernel so its time to make some changes.

cd linux
make menuconfig

Now you need to go to the bottom of the menu and select load config it should already be filled with .config so select ok.
Now you can go through the menu making the changes you require. you probably want to add support for a new chip set of SATA controller so have a look in the drivers section for what you require. I recommend compiling in your options a posed to making modules as this takes up space in the rootfs later on which has a fixed max size. So set your options to have a * a posed to a M if possible.
When finished exit out and save your config.
Now you can compile your kernel enter the following:

make
make modules_install


That’s it, watch the screen go flying by for a while and eventually it will finish if it ends with lines with ERROR: in them something has gone wrong. But hopefully this wont happen.
Your new kernel will be waiting for you in the folder /usr/src/linux/arch/x86/boot/ the kernel file is the one called bzImage.
Copy this out to a safe place and rename to “linux” all lower case.
Now we need to mount the rootfs file to make some changes.

mkdir /mnt/rootfs
mount -o loop /root/rootfs /mnt/rootfs
cd /mnt/rootfs

you are now inside the rootfs file. We now need to update the modules for the kernel:

cd lib/modules
rm -r 2.6.18.8  (or what ever folder is there)
cp -r /lib/modules/2.6.**.* /mnt/rootfs/lib/modules/2.6.**.*

You will probably also want to update your pci detection list. to do this enter:

update-pciids
cp /usr/share/misc/pci.ids /mnt/rootfs/usr/share/pci.ids
cp /usr/share/misc/pci.ids /mnt/rootfs/usr/local/share/pci.ids

You can make more changes if needed. When finished unmount the rootfs:

umount /mnt/rootfs

now copy your /root/rootfs file out to some ware safe.
Thats it a new kernel is compiled.
To use this kernel and root fs over right the linux and rootfs files in the \bootwiz\platforms\linux\x86\base\ folder with the onse you have just made.
Then make a new Linux PXE option or edit an existing one to force a rebuild. Using the regenerate images doesn’t work at least in 6.9 sp2 of the DS.
Now boot your kernel and see how it goes.
If you want to see your kernel boot and get a bit more debug info from it you can remove the quiet commend from the pxeconfig file located in \bootwiz\platforms\linux\x86\misc\ you also need to rebuild the image after this as above.

How to build a driver module

Now you have built a kernel you can build driver modules for that kernel (important)
when you have found your driver source files copy them and extract them to a folder I use /usr/scr/drivers/
then cd in to the driver directory you might find another folder in that named src if so cd into there as well. you should now be in a folder with files with extensions of .c and .h. enter the following commands:

make -C /usr/src/linux SUBDIRS=$(pwd) modules

You will now have a .ko file that was not there before this is your driver and it needs to be copied to your bootwiz folder to the following directory string.
“.\Boozwiz\platforms\Linux\x86\Drivers\CUSTOM\lib\modules\_ver_\kernel\opt\bdc”
You will need to make all those folder if they are not already there. Then recreate your PXE image as before.

First I ran:

ntfrsutl inlog > c:\sometextfile.txt

This creates a list of the items that are being inbound replicated on the problem server. I went through the file looking for the line IBCO_INSTALL_RETRY as described in the KB but it did not find it. Then I decided to go through the file manually reading the hole thing. I found that I had a slight variation on the KB article on some items I had the files marked with IBCO_DEL_RETRY and IBCO_RENAME_RETRY. I then ran the GUID’s for these files through the following command to find out what they were.

ntdfsutl idtable {GUID} > c:\someothertextfile.txt

This relieved that some folders that had been deleted would not replicate off the server and also a file that had been renamed would not replicate the change. I found that I had a permission issue with these folders and files and was able to fix it.

You may need to change the paths for your installation but this should work quite well.
As allways take a backup before you run this just in case.

First I decided to have two types of links core links with a cost of 10 and default site links with a cost of 100. Now I decided to put all my core sites (HQ’s and sites with large user populations) in to one site link called the hub. It should be noted that the KCC will fully mesh all sites that are in one link so if you find you are going to have alot of core hub sites you may want to construct the mesh manually by creating individual site links for the core. I would say more that 5 core sites probably requires manual link creation.

Next you need to create site links for all of your other sites. It is recommended to only have 2 sites in a link (apart from the core) this means that you can have full control of your replication paths. If you require backup links you can add these using a link cost of say 200. I decided to have sites that connected to the same MPLS core networks link together. This means that your replication traffic will only traverse the network via the core hub sites and not all the other sites. This cuts down on unnecessary bandwidth usage.

You should have no more than default satellite sites connected to one hub site. If you do you ether need to make sure the hub site has the resources in bandwidth and server performance to take the load or create another hub site and move some sites across to the new site.

You will also need to decide on replication intervals and schedules. This can be decided by how often you make changes and how quickly you need them to replicate.

To monitor your replication system I would recomend installing Ultrasound from Microsoft it is free and will monitor and debug any issues you might get in the future.