Re: netbsd-10, merging device-streams (xstreamtodev, rdbinfo)

[David Brownlee <abs%netbsd.org@localhost>]

OK, looks good. What I propose to do (testing an updated build with
them all uuencoded for comedy historic reasons now:)

- Replace device-streams.tar.gz with device-streams-2.2.0-src.tar.gz &
device-streams-2.2.0.lha (both downloaded from your github)
- Add a copy of README as device-streams.README.md
- Add devtostream streamtodev xdevtostream executables
- Update rdbinfo and xstreamtodev executables

Does that seem reasonable?

On a related note - could the README.md be updated to include a brief
note on each executable and what it does, plus a link back to your
github?

I have a couple of other questions (updating the copy in-tree is not
conditional on any of this):
- Would anyone be interested in putting together a pkgsrc entry for
the tools to build device-streams? It would be nice to be able to
rebuild from any pkgsrc supporting box
- Would you be interested in dual licencing your changes under GPL and
BSD (I would need to Christian E. Hopps also, but wanted to ask here
first). I'm toying with the idea of adding a full copy of the actual
source properly in the NetBSD tree and it's generally encouraged to
have things available as BSD licence. (Note a "No" answer will result
in an "OK", rather than waving of hands and decrying that the world is
ending :)

Once again, thanks for the work!

David

On Tue, 14 Mar 2023 at 20:04, David Brownlee <abs%netbsd.org@localhost> wrote:
>
> Hi Roc,
>
> I'm dealing with a sudden burst of $dayjob related stuff, but I should get time to look at this in a day or so - thanks again for the work on this
>
> David
>
> On Mon, 13 Mar 2023 at 05:04, Roc Vallès <vallesroc%gmail.com@localhost> wrote:
>>
>> Hi Carlos,
>>
>> Yes, this updates xstreamtodev. This "device-streams" name comes from
>> what the uuencoded source code tarball in netbsd's CVS is called. Its
>> makefile builds: streamtodev, devtostream, xstreamtodev, xstreamtodev
>> and rdbinfo.
>>
>> My changes make it so that it builds with the most common AmigaOS
>> crossdev toolchain today (it used SAS/C back in the day). I also
>> cleaned it up and changed everything necessary for large disk support
>> when available (TD64 and NSD) and otherwise to be safe against 4GB+
>> access.
>>
>> This work is in the github I linked, including the full history of the
>> changes I made. The license is of course kept to what the original
>> author had.
>>
>> A developer with commit access would have to uuencode and update the
>> rdbinfo and xstreamtodev binaries. Using mine outright (github release
>> binaries or aminet, they are the same) is an option.
>>
>> As the version we currently have in the netbsd CVS repo will happily
>> clobber your data if asked to write past the 4GB mark, it would be
>> particularly nice for this to be included in the netbsd-10 release.
>>
>> Regards,
>> Roc
>>
>>
>> On Sun, 12 Mar 2023 at 21:03, Carlos Milán Figueredo
>> <cmilanf%hispamsx.org@localhost> wrote:
>> >
>> > From: port-amiga-owner%NetBSD.org@localhost <port-amiga-owner%NetBSD.org@localhost> On Behalf Of Roc Vallès
>> > Sent: jueves, 9 de marzo de 2023 06:05
>> >
>> > > A while back, I updated device-streams, motivated by awareness it
>> > > clobbered data if writes were done above 32bit offsets, which is very
>> > > easy to do as the program targets partitions, they can exist above 4GB
>> > > boundary and large disks are common today.
>> >
>> > Sorry for not being able to answer your question, but I had another one: would this tool replace xstreamtodev?
>> >
>> > Regards,
>> > Carlos
>> >
>> > Carlos Milán Figueredo | HispaMSX System Operator | http://www.hispamsx.org | telnet://bbs.hispamsx.org | https://calnus.com