public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Helge Hafting <helgehaf@idb.hist.no>, linux-kernel@vger.kernel.org
Subject: Re: Journaling: Surviving or allowing unclean shutdown?
Date: Fri, 5 Jan 2001 23:05:46 +0100	[thread overview]
Message-ID: <20010105230546.A301@bug.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.30.0101031847120.11227-100000@springhead.px.uk.com> <3A544925.B9BF4241@idb.hist.no>
In-Reply-To: <3A544925.B9BF4241@idb.hist.no>; from Helge Hafting on Thu, Jan 04, 2001 at 10:57:57AM +0100

Hi!

> > > Being able to shut down by hitting the power switch is a little luxury
> > > for which I've been willing to invest more than a year of my life to
> > > attain.  Clueless newbies don't know why it should be any other way, and
> > > it's essential for embedded devices.
> > 
> > Clueless newbies (and slightly less clueless less newbie) type people
> > don't think that they should HAVE to. My two interests are coping with
> > particularly pedantic people who don't want there computer to hastle them
> > about what they should or shouldn't do, and slightly embedded systems
> > (e.g. set top box/web browsery thing that you want to be able to turn off
> > like a TV but it should still be able to have a writeable disc for config
> > and stuff you download/cache etc).
> 
> Nothing wrong with a filesystem (or apps) that can handle being powered
> down.
> But I prefer to handle this kind of users with a power switch that
> merely
> acts as a "shutdown button"  instead of actually killing power.
> The os will then run the equivalent of "shutdown -h now" 
> You may not have this luxury on an ordinary pc, but you do if you design
> embedded
> devices.  You will then be free to use existing GPL software that
> not necessarily handle a power failure well.

Heck, I hate hardware like that. Power button should kill the power,
immediately. It should not sync, it should not tell system, it should
just cut off the power. There _might_ be other button telling system
to shutdown.

Why is power button important? I already had 2 situations where
softpower could be pretty fatal, and one where it _was_ fatal.

1. on times of 486, badly inserted ISA card led to explosion of one of
low-integration chips. I've actually seen blue light. You can see
that soft-power-off is just not appropriate for such situation. [But I
probably could have survived soft-power off. Chip exploded and no more
damage seemed to happen.]

2. on the same 486, one wire got short-circuited. Smoke started
comming out of the box. By powering it down I even saved the wire (its
isolation started boiling).

3. few days ago, our hot-wave owen commited suicide. Device with soft
power controlled by CPU. During one night, CPU got crazy (power
glitch? EMI?) and heating turned on itself. Fan did not. Owen
destroyed itself.
								Pavel
-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-01-08 19:41 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-03 12:55 Journaling: Surviving or allowing unclean shutdown? Dr. David Gilbert
2001-01-03 15:26 ` Rik van Riel
2001-01-03 15:38   ` Michael Rothwell
2001-01-03 16:18   ` Andi Kleen
2001-01-03 16:27   ` Daniel Phillips
2001-01-03 16:42     ` Alex Belits
2001-01-04  8:00       ` Daniel Phillips
2001-01-04 17:39         ` Alex Belits
2001-01-03 18:52     ` Dr. David Gilbert
2001-01-04  9:57       ` Helge Hafting
2001-01-04 10:14         ` Daniel Phillips
2001-01-04 10:25           ` David Woodhouse
2001-01-04 17:43           ` David Lang
2001-01-04 17:52             ` David Woodhouse
2001-01-04 18:00               ` David Lang
2001-01-04 18:11                 ` Alan Cox
2001-01-05  4:12                   ` Chipzz
2001-01-05  4:18                     ` Alan Cox
2001-01-05 16:55                   ` Mike Touloumtzis
2001-01-05 16:57                   ` David Woodhouse
2001-01-05 22:09                 ` Pavel Machek
2001-01-04 17:59             ` Alan Cox
2001-01-04 18:10               ` Chris Wedgwood
2001-01-04 18:15                 ` Mo McKinlay
2001-01-04 18:19                   ` David Lang
2001-01-04 18:20                     ` Mo McKinlay
2001-01-04 19:42                       ` Richard B. Johnson
2001-01-04 20:31                         ` egger
2001-01-04 20:59                           ` Richard B. Johnson
2001-01-04 21:05                             ` egger
2001-01-04 22:45                             ` Erik Mouw
2001-01-04 18:23                   ` Chris Wedgwood
2001-01-05 12:04                   ` David Woodhouse
2001-01-04 18:21               ` Dr. David Gilbert
2001-01-04 18:11             ` Mo McKinlay
2001-01-04 21:00         ` Brett G. Person
2001-01-05 22:05         ` Pavel Machek [this message]
2001-01-04 19:21     ` Stephen C. Tweedie
2001-01-04 21:08       ` Stefan Traby
2001-01-04 22:49         ` Stephen C. Tweedie
2001-01-05  1:01           ` Stefan Traby
2001-01-05  8:10             ` Andreas Dilger
2001-01-05 11:05             ` Stephen C. Tweedie
2001-01-05 11:58         ` David Woodhouse
2001-01-06 19:57           ` Marc Lehmann
2001-01-06 20:09             ` Stefan Traby
2001-01-06 20:35               ` Chris Mason
2001-01-06 21:49                 ` Marc Lehmann
2001-01-08 12:02             ` Stephen C. Tweedie
2001-01-09  9:34               ` Roger Gammans
2001-01-05  0:31       ` Daniel Phillips
2001-01-05  8:00         ` Andreas Dilger
2001-01-05 12:46           ` Alan Cox
2001-01-05 12:59             ` Chris Wedgwood
2001-01-05 13:22             ` Stephen C. Tweedie
2001-01-05 10:31         ` Stephen C. Tweedie
     [not found] <fa.e3022cv.v2ucim@ifi.uio.no>
     [not found] ` <fa.naq8vev.74ai08@ifi.uio.no>
2001-01-04 22:38   ` Dan Maas
  -- strict thread matches above, loose matches on Subject: below --
2001-01-08 23:19 Bernd Eckenfels

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=20010105230546.A301@bug.ucw.cz \
    --to=pavel@suse.cz \
    --cc=helgehaf@idb.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    /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