Re: syscall reference
- From: Joe Pfeiffer <pfeiffer@xxxxxxxxxxx>
- Date: Tue, 22 Apr 2008 22:18:00 -0600
"Bill Cunningham" <nospam@xxxxxxxxx> writes:
In other words IPC looks like a good place to begin learning the kernel.
Even if technically I am not using the kernel. And there is alot more than
pipes, there's signals and so on here but pipes are a good place to start.
Read and write are only a couple of examples of what a complete syscall
reference should give. The trouble is that the linux kernel is living. By
that I mean it's not like and old Unix v6 or 7 for a pdp.
But for those calls -- and, really, for the vast majority of calls a
user needs to deal with -- it is. write() is really simple: you pass
it a file descriptor, the address of a buffer containing data you want
to send, and how many bytes you want to send. It does it. That's
what it did in v6 when I started on an 11/34, and that's what it does
now.
So much has
changed from 2.0 or even the 2.2 code to buy a reference might seem in the
long run fruitless. Then again it might be worth it.
But it hasn't. The stuff that's changed is down in the kernel
internals, and you're not doing anything anywhere near that. The old
4.4bsd ipc tutorial (easily found through google) is as relevant now
as it was in 1980 or whenever it came out.
You've started with an almost-working piece of code you got from
somebody. Want to find out how the calls work? 'man 2 read'
.
- Follow-Ups:
- Re: syscall reference
- From: Bill Cunningham
- Re: syscall reference
- References:
- syscall reference
- From: Bill Cunningham
- Re: syscall reference
- From: Joe Pfeiffer
- Re: syscall reference
- From: Bill Cunningham
- syscall reference
- Prev by Date: Way cool
- Next by Date: Re: Way cool
- Previous by thread: Re: syscall reference
- Next by thread: Re: syscall reference
- Index(es):
Relevant Pages
|
