All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: about __ARCH_WANT_SYS_GETHOSTNAME
Date: Sat, 01 Apr 2006 11:53:26 -0700	[thread overview]
Message-ID: <m1slox86vt.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0603310911260.6105@shark.he.net> (Randy Dunlap's message of "Fri, 31 Mar 2006 09:21:43 -0800 (PST)")

"Randy.Dunlap" <rdunlap@xenotime.net> writes:

> Hi,
>
> What was/is the purpose of __ARCH_WANT_SYS_GETHOSTNAME?
> and why do a few arches not #define it?
>
> If it is not #defined, should those arches supply their own
> sys_gethostname() function?
>
> 21 arches #define __ARCH_WANT_SYS_GETHOSTNAME.
> A few don't:  frv, ia64, & xtensa.
> But all arches (except for um) #define __NR_gethostname.
>
> Is __ARCH_WANT_SYS_GETHOSTNAME just crufty and doesn't matter
> any more?

I know you can implement it by simply calling uname.
Beyond that I am puzzled.

Eric

      reply	other threads:[~2006-04-01 18:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31 17:21 about __ARCH_WANT_SYS_GETHOSTNAME Randy.Dunlap
2006-04-01 18:53 ` Eric W. Biederman [this message]

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=m1slox86vt.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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.