Slashdot Mirror

← Back to Stories (view on slashdot.org)

Slashdot is Moving

Posted by CmdrTaco on from the there's-free-farmland-out-west dept.

As I mentioned yesterday, Slashdot is moving from Exodus East to West. This will be happening at around 11pm Eastern. We hope the downtime will be relatively minimal, but DNS may be a little slower to catch up. You can use brak.slashdot.org for a few days if your DNS is slow to catch up to reality. Hopefully we'll see you on the other side. Hopefully. In the meantime talk amongst yourselves. Here's a topic: Is Agent-X Deadpool?

7 of 122 comments (clear)

  1. great! by GoatPigSheep · · Score: 5, Funny

    since I live in the east, I am looking forward to slashdot getting much much slower.

    Thanks alot

    --
    GoatPigSheep, the 3 most important food groups
  2. Re:Perhaps I'm missing something but... by lukew · · Score: 4, Funny

    Being an Aussie with fuck all knowledge of american geography, I'll take a guess here. I'm assuming that they are moving from a datacentre hosted at Exodus on the East coast of america to a datacentre hosted on the West coast. Anyone correct me if I'm wrong.

  3. First Post... by flogger · · Score: 5, Funny

    No.. I mean Last Post!

    hehe.

    --
    ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
    "First things first -- but not necessarily in that order"
    -- The Doctor, "Doctor
  4. Re:Perhaps I'm missing something but... by Fnkmaster · · Score: 4, Informative
    Well, Exodus is a bankrupt colocation company. At least last I checked they were bankrupt. They apparently were acquired (at least their assets and such were acquired) by Cable and Wireless back in February.
    I had a friend whose company was bought by Exodus. Luckily he managed to sell some of his Exodus stock before they fell into the shitter.


    Apparently some of their colo facilities must still be operated by Cable and Wireless - hope they aren't as empty as they were a year ago. I had some friends who went into an Exodus colo and said it looked like a ghost town at the time.

  5. Re:Gulag Taco by Fnkmaster · · Score: 4, Insightful
    Agreed, I think some "meta conversation" could greatly improve Slashdot. I realize that /. will always be Rob Malda's playground and the editors can do whatever they please, but treating a community like their personal fiefdom has driven a lot of people away (to k5 and other places).


    I am not saying that they should throw away their own principles or ideas or turn this into a democracy experiment, but really, open it up to discussion, see what ideas are well received in the threads and consider adopting at least some of them if they make sense.

  6. Tech Update? by TheRedHorse · · Score: 5, Interesting

    After the move to Exodus West can the slashdot readership get an update on what hardware slashdot is running on? The description in the FAQ is dated and I expect the tech to change slightly if not largely with the move to Exodus West.

    I'm sure that I am not the only /. reader interested in a hardware update.

  7. Re:DNS may take a while to update, eh? by Electrum · · Score: 5, Informative

    Set the expire times to 12 hours a few days in advance, 4 hours on the last day, then half an hour in the last 5 or so hours, and three to five minutes for the last forty minutes?

    Why bother? With tinydns, you can specify a timestamp for each record and automatically handle updates:

    You may include a timestamp on each line. If ttl is nonzero (or omitted), the timestamp is a starting time for the information in the line; the line will be ignored before that time. If ttl is zero, the timestamp is an ending time (``time to die'') for the information in the line; tinydns dynamically adjusts ttl so that the line's DNS records are not cached for more than a few seconds past the ending time. A timestamp is an external TAI64 timestamp, printed as 16 lowercase hexadecimal characters. For example, the lines

    +www.heaven.af.mil:1.2.3.4:0:4000000038af1379
    +www.heaven.af.mil:1.2.3.7::4000000038af1379

    specify that www.heaven.af.mil will have address 1.2.3.4 until time 4000000038af1379 (2000-02-19 22:04:31 UTC) and will then switch to IP address 1.2.3.7.