From: ariel@yon.engr.sgi.com (Ariel Faigon)
To: lm@neteng.engr.sgi.com (Larry McVoy)
Cc: davem@jenolan.rutgers.edu, ariel@sgi.com, linux@neteng.engr.sgi.com
Subject: Re: Name the external domain
Date: Fri, 30 May 1997 16:12:29 -0700 (PDT) [thread overview]
Message-ID: <199705302312.QAA22076@yon.engr.sgi.com> (raw)
In-Reply-To: <199705302244.PAA11945@neteng.engr.sgi.com> from "Larry McVoy" at May 30, 97 03:44:59 pm
:
:OK, I got a better idea. Make the top level domain linux.sgi.com and
:the machine[s] stuff like
:
: linus.linux.sgi.com # because we like him (alias)
linus.youre-hired.sgi.com (well, we tried :-) (*)
: ftp.linux.sgi.com # because people will remember it (alias)
: www.linux.sgi.com # alias
: linux.linux.sgi.com # real machine
:
:Watcha all think?
:
Except for the fact that this is not scalable beyond linux stuff
I like it. It is certainly the easiest to remember and we can always
add entertaining names/aliases at the hostname level. 'friends' was my
next favorite.
If everyone agrees (and vernon doesn't object) I think we should go
with Larry's scheme.
(*) and we haven't gave up yet.
--
Peace, Ariel
WARNING: multiple messages have this Message-ID (diff)
From: ariel@yon.engr.sgi.com (Ariel Faigon)
To: Larry McVoy <lm@neteng.engr.sgi.com>
Cc: davem@jenolan.rutgers.edu, ariel@sgi.com, linux@neteng.engr.sgi.com
Subject: Re: Name the external domain
Date: Fri, 30 May 1997 16:12:29 -0700 (PDT) [thread overview]
Message-ID: <199705302312.QAA22076@yon.engr.sgi.com> (raw)
Message-ID: <19970530231229.9MK3f985iUwZhe-i4Wdg5Z8f1EgRErl7MbzVtuX_GHA@z> (raw)
In-Reply-To: <199705302244.PAA11945@neteng.engr.sgi.com> from "Larry McVoy" at May 30, 97 03:44:59 pm
:
:OK, I got a better idea. Make the top level domain linux.sgi.com and
:the machine[s] stuff like
:
: linus.linux.sgi.com # because we like him (alias)
linus.youre-hired.sgi.com (well, we tried :-) (*)
: ftp.linux.sgi.com # because people will remember it (alias)
: www.linux.sgi.com # alias
: linux.linux.sgi.com # real machine
:
:Watcha all think?
:
Except for the fact that this is not scalable beyond linux stuff
I like it. It is certainly the easiest to remember and we can always
add entertaining names/aliases at the hostname level. 'friends' was my
next favorite.
If everyone agrees (and vernon doesn't object) I think we should go
with Larry's scheme.
(*) and we haven't gave up yet.
--
Peace, Ariel
next prev parent reply other threads:[~1997-05-30 23:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-05-30 22:44 Name the external domain Larry McVoy
1997-05-30 23:12 ` Ariel Faigon [this message]
1997-05-30 23:12 ` Ariel Faigon
1997-06-02 6:44 ` Martin Knoblauch
-- strict thread matches above, loose matches on Subject: below --
1997-05-30 22:32 Ariel Faigon
1997-05-30 22:32 ` 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
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=199705302312.QAA22076@yon.engr.sgi.com \
--to=ariel@yon.engr.sgi.com \
--cc=ariel@sgi.com \
--cc=davem@jenolan.rutgers.edu \
--cc=linux@neteng.engr.sgi.com \
--cc=lm@neteng.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