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

--0000000000009c7c8c05f6e1bcc3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=C3=A8s <[email protected]> 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=C3=A1n Figueredo
> <[email protected]> wrote:
> >
> > From: [email protected] <[email protected]> On
> Behalf Of Roc Vall=C3=A8s
> > 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 4G=
B
> > > 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=C3=A1n Figueredo | HispaMSX System Operator |
> http://www.hispamsx.org | telnet://bbs.hispamsx.org | https://calnus.com
>

--0000000000009c7c8c05f6e1bcc3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Roc,</div><div><br></div><div>I&#39;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</div><div><br></div=
><div>David<br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D"gmail_attr">On Mon, 13 Mar 2023 at 05:04, Roc Vall=C3=A8s &lt;<a h=
ref=3D"mailto:[email protected]">[email protected]</a>&gt; wrote:<br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Carlos,<br>
<br>
Yes, this updates xstreamtodev. This &quot;device-streams&quot; name comes =
from<br>
what the uuencoded source code tarball in netbsd&#39;s CVS is called. Its<b=
r>
makefile builds: streamtodev, devtostream, xstreamtodev, xstreamtodev<br>
and rdbinfo.<br>
<br>
My changes make it so that it builds with the most common AmigaOS<br>
crossdev toolchain today (it used SAS/C back in the day). I also<br>
cleaned it up and changed everything necessary for large disk support<br>
when available (TD64 and NSD) and otherwise to be safe against 4GB+<br>
access.<br>
<br>
This work is in the github I linked, including the full history of the<br>
changes I made. The license is of course kept to what the original<br>
author had.<br>
<br>
A developer with commit access would have to uuencode and update the<br>
rdbinfo and xstreamtodev binaries. Using mine outright (github release<br>
binaries or aminet, they are the same) is an option.<br>
<br>
As the version we currently have in the netbsd CVS repo will happily<br>
clobber your data if asked to write past the 4GB mark, it would be<br>
particularly nice for this to be included in the netbsd-10 release.<br>
<br>
Regards,<br>
Roc<br>
<br>
<br>
On Sun, 12 Mar 2023 at 21:03, Carlos Mil=C3=A1n Figueredo<br>
&lt;<a href=3D"mailto:[email protected]" target=3D"_blank">cmilanf@hispa=
msx.org</a>&gt; wrote:<br>
&gt;<br>
&gt; From: [email protected] &lt;[email protected]&gt; =
On Behalf Of Roc Vall=C3=A8s<br>
&gt; Sent: jueves, 9 de marzo de 2023 06:05<br>
&gt;<br>
&gt; &gt; A while back, I updated device-streams, motivated by awareness it=
<br>
&gt; &gt; clobbered data if writes were done above 32bit offsets, which is =
very<br>
&gt; &gt; easy to do as the program targets partitions, they can exist abov=
e 4GB<br>
&gt; &gt; boundary and large disks are common today.<br>
&gt;<br>
&gt; Sorry for not being able to answer your question, but I had another on=
e: would this tool replace xstreamtodev?<br>
&gt;<br>
&gt; Regards,<br>
&gt; Carlos<br>
&gt;<br>
&gt; Carlos Mil=C3=A1n Figueredo | HispaMSX System Operator | <a href=3D"ht=
tp://www.hispamsx.org" rel=3D"noreferrer" target=3D"_blank">http://www.hisp=
amsx.org</a> | telnet://<a href=3D"http://bbs.hispamsx.org" rel=3D"noreferr=
er" target=3D"_blank">bbs.hispamsx.org</a> | <a href=3D"https://calnus.com"=
 rel=3D"noreferrer" target=3D"_blank">https://calnus.com</a><br>
</blockquote></div>

--0000000000009c7c8c05f6e1bcc3--