Proper way to release binary-only driver?

I have the need to distribute a binary-only driver (no flames, please), but I am not certain how to build it so that it can be used on multiple kernel versions. (Or is this impossible?) I didn't find any "HOWTO (or recommendation) for proper binary-only driver release etiquette", so if there ar

smp_num_cpus redefined? (compiling 2.2.18 for non-SMP?)

I have a problem that would have started out as "I can't compile my device driver with 2.2.18". I was compiling my device driver for non-SMP while my kernel (and thus /usr/src/linux) was SMP. So I looked at compiling the kernel for non-SMP so that my /usr/src/linux would be non-SMP and my devic

RE: bidirectional named pipe?

Many thanks to all who have suggested to use UNIX domain sockets. That was my first thought--I just didn't know how to preserve the existing named interface. And yes, I have consulted several "decent" UNIX programming books which have led me to the likelihood that what I want to do cannot be do

RE: bidirectional named pipe?

I thought mkfifo was only unidirectional... Brendan Please cc: me personally, as I am not subscribed. -Original Message- From: J . A . Magallon [mailto:[EMAIL PROTECTED]] Sent: Friday, February 02, 2001 4:47 PM To: Miller, Brendan Cc: 'linux-kernel @ vger . kernel . org' S

bidirectional named pipe?

I've countless web searches and linux-kernel archives, but I haven't yet found the answer to my question. I'm porting some software to Linux that requires use of a bidirectional, named pipe. The architecture is as follows: A server creates a named pipe in the /tmp directory. Any client can th