On 10/7/19 11:11 AM, Mischa Baars wrote: > On Mon, 2019-10-07 at 10:45 +0200, Hannes Reinecke wrote: >> On 10/7/19 10:07 AM, Mischa Baars wrote: >>> On Mon, 2019-10-07 at 09:23 +0200, Hannes Reinecke wrote: >>>> On 10/7/19 9:02 AM, Mischa Baars wrote: >>>>> On Sun, 2019-10-06 at 09:10 -0600, Jens Axboe wrote: >>>> [ .. ] >>>>>> I'm saying that you are comparing apples to oranges. The floppy driver >>>>>> might be older tech, but it's much more used than pktcdvd. It's not the >>>>>> case that we must pick one over the other, in terms of what stays and >>>>>> what goes. >>>>>> >>>>> >>>>> Yes we are, sort of. You can even have my pear. That's exactly the problem with your story :) >>>>> >>>>> A DVD is 4Gb and Blueray goes all the way up to 100Gb, while a floppy disc is 1.44Mb. >>>>> Who would want to write his backup files to 1.44Mb floppy disc these days? >>>>> >>>> Why do you keep on bringing up floppy? >>>> I was under the impression that you wanted to use pktdvd, not floppy... >>>> And as Jens made it clear, any potential removal of the floppy driver >>>> will have _zero_ influence on the future of pktdvd. >>> >>> I do not keep bringing up the floppy drives. I'm merely trying to point >>> out that removing the floppy driver is the more logical course of action. >>> >> ?? >> >>> Also, you must be mistaken. It's not about the potential removal of the >>> floppy driver, it's about the removal of the packet writing driver. There >>> will be no pktcdvd kernel module in the future. To be precise, both reading >>> and writing dvd's is already unsupported in the latest linux-next kernel. >>> >> I know what pktcddvd is, and I know what it's used for. >> All what Jens has been complaining is that the code has been >> unmaintained for quite a while, and only very few bugfixes coming in. >> Which typically indicates that there are only very few users left, if any. > > Well, I was using it :( > > Hope that isn't any problem? > >>>> And in either case, the main question here was: >>>> Will you rebase your project to latest mainline once it's ready? >>>> Or will you settle on a kernel version to do your development on, and >>>> continue using that for your project? >>> >>> No, the code is intended for companies like AMD, Intel or ARM. It >>> is not indended for the opensource community. Does that mean that >>> I cannot develop on an opensource platform? Is that you are trying to tell me? >>> >> No. >> What we are trying to tell you is that: >> a) The code is unmaintained, and (as of now) there hadn't been anyone >> expressing an interest. If you require this driver for your project, >> send a mail to Jens Axboe that you are willing to take over >> maintainership for this driver. Then you get to decide if and when the >> driver should be obsoleted. You'll be responsible for fixing issues with >> that driver, true, but to quote the brexit axiom: you can't have the >> cake and eat it ... >> b) The underlying hardware is becoming obsolete. SCSI CD-ROM drivers are >> a thing of the past, and ATAPI hardware is on its way to be replaced >> with USB Flash. Case in point: ATAPI support got dropped from the ATA >> spec ACS-4, and most laptops nowadays don't even have a DVD slot >> anymore. Hence I would question the need for DVD support in the future. >> Unless, of course, you do happen to work for a company producing said >> devices, in which case I would strongly recommend going for a) above. > > b) My point exactly, CD, DVD and Blueray is being replaced by USB Flash. > The problem is, as you can read in my first mail, is that USB is rewritable. Also, I > can't even image that 100Gb Blueray is a thing of the past. Slots can be > replaced by USB, but that doesn't make the writer obsolete. > Kingston 128GB USB flash, USD 15 per unit. What was your question? > > a) If neccesary I could do the maintaining, sure. > Guess it is. Please send a mail to Jens Axboe applying for pktdvd maintainership. Cheers, Hannes -- Dr. Hannes Reinecke Teamlead Storage & Networking hare@xxxxxxx +49 911 74053 688 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 247165 (AG München), GF: Felix Imendörffer
