When I upgrade my kernel in either Slackware or Gentoo, I always do zcat /proc/config.gz > [new kernel]/.config. Then I ran "make oldconfig". This sets up the new kernel using the same settings as the previous kernel version. Then I run "make menuconfig" because I prefer ncurses instead of QT GUI. After I quadruple check the options, I type "make && make modules_install". These steps are for 2.6.x kernels. I do not remember the steps for 2.4.x kernels, so read the documentation on how to compile 2.4.x kernels. After it is compiled bzImage have to be copied from [new kernel]/boot/arch/i386 to /boot. It is best to include the version of the kernel to make it easier to separate the old version and the new version. Also you will have to make an initrd file that includes any necessary modules to boot up Linux. Use mkinitrd to help you make one. You could make one your self but it is time consuming.

NTFS support from the kernel is still experimental. I suggest disable write support and enable NTFS logging while using it. There is Linux-NTFS project that is a lot better than the kernel's NTFS support. This project provides 99% of write support. Go to http://www.linux-ntfs.org/.

I do not recommend having the following lines in the Screen section because it will cause some conflicts when using more than one card.
The lines should be place where the video card driver is specify. This will not cause any conflicts but provide more organization and control of the X Window System. XVideo is automatically enabled by default.

In Windows the color depth 32 is 24-bit color which is already noted, but the other 8-bit is an opaque layer or in laymen terms transparency layer. The opaque layer in Linux is the composite module. Xorg 7 and above enables the composite module by default.

TTF fonts from Windows can be used in X Window System. These fonts may have to be converted to pcf fonts depending what the distribution used for its options during compiling the X Window System.

The ldconfig utility only needs to be run after adding or removing a library from the system. It really does not need be run upon boot up. Though it does not hurt to keep the cache refresh and consistent by running ldconfig during boot up.

Use gtf to help create modelines, so X Window System does not have to take time create them by it self. Place the modelines in the monitor section.

umask=0000 is dangerous. Everybody will have root access to the drive and be able to delete and take any file. umask=000 is a little safer or even better umask=002 or umask=022.

Hiya Electro :) Thank you for the added advice in your last post, especially regarding the NTFS writing, the Windows fonts, umask 000, and explaining ldconfig :). From my own experience, having difficulties with libraries a little while back, I think I'll just leave the ldconfig the way it is at boot, better safe than sorry by forgetting to run it.

The original poster will appreciate your info on NTFS writing for sure. I no longer have any MS installations :D and plan to keep it like this!

RE: the extra stuff in xorg.conf -- It's taken directly from the nVIdia README pertaining to the AGP drivers, as well as from my experimentation with what has worked optimally for me using 2 displays on my MX440 card. While nVidia suggests these items may go in either the screen OR device sections; I chose the screen-section method because I have different settings per-screen; thanks though for that tip about possible conflicts when using 2 cards. There are a lot of people it seems who are using nVidia cards, which is good, as they are so very compatible.

Original poster has been 2 steps ahead of me through this whole thread :) I don't think I'll be able to help him much longer, he knows everything I know now (which is relatively little, mind you -- I'm still brand-new too!).

Take care Electro; thx again..
Sasha

Yes, thanks for the NTFS info, but I think it'd be too much trouble to deal with... I created an "exchange" vfat partition, so I'll just use that.

I'm wondering, is there a specific log that only has EXACTLY what was printed on the console during bootup? All the other logs seem to be missing some stuff I saw during bootup, i.e. that dma error message.

Also, all of the startup scripts are in /etc/rc.d , right? Linux is still trying to start up some modules that I have included into the kernel, and I want to turn that off.

Thanks both of yall
--David

Hi David.. There doesn't seem to be an EXACT log of ALL sentences from bootup.
Between the logs in /var/log and the logs in /var/adm that's everything.
You might browse around all the stuff in /Proc but I'm not sure if there's any log-type stuff in there. Specifically, var/log/messages and var/log/syslog and var/log/dmesg should have the majority of boot messages.
Verbose output from the rc.<scripts> is not logged unless you specifically set some mechanism up to do so. In other words, printf, print, and echo statements from within the rc.<script> files may not be logged.

OK, have you disabled rc.hotplug by CHMOD'ing it (change mode/permissions) to NON-executable?
Next, check for stuff in rc.modules, rc.local, rc.modules.* and similar files, comment out anything you don't want to be modprobed.
Yes, most everything as far as boot scripts are in /etc/<somewhere> and /etc/rc.d/<somewhere>

OK, I'll muddle my way through that, more important things to do lol.

If you program I have a question for you:

I am in an Assembly language class this semester. The teacher wants us to submit the source as well as the .exe file. Now is it possible to produce a .exe file in Linux, even though it would not be able to use it?

I don't know why there would need to be a cross compiler, I'm already using assembly.

And, if there is no other way to produce a .exe file w/o a cross compiler, then how could I incorporate it into a makefile? I've never made a makefile, but I have simple instructions.


I had another question, but I just blanked out on it lol.

Thanks

That is getting beyond my abilities (My assembly skills are pretty outdated, and my knowledge of C is limited). You may do well to submit a post or browse in the programming forum. But here's the bit I know:
As for an .EXE, I guess you want a Windows executable?
A Cross compiler makes source code runnable on different platforms, I think.
And have absolutely no idea how to incorporate anything into a makefile :D
( See? Told you I know nothing :) )
All I can suggest, is the programming forum, and Gooooooooogle!\
LOL. Best of luck with that; I'm sure there are some extremely capable folks that can help, around here somewhere!

lol ok no prob thanks anyway
Imma figure it out!