On Tue, 18 Sep 2001, Usman S. Ansari wrote: > Erik, > > I understand what you are saying. My module will be a product (other pieces > comming from other people in the team), and is not extension to the kernel. > User application provide authentication (lot of maths). My module needs to run > in the kernel. Other point, I will not be able to export sys_select, as this > product will be shipped as a mdule and we will not be able to recompile kernel > on the end user machine. If you MUST run in the kernel, and you MUST communicate via sockets, then split your code into a lightweight module and a userspace program which uses sockets. They can then communicate via standard mechanisms (ie. /dev, /proc and ioctl). The lightweight module should contain ONLY the code which has to run in the kernel, nothing more. Regardless of what I say though, listen to Erik. He knows what he's talking about. Regards, Paul Gearon Software Engineer Telephone: +61 7 3876 2188 Plugged In Software Fax: +61 7 3876 4899 http://www.PIsoftware.com PGP Key available via finger Catapultam habeo. Nisi pecuniam omnem mihi dabis, ad caput tuum saxum immane mittam. (Translation from latin: "I have a catapult. Give me all the money, or I will fling an enormous rock at your head.") - Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ IRC Channel: irc.openprojects.net / #kernelnewbies Web Page: http://www.kernelnewbies.org/
