From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eduardo Pereira Habkost Subject: Re: Mess over open( Date: Tue, 20 Jul 2004 12:28:11 -0300 Sender: linux-8086-owner@vger.kernel.org Message-ID: <20040720152811.GF6069@duckman.distro.conectiva> References: <20040720021951.99294.qmail@web51303.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TiqCXmo5T1hvSQQg" Return-path: Content-Disposition: inline In-Reply-To: <20040720021951.99294.qmail@web51303.mail.yahoo.com> List-Id: To: linux-8086@vger.kernel.org --TiqCXmo5T1hvSQQg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable You have made exactly the same question about the "execve" sytem call, some weeks ago. 8) System calls are not linked magically using their names, but we should have a system call interface that makes libc notify the kernel that some syscall should be called. Take a look at arch/i86/kernel/syscall.dat, mkentry.sh and the entry.c (it is generated by mkentry.sh), if you want to know how it works. If you are looking for the system calls' implementations, look at sys_execve, sys_open, sys_fork, and others sys_* functions. On Mon, Jul 19, 2004 at 07:19:51PM -0700, Tommy McCabe wrote: > Although the open( call seems to be used everywhere > (in around 70 source code files), it isn't defined > anywhere. How can ELKS get past booting if a call > isn't defined? >=20 --=20 Eduardo --TiqCXmo5T1hvSQQg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFA/ToLcaRJ66w1lWgRAtexAJ430CTTej/Q36x2MJK44doOkAx5HACfQILz 1C0oY6bfY+ms5aFmIEbXn6Q= =gcE1 -----END PGP SIGNATURE----- --TiqCXmo5T1hvSQQg--