mount_smbfs LIBSMBCRYPTO [was Re: Kernel module path]
On Wed, 7 Jun 2006 12:28:46 -0500 Nikolas Britton [EMAIL PROTECTED] wrote: (snip) Do you know if they ever fix crypto bug in mount_smbfs in FreeBSD 6.1? Yeah, they did... Assuming you're thinking of the same thing I am, whereby attempting to authenticate to a server for SMB access resulted in being told that cryptography wasn't availabl e (or some such). I think it had something to do with a LIBSMBCRYPTO setting, or similar, but can't recall. -- Nick Withers email: [EMAIL PROTECTED] Web: http://www.nickwithers.com Mobile: +61 414 397 446 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel module path
On Wed, Jun 07, 2006 at 11:28:09AM +0100, Richard Jones wrote: Hi, I'm having trouble loading kernel modules. Put simply make installkernel seems install native kernel modules into /boot/kernel/, but kldload seems to want to load them from /boot/modules. Obviously I can load modules by hand and/or copy the modules into /boot/modules, but surely there's a better way - either by modifying the installkernel behaviour or kldload. And in answer to my own question, I've found the answer. Despite the man page suggesting the default value for module_path being /boot/kernel;/boot/modules, my /boot/defaults/loader.conf had just /boot/modules. I've checked in /usr/src/sys/boot and this seems to be system default, does anyone know why this is? Regards, Richard -- Richard Jones MSN: [EMAIL PROTECTED] Y!M: rwkjones http://www.jonze.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel module path
Hi, I'm having trouble loading kernel modules. Put simply make installkernel seems install native kernel modules into /boot/kernel/, but kldload seems to want to load them from /boot/modules. Obviously I can load modules by hand and/or copy the modules into /boot/modules, but surely there's a better way - either by modifying the installkernel behaviour or kldload. R -- Richard Jones MSN: [EMAIL PROTECTED] Y!M: rwkjones http://www.jonze.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel module path
On Wed, 7 Jun 2006 11:28:09 +0100 Richard Jones [EMAIL PROTECTED] wrote: Hi, I'm having trouble loading kernel modules. Put simply make installkernel seems install native kernel modules into /boot/kernel/, but kldload seems to want to load them from /boot/modules. From kldload's man page: FILES /boot/kernel directory containing loadable modules. Modules must have an extension of .ko. This having been said, it _does_ look in /boot/modules as well. I'm able to load a module from either directory without specifying the full path and / or extension and without either directory being my current working directory on 6.1-RELEASE. What's the problem you're actually having? What version of FreeBSD are you running? Obviously I can load modules by hand and/or copy the modules into /boot/modules, but surely there's a better way - either by modifying the installkernel behaviour or kldload. I believe that base system kernel modules for the currently installed kernel should be installed to /boot/kernel and that kernel modules from outside FreeBSD (e.g.: nvidia.ko) are installed to /boot/modules. R -- Richard Jones MSN: [EMAIL PROTECTED] Y!M: rwkjones http://www.jonze.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Nick Withers email: [EMAIL PROTECTED] Web: http://www.nickwithers.com Mobile: +61 414 397 446 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel module path
On Wed, Jun 07, 2006 at 11:28:09AM +0100, Richard Jones wrote: Hi, I'm having trouble loading kernel modules. Put simply make installkernel seems install native kernel modules into /boot/kernel/, but kldload seems to want to load them from /boot/modules. Obviously I can load modules by hand and/or copy the modules into /boot/modules, but surely there's a better way - either by modifying the installkernel behaviour or kldload. kldconfig(8) might be of help here. Dan -- Daniel Bye PGP Key: http://www.slightlystrange.org/pgpkey-dan.asc PGP Key fingerprint: D349 B109 0EB8 2554 4D75 B79A 8B17 F97C 1622 166A _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgp2oiJytjsnL.pgp Description: PGP signature
Re: Kernel module path
On Wed, Jun 07, 2006 at 10:40:54PM +1000, Nick Withers wrote:
On Wed, 7 Jun 2006 11:28:09 +0100
Richard Jones [EMAIL PROTECTED] wrote:
Hi,
I'm having trouble loading kernel modules. Put simply make
installkernel seems install native kernel modules into /boot/kernel/,
but kldload seems to want to load them from /boot/modules.
From kldload's man page:
FILES
/boot/kernel directory containing loadable modules.
Modules must have an extension of .ko.
This having been said, it _does_ look in /boot/modules as well.
I'm able to load a module from either directory without
specifying the full path and / or extension and without either
directory being my current working directory on 6.1-RELEASE.
What's the problem you're actually having? What version of
FreeBSD are you running?
Yes, sorry, that wasn't the most infomational email.
FreeBSD-6.1-RELEASE.
me ~ # ls -1 /boot/kernel
fire_saver.ko
if_tun.ko
ipfw.ko
kernel
libiconv.ko
libmchain.ko
linker.hints
linux.ko
smbfs.ko
me ~ # ls -1 /boot/kernel
nvidia.ko
linker.hints
me ~ # kldload smbfs
kldload: can't load smbfs: No such file or directory
me ~ # cp /boot/kernel/{smbfs.ko,libiconv.ko,libmchain.ko} /boot/modules/
me ~ # kldload smbfs
short pause
me ~ # kldstat
Id Refs AddressSize Name
1 12 0xc040 3c68c4 kernel
22 0xc07c7000 1f280linux.ko
31 0xc07e7000 3f2e00 nvidia.ko
61 0xc50e 2smbfs.ko
72 0xc4f51000 4000 libiconv.ko
82 0xc4154000 3000 libmchain.ko
--
Richard Jones
MSN: [EMAIL PROTECTED]
Y!M: rwkjones
http://www.jonze.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel module path
On 6/7/06, Richard Jones [EMAIL PROTECTED] wrote: Hi, I'm having trouble loading kernel modules. Put simply make installkernel seems install native kernel modules into /boot/kernel/, but kldload seems to want to load them from /boot/modules. 3rd party kernel modules go in /boot/modules and /boot/kernel is for FreeBSD only. Obviously I can load modules by hand and/or copy the modules into /boot/modules, but surely there's a better way - either by modifying the installkernel behaviour or kldload. Yes, this drives me nuts too. For example the kqemu port gets installed in /boot/kernel and highpoint's manuals tell you to install drivers there too. The problem is that if you rebuild your kernel or do a buildworld et. al. it will wipeout everything in /boot/kernel... This is why we have /boot/modules, everything in here will survive a kernel rebuild, buildworld, etc... From the loader man page (FreeBSD 6.1): module_path Sets the list of directories which will be searched for modules named in a load command or implicitly required by a dependency. The default value for this variable is ``/boot/kernel;/boot/modules''. From the hier man page (FreeBSD 6.1): /boot/ programs and configuration files used during operating system bootstrap defaults/ default bootstrapping configuration files; see loader.conf(5) kernel/pure kernel executable (the operating system loaded into memory at boot time). modules/ third-party loadable kernel modules; see kldstat(8) -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel module path
On Wednesday 07 June 2006 12:22, John Nielsen wrote: On Wednesday 07 June 2006 08:41, Daniel Bye wrote: On Wed, Jun 07, 2006 at 11:28:09AM +0100, Richard Jones wrote: Hi, I'm having trouble loading kernel modules. Put simply make installkernel seems install native kernel modules into /boot/kernel/, but kldload seems to want to load them from /boot/modules. Obviously I can load modules by hand and/or copy the modules into /boot/modules, but surely there's a better way - either by modifying the installkernel behaviour or kldload. kldconfig(8) might be of help here. There is a sysctl that controls this. By default on my 6-STABLE it is: %sysctl kern.module_path kern.module_path: /boot/kernel;/boot/modules;/usr/local/modules So the FreeBSD 5.x and newer default of putting kernel modules in /boot/kernel is covered. Check the output of the above command on your system and check /etc/sysctl.conf for any overrides. Oh, I don't think /usr/local/modules is there by default. It was added on my system by one of the FUSE ports I'm using. The first two are definitely there by default, though. Sorry for the misinformation. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel module path
On Wednesday 07 June 2006 08:41, Daniel Bye wrote: On Wed, Jun 07, 2006 at 11:28:09AM +0100, Richard Jones wrote: Hi, I'm having trouble loading kernel modules. Put simply make installkernel seems install native kernel modules into /boot/kernel/, but kldload seems to want to load them from /boot/modules. Obviously I can load modules by hand and/or copy the modules into /boot/modules, but surely there's a better way - either by modifying the installkernel behaviour or kldload. kldconfig(8) might be of help here. There is a sysctl that controls this. By default on my 6-STABLE it is: %sysctl kern.module_path kern.module_path: /boot/kernel;/boot/modules;/usr/local/modules So the FreeBSD 5.x and newer default of putting kernel modules in /boot/kernel is covered. Check the output of the above command on your system and check /etc/sysctl.conf for any overrides. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel module path
On 6/7/06, Richard Jones [EMAIL PROTECTED] wrote:
On Wed, Jun 07, 2006 at 10:40:54PM +1000, Nick Withers wrote:
On Wed, 7 Jun 2006 11:28:09 +0100
Richard Jones [EMAIL PROTECTED] wrote:
Hi,
I'm having trouble loading kernel modules. Put simply make
installkernel seems install native kernel modules into /boot/kernel/,
but kldload seems to want to load them from /boot/modules.
From kldload's man page:
FILES
/boot/kernel directory containing loadable modules.
Modules must have an extension of .ko.
This having been said, it _does_ look in /boot/modules as well.
I'm able to load a module from either directory without
specifying the full path and / or extension and without either
directory being my current working directory on 6.1-RELEASE.
What's the problem you're actually having? What version of
FreeBSD are you running?
Yes, sorry, that wasn't the most infomational email.
FreeBSD-6.1-RELEASE.
me ~ # ls -1 /boot/kernel
fire_saver.ko
if_tun.ko
ipfw.ko
kernel
libiconv.ko
libmchain.ko
linker.hints
linux.ko
smbfs.ko
me ~ # ls -1 /boot/kernel
nvidia.ko
linker.hints
me ~ # kldload smbfs
kldload: can't load smbfs: No such file or directory
me ~ # cp /boot/kernel/{smbfs.ko,libiconv.ko,libmchain.ko} /boot/modules/
me ~ # kldload smbfs
short pause
me ~ # kldstat
Id Refs AddressSize Name
1 12 0xc040 3c68c4 kernel
22 0xc07c7000 1f280linux.ko
31 0xc07e7000 3f2e00 nvidia.ko
61 0xc50e 2smbfs.ko
72 0xc4f51000 4000 libiconv.ko
82 0xc4154000 3000 libmchain.ko
Do you know if they ever fix crypto bug in mount_smbfs in FreeBSD 6.1?
--
BSD Podcasts @:
http://bsdtalk.blogspot.com/
http://freebsdforall.blogspot.com/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
