Emulate a Sun Ultra 1 running NetBSD

Introduction

Getting the tme software

Making the machine-specific data

In general, any working directory filename that begins with my- or MY- is a file that is specific to your individual emulated machine. With the exception of the disk image, these are mostly text files, and you are encouraged to edit many of them to suit yourself.

% mkdir /some/where/my-sun4u
% cd /some/where/my-sun4u

Now populate this directory:

1. Copy the SUN-ULTRA-1 machine description file into the working directory:

   % cp /usr/pkg/share/examples/tme/SUN-ULTRA-1 ./MY-SUN4U
   

   This file contains tmesh commands that create a Sun Ultra 1. If you don't change this file, it creates a Sun Ultra 1 with a cgsix framebuffer, type-4 keyboard and mouse, one disk drive, one tape drive, and an unconnected network interface.

   WARNING: Although tme enables the cgsix emulation in SUN-ULTRA-1 by default, this is only because NetBSD/sparc64 currently does not support a cgthree console. The tme cgsix emulation is extremely poor. It's usable for the OpenBoot and NetBSD console, but it will definitely not run X.

   If you can't use the emulated framebuffer (because, for example, you aren't running X or didn't build tme with GTK), you must edit this file to disable the GTK-based display and enable the serial console instead. Comments in the MY-SUN4U file should explain how to do this.
2. Copy the ROM images into the working directory:

   % cp /some/where/SUNW,501-3082-update7.bin .
   % cp /some/where/SUNW,501-1415.bin .
   % cp /some/where/SUNW,501-2325.bin .
   

3. Make a Sun Ultra 1 NVRAM file in the working directory:

   The Sun Ultra 1 NVRAM contents are kept in a file. Creating an initial NVRAM file involves writing a file with a specific number of zeroes.

   % dd if=/dev/zero bs=1 count=8176 of=my-sun4u-nvram.bin
   

4. If you do want to use the GTK-based display, copy the Sun keyboards map, and keyboard macros file into the working directory:

   % cp /usr/pkg/share/examples/tme/sun-keyboards.txt .
   % cp /usr/pkg/share/examples/tme/my-sun-macros.txt ./my-sun-macros.txt
   

   You should not edit the sun-keyboards.txt file, however you may want to edit the my-sun-macros.txt file. The two files work together to transform key events on your keyboard into Sun type-4 scan codes.

   The sun-keyboards.txt file lists all of the symbols (in X terminology, all of the "keysyms") on a Sun type-4 keyboard, and gives for each keysym a Sun type-4 scan code and some modifier information. Because Sun type-4 keyboards are never going to change, you shouldn't change this file, even if you think it lists keysyms that your keyboard doesn't have, like L1, R11, etc.

   The my-sun-macros.txt file is meant to adapt your keyboard to the Sun type-4 keyboard. Any keysyms that the Sun type-4 keyboard has, that your keyboard doesn't have, can be generated by macros added to this file. For example, tmesh may complain that:

   [/display0.0]: cannot generate keysym 'R9' directly, or through a macro: No such file or directory
   

   The odds are good that you don't care about generating the R9 key - it's one of the keysyms on the strange, original Sun numeric keypad. But if you absolutely must be able to generate the R9 key, you could add a line similar to the following to your my-sun-macros.txt file:

   Alt_R F9 = R9
   

   Then, you could simulate pressing R9 by pressing the right Alt key and then the F9 key.

   The my-sun-macros.txt that you copied from sun-macros.txt contains a small number of macros for generating the L1, L2, etc., keys. These macros should be sufficient for general use - simply ignore the tmesh warnings about other, obscure keysyms.

   Under X, to learn about the keysyms present on your keyboard, the xmodmap -pk command will print out your current keyboard map. Alternately, the xev command may be a more convenient way to see what key combinations on your keyboard generate which keysyms.

5. Create the empty disk image file. Decide how big you want the emulated disk to be, in bytes, and substitute that number for NNNNNNNN below:

   % dd if=/dev/zero of=my-sun4u-disk.img bs=1 count=1 seek=NNNNNNNN
   

   It's not immediately wasteful to choose a very large disk size - this dd command will create a disk image that initially takes up almost zero real space on your host's disk. Only as the disk is populated will your host's operating system allocate more real space to the image.

Installing NetBSD 5.0.1

Running sysinst