mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: jmorris@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: sysctl vs /proc/sys
Date: Fri, 12 Dec 2003 22:46:49 +0900 (JST)	[thread overview]
Message-ID: <20031212.224649.20046672.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <Xine.LNX.4.44.0312120815170.2611-100000@thoron.boston.redhat.com>

In article <Xine.LNX.4.44.0312120815170.2611-100000@thoron.boston.redhat.com> (at Fri, 12 Dec 2003 08:20:41 -0500 (EST)), James Morris <jmorris@redhat.com> says:

> On Fri, 12 Dec 2003, YOSHIFUJI Hideaki / [iso-2022-jp] ^[$B5HF#1QL@^[(B wrote:
> 
> > Or, I'd rather propose introducing sysctlbyname(2).
> 
> See the thread at 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=105788786819578&w=2

Thanks, James. I think I missed the thread.

Well, some applications which can run on *BSD* and Linux uses sysctl.
Because using procfs changes the semantics, I'd love to have sysctlbyname().

Can we get the exact previous value from /proc/sys atomicly?
If so, I'm ok not to have sysctlbyname(2) 
because we can have sysctlbyname(3).

If no, please let's have sysctlbyname(2); there ARE
something we cannot do only without sysctl variants.

Note: sysctlbyname(3) and sysctlnametomib(3) is in FreeBSD.

--yoshfuji



 

  reply	other threads:[~2003-12-12 13:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-12 12:58 YOSHIFUJI Hideaki / 吉藤英明
2003-12-12 13:20 ` James Morris
2003-12-12 13:46   ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2003-12-12 14:28     ` James Morris
2003-12-12 18:15       ` Mike Fedyk
2003-12-13  0:42         ` YOSHIFUJI Hideaki / 吉藤英明
2003-12-13  1:31           ` H. Peter Anvin
2003-12-13  2:06             ` Linux Kernel 2.6.0-test11 VFS problem Ananda Bhattacharya
2003-12-13  2:30               ` Mike Fedyk

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=20031212.224649.20046672.yoshfuji@linux-ipv6.org \
    --to=yoshfuji@linux-ipv6.org \
    --cc=jmorris@redhat.com \
    --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
all inboxes | Powered by JetHome®