All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Schilling <schilling@fokus.fraunhofer.de>
To: schilling@fokus.fraunhofer.de, jengelh@linux01.gwdg.de
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, drepper@redhat.com,
	austin-group-l@opengroup.org
Subject: Re: The naming of at()s is a difficult matter
Date: Tue, 14 Feb 2006 16:09:54 +0100	[thread overview]
Message-ID: <43F1F2C2.nailMWZGOQDYR@burner> (raw)
In-Reply-To: <Pine.LNX.4.61.0602140916440.7198@yvahk01.tjqt.qr>

Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:

>
> >> > I have noticed that the new ...at() system calls are named in what
> >> > appears to be a completely haphazard fashion.  In Unix system calls,
> >> > an f- prefix means it operates on a file descriptor; the -at suffix (a
> >> > prefix would have been more consistent, but oh well) similarly
> >> > indicates it operates on a (directory fd, pathname) pair.
> >> >
> >> shmat operates on dirfd/pathname?
> >
> >Do you have a better proposal for naming the interfaces?
> >
>
> chownfn maybe. (fd + name)

I am not shure if this would match the rules from the Opengroup.
Solaris has these interfaces since at least 5 years.

Jörg

-- 
 EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
       js@cs.tu-berlin.de                (uni)  
       schilling@fokus.fraunhofer.de     (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily

  reply	other threads:[~2006-02-14 15:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-12  3:33 The naming of at()s is a difficult matter H. Peter Anvin
2006-02-12 10:37 ` Jan Engelhardt
2006-02-12 17:42   ` H. Peter Anvin
2006-02-13 14:09   ` Joerg Schilling
2006-02-13 15:56     ` H. Peter Anvin
2006-02-14  8:17     ` Jan Engelhardt
2006-02-14 15:09       ` Joerg Schilling [this message]
2006-02-14 15:21         ` H. Peter Anvin
2006-02-14 16:13           ` Matthew Frost
2006-02-14 17:00           ` Joerg Schilling
2006-02-14 17:35             ` H. Peter Anvin
2006-02-14 18:07         ` Jan Engelhardt
2006-02-14 18:12           ` H. Peter Anvin
2006-02-14 18:17             ` Jan Engelhardt
2006-02-14 18:53             ` Joerg Schilling
2006-02-14 18:51           ` Joerg Schilling
2006-02-12 14:41 ` Jim Meyering

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=43F1F2C2.nailMWZGOQDYR@burner \
    --to=schilling@fokus.fraunhofer.de \
    --cc=austin-group-l@opengroup.org \
    --cc=drepper@redhat.com \
    --cc=hpa@zytor.com \
    --cc=jengelh@linux01.gwdg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.