From: n0ano@n0ano.com
To: linux-ia64@vger.kernel.org
Subject: Re: Problems with the linuxia64.org domain
Date: Thu, 15 Apr 2004 21:18:47 +0000 [thread overview]
Message-ID: <20040415211847.GD19437@tlaloc.n0ano.com> (raw)
In-Reply-To: <20040415165428.GA19437@tlaloc.n0ano.com>
Haven't even thought of pursuing that yet. I have no idea what they
might want and I also have no idea where the money would come from to
pay them off (in a perfect world VA would resolve this since it was
their mistake that caused it in the first place but I'm not holding
my breath for that to happen).
On Thu, Apr 15, 2004 at 12:26:50PM -0500, Matt Domsch wrote:
> On Thu, Apr 15, 2004 at 10:54:28AM -0600, n0ano@n0ano.com wrote:
> > Imagine my surprise when I checked today and discovered that, although
> > a DNS entry for `linuxia64.org' is back, it doesn't point to VA.
> > It looks like VA let the registration lapse and some company called
> > Speed Edge Technologies has hijacked our domain.
>
> Have you asked how much they might want to get it back?
>
> --
> Matt Domsch
> Sr. Software Engineer, Lead Engineer
> Dell Linux Solutions linux.dell.com & www.dell.com/linux
> Linux on Dell mailing lists @ http://lists.us.dell.com
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@n0ano.com
Ph: 303/447-2201
next prev parent reply other threads:[~2004-04-15 21:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 16:54 Problems with the linuxia64.org domain n0ano
2004-04-15 17:12 ` Matthew Wilcox
2004-04-15 17:19 ` n0ano
2004-04-15 17:26 ` Matt Domsch
2004-04-15 17:35 ` David Mosberger
2004-04-15 21:18 ` n0ano [this message]
2004-04-15 22:22 ` Matt Domsch
2004-04-15 23:55 ` Tim Potter
2004-04-16 2:26 ` Matt Domsch
2004-04-19 19:10 ` Matthew Wilcox
2004-04-19 19:20 ` Matt Domsch
2004-04-21 18:44 ` David Mosberger
2004-04-27 22:38 ` Andreas Schwab
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=20040415211847.GD19437@tlaloc.n0ano.com \
--to=n0ano@n0ano.com \
--cc=linux-ia64@vger.kernel.org \
/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