Date: Sun, 5 Sep 2004 11:31:14 -0700
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: eric@cisu.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Quick Syscall question
Message-Id: <20040905113114.313efdf2.rddunlap@osdl.org>
In-Reply-To: <200409051317.42691.eric@cisu.net>
References: <200409051317.42691.eric@cisu.net>
Organization: OSDL
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1096
Lines: 26

On Sun, 5 Sep 2004 13:17:42 -0500 Eric Bambach wrote:

| Hello,
| 
| 	This may seem like a silly question, however we were all beginning 
| programmers once ;)
| 
| 	I want to do some manipulating of network interfaces and routing and such. I 
| am reading through some of the linux net sources but am confused on what are 
| internal, kernel-only functions and what are externally visable syscalls. How 
| can I tell from the source what is user-space visable that I can hook into 
| and what is intternel stuff? Should I just be looking at headers or do I have 
| to delve into the .c sources? I can do either, I just need a pointer on where 
| to start and what I should be looking for.

Most syscalls are listed in include/linux/syscalls.h.
Also look in include/asm-*/unistd.h.
Also in entry.S in arch/*/ (various sub-directory levels).

--
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/