From: Jens Axboe <axboe@kernel.dk>
To: Mischa Baars <mjbaars1977.linux-block@cyberfiber.eu>,
linux-block@vger.kernel.org
Subject: Re: packet writing support
Date: Sat, 5 Oct 2019 09:50:59 -0600 [thread overview]
Message-ID: <6e381f83-9a12-30d7-8f99-caaa6a608c4f@kernel.dk> (raw)
In-Reply-To: <db5c89c3fe26e4b7ec96443ec97a05df97162889.camel@cyberfiber.eu>
On 10/5/19 4:12 AM, Mischa Baars wrote:
> Advised by the linux-next mailing list to repost this message on the linux-block mailing list:
>
> Hi,
>
> If I'm correct, packet writing support is going to be removed from the
> Linux kernel. Is there any particular reason for
> this, as far as you people know? Both DVD-writers and Blueray-writers are
> still being sold to date.
The reasons are mostly that it's ancient technology and my doubt was
that nobody used it, and it's completely unmaintained code as well.
> I'm currently working on quite a large project. I would be dependent
> solely on USB to store my backup files, when the packet writing support
> is removed. Actually I'm quite uncomfortable with that idea, because
> USB is rewritable. Any serious attempt to do damage to my project will
> result a permanent loss of code. Personally I would do anything to keep
> packet writing support in the kernel.
If there are folks using the code (successfully), it's not going away.
But I can't quite tell from your email if you're just planning to use
it, or if you are using it already and it's working great for you?
> I'd hoped you could remove normal floppy disc support instead. That
> seems the more logical course of action. Floppy disc drives aren't
> being sold anymore for quite some years now.
It's not really a case of quid pro quo, if someone gets removed,
something else can stay. I'd argue that the floppy driver is probably
used by orders of magnitude more people than the packet writing code,
and as such that makes it much more important to maintain.
--
Jens Axboe
next prev parent reply other threads:[~2019-10-05 15:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 10:12 packet writing support Mischa Baars
2019-10-05 15:50 ` Jens Axboe [this message]
2019-10-06 7:31 ` Mischa Baars
2019-10-06 15:10 ` Jens Axboe
2019-10-07 7:02 ` Mischa Baars
2019-10-07 7:23 ` Hannes Reinecke
2019-10-07 8:07 ` Mischa Baars
2019-10-07 8:45 ` Hannes Reinecke
2019-10-07 9:11 ` Mischa Baars
2019-10-07 9:17 ` Mischa Baars
2019-10-07 14:22 ` Bart Van Assche
2019-10-07 14:36 ` Mischa Baars
2019-10-07 16:13 ` Mischa Baars
2019-10-07 16:19 ` Jens Axboe
2019-10-07 17:31 ` Mischa Baars
2019-10-07 10:02 ` Hannes Reinecke
2019-10-07 14:10 ` Jens Axboe
2019-10-07 14:19 ` Mischa Baars
2019-10-06 8:31 ` Mischa Baars
2019-10-06 20:48 ` Laurence Oberman
2019-10-07 8:10 ` Mischa Baars
2019-10-07 9:02 ` Mischa Baars
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=6e381f83-9a12-30d7-8f99-caaa6a608c4f@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=mjbaars1977.linux-block@cyberfiber.eu \
/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;
as well as URLs for NNTP newsgroup(s).