From: Stan Hoeppner <stan@hardwarefreak.com>
To: Ben Myers <bpm@sgi.com>
Cc: Robert Widmer <robertwidmer@gmail.com>, xfs@oss.sgi.com
Subject: Re: Power loss and zero-length files
Date: Fri, 23 Aug 2013 21:35:31 -0500 [thread overview]
Message-ID: <52181BF3.5050002@hardwarefreak.com> (raw)
In-Reply-To: <20130823225035.GQ7153@sgi.com>
On 8/23/2013 5:50 PM, Ben Myers wrote:
> Hey Stan,
>
> On Fri, Aug 23, 2013 at 05:32:26PM -0500, Stan Hoeppner wrote:
>> On 8/23/2013 10:45 AM, Ben Myers wrote:
>>> On Fri, Aug 23, 2013 at 11:27:19AM -0400, Robert Widmer wrote:
>>>> On Fri, Aug 23, 2013 at 11:20 AM, Ben Myers <bpm@sgi.com> wrote:
>>
>>>> The person ran the script, unplugged the machine (instead of shutting
>>>> it down like they were told), and boxed it up.
>>>
>>> lol ;)
>>
>> Yeah, that's pretty ignorant. Reminds me of this thread in March:
>>
>> http://oss.sgi.com/archives/xfs/2013-03/msg00152.html
>>
>> But "we" (IT industry) shot ourselves in the foot when we began using
>> the word "appliance". No wonder then that some people literally treat
>> them as such.
>
> On the other foot, it's probably not such an unreasonable expectation for
> someone coming from a different background to expect that once it *looks* done
> it actually *is* done.
>
> It's as if you were to take me scuba diving, or drag racing... I have zero
> expertise and I'd probably be doing all the silly ignorant things too.
>
> Or... maybe the tech was just in a hurry and didn't think all the way through
> the consequences. I've been there. ;)
I think the problem in many of these cases is that the people using the
hardware are not technicians, at least in the traditional sense. So
when 'we' use the word appliance they treat the hardware like a TV or
DVD player. With either, pulling the plug while it's running has no
detrimental effect.
The SCUBA and drag racing analogies don't really fit here as you're
completely out of your element. And acquiring the skills to do either
requires many weeks of training, time in the water or behind the wheel.
"shutdown -h now <ENTER>" requires no training, but just reading one
line on an instruction sheet and typing it in. ;)
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-08-24 2:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 14:59 Power loss and zero-length files Robert Widmer
2013-08-23 15:20 ` Ben Myers
2013-08-23 15:27 ` Robert Widmer
2013-08-23 15:45 ` Ben Myers
2013-08-23 22:32 ` Stan Hoeppner
2013-08-23 22:50 ` Ben Myers
2013-08-24 2:35 ` Stan Hoeppner [this message]
2013-08-24 11:15 ` Christoph Hellwig
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=52181BF3.5050002@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=bpm@sgi.com \
--cc=robertwidmer@gmail.com \
--cc=xfs@oss.sgi.com \
/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