From: Matt Domsch <Matt_Domsch@dell.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Problems with the linuxia64.org domain
Date: Fri, 16 Apr 2004 02:26:19 +0000 [thread overview]
Message-ID: <20040416022619.GA10857@lists.us.dell.com> (raw)
In-Reply-To: <20040415165428.GA19437@tlaloc.n0ano.com>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
On Fri, Apr 16, 2004 at 09:55:44AM +1000, Tim Potter wrote:
> On Thu, Apr 15, 2004 at 05:22:05PM -0500, Matt Domsch wrote:
>
> > registration, business planning, ...). linuxia64.org is redirecting to
> > java-training.com which is owned by the same company, and which
> > expired in February...
>
> Why don't you reregister java-training.com and swap it for linuxia64.org?
My thought exactly, but though it's showing as expired, the registrars
all claim it's taken still. The registrar is messed up, as they think
it was last updated 7 months from now too...
| Registrar: DomainTheNet.com
|
| Domain Name: java-training.com
| Created on ............. 26-nov-2003
| Expires on ............. Feb 17 2004 3:17AM
| Record last updated on . 26-nov-2004
| Status .................LOCK
I'm sure it's not really expired.
--
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
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-04-16 2:26 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
2004-04-15 22:22 ` Matt Domsch
2004-04-15 23:55 ` Tim Potter
2004-04-16 2:26 ` Matt Domsch [this message]
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=20040416022619.GA10857@lists.us.dell.com \
--to=matt_domsch@dell.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