• Home
  • About

Saved searches

  • Remove
  • Verified account @
Suggested users
  • Verified account @
  • Verified account @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
By using Twitter’s services you agree to our Cookie Use and Data Transfer outside the EU. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.
thatcks's profile
Chris Siebenmann
Chris Siebenmann
Chris Siebenmann
@thatcks

Chris Siebenmann

@thatcks

That cks. Overcommitted sysadmin, photographer, bicyclist, and other multitudes. I write a lot of words for a programmer.

Joined December 2011
  • © 2016 Twitter
  • About
  • Help
  • Terms
  • Privacy
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • Verified account @
Suggested users
  • Verified account @
  • Verified account @

Retweet this to your followers?

Optional comment for Retweet
 
 

Saved searches

  • Remove
  • Verified account @
Suggested users
  • Verified account @
  • Verified account @
140

Are you sure you want to delete this Tweet?

Promote this Tweet

Block

  • Add a location to your Tweets

    When you tweet with a location, Twitter stores that location. You can switch location on/off before each Tweet and always have the option to delete your location history. Learn more

    Profile summary

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Your reply includes the people in this conversation up to this point. Learn more

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    Preview

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Buy Now

    Hmm... Something went wrong. Please try again.

    Previous Tweet Next Tweet
    1. dadpool ‏@lusis Apr 22

      given a choice, your "enterprise" customer will run a two year old version of your stack

      2 retweets 10 likes
    2. Chris Siebenmann ‏@thatcks Apr 22

      @lusis We have a ton of machines where we want to freeze them and never touch anything, because they work now & why risk that changing?

      0 retweets 0 likes
    3. dadpool ‏@lusis Apr 22

      @thatcks because security? A frozen state doesn't magically never have security issues or bugs.

      0 retweets 0 likes
      Chris Siebenmann ‏@thatcks Apr 22

      @lusis For the machines we freeze in liquid nitrogen, we lock everything down and keep an eye on the remaining risks (usually low).

      8:48 PM - 22 Apr 2016
      0 retweets 0 likes
        1. dadpool ‏@lusis Apr 22

          @thatcks did you just troll me? ;)

          0 retweets 0 likes
        2. Chris Siebenmann ‏@thatcks Apr 22

          @lusis I'm serious about our strategy for some machines. Eg our iSCSI backends will probably never be updated & they're mostly inaccessible.

          0 retweets 1 like
        3. dadpool ‏@lusis Apr 22

          @thatcks I guess by this point you've probably hit any rollover bugs and such heh.

          0 retweets 0 likes
        4. Chris Siebenmann ‏@thatcks Apr 22

          @lusis Yep! Current uptimes for the production backends are 512 days to 561 days. (Someday we'll have a power outage.)

          0 retweets 0 likes
        5. ɯıɹɹıʍʇ ‏@Twirrim Apr 22

          @thatcks @lusis I assume you're hoping and praying that they'll actually boot cleanly?

          0 retweets 0 likes
        6. Chris Siebenmann ‏@thatcks Apr 22

          @Twirrim @lusis We haven't changed anything on them since they last rebooted, so we think the odds are pretty good they'll be okay.

          0 retweets 0 likes

      Loading seems to be taking a while.

      Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

        Promoted Tweet

        false

        • © 2016 Twitter
        • About
        • Help
        • Terms
        • Privacy
        • Cookies
        • Ads info