From owner-freebsd-arch@freebsd.org Sun Dec 3 08:41:38 2017 Return-Path: Delivered-To: freebsd-arch@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 DF942DF43A4 for ; Sun, 3 Dec 2017 08:41:38 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id CA1CE70D01 for ; Sun, 3 Dec 2017 08:41:38 +0000 (UTC) (envelope-from hps@selasky.org) Received: by mailman.ysv.freebsd.org (Postfix) id C97A8DF43A3; Sun, 3 Dec 2017 08:41:38 +0000 (UTC) Delivered-To: arch@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 C91FBDF43A2 for ; Sun, 3 Dec 2017 08:41:38 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7825F70CFF for ; Sun, 3 Dec 2017 08:41:38 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id C01F42603A1; Sun, 3 Dec 2017 09:41:28 +0100 (CET) Subject: Re: Deprecating / Removing floppy drive support To: Cy Schubert , Warner Losh Cc: Eitan Adler , "freebsd-arch@freebsd.org" References: <201712030616.vB36GFEg026146@slippy.cwsent.com> From: Hans Petter Selasky Message-ID: <43746890-e60a-5c8f-4c77-bbfe9a5a6aa9@selasky.org> Date: Sun, 3 Dec 2017 09:38:41 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <201712030616.vB36GFEg026146@slippy.cwsent.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2017 08:41:39 -0000 On 12/03/17 07:16, Cy Schubert wrote: > In message om> > , Warner Losh writes: >> --001a1144e7002bf7b0055f684ec8 >> Content-Type: text/plain; charset="UTF-8" >> >> On Sat, Dec 2, 2017 at 8:31 PM, Cy Schubert >> wrote: >> >>> bms@ has given me USB floppy formatting code which I'd planned to merge >>> >> into fdformat but considering the underlying devices are so very different >>> it would be a difficult marriage. I'd be willing to support a ufdformat >>> instead. >> >> >> I'm keen on getting that into the tree. I have a ufd device and a need to >> use it from time to time. If nothing else, I can be a reviewer of the code. >> Is ufd working for you? > > It does work. My todo was to merge ufdformat into fdformat but as I said > they are different enough that I need to work out how best to merge them. > Having said that, now that there's discussion of removing fdc(4) maybe it's > best to simply use ufdformat separately from fdformat that when we have the > inclination to remove fdc(4), which may be very soon now -- it would be > much less messy. I'm open to either option. > >> >> >>>> >>>> Normally, I'd argue we might want to have a release where it's >>> deprecated, >>>> but it already was unusable in 11, and barely usable in 10 and has been a >>>> shadow of its former self for much longer than that. >>> >>> The reason to keep some form of floppy support, eder fd or ufd is for the >>> purpose of copying (dd) floppy media into image files for use with >>> virtualbox or bhyve VMs. -- (One could say the same for CD and DVD drives. >>> My new laptop at $JOB has no CD/DVD drive.) I digress. I think the ability >>> to copy media to image files for VMs might be a reason to keep some form of >>> support fd or ufd. >> >> >> I'm not sure I understand what you're saying here... > > What I'm saying is that maintaining some form of fdc support whether it be > in fdc(4) or a USB floppy the ability to dd floppy images for subsequent > use in a VM would be desirable. I'm thinking of one example brought to my > attention about a month ago where a person I know needed to copy old floppy > disks to images on his hard drive in order to install an old sewing machine > application in a virtualbox VM running Windows. > > Tangentially speaking, we could make the same case for CD and DVD drives > not too many years from now... > > Personally, I don't care much (well maybe just a little) if fdc(4) itself > is removed however I think we need some kind of support, which USB fd can > supply if or when fdc(4) is removed. Maybe we should deprecate in 12 and > remove in 13? > > Hi, I think as long as you can read and write USB floppy drives under FreeBSD, this change is OK. Even though floppies are old-tech they are still important: https://news.slashdot.org/story/16/05/25/2054255/us-military-uses-8-inch-floppy-disks-to-coordinate-nuclear-force-operations And from time to time we see criminal cases popping up with crazy people using old C64's with floppy disks. I would feel bad if removing support for floppies from FreeBSD would mean you would depend on a Windows installation to read such disks. Further, keep this change two-step. First remove the code from GENERIC. Then wait a year and see if anyone complains. Then delete the source code. --HPS --HPS