[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linuxsh-dev
Subject:    Re: Why syscall number changed on 2.6.21 ?
From:       Paul Mundt <lethal () linux-sh ! org>
Date:       2007-05-10 7:21:50
Message-ID: 20070510072150.GB27316 () linux-sh ! org
[Download RAW message or body]

On Thu, May 10, 2007 at 04:04:34PM +0900, SUGIOKA Toshinobu wrote:
> Syscall number from '__NR_add_key' to '__NR_inotify_rm_watch'
> have been changed in 2.6.21
> 
> So, glibc is now incompatible on latest kernel.
> Why these are changed ?
> 
inotify was there first, and libinotify has been using that number for
some time. It was accidentally renumbered earlier when the key syscalls
went in, so this is just correcting that behaviour.

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
linuxsh-dev mailing list
linuxsh-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsh-dev
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic