Update/Compile my Kernel after changing param.h file

[microchip8]

I see in your pevious post that there's an X connection refusal which usually means that there's no authorization. To allow all clients to connect to X from any host, type: xhost +

for the colors, either type 'dircolors' or 'echo $LS_COLORS' (without quotes), they don't specifically mean anything but are used to distinguish between different file types

[BenderBendingRodriguez]

It is best for you to COPY the actual kernel sources to a new folder in /usr/src/<whatever-you-name-your-copy>, there work on this kernel keeping the "safe" default kernel intact. You modify the copy (don't forget to change it's local name or something, it CANNOT be named the same as your actual kernel or you will have troubles, that option is somewhere at the beginning)

compile with make, make modules_install, make install,

(i skipped the make xconfig part as you already know how to do that). After that you need to create a symlink to your new sources with

ln -s /usr/src/<whatever-you-name-your-copy> /usr/src/linux

And voila. You're done.

[microchip8]

And whay are you repeating essentially the same thing what I said? Also he already compiled his kernel following my instructions and is up and running, including VMWare and the NV driver

[BenderBendingRodriguez]

He may be up and running but you didn't teach him to keep the "working" kernel and kernel-source intact, what you propose is to modify the original kernel source what may wreak havoc in the system if he wanted to compile something or install nVidia drivers.

[microchip8]

I already told him to change the local version in order not to overwrite existing kernel, thus keeping the default intact. As for kernel sources, it won't break anything since the values in the param.h are there to be tuned if needed

[BenderBendingRodriguez]

It is fine if he will keep only the compiled kernel, but if he ever tries to compile something using the default kernel with modified kernel-sources then he may be in trouble. Anyway it's fine now that he resolved his issues

[microchip8]

Yes, i should have said to back up the original source but it can the reverted pretty easy. Change back the values in param.h to defaults, copy /boot/config-<original-kernel-version> to /usr/src/linux/.config and then make prepare and make modules_preapre

The changes he did are very small so they are easily reveted

[bobcal2000]

No fighting! Please. Both of you helped me a lot!

I understand what is going on now. Now when I read the book I understand what they are talking about.

I will not be making big changes to the kernel's source code, but I do understand keeping the original code safe.

One last question and we can put this thread to bed.

QUESTION: Why did I receive warning during the compile? Are they normal? What should I be looking for next time?

Again Thank you both!

[BenderBendingRodriguez]

They are compilator warnings i guess. Next time you may look to slim your kernel down by not compiling unnecessary stuff You can cut off compile time and with some modules boot time making some modules built in, for example set a sound module to have it built in, you can check hat you need by using lsmod and looking what is loaded and this way you can trim your kernel down. When i compile my kernel i get rid of LOTS of stuff, unnecessary sound modules, video drivers, cifs and nfs, unnecessary filesystems, or partition tables (there are many for unix etc.) Just don't compile what you don't use

[bobcal2000]

I would like to do this! But before that. I need to Learn how to load and use Samba.

Any documents to that explain "how not to compile stuff I don't need" would be great!

Also, if Samba is part of the OpenSUSE distro how come I can configure it with YaST be the files are not in /usr/local/samba-3... ?