From owner-freebsd-chat@FreeBSD.ORG Wed Jan 13 23:39:14 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 B05B6106566C for ; Wed, 13 Jan 2010 23:39:14 +0000 (UTC) (envelope-from deeptech71@gmail.com) Received: from mail-ew0-f211.google.com (mail-ew0-f211.google.com [209.85.219.211]) by mx1.freebsd.org (Postfix) with ESMTP id 48A6C8FC24 for ; Wed, 13 Jan 2010 23:39:13 +0000 (UTC) Received: by ewy3 with SMTP id 3so239091ewy.13 for ; Wed, 13 Jan 2010 15:39:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=wnGTdO4NHE4Q6BZHhRjTwc9qImLrl9fw8qTkWYGAE3I=; b=u1kNugpRagw+qNF0ZqPCPzM5ytU9OfqzYNr91jFAJ6SL3C4I/3Kt+2OSmXkp7GNgJK jrE9jcBVG7ziKuc14u1laqkxM4N7skXvkgIIu+H5O+CmseWveFPLypAH9LRQTDeTmUqw yJcJIsO3O5B5ISZoN9tsgQ060LwZz2OV5AtGk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=igJ3hw7UB9T3Rm6mIp0deeq5Nc4cpFm8pAkpGakbNfVqqdkVlAan0BwbI51mEeXFIl LbM1tL69x/otR5x0l7JIY+D2AYBiHMifLVm/HyF4Xp/lSUUIJZV3FuXCEqKfRHsSkCHj Sna1gywoN6cO6qMt4s2SCW0P5+S6hrtXNCFsg= MIME-Version: 1.0 Received: by 10.216.90.135 with SMTP id e7mr624134wef.34.1263424176769; Wed, 13 Jan 2010 15:09:36 -0800 (PST) Date: Thu, 14 Jan 2010 00:09:36 +0100 Message-ID: <3f2022cd1001131509o3b31e884m512d9faf9ac0730b@mail.gmail.com> From: "deeptech71@gmail.com" To: freebsd-chat@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: 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: Wed, 13 Jan 2010 23:39:14 -0000 Well, well. Who would have thought that the FreeBSD Team would decide to implement a hack that would block booting of any Windows-like, and possibly other non-FreeBSD based operating environments? 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. So I continued to use only FreeBSD. It didn't hinder me (much), maybe FreeBSD as a desktop system was bit of a nuisance for some things I used to do only on Windows, but I got used to it later. So I can say that this facilitated (well, forced) a switch to using FreeBSD as a desktop system. Despite that I lost the ability to boot XP from my disk, I'm happy with the switch, and that is all that matters. :D ========================= OK, seriously. 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". But how can this destroy Windows apps? I mean FreeBSD works just fine, and can read everything from the FAT32 and NTFS partitions. So what does Windows stuff suck at? Should the disk geometry proposed in sysintall work according to some standard, but yet it doesn't, because Windows stuff is buggy? Or is it non-standard but, uniquely, FreeBSD works with it? Or is it something totally different?