From: Helge Deller <deller@gmx.de>
To: "Matt Taggart" <matt@lackof.org>,
"Thibaut Varène" <T-Bone@parisc-linux.org>
Cc: dann frazier <dannf@dannf.org>,
"Craig Lamparter (ISS Linux)" <craig.lamparter@hp.com>,
John David Anglin <dave.anglin@bell.net>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-parisc@vger.kernel.org
Subject: Re: parisc-linux.org losing hw hosting after this month
Date: Sat, 09 Nov 2013 21:25:50 +0100 [thread overview]
Message-ID: <527E9A4E.5000008@gmx.de> (raw)
In-Reply-To: <20131109191725.DDCE31A1@taggart.lackof.org>
On 11/09/2013 08:17 PM, Matt Taggart wrote:
> Thibaut Var=E8ne writes:
>> Until then, it's presumably impossible to move the domain to a new
>> owner. I've just tried with my registrar of choice (ovh.com) and it
>> says that I can only move the domain there *without* changing owners=
hip
>=20
> Weird. So does that mean to change ownership either you are going to =
have=20
> to move it within my registrar or I am going to have to move it withi=
n=20
> yours?
>=20
>> As a temporary workaround, I could give you the IP addresses of my D=
NS
>> servers (once I've readied them for handling p-l.o, which, to begin
>> with, means I have to copy the existing zone), which would for all
>> practical purposes give me control over the domain until it can be
>> properly moved next summer (which must not be forgotten, especially =
now
>> that you've unlocked the domain).
>=20
> I can change the nameservers (or anything else about the domain) when=
ever,=20
> just let me know. taggart@OFTC
Just as a side-note:
Could we let it run as-is as long as possible? At least until the A500 =
is really turned off?
Dave & me have the parisc-linux debian dpkg repository still on the A50=
0 which is still in=20
heavy use until the debian-ports repository is mostly filled...
Helge
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc"=
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-11-09 20:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 0:35 parisc-linux.org losing hw hosting after this month dann frazier
2013-11-05 0:56 ` James Bottomley
2013-11-05 1:07 ` John David Anglin
2013-11-05 2:22 ` dann frazier
2013-11-05 3:58 ` Craig Lamparter (ISS Linux)
2013-11-08 22:22 ` Helge Deller
2013-11-08 22:38 ` dann frazier
2013-11-09 8:20 ` Matt Taggart
2013-11-09 17:56 ` Thibaut Varène
2013-11-09 19:17 ` Matt Taggart
2013-11-09 20:25 ` Helge Deller [this message]
2013-11-09 20:33 ` John David Anglin
2013-11-09 20:40 ` Helge Deller
2013-11-09 20:55 ` John David Anglin
2013-11-09 21:26 ` Thibaut Varène
2013-11-09 21:31 ` Helge Deller
2013-11-10 17:26 ` John David Anglin
2013-11-11 19:43 ` Thibaut Varène
2013-11-11 19:57 ` Martin K. Petersen
2013-11-12 19:47 ` Helge Deller
2013-11-12 20:27 ` James Bottomley
2013-11-20 10:35 ` Thibaut Varène
2013-11-09 21:22 ` Thibaut Varène
2013-11-05 10:51 ` Aw: " Helge Deller
2013-11-05 18:28 ` John David Anglin
2013-11-05 21:35 ` Helge Deller
2013-11-05 22:23 ` John David Anglin
2013-11-05 2:14 ` dann frazier
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=527E9A4E.5000008@gmx.de \
--to=deller@gmx.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=T-Bone@parisc-linux.org \
--cc=craig.lamparter@hp.com \
--cc=dannf@dannf.org \
--cc=dave.anglin@bell.net \
--cc=linux-parisc@vger.kernel.org \
--cc=matt@lackof.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