From: Paul Bristow <paul@paulbristow.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Align removeable media behaviour?
Date: Thu, 14 Feb 2002 00:07:02 +0100 [thread overview]
Message-ID: <3C6AF196.4060206@paulbristow.net> (raw)
During the 2.5 cycle, I see we are going to remove ide-scsi. This means
Iomega are going to have to accept that ide-floppy works for ATAPI
Zip/PocketZip drives and they may wish to consider not trying to force
people to use ide-scsi any more. I guess they will want some IOCTLs
implemented to do this.
Rather than add yet more code to ide-floppy, (yes I know it needs
cleaning - if I ever get a 2.5.x to compile I may be able to do so),
should we consider aligning the behaviour of all removeable devices? I
know Jens is working on the ATAPI CD burning and MO drives, but we have
parallel port drives, USB, Firewire, ATAPI, SCSI, floppy and god knows
what else out there, all in different subsystems with different
maintainers. Should we attempt to have a common set of IOCTLs for ll
format, lock, unlock, eject, validate, grok_partitions etc etc?
It might be a lot easier for userland utilities to have a set of
expected behaviours and supported IOCTLs from the drivers.
--
Paul Bristow
Email:
paul@paulbristow.net
Web:
http://paulbristow.net
ICQ:
11965223
reply other threads:[~2002-02-13 23:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3C6AF196.4060206@paulbristow.net \
--to=paul@paulbristow.net \
--cc=linux-kernel@vger.kernel.org \
/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