 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
nemesis wrote:
> Invisible escreveu:
>> So I'm sitting at my desk reading VG Cats. And then I hear raised voices
>> from somewhere in the offices. (The walls here are like paper.) And then
>> I hear two female voices properly *shouting* at each other. And then I
>> hear what sounds like an actual fist fight break out! O_O
I remember when still in the fire brigade two firemen having a full-on
fist-fight in the dispatch center. They practically dived right over top of
me to get at each other. I immediately hit a fire bell and fortunately the
shift officer showed up in a few seconds.
Best thing to do is stay out of it, and prepare to duck under your desk if
it gets physical. Try not to witness it, otherwise you might have to make a
statement (which I had to do, and didn't like, since the disciplinary
hearing after the above incident hinged on my testimony - and I had good
relations with both guys fighting!)
--
Stefan Viljoen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Darren New" <dne### [at] san rrcom> wrote in message
news:4af1fd72$1@news.povray.org...
> One day, after this, on the "reference" machine, after much programming, I
> typed "DEL *.SRC" instead of "DEL *.SCR". Since it took about 1.5 seconds
> instead of the usual quarter second, I looked again at the command line
> again and very quietly said "Oh, shit." About five people stuck their
> heads up over the partitions asking what's wrong, since nobody ever
> cursed.
Long ago, one of my semi-regular duties was to install a fresh copy of a
demo program onto a machine, this being the easiest way to make sure that
the demo was always the same for the sales guys. It was installed off of a
5-1/4 inch floppy, and all I needed to to do was type "tar -xv -f/dev/fd1"
to extract the files, after changing to the right directory.
Ever notice that the "c" key is right next to the "x"? And, of course, the
floppy wasn't write-protected. So, I typed "tar -cv" and erased the floppy
(well, trashed the tar header, which amounted to the same thing for me at
the time). Our only copy of the demo, of course. And, this was less than an
hour before the prospect was to arrive.
We cracked open a live copy and activated it (much simpler process, in those
days, fortunately), then ordered a new demo disk.
Funny thing was, I don't think the salesman even noticed the difference.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Stefan Viljoen wrote:
> Hehe that's like the typical UNIX typo-while-root rm * .scr instead of rm
> *.scr...! :)
You don't even have to be root for that to screw you. You just have to own
all your source code files. :-)
--
Darren New, San Diego CA, USA (PST)
I ordered stamps from Zazzle that read "Place Stamp Here".
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Captain Jack wrote:
> Ever notice that the "c" key is right next to the "x"?
Somewhere in the intervening years, some programmer got hit by this badly
enough that tar will now say "cowardly refusing to create an empty archive"
in that situation. :-) Now that I figured out what it means, it's easy to
find the typo that caused it.
--
Darren New, San Diego CA, USA (PST)
I ordered stamps from Zazzle that read "Place Stamp Here".
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Darren New schrieb:
> "cowardly refusing to create an empty archive"
Heh, I like that! :-)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> "cowardly refusing to create an empty archive"
>
> Heh, I like that! :-)
I prefer "the printer is on fire" and "penguin on the SCSI bus"...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible wrote:
>>> "cowardly refusing to create an empty archive"
>>
>> Heh, I like that! :-)
>
> I prefer "the printer is on fire" and "penguin on the SCSI bus"...
http://en.wikipedia.org/wiki/Printer_on_fire
http://en.wikipedia.org/wiki/Operation_completed_successfully
etc.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible wrote:
> http://en.wikipedia.org/wiki/Printer_on_fire
Been there, done that. Came in at 11PM to turn things off. Came in 11AM
the next morning while the operators are cleaning up. "Darren, did you see
this?" "Indeed. I was the one that turned it off." "And you didn't come
in early to help clean it up?" "Quite intentionally, I assure you."
I had no desire to clean up 700 pages worth of the middle of the "0"
character spewed around the room in paper and ribbon.
--
Darren New, San Diego CA, USA (PST)
I ordered stamps from Zazzle that read "Place Stamp Here".
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Darren New wrote:
> Stefan Viljoen wrote:
>> Hehe that's like the typical UNIX typo-while-root rm * .scr instead of rm
>> *.scr...! :)
>
> You don't even have to be root for that to screw you. You just have to own
> all your source code files. :-)
>
That's true... I always -check- and then -recheck- - ever experienced the
fun rm dirname * -rf can cause vs. rm dirname* -rf if you want to delete
similarly named dirs? NOT good.
--
Stefan Viljoen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Stefan Viljoen wrote:
> That's true... I always -check- and then -recheck- - ever experienced the
> fun rm dirname * -rf can cause vs. rm dirname* -rf if you want to delete
> similarly named dirs? NOT good.
A friend once deleted the kernel image on his Mac by typing "rm foo *"
instead of "rm foo*". As root. In the root directory. And thank god he
didn't use -r.
People trying to help him on IRC (taking the kernel from their machines, for
example) all asked "what the heck were you doing with a root command line on
a *Mac* anyway?"
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
