hi can any1 tell me what is /lib/modules/modules.dep ?

after i compiled kernel it cant find this file while booting
many errors.

pls help

This file (normally located under /lib/modules/kernel-version/modules.dep) contains all the dependencies between the kernel modules.

When you try to load a module using modprobe for example, the kernel reads this file to know which other modules it has to load before the one you asked for.

When you compiled your new kernel, you should maybe have typed make modules. If you did it try to type depmod -a 2.x.xx (replace 2.x.xx with your new kernel version of course)

see the depmod man page for more information

Hope this helps

--Backslash

how did you compile your kernel? Did you install the new kernel modules?


FYI, I use:

make mrproper
* copy the .config...
* edit the revision-version of the Makefile
make menuconfig
make dep
make clean
make bzImage
make modules
make modules_install
* copy System.map to /boot/System.map-version
* update the links there to System.map
* copy /usr/src/linux/arch/i386/boot/bzImage to /boot/kernel-version
* edit /etc/lilo.conf, and run lilo

i use suse 8.2 so there is grub i cant run lilo
i got that working by now but not all

my vfat modules cant be found and i set m in xconfig
and did make modules make modules_install
is it because i didnt copy systam map ?
what do i need system.map for ?
im working with linux just 5 days so im sorry

thx

Did you try simply make install ?

no is it any good?
i give it a try now

I don't use "make install" at all, because I'd like to have a little more control about the last steps (see my post above)

ok i have done all of that
it made modules.dep
but if i want to acces my vfat of windows i cant
by boot it says cant locate module vfat modprobe faild
if i look in folder with modules its not there
it didnt even created one by compileing even i clicked m in xconfig
it just didnot made this bloody module .

if i compile it directy in kernel i can aces my win discs and dvd
but just as a root and they are not directly mounted by boot
before they were mounted allready when i started my xwindows
and if i try as normal user it say something like
mount : bad ss ,bad superblock , or too many mounted file systems

do i have to compile more things into kernel directly like a msdos,vfat.
or pls tell me haw to make that bloody modules

pls help.
thx

all right I'll try to explain.

There are 2 ways of building your kernel: one monolithic kernel with every option build in, or a modular kernel. Also, you can choose between using the auto-module loader, or do everything yourself.

I'd recommend to build a few things as module:
- A lot of your hardware components (floppy / sound / network / loop / serial / usb / video / parallel port) because you can unload and upgrade those modules without rebooting your computer (such as reloading your floppy module, instead of rebooting)
- build all other features in the kernel, such as file systems. (it's faster) But choose only what you need, but don't forget support for ext2/3, vfat, ntfs, iso, udf, samba, and proc.
- Compiling a kernel allows you to make a specific kernel for your hardware. Use that (and don't compile everything in your kernel) If you doubt between 2 options, you could always compile them as module, in case you might need them.

You should enable "loadable module support", but could disable "kernel module loader". This kernel-feature tries to auto-load a module when a driver is not loaded (which is required by a certain feature). This is really cool, because it allows you to boot with a small kernel, and load features automatically when the kernel needs them.. (or even when you start to use certain hardware)

If you disable the "kernel module loader", you'll have to 'modprobe' all modules manually. Then you'll dictate what modules to use. (slackware has /etc/rc.d/rc.modules for this; but I suggest to rewrite that file )

Decide what you want For servers for example, you might not want a "smart" kernel. A workstation where you can plug-in devices, and make them work instantly is cool on the other hand (this also requires hotplug) an autoloader is easier, but I have to adjust it sometimes using /etc/modules.conf Personally, I don't like a computer to think for me. That's what made me run away from Windows XP after a year. (I do use the autoloader at this moment, and compiled all usb-drives as modules, because I want to plug-and-play)

Then you're using the auto-loader feature of the kernel, but this fails for an obvious reason: you don't supply an vfat module either.

btw, I didn't mention how to create modules, but I don't know how xconfig works either. (because I run "make menuconfig" from the console) In the menuconfig, you can press 'space' to enable a feature, and twice (or "m") to create a module. Unless you are an GUI addict, I'd suggest running menuconfig instead. (but this is a personal decision)

This is a security feature. You should adjust your /etc/fstab to allow users to mount. Play with the umask, and uid or gid values, but this requires some knowledge of the file permissions system.

Take for example, this fstab field:
I've created an user-group (happens to be no. 307) The umask (reverse of a chmod-code) denies others (the last field) to write to the drive. (only root, and group #307) (4 = read, 2 = write, 1 = execute/browse)

If you want the drive to mount automatically, add the "auto" keyword to the options-field. I don't want other users to mount the drive; it's mounted by default, and only root does my administration tasks

thx for nice info i got things working now