All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Chuck <chuck@intelligence.org>
Cc: netdev@vger.kernel.org
Subject: Re: How to set domainname with iproute2? (net-tools deprecation)
Date: Fri, 13 Mar 2020 10:00:41 -0700	[thread overview]
Message-ID: <20200313100041.374b26da@hermes.lan> (raw)
In-Reply-To: <CAPwpnyTDpkX2hxiqYLxTuMM38cq+whPSC0yoee-YPLEAwfvqpQ@mail.gmail.com>

On Fri, 13 Mar 2020 09:21:52 -0700
Chuck <chuck@intelligence.org> wrote:

> I see calls to move the world from net-tools to iproute2 [1] [2] [3].
> 
> My Linux distro uses the `hostname` executable from net-tools to set the
> hostname, which simply passes it through to the `sethostname` system call.
> I don't see any references to `sethostname` in the iproute2 sources.  I
> guess the replacement is systemd's `hostnamectl set-hostname`?
> 
> My distro uses the `domainname` executable (which is a symlink to
> `hostname`) from net-tools to set the domain name, which simply passes it
> through to the `setdomainname` system call.  I don't see any calls
> to `sethostname` in either iproute2 or systemd.
> 
> What is the recommended way to set the domain name during system
> start-up without net-tools?
> 
> (Asking here because iproute2 is supposed to replace net-tools.  If this is
> not the right list for this, 1. Apologies, and 2. Where is the right place
> for this inquiry?)
> 
> [1] https://lwn.net/Articles/710533/
> [2] https://lwn.net/Articles/710535/
> [3] https://wiki.linuxfoundation.org/networking/iproute2

Iproute2 is focused around netlink and supporting the kernel networking.

      reply	other threads:[~2020-03-13 17:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-13 16:21 How to set domainname with iproute2? (net-tools deprecation) Chuck
2020-03-13 17:00 ` Stephen Hemminger [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=20200313100041.374b26da@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=chuck@intelligence.org \
    --cc=netdev@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.