<p>Hi !</p>
<p>I can sponsor VAX remote access if you dont have machine and you want to hack the code on them. I got microvax 3100 and vaxstation 3100 and 4000/90. Its hard to say when I can find the time to install something to them, because I am busy with work lately, it surely wont happen before new year. Keep up with the good work I am looking forward to that.</p>
<p>Kind regards,<br>
Jan Prunk</p>
<p><blockquote type="cite">On Dec 3, 2012 4:07 PM, "Maciej W. Rozycki" <<a href="mailto:macro@linux-mips.org">macro@linux-mips.org</a>> wrote:<br><br><p><font color="#500050">Toby,<br><br>> > > I too have a working mopd based netboot for a MicroVAX II. I did however<br>
> > > have<br>> >...</font></p> I've had a look and it seems to me that your tree has none of the changes<br>
I made over 10 years ago (I can see my last build, rev. 15, is dated 17th<br>
Nov 2002). Chances are you've been working on issues that have been long<br>
fixed. :(<br>
<br>
If you have a record of changes readily available (I can't see offhand<br>
how to extract any diffs out of <a href="http://github.com" target="_blank">github.com</a>), then I can see how I can<br>
integrate them into my sources. It may be easier than the other way round<br>
as I have collected 16 patches so far, on top of the genuine 2.5.3 tarball<br>
(dated 21st Aug 1996) that has since gone from its original distribution<br>
site at <a href="http://ftp.stacken.kth.se" target="_blank">ftp.stacken.kth.se</a>. If there are any conflicts, it may take less<br>
effort to resolve them in your change rather than in the other 16.<br>
<br>
I've got copies of mopd-2.5.3.tar.gz mentioned above at:<br>
<br>
<a href="ftp://ftp.linux-mips.org/pub/linux/mips/people/macro/mopd/" target="_blank">ftp://ftp.linux-mips.org/pub/linux/mips/people/macro/mopd/</a><br>
<br>
and in the source RPM packages elsewhere at my site.<br>
<p><font color="#500050"><br>> Since I have three MicroVAX IIs here, maybe I could find time next year to<br>> play with Linux/VAX....</font></p> No idea, perhaps someone else could comment. I can see there is an<br>
arch/vax/kernel/cpu_ka630.c module in the tree, but I have no such<br>
hardware, so I can't say how functional or complete it is. The devil<br>
might lie in the peripherals, at the very least the serial console and the<br>
network interface need to work for the kernel to be of any use.<br>
<br>
Your best bet might be to try out and report your findings here. ;)<br>
<p><font color="#500050"><br>> Thanks for your hard work, Maciej.<br></font></p> My pleasure! :)<br>
<p><font color="#500050"><br> Maciej<br>_______________________________________________<br>Vax-linux mailing list<br>Vax-linux@vax-linux...</font></p></blockquote></p>