The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: krewat@kilonet.net (Arthur Krewat)
Subject: [TUHS] Names of famous, historical UNIX machines?
Date: Fri, 3 Feb 2017 10:12:20 -0500	[thread overview]
Message-ID: <268ca806-3c70-5f2e-13dc-f8f54f7393a3@kilonet.net> (raw)
In-Reply-To: <67b5fc0baf200260db0f035f858929ed@xs4all.nl>

owl% nslookup kremvax.demos.su
Server:         199.89.231.20
Address:        199.89.231.20#53

Non-authoritative answer:
Name:   kremvax.demos.su
Address: 194.87.0.20

owl% whois -h whois.ripe.net 194.87.0.20
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to '194.87.0.0 - 194.87.3.255'

% Abuse contact for '194.87.0.0 - 194.87.3.255' is 'abuse at relcom.net'

inetnum:        194.87.0.0 - 194.87.3.255
netname:        DEMOS-CORP
descr:          DEMOS Corporate Network
descr:          Demos Plus Co. Ltd.
descr:          Moscow, Russia
country:        RU
admin-c:        DNOC-ORG
tech-c:         DNOC-ORG
status:         ASSIGNED PA
mnt-by:         AS2578-MNT
created:        2002-05-24T05:47:32Z
last-modified:  2006-10-19T12:41:45Z
source:         RIPE

http://kremvax.demos.su/


  kremvax.demos.su


  1992-1995-2016


  R.I.P.




On 2/3/2017 9:11 AM, Jacob Goense wrote:
> On 2017-02-03 09:04, Dave Horsfall wrote:
>> On Wed, 1 Feb 2017, Jacob Goense wrote:
>>
>>> - kremvax
>>> Fictional machine. Suitable for jokes, routers related to anything 
>>> in the
>>> east.
>>
>> The most famous spoofed address would be moscvax!kremvax!kgbvax!gorby 
>> ...
>>
>> I think KRE posted from there back one April 1st (alas, I never saved 
>> it).
>
> Piet saved it at http://godfatherof.nl/kremvax.html
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170203/455704e9/attachment.html>


  reply	other threads:[~2017-02-03 15:12 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01 20:43 Michael Kjörling
2017-02-01 20:46 ` Clem Cole
2017-02-01 20:50 ` Clem Cole
2017-02-01 21:11   ` Lars Brinkhoff
2017-02-01 21:20   ` Noel Chiappa
2017-02-01 21:42     ` Michael Kjörling
2017-02-01 21:43       ` Cory Smelosky
2017-02-01 22:16         ` Cory Smelosky
2017-02-01 21:50       ` William Pechter
2017-02-01 22:06     ` Clem Cole
2017-02-01 22:11       ` Larry McVoy
2017-02-01 22:21         ` Clem Cole
2017-02-01 22:28         ` Clem Cole
2017-02-01 22:44           ` William Pechter
2017-02-02  1:14             ` Rico Pajarola
2017-02-02  1:34               ` Clem Cole
2017-02-02  1:18             ` Clem Cole
2017-02-02  1:29               ` Clem Cole
2017-02-02 13:11           ` arnold
2017-02-04  3:46             ` Steve Johnson
2017-02-04  3:56               ` Larry McVoy
2017-02-04 22:48                 ` Nemo
2017-02-01 22:26     ` Arthur Krewat
2017-02-02  7:38       ` Lars Brinkhoff
2017-02-01 21:33 ` Larry McVoy
2017-02-01 21:57   ` Clem Cole
2017-02-01 22:08     ` Larry McVoy
2017-02-01 22:20       ` Steve Nickolas
2017-02-03  1:51   ` Dave Horsfall
2017-02-01 22:54 ` Jacob Goense
2017-02-03 12:59   ` Tim Bradshaw
2017-02-03 14:04   ` Dave Horsfall
2017-02-03 14:11     ` Jacob Goense
2017-02-03 15:12       ` Arthur Krewat [this message]
2017-02-06  5:41       ` Dave Horsfall
2017-02-03  5:50 ` Lars Brinkhoff
2017-02-01 22:16 Noel Chiappa
2017-02-01 22:27 Berny Goodheart
2017-02-02  9:59 Rudi Blom

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=268ca806-3c70-5f2e-13dc-f8f54f7393a3@kilonet.net \
    --to=krewat@kilonet.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).