Research UNIX v9

v9 on TME

This just in, I have just booted Research UNIX v9 on TME’s SUN-3 emulator!

And there we are booted up and logged in.. pardon the disk error..

funinthe

I’m slightly hesitant about uploading it, as it clearly isn’t right… And this is only the binary component, I have integrated the source tree onto the disk image.  But I haven’t actually tried to compile anything except a simple hello-world program.  You can download it here from sourceforge: SUN3-research_v9.7z  If anyone want’s to browse the source, it’s on my CVS browser thing.

17 thoughts on “Research UNIX v9

  1. I can’t get tme to compile on linux 16.04, even following the guide. I keep getting errors along the lines of:
    /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libgtk-x11-2.0.so: undefined reference to symbol ‘g_source_remove’
    /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libglib-2.0.so: error adding symbols: DSO missing from command line
    collect2: error: ld returned 1 exit status

    • You are proably using someting far far too new. That’s why I was using Debian 4… Linux/GTK is far too unforgiving when it comes to code drift. Also I built it for the x86, not the x64, as I wasn’t even sure if it was 64bit friendly.. In my dump file I did include a binary

    • I’ve had plenty of disk issues stressing the system… And I wanted to get stuff like the source in, which I’ve fixed in the latest 30MB version. Nothing too scary.

  2. My first real Sun computer was a Sun 3-/180 full height 19-inch rack with two super eagle 575MB drives. I had to fire one drive up, let it spin up, then the second, let it spin up, and then finally the CPU, any other order and it would trip a 20 amp breaker.

    Now I am trying to get SunOS 4.1.4 running on a qemu sparc emulator. When I try to partition the drive, it fails to write saying drive is unformatted. If I attempt to format,
    it fails. Not sure how to get past this.

    • I ran 4.1.4 on qemu for some time, from memory I did “format -s” from a single-user session (booting off the cd). Did you chose an arbitrary size of disk? I think sunos is relatively picky about disks, and you must chose something that it has in its format table. On solaris 10 I commonly chose the same size as a ST39175LW, which is defined as 23397 cylinders, 2 alt cylinders, 19 heads, 40 sectors.

      Or perhaps you just forgot to enter the command “label” when in format.

      Maybe take a look at this:
      https://en.wikibooks.org/wiki/QEMU/SunOS_4.1.4

      Or finally why don’t you just image one of the disks from your sun4m and boot it?

    • wow it’s hard to imagine a ‘little’ machine with a 68020 that could trip a 20amp breaker! I’ve read time and time again about those super eagle disks, they must have been so popular as they do come up from time to time.

      I recently installed 4.1.4 on SPARC, although I don’t recall doing anything special…

      I just see this in my scripts…

      qemu-system-sparc -monitor tcp::4444,server,nowait -bios ss5.bin -m 32 -nographic -hda sunos414.img -hdb SunOS-4.1.4.iso -net nic,netdev=qemu-lan -netdev vde,id=qemu-lan,sock=/tmp/local/ -nographic -serial mon:telnet:127.0.0.1:23,server,nowait

      and

      qemu-system-sparc -monitor tcp::4444,server,nowait -bios ss5.bin -m 32 -nographic -hda sunos414.img -net nic,netdev=qemu-lan -netdev vde,id=qemu-lan,sock=/tmp/local/ -nographic -serial mon:telnet:127.0.0.1:23,server,nowait

      the second is to run it, the first is to install it… the disk image is 2GB, along with using version 2.8.0

  3. And in this case the system is running Slackware64-14.2 and the TME source code I grabbed, explodes in much the same fashion towards the end.

    I’d need to see about getting it to work inside a Docker image of 13.37 also 64 bit, that is built first then trying it out in similar fashion before I imported it back.

    I believe that the author who does not leave his contact info on the Alumni site does not support it any longer……

    • I think I’m going to try to take another stab at setting up anoncvs…. In the meantime, the whole source tree ought to be out there

    • I made a few changes, and went through some crazy stuff with CVS regarding what path it actually expects for pserver, while everything else didn’t care…


      cvs -d:pserver:[email protected]:/research login
      cvs -d:pserver:[email protected]:/research checkout researchv9/cmd/emacs

      That should do it.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.