Re: Export Symbols from shared library without source

> > LD_PRELOAD=/topath/to/libdriver.so
> > export LD_PRELOAD
> > 
> > I get:
> > 
> > insmod ./interceptor.ko
> > insmod: error while loading shared libraries:
> > /path/to/libdriver.so: ELF file's phentsize not the 
> > expected size
> 
> Using LD_PRELOAD to pre-load a library is a facility useful
> for user applications. This will not help in whatever you
> are trying to do. The error you are seeing is not from
> insmod, it's from the run-time linker. If you had run 'ls'
> instead of insmod, you would have seen the same error.

Enlightened. And yes, I get the same error whenever i execute 
something. A constant reminder.

> > > insmod ./interceptor.ko
> > > Error inserting './interceptor.ko': -1 Unknown symbol in module
> > > 
> > > And in my log, I get this:
> > > 
> > > Jun 28 11:22:44 philyra kernel: interceptor: Unknown symbol
> > CniPluginUnload
> > > Jun 28 11:22:44 philyra kernel: interceptor: Unknown symbol
> > CNICallbackTable
> > > ...
> > > ...

RE: Device driver Major number

> However I want the system to dynamically allocate the 
major number

This can be done by passing 0 as the major number to register_chrdev,
It would return the major number assigned.

From 2.4 onwards the device filesystem or devfs was introduced

If you want to forget using mknod then use devfs_register_chrdev or
devfs_register_blkdev read 
http://www.linux-mag.com/2000-05/gear_01.html

Regards,
Gopu Bhaskar

--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/

Newbie Question

As a first step towards learning about Linux Kernel, i have compiled 
linux source code, and succesfully booted my machine using it (after 
having changed lilo).

What is the next steps i should take ?
I tried reading through O'Reilly's book on Linux Kernel, but not able to 
make out much. A lot of info. there is about various registers etc.. 
which i find difficult to understand at the moment.
I am new to C programming too.

Any inputs are very much appreciated.

Thanks.

--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/

Re: Kernel Compile Errors

Please do not send me personal mails.
Madhu Reddy wrote:
> So we shouldn't use existing config file.
It may not be  a good idea. Try configuring afresh.

Hth,
om

--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/

Getting drivers supported by Linux

Re: Getting drivers supported by Linux

Re: Newbie Question

I would start with learning C first, there are numerous books on this subject. 
After that 
http://www.moses.uklinux.net/patches/lki.html
and
http://www.win.tue.nl/%7Eaeb/linux/lk/lk.html
are good places to start for a broader understanding to work upto the O'Riely 
books.

On Monday 30 June 2003 10:42 pm, j4linman wrote:
> As a first step towards learning about Linux Kernel, i have compiled
> linux source code, and succesfully booted my machine using it (after
> having changed lilo).
>
> What is the next steps i should take ?
> I tried reading through O'Reilly's book on Linux Kernel, but not able to
> make out much. A lot of info. there is about various registers etc..
> which i find difficult to understand at the moment.
> I am new to C programming too.
>
> Any inputs are very much appreciated.
>
> Thanks.
>
> --
> Kernelnewbies: Help each other learn about the Linux kernel.
> Archive:       http://mail.nl.linux.org/kernelnewbies/
> FAQ:           http://kernelnewbies.org/faq/

--

-- 
Tom Bradley
Software Engineer
Jaycor / Titan Systems

--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/

Re: kernel module -> non-module

Please don't send me personal mails.
> 
> I was thinking about to compile the module not as a module rather
> statically into the kernel.
> (I don't want to load it with insmod rather is shall be part of vmlinuz.)
For both modules and statically linked ones, code will remain same.
you will have to put your module_init and module_exit functions like

#ifdef MODULE
module_init(my_mod_init)
module_exit(my_mod_exit)
#endif

You will have to call the module init function in one of the 
initialization functions. I forgot which one is it. Somebody will be 
able to do this.
 >>go to the directory in which you want to put your module in linux kernel
 >>source. open Config.in, and add you module's script.
 >>Modify the makefile in the directory to reflect your module addition.
 >>

To get a choce of module statically linked/dynamically linked, please 
follow this procedure

Hth,
Om.

--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/

Sleeping in the interrupt handler

Hi,

I know, that you are not allowed to sleep in an interrupt handler. How ever I am interested to understand the
reason(s) for that. Was this a design decision (e.g. to
simplify things) for the Linux kernel, or is there a fundamental reason that makes sleeping interrupt
handlers simply impossible? What about the page fault handler - it
(probably) sleeps when it has to swap in a page, why is it possible to sleep for the page fault handler and not
for an interrupt handler?

Thanks in advance for any answers
with best regards
Martin Maletinsky

P.S. Pls. put me on cc: in your reply, since I am not on the mailing list.

--
Supercomputing System AG          email: maletinsky <at> scs.ch
Martin Maletinsky                 phone: +41 (0)1 445 16 05
Technoparkstrasse 1               fax:   +41 (0)1 445 16 10
CH-8005 Zurich
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/