• Marnee (unregistered)

    Why didn't he have a backup of his test database? I do.

  • 126532 (unregistered) in reply to Marnee

    Wow, grammatical error in the first sentence. 'employer' is singular.

  • 126532 (unregistered) in reply to Marnee

    Wow, grammatical error in the first sentence. 'employer' is singular.

  • Evan (unregistered)

    Is "dupe post" singular or plural? :-)

  • Norman Diamond (unregistered) in reply to 126532
    126532:
    Wow, grammatical error in the first sentence. 'employer' is singular.
    This story did not take place in the US. The first sentence was grammatically correct English, not Yanklish.
  • bene (unregistered) in reply to Norman Diamond
    Norman Diamond:
    This story did not take place in the US. The first sentence was grammatically correct English, not Yanklish.
    I don't see how it matters where the story took place - if it did, then based on the names it should presumably be written in French.

    (That's not to suggest that I'd prefer it to be written in American, mind you.)

  • Tomalak Geret'kal (unregistered) in reply to the beholder
    the beholder:
    If your subcontractor screwed up, the customer has all the right to say you're at fault because he didn't choose the subcontractor. You (as in, your company) did, under the assumption that they would do a decent job. The fact that they didn't means it was (most likely) a poor job choosing which subcontractor to pick, ergo: YOUR fault.

    Well, no; it's your responsibility, but it's not your fualt.

  • Tomalak Geret'kal (unregistered) in reply to Norman Diamond
    Norman Diamond:
    126532:
    Wow, grammatical error in the first sentence. 'employer' is singular.
    This story did not take place in the US. The first sentence was grammatically correct English, not Yanklish.

    No, not really.

  • Pista (unregistered)

    WTF is this background on the site?

  • (cs) in reply to Pista
    Pista:
    WTF is this background on the site?

    QFT. I'm making a user script to disable it so I can read the motherfucking story.

  • Unix IS Best (unregistered) in reply to anon
    anon:
    Jim:
    Wow, what database engine would allow you to move a database file that's in use?

    We all know that would never happen on a windows-box. If a process even thinks about maybe having access to a file, then that file's going to be there until you reboot. I finally understand why.

    You don't understand, then. Windows file handling is f*cked up! Being able to replace a file when you need to is a big reason why Unix DOESN'T need rebooted because you changed some arbitrary bit of some file. Heck, you can update the WHOLE DAMN KERNEL on Unix and not need an immediate reboot in most cases.

    No, Windows got it wrong. And so did the dude who REMOVED a file the system needed. If he has to have a file lock "remind" him to not remove an essential file, then he doesn't need that job!

    Gosh, it sucks that people are doing jobs that if it weren't for some OS just not letting them f*ck things up, nothing would work.

    (MCSE != qualified)

  • SJ (unregistered) in reply to Unix IS Best
    Unix IS Best:
    anon:
    Jim:
    Wow, what database engine would allow you to move a database file that's in use?

    We all know that would never happen on a windows-box. If a process even thinks about maybe having access to a file, then that file's going to be there until you reboot. I finally understand why.

    You don't understand, then. Windows file handling is f*cked up! Being able to replace a file when you need to is a big reason why Unix DOESN'T need rebooted because you changed some arbitrary bit of some file. Heck, you can update the WHOLE DAMN KERNEL on Unix and not need an immediate reboot in most cases.

    No, Windows got it wrong. And so did the dude who REMOVED a file the system needed. If he has to have a file lock "remind" him to not remove an essential file, then he doesn't need that job!

    Gosh, it sucks that people are doing jobs that if it weren't for some OS just not letting them f*ck things up, nothing would work.

    (MCSE != qualified)

    Pretty sure the slight hint of sarcasm in that comment just went right over your head...

  • JimTheJam (unregistered) in reply to Unix IS Best
    Unix IS Best:
    anon:
    Jim:
    Wow, what database engine would allow you to move a database file that's in use?

    We all know that would never happen on a windows-box. If a process even thinks about maybe having access to a file, then that file's going to be there until you reboot. I finally understand why.

    You don't understand, then. Windows file handling is f*cked up! Being able to replace a file when you need to is a big reason why Unix DOESN'T need rebooted because you changed some arbitrary bit of some file. Heck, you can update the WHOLE DAMN KERNEL on Unix and not need an immediate reboot in most cases.

    No, Windows got it wrong. And so did the dude who REMOVED a file the system needed. If he has to have a file lock "remind" him to not remove an essential file, then he doesn't need that job!

    Gosh, it sucks that people are doing jobs that if it weren't for some OS just not letting them f*ck things up, nothing would work.

    (MCSE != qualified)

    Ah, Yes. I remember the time I deleted (rm'ed) the operating system at the insistence of a manager who thought that any file that big could not be important. Not knowing Unix at all, I reluctantly complied.

    To those who don't know, nothing bad happens until the next reboot.

  • (cs) in reply to oheso
    oheso:
    Pista:
    WTF is this background on the site?

    QFT. I'm making a user script to disable it so I can read the motherfucking story.

    Remember p0rn is banned on website.

  • Shea (unregistered)

    Any veteran knows it instinctively:

    No matter how bad something is right now, you can ALWAYS make it worse.

Leave a comment on “Non-Restorative Restoration”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article