Date: Sun, 10 Feb 2013 13:28:44 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: "C. P. Ghost" <cpghost@cordula.ws> Cc: current@freebsd.org Subject: Re: Time to kill fdc ? Message-ID: <80406.1360502924@critter.freebsd.dk> In-Reply-To: <CADGWnjUn66K_Ngwn0Y_wyqX=RTT13h2FC23NeBH3WqNBBwd%2BXw@mail.gmail.com> References: <79955.1360494404@critter.freebsd.dk> <CADGWnjUn66K_Ngwn0Y_wyqX=RTT13h2FC23NeBH3WqNBBwd%2BXw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Content-Type: text/plain; charset=ISO-8859-1 -------- In message <CADGWnjUn66K_Ngwn0Y_wyqX=RTT13h2FC23NeBH3WqNBBwd+Xw@mail.gmail.com> , "C. P. Ghost" writes: >> Unless somebody fixes the fdc driver to work in -current, I intend >> to dust of my axe and cut it from the tree later this spring. > >Any chance to get a user-mode fdc(4) replacement then? Maybe >in ports? Uhm, just how would that work ? If you just want virtual floppies, md(4) is your driver... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?80406.1360502924>