public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Arnd Bergmann <arnd@bergmann-dalldorf.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: klibc development release
Date: Fri, 09 Aug 2002 11:55:20 -0700	[thread overview]
Message-ID: <3D541018.4050004@zytor.com> (raw)
In-Reply-To: 200208091754.g79HsJkN058572@d06relay02.portsmouth.uk.ibm.com

Arnd Bergmann wrote:
>> You could say you are 50% there ;-)
> 
> For the autogenerated system call objects, a quick grep in include/asm-*/unistd
> showed some more that appear to be missing on some platforms:
> 
> alpha: alarm, fdatasync, getegid, geteuid, getgid, getpid, getppid, getuid, nice,
> 	pause, umount2, utime, time
> ia64:	alarm, fork, getpgrp, nice, pause, umount2, utime, vfork, time
> mips64: pivot_root, select, vfork
> mips:	vfork
> parisc: select, umount
> x86_64:	nice, umount
> sparc: setresgid, setresuid
> s390x: time
> s390: select
> m68k: pivot_root
 >

Hmf... some of these seem to be outright omissions (pivot_root() and 
umount2() especially), and probably indicate bugs or that the stock 
kernel isn't up to date anymore.

I can see umount() being missing (as in "use umount2()").  time() I 
guess can be emulated with gettimeofday(), but select() being missing is 
rather odd (is this a "emulate using poll()" philosophy?  Barf...)

If the maintainers of the above ports could give me a pointer to how the 
above system calls are expected to be done I'd appreciate it.  I'll 
probably look through the glibc sources for hints in the meantime.

	-hpa


  reply	other threads:[~2002-08-09 18:51 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-09  3:39 klibc development release H. Peter Anvin
2002-08-09 10:14 ` Andreas Schwab
2002-08-09 18:22   ` H. Peter Anvin
2002-08-09 11:33 ` Arnd Bergmann
2002-08-09 19:53   ` Arnd Bergmann
2002-08-09 18:55     ` H. Peter Anvin [this message]
2002-08-09 19:04       ` David Mosberger
2002-08-09 19:14         ` H. Peter Anvin
2002-08-09 22:27           ` Matti Aarnio
2002-08-09 22:37             ` H. Peter Anvin
2002-08-10  6:22             ` Erik Andersen
2002-08-10  6:24               ` H. Peter Anvin
2002-08-10 10:40             ` Christoph Hellwig
2002-08-10 10:48               ` H. Peter Anvin
2002-08-10 10:51                 ` Christoph Hellwig
2002-08-10 10:52                   ` H. Peter Anvin
2002-08-10  6:21           ` Erik Andersen
2002-08-09 19:55         ` H. Peter Anvin
2002-08-09 20:22           ` David Mosberger
2002-08-09 20:29             ` H. Peter Anvin
2002-08-09 20:16 ` Albert D. Cahalan
2002-08-09 20:22   ` H. Peter Anvin
2002-08-11  5:02     ` Rob Landley
2002-08-11 13:13       ` Alexander Viro
2002-08-12  2:29         ` Oliver Xymoron
2002-08-12  4:39           ` Alexander Viro
2002-08-09 22:03 ` Oliver Xymoron
2002-08-11  5:11   ` Rob Landley
2002-08-11 15:56     ` Oliver Xymoron
2002-08-11 18:20       ` Albert D. Cahalan
2002-08-11 15:31         ` Rob Landley
2002-08-11 21:04           ` Erik Andersen
2002-08-11 22:18             ` H. Peter Anvin
2002-08-12  3:17           ` Jamie Lokier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D541018.4050004@zytor.com \
    --to=hpa@zytor.com \
    --cc=arnd@bergmann-dalldorf.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox