10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am getting this error:
Can't locate loadable object for module IO::Tty in @INC (@INC contains: /production/79p/perl5/lib/site_perl/5.28.0/x86_64-linux /production/79p/perl5/lib/site_perl/5.28.0 /production/79p/perl5/lib/5.28.0/x86_64-linux /production/79p/perl5/lib/5.28.0... (2 Replies)
Discussion started by: mrn6430
2 Replies
2. Linux
Hi everyone,
I am trying to prevent the ehci_hcd kernel module to load at boot time.
Here's what I've tried so far:
1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here):
2) Blacklisted the module by adding the following string to
3) Tried to blacklist the module... (0 Replies)
Discussion started by: gacanepa
0 Replies
3. UNIX for Advanced & Expert Users
Hi all!
I am trying to register a device in an existing device class, but I am
having trouble getting the pointer to an existing class.
I can create a class in a module, get the pointer to it and then use
it to register the device with:
*cl = class_create(THIS_MODULE, className);... (0 Replies)
Discussion started by: hdaniel@ualg.pt
0 Replies
4. Programming
cannot generate .ko file on my linux, although it can generate module.symvers.
But when I copy .c file and Makefile to another linux computer, there's no problem.
The strange thing is: make is successfuly executed, and returned 0;
make output:
make -C /lib/modules/2.6.18-92.el5xen/build ... (4 Replies)
Discussion started by: vistastar
4 Replies
5. Programming
can a linux kernel module call libc functions, such as printf(), strcpy(), etc...? (9 Replies)
Discussion started by: vistastar
9 Replies
6. Shell Programming and Scripting
I am trying to use the GD module on a on Unix Solaris environment machine by including gd.pm from a temporary location
but I am receiving the following error:
perl -w polyline.pl > imageoutput.png
Can't locate loadable object for module GD in @INC (@INC contains:... (1 Reply)
Discussion started by: wadhwa.pooja
1 Replies
7. UNIX for Dummies Questions & Answers
Hi,
Does anyone know if it is possible to know the current value of a kernel module parameters after the module is loaded. Are the values of the parameters advertised at some /proc or /sys location ?
The only thing I know is modinfo, that actually looks a the module .ko and gives a... (3 Replies)
Discussion started by: macL
3 Replies
8. SuSE
Hi All,
Is there a max number of slabs that can be used per kernel module? I'm having a tough time finding out that kind of information, but the array 'node_zonelists' (mmzone.h) has a size of 5. I just want to avoid buffer overruns and other bad stuff.
Cheers,
Brendan (4 Replies)
Discussion started by: Brendan Kennedy
4 Replies
9. Solaris
I have Apache 2 webserver as delivered with the Solaris 10 installation.
How to verify if Apache is configured with loadable module support?
Or if needs to be recompiled with loadable module support. (2 Replies)
Discussion started by: kavera
2 Replies
10. Linux
Hi Everyone!
How can we make a socket() system call from a linux module executing in kernel space?
If any one knows, kindly tell me. It will be great.
I want to use the socket interface in linux kernel space for sending raw packets over the network.
Hamayun (0 Replies)
Discussion started by: mian_m_hamayun
0 Replies
KLD(4) BSD Kernel Interfaces Manual KLD(4)
NAME
kld -- dynamic kernel linker facility
DESCRIPTION
The LKM (Loadable Kernel Modules) facility has been deprecated in FreeBSD 3.0 and above in favor of the kld interface. This interface, like
its predecessor, allows the system administrator to dynamically add and remove functionality from a running system. This ability also helps
software developers to develop new parts of the kernel without constantly rebooting to test their changes.
Various types of modules can be loaded into the system. There are several defined module types, listed below, which can be added to the sys-
tem in a predefined way. In addition, there is a generic type, for which the module itself handles loading and unloading.
The FreeBSD system makes extensive use of loadable kernel modules, and provides loadable versions of most file systems, the NFS client and
server, all the screen-savers, and the iBCS2 and Linux emulators. kld modules are placed by default in the /boot/kernel directory along with
their matching kernel.
The kld interface is used through the kldload(8), kldunload(8) and kldstat(8) programs.
The kldload(8) program can load either a.out(5) or ELF formatted loadable modules. The kldunload(8) program unloads any given loaded module,
if no other module is dependent upon the given module. The kldstat(8) program is used to check the status of the modules currently loaded
into the system.
Kernel modules may only be loaded or unloaded if the system security level kern.securelevel is less than one.
MODULE TYPES
Device Driver modules
New block and character device drivers may be loaded into the system with kld. Device nodes for the loaded drivers are automatically created
when a module is loaded and destroyed when it is unloaded by devfs(5). You can specify userland programs that will run when new devices
become available as a result of loading modules, or existing devices go away when modules are unloaded, by configuring devd(8).
FILES
/boot/kernel directory containing module binaries built for the kernel also residing in the directory.
/usr/include/sys/module.h file containing definitions required to compile a kld module
/usr/share/examples/kld example source code implementing a sample kld module
SEE ALSO
kldfind(2), kldfirstmod(2), kldload(2), kldnext(2), kldstat(2), kldunload(2), devfs(5), devd(8), kldload(8), kldstat(8), kldunload(8),
sysctl(8)
HISTORY
The kld facility appeared in FreeBSD 3.0 and was designed as a replacement for the lkm facility, which was similar in functionality to the
loadable kernel modules facility provided by SunOS 4.1.3.
AUTHORS
The kld facility was originally implemented by Doug Rabson <dfr@FreeBSD.org>.
BUGS
If a module B, is dependent on another module A, but is not compiled with module A as a dependency, then kldload(8) fails to load module B,
even if module A is already present in the system.
If multiple modules are dependent on module A, and are compiled with module A as a dependency, then kldload(8) loads an instance of module A
when any of the modules are loaded.
If a custom entry point is used for a module, and the module is compiled as an 'ELF' binary, then kldload(8) fails to execute the entry
point.
kldload(8) returns the cryptic message 'ENOEXEC (Exec format error)' for any error encountered while loading a module.
When system internal interfaces change, old modules often cannot detect this, and such modules when loaded will often cause crashes or myste-
rious failures.
BSD
November 8, 1998 BSD