Re: adding new system call problem

phil-news-nospam_at_ipal.net
Date: 03/29/05 

Date: 29 Mar 2005 00:15:27 GMT

On Mon, 28 Mar 2005 11:35:21 +0200 Kasper Dupont <kasperd@daimi.au.dk> wrote:

| "linux.lover" wrote:
|>
|> Hello,
|> How to resolve new system call number assignments. On Fedora
|> Core 1 i got next
|> .long SYMBOL_NAME(sys_myservice) /*259*/
|
| Avoid reserved system call numbers. Looks like 0-288 are
| currently reserved. And this will grow in the future.

Are there any reserved specifically for outside the scope of the kernel
development, or at least usable by a subdevelopment branch? Or would it
be better to get a number reserved in the main tree even though that
implementation would not be included there?

Of course, it would be good to avoid waste of a precious resource for
things like system call numbers.

I've got an ioctl() I implemented. Is there a safe number to use for it?
I'm using one now that has the same high order 8 bits as others for the
same type of device, and a higher (0xf0) value for the low 8 bits. And if
I were to submit it for main development inclusion and it were accepted,
would it be safe to assume the appropriate version developer would change
the actual value to an appropriate one? Or would I be expected to find
such a value myself, first? 

-- 
-----------------------------------------------------------------------------
| Phil Howard KA9WGN       | http://linuxhomepage.com/      http://ham.org/ |
| (first name) at ipal.net | http://phil.ipal.org/   http://ka9wgn.ham.org/ |
-----------------------------------------------------------------------------