From: ariel@yon.engr.sgi.com (Ariel Faigon)
To: linux@yon.engr.sgi.com
Cc: vjs@yon.engr.sgi.com (Vernon Schryver),
dmk@yon.engr.sgi.com (David Marc Katinsky)
Subject: Name the external domain
Date: Fri, 30 May 1997 15:32:28 -0700 (PDT) [thread overview]
Message-ID: <199705302232.PAA21736@yon.engr.sgi.com> (raw)
Hi Linuxies,
Next Wednesday we are finally going to have our external
linux machine online. As it turns out the networking
gurus (vernon) require us to use a third level domain
for very good reasons, so we cannot call the machine
"linux.sgi.com".
We want a domain name that's cool, friendly to outside
people, entertaining, that doesn't sound too official
and that's scalable" (general enough to put more
"share with the world" hostnames under it in the future.
I hate to start a long thread but this name will last
for many years so I cannot have my fascist opinion rule
here. Here's what people suggested so far:
[linux.] outside.sgi.com
[linux.] unchained.sgi.com
[linux.] untied.sgi.com
[linux.] at.sgi.com
[linux.] friends.sgi.com
Lets have some more suggestions and then vote on this.
We need to give Vernon a name soon.
--
Peace, Ariel
WARNING: multiple messages have this Message-ID (diff)
From: ariel@yon.engr.sgi.com (Ariel Faigon)
To: linux@yon.engr.sgi.com
Cc: Vernon Schryver <vjs@yon.engr.sgi.com>,
David Marc Katinsky <dmk@yon.engr.sgi.com>
Subject: Name the external domain
Date: Fri, 30 May 1997 15:32:28 -0700 (PDT) [thread overview]
Message-ID: <199705302232.PAA21736@yon.engr.sgi.com> (raw)
Message-ID: <19970530223228.ReBIKyWoe78YEh27XZWcfhtIAJLd0bb3cSmwSWdfywQ@z> (raw)
Hi Linuxies,
Next Wednesday we are finally going to have our external
linux machine online. As it turns out the networking
gurus (vernon) require us to use a third level domain
for very good reasons, so we cannot call the machine
"linux.sgi.com".
We want a domain name that's cool, friendly to outside
people, entertaining, that doesn't sound too official
and that's scalable" (general enough to put more
"share with the world" hostnames under it in the future.
I hate to start a long thread but this name will last
for many years so I cannot have my fascist opinion rule
here. Here's what people suggested so far:
[linux.] outside.sgi.com
[linux.] unchained.sgi.com
[linux.] untied.sgi.com
[linux.] at.sgi.com
[linux.] friends.sgi.com
Lets have some more suggestions and then vote on this.
We need to give Vernon a name soon.
--
Peace, Ariel
next reply other threads:[~1997-05-30 22:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-05-30 22:32 Ariel Faigon [this message]
1997-05-30 22:32 ` Name the external domain Ariel Faigon
1997-05-30 22:36 ` David S. Miller
1997-05-30 22:39 ` Mike Shaver
1997-06-02 6:43 ` Martin Knoblauch
1997-06-03 6:19 ` Raj Mathur
1997-05-30 22:51 ` richard offer
1997-05-30 23:04 ` Bob Mende Pie
[not found] ` <mende@piecomputer.engr.sgi.com>
1997-06-02 17:58 ` Christopher W. Carlson
-- strict thread matches above, loose matches on Subject: below --
1997-05-30 22:44 Larry McVoy
1997-05-30 23:12 ` Ariel Faigon
1997-05-30 23:12 ` Ariel Faigon
1997-06-02 6:44 ` Martin Knoblauch
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=199705302232.PAA21736@yon.engr.sgi.com \
--to=ariel@yon.engr.sgi.com \
--cc=ariel@sgi.com \
--cc=dmk@yon.engr.sgi.com \
--cc=linux@yon.engr.sgi.com \
--cc=vjs@yon.engr.sgi.com \
/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