public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005-hi6Y0CQ0nG0@public.gmane.org>
To: Erik Slagter <erik-KW7PGP3XNp7a5EbDDlwbIw@public.gmane.org>
Cc: Hans Kristian Rosbach
	<hk-lnVXpwuIOH4XWF+eFR7m5Q@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: ACER Aspire 5000 <- Will these bios bugs ever be	fixed?
Date: Wed, 31 Aug 2005 12:15:10 +0200	[thread overview]
Message-ID: <4315832E.6040005@gmx.net> (raw)
In-Reply-To: <1125478354.20251.5.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>

Erik Slagter schrieb:
> On Wed, 2005-08-31 at 10:01 +0200, Hans Kristian Rosbach wrote:
> 
> 
>>I did contact Acer and ask them to just apply some easy fixes
>>for the Ferrari 4005 battery detection. The reply I got was
>>very surprising. Basicly she told me they don't want my
>>business if I use anything other than windows.
> 
> 
> Dell is even worse. If you tell them you run Linux on your laptop they
> will try to convince you it may damage your hardware and you won't get
> any guarantee whatsoever etc. (this in reply to a simple purely hardware
> based question)

There are enough programs available for windows which can damage
hardware just fine. Besides that, it is impossible to determine
whether Linux ever was installed on such a machine if you make
a backup of the harddisk before the first boot and restore that
backup if problems appear.


Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

  parent reply	other threads:[~2005-08-31 10:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-29 18:08 ACER Aspire 5000 Matt R Hall
2005-08-30 14:36 ` Manuel J.Galan
     [not found]   ` <loom.20050830T163344-565-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2005-08-31  8:01     ` Re: ACER Aspire 5000 <- Will these bios bugs ever be fixed? Hans Kristian Rosbach
2005-08-31  8:52       ` Erik Slagter
     [not found]         ` <1125478354.20251.5.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-08-31 10:15           ` Carl-Daniel Hailfinger [this message]
     [not found]             ` <4315832E.6040005-hi6Y0CQ0nG0@public.gmane.org>
2005-08-31 10:22               ` Erik Slagter
2005-08-31 13:10           ` Alan Cox
     [not found]             ` <1125493848.3355.8.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-08-31 13:26               ` Carl-Daniel Hailfinger
     [not found]                 ` <4315B00F.1080805-hi6Y0CQ0nG0@public.gmane.org>
2005-08-31 17:51                   ` Janosch Machowinski
2005-08-31 13:09       ` Alan Cox
     [not found] ` <20050829180845.98096.qmail-ZDCUxwME616A/QwVtaZbd3CJp6faPEW9@public.gmane.org>
2005-08-29 22:30   ` ACER Aspire 5000 Andreas Domfors
2005-08-31 20:19   ` Matt R Hall

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=4315832E.6040005@gmx.net \
    --to=c-d.hailfinger.devel.2005-hi6y0cq0ng0@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=erik-KW7PGP3XNp7a5EbDDlwbIw@public.gmane.org \
    --cc=hk-lnVXpwuIOH4XWF+eFR7m5Q@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