From owner-freebsd-chat@FreeBSD.ORG Mon Apr 5 18:02:12 2010 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 58107106566B for ; Mon, 5 Apr 2010 18:02:12 +0000 (UTC) (envelope-from sektie@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 27DE18FC08 for ; Mon, 5 Apr 2010 18:02:11 +0000 (UTC) Received: by pvc7 with SMTP id 7so2018744pvc.13 for ; Mon, 05 Apr 2010 11:02:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:received:message-id:subject :from:to:cc:content-type; bh=dtAfx8AoI6/fkhRV0QT1fS6ocW/dQ4Pvolefqxt22BQ=; b=Ia8J3jzAOObDH0rwW6NqAge4LiSAdnfGowqfR+HIyMhCas1nFCV0E3ky6VW6RhRDi4 YIQ+Aip2rsnVgCimb524rfgfhZCJe3ncUyF+fkv4QZ3YH+ebPA+UACr23eMv3SdsE4PG HAAdomgx0xP3tEe/nqBykhQMp/KG3iGS3un9U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=QC2tCIlaHqdHH1rYL9loa4+KZzNRE+vmyjNHgEFPUR+GmoZP10PcrKOpfvqYXDTTOA Fl/qp+s9mfB3JRZ3D5xdQPRBirCbc4gM8H4xyZzcTFBBXic3X8ZW9PCDVmpyIZHaUxk6 64iIPb2wn33sDQ0Iu9G/DHQF68WbPr8B/IYvU= MIME-Version: 1.0 Sender: sektie@gmail.com Received: by 10.140.172.16 with HTTP; Mon, 5 Apr 2010 11:02:00 -0700 (PDT) In-Reply-To: <4BBA3264.5050702@gmail.com> References: <4BBA3264.5050702@gmail.com> Date: Mon, 5 Apr 2010 11:02:00 -0700 X-Google-Sender-Auth: f1486be9cbb6bcf7 Received: by 10.141.15.5 with SMTP id s5mr4171783rvi.177.1270490520274; Mon, 05 Apr 2010 11:02:00 -0700 (PDT) Message-ID: From: Randi Harper To: deeptech71@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-chat@freebsd.org Subject: Re: FreeBSD anti-competitive activities X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Apr 2010 18:02:12 -0000 On Mon, Apr 5, 2010 at 11:56 AM, wrote: > deeptech71@gmail.com wrote: >> Just as soon as FreeBSD 8.0 came out, I downloaded a boot-only disc >> image and went off to reinstall FreeBSD (don't ask why). OK, it worked >> whatsoever. But as it turns out, I wasn't able to boot my Windows XP >> installation anymore. The system just froze when I tried booting my >> Windows XP slice. First I thought that the installation damaged the >> other partitions (someone added buggy code in sysinstall lately?). At >> that point I didn't dare to boot anything on the disk. I decided to >> give a try to Hiren's Boot CD, which has loads of warezed >> slicing/partitioning, recovery and backup tools, and also a loadable >> Mini Windows XP. I hoped I would be able to find out what happened. >> >> But guess what? Neither of the Boot CD tools were able to start up, >> not even the Mini Windows XP! They all froze just like my Windows XP. >> But that's just weird. On a whim, I disabled my disk drive in the BIOS >> settings. And guess what? Both the Mini Windows XP and the tools were >> able to start because of that. I was able to read the >> slices/partitions with them, and noticed that all my files on the >> FAT32 and NTFS slices were intact. > [...] >> sysinstall asked something new when I installed 8.0, something like >> "It is safe to use a disk geometry of 123/45/6789 on modern >> computers... Would you like to use this disk geometry?", I chose >> "Yes". Safe my ass. I guess my computer doesn't fit in sysinstall's >> definition of "modern". > > Reinstalling FreeBSD and chosing "No" seems to have revived the Windows > partition. I'm not sure why I didn't see the original email in this thread - maybe I saw the subject and figured it was a troll. Seriously? FreeBSD anti-competitive activities? I suggest you wear your tinfoil hat, because they are all out to get you. It's a problem with sysinstall & libdisk. File a bug. That's generally how problems are handled, not by claiming there's some sort of anti-windows conspiracy. -- randi