> If "grep cifs$ /proc/filesystems" doesn't show anything then support > definitely isn't available. This means it's either not statically > built into the kernel or that it's not available as a loadable moduel > for whatever reason.
Yes, cifs wasn't there. However, smbsf was and I was able to connect with it. :) > > If it is something you intend to use consistently then I don't see > much point in building it as a module. Nonetheless, here are a few > tips relating to the usage of loadable kernel modules: Thanks for the practical advise. > 1) If you enable an option as a module where previously it wasn't > enabled at all then, in most cases you can get away with: make modules > && make modules_install. The modules_install step is necesary to move > them to the correct place under /lib/modules/($uname -r). This is where my problem was. I was only "make module". I preformed "modules_install" and now I am able to load the cifs module and connect to my windows share using it. Thanks for the help. > 2) There are some exceptions to the above rule. If in doubt, it's > safer to do this: make && make modules_install. > > 3) Make sure your bootloader is booting a kernel built from the source > tree that you're actually manipulating! This is particularly pertinent > if you have multiple source trees installed. For sanity's sake, also > make sure you have /usr/src/linux symlinked to whichever tree you want > to work from. yes, thank goodness for eselect :). Thanks your for all of your help and guidence. Regards, Richard Broersma Jr. -- [email protected] mailing list
