public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: Nick Bartos <spam99-1EIjRwF9Gc5s5w19saIqfg@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: acpi=force safe?
Date: Sat, 7 Feb 2004 04:31:30 +0100	[thread overview]
Message-ID: <20040207033130.GP13262@poupinou.org> (raw)
In-Reply-To: <40747.65.164.3.3.1076104152.squirrel-gjzqEhKAtSBis2HOlLKa7kEOCMrvLtNR@public.gmane.org>

On Fri, Feb 06, 2004 at 03:49:12PM -0600, Nick Bartos wrote:
> >
> > Why not let user decide at boot time?  That easy to do so with syslinux
> > for example.
> 
> I do use syslinux, but these boxes are supposed to be shrink rapped
> solutions for customers where the user really just uses the web interface
> (and some of the boxes are headless), so having the user modify boot parms
> really isn't possible.  Also, the entire distro is based on a single
> config and upgrading overrites the bootloader config, so setting user
> defined defaults really wouldn't work.
> 
> As long as there aren't any changes in the linux acpi implementation that
> make a board stop working on an upgrade (obviously it will be tested on
> the inital install), then it should be fine.  How probable is it for that
> to happen?  If the hardware is unchanged I would hope that updating the
> kernel (with acpi=force) wouldn't prevent the system from booting.
> 

Well, you just have to implement a quality policy then, but I guess
you already have one.

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

  parent reply	other threads:[~2004-02-07  3:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-06 16:17 acpi=force safe? Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB685-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org >
2004-02-06 17:16   ` Nick Bartos
     [not found]     ` <16644.65.164.3.3.1076087775.squirrel-gjzqEhKAtSBis2HOlLKa7kEOCMrvLtNR@public.gmane.org>
2004-02-06 21:13       ` Bruno Ducrot
     [not found]         ` <20040206211334.GH13262-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-02-06 21:49           ` Nick Bartos
     [not found]             ` <40747.65.164.3.3.1076104152.squirrel-gjzqEhKAtSBis2HOlLKa7kEOCMrvLtNR@public.gmane.org>
2004-02-07  3:31               ` Bruno Ducrot [this message]
2004-02-06 22:46           ` Nick Bartos
     [not found]             ` <24294.65.164.3.3.1076107609.squirrel-gjzqEhKAtSBis2HOlLKa7kEOCMrvLtNR@public.gmane.org>
2004-02-06 23:06               ` Bruno Ducrot
  -- strict thread matches above, loose matches on Subject: below --
2004-02-06  5:14 Nick Bartos
     [not found] ` <40678.65.28.18.238.1076044455.squirrel-gjzqEhKAtSBis2HOlLKa7kEOCMrvLtNR@public.gmane.org>
2004-02-06  5:40   ` Andi Kleen
     [not found]     ` <20040206064023.2a80a4dd.ak-l3A5Bk7waGM@public.gmane.org>
2004-02-06 12:54       ` Nick Bartos

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=20040207033130.GP13262@poupinou.org \
    --to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=spam99-1EIjRwF9Gc5s5w19saIqfg@public.gmane.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