9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Anthony Sorace <a@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] first questions from a lurker
Date: Mon, 10 Mar 2014 11:40:24 -0400	[thread overview]
Message-ID: <2113BA17-9067-44DD-A7BB-4709C99D52C3@9srv.net> (raw)
In-Reply-To: <201403101441.s2AEfCe1009674@freefriends.org>

[-- Attachment #1: Type: text/plain, Size: 2470 bytes --]

Welcome to the party.

On Mar 10, 2014, at 10:41 , arnold@skeeve.com wrote:

> 0. How to see my IP address? Cat a file in /net/... somewhere?

As Charles said, 'cat /net/ipselftab'. You most likely want the lines
with 'u' in the flags filed (third column), which will most likely include
just the loopback address and your "real" address.

> 1. How to change the hostname - just edit /rc/bin/termrc and choose
>   whatever I want to echo into /dev/sysname?  Will that get reflected
>   back out to the corporate net via DHCP?

You could do that. The "right" way to do it is make your ndb
database in /lib/ndb map your ip address to the sysname you want.
Take a look at the examples in there and ndb(6) and see if that gets
you what you're after.

I'm not sure what your second sentence means. DHCP clients don't
broadcast changes out. If you want that server to advertise things,
you'll have to look there.

> 2. How to use DHCP to get to the corporate DNS servers?  (This worked
>   pretty much OOTB on the labs dist, but I think that 9atom will be
>   the better match for the work we want to do.)  Right now all
>   hostname lookups (via ping) fail.

I'm not sure why this would behave differently. Check if the local dns
resolver is running; 'ps | grep dns' and 'ls /srv/dns' should both give
positive results. If either one doesn't, it's not running; rm any stale
/srv/dns and re-start it with 'ndb/dns -r'.

I don't know that VBox's NAT will do anything helpful with the dhcp
requests, though.

> 3. I would like to generate a PDF (or even .PS file) of Volume 1 of the
> manual. What's in the dist has dates from over 10 years ago. I tried
> running 'mk print.out' in the manual directory (as glenda) but got
> an error.  (Erik - can you do that automatically as part of your build
> process? :-)  So. How can I produce such a file suitable for duplex
> printing? (Bonus points if the intro(N) page of each section comes
> out first. :-)

What error did you get? I just tried that on my (slightly out-of-date)
9atom installation (as myself) and it worked fine. The resulting
print.out is troff output; lp can give you PostScript from that.

You could also buy a lovely bound copy of both volumes from Vita
Nuova. :-) Hard copy is still very nice from time to time.

> 4. How to do the moral equivalent of shutdown -h now?

'fshalt -h'. I'm not confident the -h part will do much in Virtual Box.

Have fun.


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 169 bytes --]

  parent reply	other threads:[~2014-03-10 15:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 14:41 arnold
2014-03-10 14:49 ` arnold
2014-03-10 15:46   ` erik quanstrom
2014-03-10 14:55 ` Peter Hull
2014-03-10 15:00 ` Charles Forsyth
2014-03-10 15:40 ` Anthony Sorace [this message]
2014-03-10 16:10 ` erik quanstrom
2014-03-10 16:55 ` Bakul Shah
2014-03-10 19:53   ` arnold
2014-03-11  9:22   ` Peter Hull
2014-03-16 15:45 trebol

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=2113BA17-9067-44DD-A7BB-4709C99D52C3@9srv.net \
    --to=a@9srv.net \
    --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).