From: "H. Peter Anvin" <hpa@zytor.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: fdutils.
Date: Tue, 13 Nov 2001 13:02:16 -0800 [thread overview]
Message-ID: <3BF18A58.9080804@zytor.com> (raw)
In-Reply-To: <Pine.GSO.3.96.1011113214448.11222E-100000@delta.ds2.pg.gda.pl>
Maciej W. Rozycki wrote:
>
>>> Hmm, Sun used to have a software-controlled standard floppy drives years
>>>ago...
>>>
>>I'm not talking about Suns.
>
> I'm just pointing out there used to be no problem with making a
> software-controlled eject for a legacy floppy device even long ago if one
> wanted to.
>
Macs have had them since, what, 1984? It's never been a question of it
being a problem, but it hasn't caught on on the PC.
>
>>> Based on local obervations hardly anyone uses floppies anymore... They
>>>are mostly used for system rescue purposes, where the kind of a device
>>>doesn't really matter.
>>>
>>... except that you no longer can fit a reasonable system rescue/install
>>setup on a floppy, so it *defintitely* matters. Also, the floppy device
>>is like a rash all over the hardware; it maintains a highly undesirable
>>legacy.
>>
>
> You only confirm what I wrote -- hardly anyone uses floppies, so there is
> no need to keep mechanical compatibility in devices -- a complete dump of
> 1.44" FD support would be almost harmless. Hence whether a Zip or a
> LS-120 -- it doesn't really matter. You need new media anyway.
>
Unfortunately other people don't seem to see it that way, and so it
doesn't happen. People ship USB floppies with new laptops, so there is
clearly a demand for them. I believe that if LS-120 had been where the
Zip drive was for a brief while, it would have stuck, just because of the
compatibility issue.
-hpa
next prev parent reply other threads:[~2001-11-13 21:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 9:11 fdutils Rajiv Malik
2001-11-13 16:44 ` fdutils Keith Owens
2001-11-15 22:51 ` fdutils Kai Henningsen
2001-11-13 18:28 ` fdutils H. Peter Anvin
2001-11-13 19:42 ` fdutils Maciej W. Rozycki
2001-11-13 19:57 ` fdutils H. Peter Anvin
2001-11-13 20:12 ` fdutils Maciej W. Rozycki
2001-11-13 20:42 ` fdutils H. Peter Anvin
2001-11-13 20:52 ` fdutils Maciej W. Rozycki
2001-11-13 21:02 ` H. Peter Anvin [this message]
2001-11-13 21:45 ` fdutils Richard B. Johnson
2001-11-14 0:22 ` fdutils Pascal Schmidt
2001-11-14 0:23 ` fdutils H. Peter Anvin
2001-11-14 0:37 ` fdutils Pascal Schmidt
2001-11-14 0:50 ` fdutils Riley Williams
2001-11-14 1:30 ` fdutils CaT
2001-11-14 1:35 ` fdutils H. Peter Anvin
2001-11-15 0:40 ` fdutils Riley Williams
2001-11-15 0:51 ` fdutils CaT
2001-11-15 1:09 ` fdutils Riley Williams
2001-11-15 6:23 ` fdutils CaT
2001-11-15 1:15 ` fdutils H. Peter Anvin
2001-11-14 2:20 ` fdutils Mr. James W. Laferriere
2001-11-14 2:18 ` fdutils. (Was Re: [Q] pivot_root and initrd) Mr. James W. Laferriere
2001-11-14 12:18 ` fdutils Maciej W. Rozycki
2001-11-13 22:03 ` fdutils Gerhard Mack
2001-11-14 12:20 ` fdutils Maciej W. Rozycki
2001-11-14 15:25 ` fdutils Gerhard Mack
2001-11-14 13:08 ` fdutils Horst von Brand
2001-11-14 14:01 ` fdutils Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2001-11-16 10:26 fdutils Rajiv Malik
2001-11-13 7:35 fdutils Rajiv Malik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BF18A58.9080804@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox