From owner-freebsd-stable@freebsd.org Mon Oct 17 12:11:16 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 E495BC1303B for ; Mon, 17 Oct 2016 12:11:16 +0000 (UTC) (envelope-from rosti.bsd@gmail.com) Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (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 A91DB648 for ; Mon, 17 Oct 2016 12:11:16 +0000 (UTC) (envelope-from rosti.bsd@gmail.com) Received: by mail-qt0-x22d.google.com with SMTP id s49so115692774qta.0 for ; Mon, 17 Oct 2016 05:11:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ixx1TDq6f5I9InRrxaWP3wRjl0U9ckyew8Tr8rkXihU=; b=BoWzVsQ4bTpxFw42h5op+66KSpggU8Xlb9tnirBQazRvkO1Hgoaf/vBKuRvEz0sMxM gzg7wWZt74XPP9X0Hiz9uBH71VZE1DE7eYaQizv4Kuad7V+B94NG2amwFi+M4HKo71K7 1Y4vWxUwISdVYHiS5I0DFbTQtSRWocf/cssV5JF0rb0xA2QB5tOOcSYrrgkogXinY/Sb hN+Y6aGsNzkmeP7ws03iUuDjYb9fp5RK97wxUpWtN6XawWreNjEwFarHkEixZWqXitHx CX8wPng5AH1bC1Tzp045hLQKzo3am4dDj3VNJTIqTIKCGlixupdSoC3MGfRti9MV5WAd ngNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ixx1TDq6f5I9InRrxaWP3wRjl0U9ckyew8Tr8rkXihU=; b=gJIQOju/s9fClkTda9WHK1kIBCOZQh8T+7KjqlUpe3fcdsM4USNHb86wz6+SY2xXsF 26VhqAb5WrUdDrLB1gOhqmSV2Uv9TJM3LCVO+2sDm7gC1ioQU8qtvCkujLwMv4gSqwII P1PGDeK5wAqoiLaWS65qsNrINMgaSQGbgbAQefdmZDsZdCWtGQefoZ/KMWtpo0hGKVCk WuFBnKDtYxC4bCCtG7KaPyXVb5o8QcST213J3E7lbhLvzy+JB7qfnfsObEv25sIhkKCl WE3YcltbLta2cDYXRJp+f+lIFDbGLoQc07HeiRCnp4nZbitRNdpkXAeBHXohH4WFke2R sb/A== X-Gm-Message-State: AA6/9RkgvctkMx/OY+XB9eunaikno3gh18FzzVnAoM68HTA+o/im+g76ZfqUMNkpgXURpjCV67KxIoGhn4Ljbg== X-Received: by 10.28.24.80 with SMTP id 77mr8587957wmy.74.1476706275402; Mon, 17 Oct 2016 05:11:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.158.130 with HTTP; Mon, 17 Oct 2016 05:11:15 -0700 (PDT) In-Reply-To: References: From: Rostislav Krasny Date: Mon, 17 Oct 2016 15:11:15 +0300 Message-ID: Subject: Re: I'm upset about FreeBSD To: freebsd-stable@freebsd.org Cc: "Eugene M. Zheganin" Content-Type: text/plain; charset=UTF-8 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: Mon, 17 Oct 2016 12:11:17 -0000 On 17.10.2016 11:57:16 +0500, Eugene M. Zheganin wrote: > Hi. > > On 17.10.2016 5:44, Rostislav Krasny wrote: > > Hi, > > > > I've been using FreeBSD for many years. Not as my main operating > > > system, though. But anyway several bugs and patches were contributed > > and somebody even added my name into the additional contributors list. > > That's pleasing but today I tried to install the FreeBSD 11.0 and I'm > > > upset about this operating system. > > > > First of all I faced an old problem that I reported here a year ago: > > http://comments.gmane.org/gmane.os.freebsd.stable/96598 > > > Completely new USB flash drive flashed by the > > FreeBSD-11.0-RELEASE-i386-mini-memstick.img file kills every Windows > > again. If I use the Rufus util to write the img file (using DD mode) > > the Windows dies immediately after the flashing. If I use the > > Win32DiskImager (suggested by the Handbook) it doesn't reinitialize > > the USB storage and Windows dies only if I remove and put that USB > > flash drive again or boot Windows when it is connected. Nothing was > > done to fix this nasty bug for a year. > > I saw this particular bug, and I must say - man, it's not FreeBSD, it's Rufus. > So far Windows doesn't have any decent tool to write the image with. As > about Rufus - somehow it does produce broken images on a USB stick > (not always though), which make every Windows installation to BSOD > immediately after inserting. And this continues until you reinitialize the > stick boot area. The DD mode in Rufus and in any other flashing util that supports the DD mode (including the native dd(1) program) just writes the image file byte by byte without any change, isn't it? If you say the boot area re-initialization resolves the BSOD issue then why the boot area isn't fixed in the image file at the first place? I agree that Windows has a serious bug but why FreeBSD doesn't try to workaround it? After all people try to install FreeBSD and if the Windows bug and the FreeBSD developers stubbornness prevent them to do so they just can't and won't install FreeBSD. This is a lose-lose situation. > P.S. By the way, win32diskimager is a total mess too. Sometimes it just > does nothing instead of writing an image. I did try almost all of the free > win32 tools to write image with, and didn't find any that would completely > satisfy me. Rufus would be the best, if it didn't have this ridiculous bug with > BSOD. Did you try the native FreeBSD dd(1) program or a MinGW version of dd(1)? And what about other issues I've described in my first email? I managed to install FreeBSD 11.0 but it still unbootable. P.S. please Cc your replies to me since I don't receive this mailing list emails directly, although I'm subscribed.