All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otto Wyss <otto.wyss@bluewin.ch>
To: David Balazic <david.balazic@uni-mb.si>, linux-kernel@vger.kernel.org
Subject: Re: Linux should better cope with power failure
Date: Fri, 23 Mar 2001 20:29:03 +0100	[thread overview]
Message-ID: <3ABBA400.2AEC97E8@bluewin.ch> (raw)
In-Reply-To: <3ABB6B82.62293CAD@uni-mb.si>

> I had a similar experience:
> X crashed , hosing the console , so I could not initiate
> a proper shutdown.
> 
> Here I must note that the response you got on linux-kernel is
> shameful.
> 
Thanks, but I expected it a little bit. All around Linux is centered
around getting the highest performance out of it and very low (to low
IMHO) is done to have a save system. The attitude "It doesn't matter
making mistakes, they get fix anyhow" annoys me most, especially if it
were easy to prevent them. 

> What I did was to write a kernel/apmd patch , that performed a
> proper shutdown when I press the power button ( which luckily
> works as long as the kernel works ).
> 
Not with a AT power supply but certainly nice to have. See that it gets
included into the kernel. I didn't lost anything important since it was
just a testing machine. I was just shocked what fsck complained on a
machine which hadn't done almost anything at all. If I'd run into this
on a productive system I'd get immediately a serial keyboard or have at
least a usable network connection. Besides USB-only is not ready yet.

> > Don't we tell children never go close to any abyss or doesn't have
> > alpinist a saying "never go to the limits"? So why is this simple rule
> > always broken with computers?
> >
Is there a similar expression which could be hammered into any
developers mind, i.e. "Don't make errors, others already do them for you".

O. Wyss

  parent reply	other threads:[~2001-03-23 19:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-23 15:28 Linux should better cope with power failure David Balazic
2001-03-23 18:22 ` Gerhard Mack
2001-03-26  9:34   ` David Balazic
2001-03-23 19:29 ` Otto Wyss [this message]
2001-03-23 22:41   ` David Ford
2001-03-24  8:44     ` Otto Wyss
2001-03-24  9:47       ` David Ford
2001-03-24 10:28         ` Otto Wyss
2001-03-26 10:22     ` David Balazic
2001-03-26 10:17   ` David Balazic
  -- strict thread matches above, loose matches on Subject: below --
2001-03-19 22:35 Otto Wyss
2001-03-19 23:12 ` John R Lenton
2001-03-19 22:11 Stephen Gutknecht (linux-kernel)
2001-03-19 22:39 ` Otto Wyss
2001-03-20 21:38   ` H. Peter Anvin
2001-03-19 21:16 Torrey Hoffman
2001-03-19 22:28 ` Stephen Satchell
2001-03-19 23:05   ` Andre Hedrick
2001-03-19 19:46 Otto Wyss
2001-03-19 19:59 ` Charles Cazabon
2001-03-19 20:15 ` Richard B. Johnson
2001-03-19 20:51   ` Brian Gerst
2001-03-19 21:08     ` Jeremy Jackson
2001-03-19 21:35     ` Richard B. Johnson
2001-03-19 21:59       ` Brian Gerst
2001-03-19 22:15       ` Jeremy Jackson
2001-03-19 15:14         ` Ben Ford
2001-03-19 23:07   ` Werner Almesberger
2001-03-19 20:19 ` William T Wilson

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=3ABBA400.2AEC97E8@bluewin.ch \
    --to=otto.wyss@bluewin.ch \
    --cc=david.balazic@uni-mb.si \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.