9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Daryl M" <glenda@mc2research.org>
To: <9fans@9fans.net>
Subject: [9fans] Newby Question on setting hostname
Date: Mon,  7 Apr 2014 19:47:02 -0700	[thread overview]
Message-ID: <001a01cf52d4$d2712ad0$77538070$@mc2research.org> (raw)

Greetings,

I spent time this weekend experimenting with, and learning about,
configuring my Plan9 machine as a simple,
DHCP client, terminal.  Networking now seems to work reliably: DNS is
resolving names, I can ping machines
locally and across the internet by both name and IP address.  I can also
connect to sources at bell labs and
browse them.  Timezone has been set and I even created another user though I
am not yet happy with the
results so have more to learn in that area.

Now, I want to set the machine's name.  From the Plan9 Wiki and searching
through the 9fans archives I now know:
          1) Editing /rc/bin/termrc to replace the default name, gnot, with
my machine's name is "not the right way".
          2) A post from earlier this year just said to edit /lib/ndb/local
and that there were plenty of examples.
	In reality, the only examples are for machines with static IP
addresses.
          3) A post from 2007 said to add an entry to /lib/ndb/local of the
form:
	  sys=<machinename>    ether=<MACaddress>
	Replacing <machinename> with the desired name of my machine and
replacing <MACaddress>
	with that machine's MAC address.  This works 	fine, but it could
get a bit unwieldy for configuring large
	numbers of machines.
          4) Another post said to just
	  echo -n <machinename> > /dev/sysname
	in /rc/bin/termrc.local.  I tested it and it also works fine and
seems to be the easiest.

My question is: What is the REAL preferred method for setting the machine
name?  #1, #3, #4, or something else?

Thank you,
Daryl M






             reply	other threads:[~2014-04-08  2:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08  2:47 Daryl M [this message]
2014-04-08  3:01 ` Lee Fallat
2014-04-08  3:59   ` Ramakrishnan Muthukrishnan
2014-04-08  4:05     ` erik quanstrom

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='001a01cf52d4$d2712ad0$77538070$@mc2research.org' \
    --to=glenda@mc2research.org \
    --cc=9fans@9fans.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).