From owner-freebsd-stable@freebsd.org Wed Oct 19 23:30:10 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB8F9C191A8 for ; Wed, 19 Oct 2016 23:30:10 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A28D6B12 for ; Wed, 19 Oct 2016 23:30:10 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-vk0-x22e.google.com with SMTP id 2so49017954vkb.3 for ; Wed, 19 Oct 2016 16:30:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=qDXWsjjDALDFfU28sq3a1HjzD0r+Bi/IwEsw0v6qaUo=; b=KwB7vUYaIyozYubpDgJBV0SF3g2RjjhEB1wkRsD5hR24DzW/tDJ4DgRQr5aX+j1RT5 eZa/Fki5djYhnx4XQo3ArcOfi6ExhaYe5uCDRAb6x4gb0ay2Yrpm/oGQ7nkXWTx1fiu8 Gby9gY2N7XVYbiNIyt27pI9FV0edC7IwQXgbVOuClUIak5P20820VLyk7BtoZZ1AqV66 /E4LV64Zh2RXNxK6k7GFqo9KEfbD4ikOVM3h3SSwFXRBhZxjwae8FP/uWRRUqRXvttt1 W9nr1M7GvguBqKn77apMwb5SS+nw/FVlOWsaO7YUIySsYKsRo+2wxGiDg1FctZwKU7Lv quxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=qDXWsjjDALDFfU28sq3a1HjzD0r+Bi/IwEsw0v6qaUo=; b=M3xiOD0N0KJkqbIljxPjnN7SVoJK6GW5PsSyl7+c8vuA47HS6EjkkQSIN5EOrOA0nR Dd7EIeP3CeEFjPS0n+SS48WpRkMS/2wYulupAFsn4Nalfq+CBv+dUS2D1R4IInjr3rwN G3fsFRozu7/BrEKD4KBij75QqXWovHy/gf49VtREeD48abKeL8BfILeSYZUmb5/MjUri PB17u2ulRKtIybTCYCl56dwZpvycErzMYv8wq+4xui8HTom6uVLr3/EnAGyMItlTCGiR /sHuG1B6cGVshy/hxAkGI+SPnRPkrlKVo9cSLDUDszJl8tMcB4vSqph7aw6Z/bb6l4t8 CVqw== X-Gm-Message-State: AA6/9RnCzIjHYpcgUcEixz7R1XBdqKs4JCUIJw5EX3jZrmFUi/QVyjF7Vdzve8jfgiBOtJqCkQcngj7jVNuv6A== X-Received: by 10.31.229.133 with SMTP id c127mr8005289vkh.153.1476919809600; Wed, 19 Oct 2016 16:30:09 -0700 (PDT) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.103.146.21 with HTTP; Wed, 19 Oct 2016 16:30:09 -0700 (PDT) In-Reply-To: References: From: Kevin Oberman Date: Wed, 19 Oct 2016 16:30:09 -0700 X-Google-Sender-Auth: oMfpl1Xb9Q7BvTKQCgwnL5fVJ4g Message-ID: Subject: Re: I'm upset about FreeBSD To: Warner Losh Cc: Rostislav Krasny , freebsd-stable Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2016 23:30:11 -0000 On Wed, Oct 19, 2016 at 3:39 PM, Warner Losh wrote: > On Wed, Oct 19, 2016 at 12:21 PM, Rostislav Krasny > wrote: > > On Tue, Oct 18, 2016 at 21:57:29 +1100, Ian Smith > wrote: > >> > >> If FreeBSD GPT images (and Kindle readers) can trigger this, so could a > >> theoretically unlimited combination of data on block 2 of USB media; > >> modifying FreeBSD to fix a Windows bug should be out of the question. > > > > Not modifying FreeBSD and not fixing Windows bug but modifying the > > FreeBSD installation media and working around the Windows bug to let > > people install FreeBSD without disappointing at very beginning. Why > > GPT is used in the memstick images at all? Why they can't be MBR > > based? I think they can. > > Can't boot UEFI off of MBR disks on all BIOSes. > > Warner > I'll go one farther. You can't boot many new PCs with traditional MBR disks. And. please don't confuse GPT with UEFI. I have yet to find an amd64 computer that has a problem with a GPT format with MBR. Due to broken BIOS, my 5-year old ThinkPad won't boot UEFI, but it has no problem with MBR, whether GPT formatted or not. As far as I know, the 11.0 memstick images are still MBR, just on a GPT structured disk, not UEFI. (Let me know if I am mistaken on this.) I do accept that some early amd64 systems and, perhaps, many i386 systems may have problems with GPT, but GPT was designed to be compatible with traditional disk formats and, while they may have problems, they really should work for single partition disks. And I understand that it is frustrating if you hit one of these cases where it fails. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683