Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1422749AbWBNSR7 (ORCPT ); Tue, 14 Feb 2006 13:17:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1422751AbWBNSR7 (ORCPT ); Tue, 14 Feb 2006 13:17:59 -0500 Received: from linux01.gwdg.de ([134.76.13.21]:26073 "EHLO linux01.gwdg.de") by vger.kernel.org with ESMTP id S1422749AbWBNSR6 (ORCPT ); Tue, 14 Feb 2006 13:17:58 -0500 Date: Tue, 14 Feb 2006 19:17:52 +0100 (MET) From: Jan Engelhardt To: "H. Peter Anvin" cc: Joerg Schilling , linux-kernel@vger.kernel.org, drepper@redhat.com, austin-group-l@opengroup.org Subject: Re: The naming of at()s is a difficult matter In-Reply-To: <43F21D84.8010907@zytor.com> Message-ID: References: <43EEACA7.5020109@zytor.com> <43F09320.nailKUSI1GXEI@burner> <43F1F2C2.nailMWZGOQDYR@burner> <43F21D84.8010907@zytor.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1011 Lines: 22 >> > > > 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. >> This is not the cdrecord thread so Solaris is a no-go in this very one. > > FWIW, I think the -at() suffix is just fine, and well established by now (yes, > there is shmat, but the SysV shared memory interfaces are bizarre to begin with > -- hence POSIX shared memory which has real names.) > Yep. Someday, Linux - or rather glibc! for that matter, as it is the one which translates FUNCTIONNAME() into a syscall -- will be like the Windows API. Full of compatibility stuff. And you can't do anything about it :) Jan Engelhardt -- - 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/