Computer History Wiki - User contributions [en]

Template talk:My sandbox

2019-04-09T12:21:06Z

Darkstar:

Why is this a template? Shouldn't this be a regular page, preferably a sub-page under the owners' user page? --[[User:Darkstar|Darkstar]] ([[User talk:Darkstar|talk]]) 00:57, 9 April 2019 (CEST)

: Good catch. We should check with [[User:Dugo|Dugo]] to make sure it's OK, but then we can do more or less as you suggest, and move the page to be sub-page of their User: page, although I'll have to look up how to include one page in another (which is presumably the reason they used a Template: page). [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 01:30, 9 April 2019 (CEST)
: Oh, it turns out to be simple; the <nowiki>{{}}</nowiki> syntax can transclude pages/sub-pages from namespaces other than Template:, all one has to do is specify the namespace. So <nowiki>{{User:Dugo/My sandbox}}</nowiki> will do it. (I used to know all this stuff back when I was an active admin on Wikipedia, but I've forgotten a lot of it, had to look it up! :-) [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 05:04, 9 April 2019 (CEST)
:: yes, but my point was rather that this is a page that looks and feels just like a sandbox page, i.e. lots of random stuff scattered around. I bet it is not designed to be transcluded into other pages (and as of this writing, it has exactly 0 active transclusions except from the user's page itself) so I don't understand why this needs to be a template at all... --[[User:Darkstar|Darkstar]] ([[User talk:Darkstar|talk]]) 14:21, 9 April 2019 (CEST)

Template talk:My sandbox

2019-04-08T22:57:45Z

Darkstar: Created page with "Why is this a template? Shouldn't this be a regular page, preferably a sub-page under the owners' user page? --~~~~"

Why is this a template? Shouldn't this be a regular page, preferably a sub-page under the owners' user page? --[[User:Darkstar|Darkstar]] ([[User talk:Darkstar|talk]]) 00:57, 9 April 2019 (CEST)

Talk:Rogue

2019-03-24T06:59:52Z

Darkstar: ArchiveRL

==Good archive==

Here is the most ( and I mean very very most ) extensive
collections and source for both executibles, and source code
to the classic game ROGUE, I have found:

https://britzl.github.io/roguearchive/

I have met Jon Lane and Glenn Wickman, [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 08:44, 22 March 2019‎ (CET)

: [https://archive.org/details/ArchiveRL.7z This] is probably even more extensive, although it covers all Roguelikes, not just Rogue itself... --[[User:Darkstar|Darkstar]] ([[User talk:Darkstar|talk]]) 07:59, 24 March 2019 (CET)

XENIX

2019-03-18T23:13:04Z

Darkstar: /* Motorola */ formatting

[[Image:Xenix 386.jpg|thumb|right|200px|Xenix on a 386]]

'''Xenix''' was [[Microsoft]] [[software port|port]] of AT&T [[UNIX]]. Based on [[UNIX Sixth Edition|v6]], [[Unix Seventh Edition|v7]], [[SYSIII]], and later [[SYSV]].

: ''XENIX was originally developed on a DEC Virtual Address Extension (VAX) running the Virtual Memory System (VMS) and a PDP-11 running UNIX V7, albeit now using Microsoft's own in-house minicomputers, and then converted into assembly language specific to the new 16-bit Motorola 68000 and Intel 8086 microprocessors. This put XENIX at the high end of the microcomputer market, which was still dominated by 8-bit machines, but well below the lowest end of the minicomputer market'' - "XENIX -- Microsoft Short-lived Love Affair with Unix "

Unfortinatly, "Xenix even incorporated the elements of BSD and became the most widely installed base of any Unix variant. Talking about the different modifications of Xenix, it was ported to Zilong Z8001, Intel 8086, Tandy Corporation’s 68000 based computers, and even a variant for Apple Lisa."

<blockquote>Modifications to Western Electric v7 included those necessary to transport the UNIX system from the larger PDP-11 mini computer to the 16-bit microprocessors. Currently scheduled machines included the DEC LSI-11/23, Zilogs Z8001 and Z8002, Intel's 8086 and 286, and Motorola's MC68000. - Robert Greenburg, uSloth. </blockquote>

Because of the price of the OS, about $500USD for the OS, and $500USD for the developer tools, combined with cheap [[IBM PC|PC]] and [[IBM-compatible PC|compatibles]], Xenix was the most widespread UNIX until the rise of [[Linux]]. Xenix due to its inherent [[multi-user]] capabilities became widespread in sales environments with POS (Point of Sales) terminals, and for scheduling systems commonly found in hotels and restaurants. Occasionally you can still find this setup still running on aging [[hardware]].

Xenix was a [[portable]] [[operating system]] with ports to various platforms, but with the rise of the [[IBM PC]], it primarily became an [[Intel x86|x86]] based OS. Xenix eventually became [[SCO Unix]], then later SCO [[OpenServer]], where it still languishes today.

= Platforms =

=== Intel ===

As mentioned in the OEM guide [http://www.tenox.tc/docs/microsoft_xenix_oem_directory.pdf pdf], Xenix supported the following platforms:

*[[IBM 386]] [386] The 32bit ones will run on Qemu/Virtual PC
*IBM [[PS/2]] [386MC] This version was specifically for [[MCA]] computers with a 386 or higher CPU.
*[[IBM AT|IBM 286]] [286] As is this version..*
*IBM PC [8088 or x86] This is 'easy' to find.

This is a list of version numbers for the various Architectures:

*8086 – 2.1.3 (SCO v2.1.3)
*286 – 2.1.3, 2.2.1, 2.3.2 ( SC0 v2.1.3, v2.2.1e, v2.2.3b, v2.3.2d)
*386 – 2.2.3, 2.3.4a, 2.3.4q ( SCO v2.2.3b, v2.3.2f, v2.3.4h)
*SysV 386 – 3.2 4.2

=== Motorola ===

* A BYTE Magazine article reviews a MC68000 expansion card that runs Xenix from a company called Sritek
** https://ia801001.us.archive.org/34/items/BYTE_Vol_09-07_1984-07_Computers_and_Video/BYTE_Vol_09-07_1984-07_Computers_and_Video.pdf
*IBM System 9000 [M68000] [c19894]
**https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?htmlfid=897/ENUS284-159&infotype=AN&subtype=CA&appname=skmwww
*[[Apple Lisa]] [M68000] [c1984] The emulator [[idle]] can run this.

=== Others ===

*[[PDP-11]] No versions of this exist online.
*[[Tandy TRS-80 Model II]] [Z80A] There are disk images floating around.
*[[Zilog Z8001]] [c1979] I have only found sales literature that mentions this.*

*Note: This sounds like vaporware since neither the Onyx 1 nor the Commodore 900 ran Xenix

More here: [http://www.softpanorama.org/People/Torvalds/Finland_period/xenix_microsoft_shortlived_love_affair_with_unix.shtml XENIX -- Microsoft Short-lived Love Affair with Unix]

== Software ==

A quick list of a few software programs that were available on Xenix. I know the [[x86]] platform was the most supported, I now know that some of these made it to the less popular [[68000]] platform.

=== Microsoft ===

Microsoft made several of their programs in the 1980's available on the Xenix platform.
Microsoft Multiplan, and the BASIC Compiler.

=== Languages ===

*[[C programming language|C]]
*[[Basic]] [[Basic Compiler]] [[Basic Interpreter]]
*[[Cobol]]
*[[FORTRAN|Fortran]]
*[[Pascal]]
*[[Assembler]]

"the base operating system does not include development tools such as a C compiler, but it does include the linker and, importantly, an assembler (which is needed to rebuild the configuration files). The assembler is, however, disguised to make it less obvious what it is by giving it a different name and that is what I have been trying to remember ever since I saw this post. Finally, this morning, it came to me. You *should* find that you have something called "storel" (read it as "s-to-rel" as in "something that transforms ".s" files into relocatable (ie ".o") files and the name becomes a little less obscure) on the system - I *think* that it lives in /bin. but it *might* be somewhere else such as /etc." http://www.vcfed.org/forum/archive/index.php/t-49002.html

=== Applications ===

*Autodesk AutoCAD 10i
*Microsoft Multiplan (available on the Apple Lisa)
*Microsoft Word v5.0
*vi ( not really an application, but more of a torture device ) ( May not be present on the x86 version, so ed will have to be used )

=== Databases ===

*Foxpro

=== Games ===

* [[Rogue]]

=== SCO* ===

*SCO Professional
*SCO Lyrix (available on the Apple Lisa)
*SCO Integra
*SCO Manager
*SCO Multiview

A history of Xenix:
[https://fossbytes.com/xenix-history-microsoft-unix-operating-system/ History Of Xenix - Microsoft's Forgotten Unix-based Operating System]

[https://soylentnews.org/article.pl?sid=17/03/03/1620222 Restoring Xenix 386 2.2.3c, Part 1]

<nowiki>*</nowiki> - ''SCO in this case refers to the original Santa Cruz Operation, and not the later SCO Group who bought the name and started the SCO/Linux lawsuits.''

Byte Magazine Article on Xenix June 1980, BYTE, pg 249

https://archive.org/details/byte-magazine-1981-06/page/n249

== Emulators with ready to run distributions ==

* [x86] Architecture

http://www.hampa.ch/pce/download.html

* [i286] Architecture

Run Xenix in a browser window!

https://www.pcjs.org/disks/pcx86/unix/sco/xenix/086/2.1.3/

https://www.pcjs.org/disks/pcx86/unix/sco/xenix/286/2.1.3/ [ Currently does none of the 286 versions boot]

https://www.pcjs.org/disks/pcx86/unix/sco/xenix/386/

== Getting this to run ==

*[[Installing Xenix 2.x on Qemu|i386/i286 Xenix 2]]
: Note: The 286 version of Xenix will only run on a 286 processor or a 286 processor emulator that handles the upper byte of the machine status word, later reserved for use on a 386, by essentially ignoring it, and letting Xenix use it. A poor programming choice as best.

Available Xenix repositories:

https://github.com/retrohun/blog/tree/master/dt/xenix286ondemand

https://archive.org/details/msxenix/history/files/pics/progman5.jpg.~1~

https://winworldpc.com/product/xenix/286

http://www.vcfed.org/forum/showthread.php?30490-Xenix-Development-Systems

These guys made some extraordinary efforts to get a few utilities to run:

https://soylentnews.org/article.pl?sid=17/03/13/086250

== Other Reference Pages ==

https://en.wikipedia.org/wiki/Xenix

http://www.edm2.com/index.php/XENIX

Extensive bibliography

http://www.softpanorama.org/People/Torvalds/Finland_period/xenix_microsoft_shortlived_love_affair_with_unix.shtml

{{semi-stub}}

{{Nav Unix}}

[[Category: Unix-based OS's]]

XENIX

2019-03-18T23:12:31Z

Darkstar: /* Intel */ formatting

[[Image:Xenix 386.jpg|thumb|right|200px|Xenix on a 386]]

'''Xenix''' was [[Microsoft]] [[software port|port]] of AT&T [[UNIX]]. Based on [[UNIX Sixth Edition|v6]], [[Unix Seventh Edition|v7]], [[SYSIII]], and later [[SYSV]].

: ''XENIX was originally developed on a DEC Virtual Address Extension (VAX) running the Virtual Memory System (VMS) and a PDP-11 running UNIX V7, albeit now using Microsoft's own in-house minicomputers, and then converted into assembly language specific to the new 16-bit Motorola 68000 and Intel 8086 microprocessors. This put XENIX at the high end of the microcomputer market, which was still dominated by 8-bit machines, but well below the lowest end of the minicomputer market'' - "XENIX -- Microsoft Short-lived Love Affair with Unix "

Unfortinatly, "Xenix even incorporated the elements of BSD and became the most widely installed base of any Unix variant. Talking about the different modifications of Xenix, it was ported to Zilong Z8001, Intel 8086, Tandy Corporation’s 68000 based computers, and even a variant for Apple Lisa."

<blockquote>Modifications to Western Electric v7 included those necessary to transport the UNIX system from the larger PDP-11 mini computer to the 16-bit microprocessors. Currently scheduled machines included the DEC LSI-11/23, Zilogs Z8001 and Z8002, Intel's 8086 and 286, and Motorola's MC68000. - Robert Greenburg, uSloth. </blockquote>

Because of the price of the OS, about $500USD for the OS, and $500USD for the developer tools, combined with cheap [[IBM PC|PC]] and [[IBM-compatible PC|compatibles]], Xenix was the most widespread UNIX until the rise of [[Linux]]. Xenix due to its inherent [[multi-user]] capabilities became widespread in sales environments with POS (Point of Sales) terminals, and for scheduling systems commonly found in hotels and restaurants. Occasionally you can still find this setup still running on aging [[hardware]].

Xenix was a [[portable]] [[operating system]] with ports to various platforms, but with the rise of the [[IBM PC]], it primarily became an [[Intel x86|x86]] based OS. Xenix eventually became [[SCO Unix]], then later SCO [[OpenServer]], where it still languishes today.

= Platforms =

=== Intel ===

As mentioned in the OEM guide [http://www.tenox.tc/docs/microsoft_xenix_oem_directory.pdf pdf], Xenix supported the following platforms:

*[[IBM 386]] [386] The 32bit ones will run on Qemu/Virtual PC
*IBM [[PS/2]] [386MC] This version was specifically for [[MCA]] computers with a 386 or higher CPU.
*[[IBM AT|IBM 286]] [286] As is this version..*
*IBM PC [8088 or x86] This is 'easy' to find.

This is a list of version numbers for the various Architectures:

*8086 – 2.1.3 (SCO v2.1.3)
*286 – 2.1.3, 2.2.1, 2.3.2 ( SC0 v2.1.3, v2.2.1e, v2.2.3b, v2.3.2d)
*386 – 2.2.3, 2.3.4a, 2.3.4q ( SCO v2.2.3b, v2.3.2f, v2.3.4h)
*SysV 386 – 3.2 4.2

=== Motorola ===

** A BYTE Magazine article reviews a MC68000 expansion card that runs Xenix from a company called Sritek
*** https://ia801001.us.archive.org/34/items/BYTE_Vol_09-07_1984-07_Computers_and_Video/BYTE_Vol_09-07_1984-07_Computers_and_Video.pdf
*IBM System 9000 [M68000] [c19894]
**https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?htmlfid=897/ENUS284-159&infotype=AN&subtype=CA&appname=skmwww
*[[Apple Lisa]] [M68000] [c1984] The emulator [[idle]] can run this.

=== Others ===

*[[PDP-11]] No versions of this exist online.
*[[Tandy TRS-80 Model II]] [Z80A] There are disk images floating around.
*[[Zilog Z8001]] [c1979] I have only found sales literature that mentions this.*

*Note: This sounds like vaporware since neither the Onyx 1 nor the Commodore 900 ran Xenix

More here: [http://www.softpanorama.org/People/Torvalds/Finland_period/xenix_microsoft_shortlived_love_affair_with_unix.shtml XENIX -- Microsoft Short-lived Love Affair with Unix]

== Software ==

A quick list of a few software programs that were available on Xenix. I know the [[x86]] platform was the most supported, I now know that some of these made it to the less popular [[68000]] platform.

=== Microsoft ===

Microsoft made several of their programs in the 1980's available on the Xenix platform.
Microsoft Multiplan, and the BASIC Compiler.

=== Languages ===

*[[C programming language|C]]
*[[Basic]] [[Basic Compiler]] [[Basic Interpreter]]
*[[Cobol]]
*[[FORTRAN|Fortran]]
*[[Pascal]]
*[[Assembler]]

"the base operating system does not include development tools such as a C compiler, but it does include the linker and, importantly, an assembler (which is needed to rebuild the configuration files). The assembler is, however, disguised to make it less obvious what it is by giving it a different name and that is what I have been trying to remember ever since I saw this post. Finally, this morning, it came to me. You *should* find that you have something called "storel" (read it as "s-to-rel" as in "something that transforms ".s" files into relocatable (ie ".o") files and the name becomes a little less obscure) on the system - I *think* that it lives in /bin. but it *might* be somewhere else such as /etc." http://www.vcfed.org/forum/archive/index.php/t-49002.html

=== Applications ===

*Autodesk AutoCAD 10i
*Microsoft Multiplan (available on the Apple Lisa)
*Microsoft Word v5.0
*vi ( not really an application, but more of a torture device ) ( May not be present on the x86 version, so ed will have to be used )

=== Databases ===

*Foxpro

=== Games ===

* [[Rogue]]

=== SCO* ===

*SCO Professional
*SCO Lyrix (available on the Apple Lisa)
*SCO Integra
*SCO Manager
*SCO Multiview

A history of Xenix:
[https://fossbytes.com/xenix-history-microsoft-unix-operating-system/ History Of Xenix - Microsoft's Forgotten Unix-based Operating System]

[https://soylentnews.org/article.pl?sid=17/03/03/1620222 Restoring Xenix 386 2.2.3c, Part 1]

<nowiki>*</nowiki> - ''SCO in this case refers to the original Santa Cruz Operation, and not the later SCO Group who bought the name and started the SCO/Linux lawsuits.''

Byte Magazine Article on Xenix June 1980, BYTE, pg 249

https://archive.org/details/byte-magazine-1981-06/page/n249

== Emulators with ready to run distributions ==

* [x86] Architecture

http://www.hampa.ch/pce/download.html

* [i286] Architecture

Run Xenix in a browser window!

https://www.pcjs.org/disks/pcx86/unix/sco/xenix/086/2.1.3/

https://www.pcjs.org/disks/pcx86/unix/sco/xenix/286/2.1.3/ [ Currently does none of the 286 versions boot]

https://www.pcjs.org/disks/pcx86/unix/sco/xenix/386/

== Getting this to run ==

*[[Installing Xenix 2.x on Qemu|i386/i286 Xenix 2]]
: Note: The 286 version of Xenix will only run on a 286 processor or a 286 processor emulator that handles the upper byte of the machine status word, later reserved for use on a 386, by essentially ignoring it, and letting Xenix use it. A poor programming choice as best.

Available Xenix repositories:

https://github.com/retrohun/blog/tree/master/dt/xenix286ondemand

https://archive.org/details/msxenix/history/files/pics/progman5.jpg.~1~

https://winworldpc.com/product/xenix/286

http://www.vcfed.org/forum/showthread.php?30490-Xenix-Development-Systems

These guys made some extraordinary efforts to get a few utilities to run:

https://soylentnews.org/article.pl?sid=17/03/13/086250

== Other Reference Pages ==

https://en.wikipedia.org/wiki/Xenix

http://www.edm2.com/index.php/XENIX

Extensive bibliography

http://www.softpanorama.org/People/Torvalds/Finland_period/xenix_microsoft_shortlived_love_affair_with_unix.shtml

{{semi-stub}}

{{Nav Unix}}

[[Category: Unix-based OS's]]

Talk:SunOS

2018-04-10T11:26:36Z

Darkstar:

I understand SunOS 4.1.1_U1 was the last version for the sun3/3x, but when was sun1 and sun2 support dropped?
:From Wikipedia: "Sun-2 systems were supported in SunOS until version 4.0.3." [https://en.wikipedia.org/wiki/Sun-2]. No idea about Sun-1 though

Talk:Installing 4.3 BSD+NFS Wisconsin Unix

2018-02-05T23:42:53Z

Darkstar: Created page with "==Trouble== I'm having some trouble setting up 4.3BSD with this recipe. First, when I boot from the miniroot linked in the articles, I get a different kernel: VAX 11/780 sim..."

==Trouble==
I'm having some trouble setting up 4.3BSD with this recipe.

First, when I boot from the miniroot linked in the articles, I get a different kernel:
VAX 11/780 simulator V4.0-0 Beta git commit id: 49911369
loading ra(0,0)boot
Boot
: ra(0,0)vmunix
290188+89696+102928 start 0x12f8
4.3 BSD UNIX #3: Mon Dec 29 11:54:56 CST 1986
tadl@brie:/usr/src/bsd/4.3/sys/GENERIC
real mem = 8388608
SYSPTSIZE limits number of buffers to 134
avail mem = 7136256
using 134 buffers containing 524288 bytes of memory
Note ''tadl@brie...'' and the timestamp differs from what is written in the recipe.

Then, the devices do not get created correctly, since MAKEDEV spits out a syntax error:
# sh MAKEDEV ra1
mknod: ra1a: File exists
mknod: ra1b: File exists
mknod: ra1c: File exists
mknod: ra1g: File exists
mknod: rra1a: File exists
mknod: rra1b: File exists
mknod: rra1c: File exists
mknod: rra1g: File exists
syntax error
MAKEDEV: chgrp: not found
MAKEDEV: chmod: not found
The error is somewhere in the ''if [ $name != hk ]'' line, I think, but it is easily overcome by manually creating the required device nodes.

The real issue I have, however, is when formatting ra0h:
# newfs ra0h ra81
write error: 759667
wtfs: Invalid argument

This is related to the disktab I guess (wrong kernel? wrong newfs executable?). Running newfs with a different disk type works (but gives less space of course):
# newfs ra0h ra80
Warning: inode blocks/cyl group (54) >= data blocks (12) in last
cylinder group. This implies 98 sector(s) cannot be allocated.
/dev/rra0h: 111104 sectors in 256 cylinders of 14 tracks, 31 sectors
56.9Mb in 16 cyl groups (16 c/g, 3.56Mb/g, 1504 i/g)
super-block backups (for fsck -b#) at:
32, 7008, 13984, 20960, 27936, 34912, 41888, 48864, 55840, 62816,
69792, 76768, 83744, 90720, 97696, 104672,

Any ideas?

Template:Nav Unix

2017-04-01T17:47:36Z

Darkstar: typo

{{Navigation
| templateName = Nav Unix
| title = [[Unix]] Versions, Vendors and Related
| body = Research Unix [[UNIX Fifth Edition]] • [[UNIX Sixth Edition]] • [[Unix Seventh Edition]] • [[Unix Eighth Edition]] • [[Unix Ninth Edition]] • [[32v]]
AT&T - [[Unix SYSIII]] • [[Unix SYSIV]] • [[Unix SYSV]]

BSD - [[2.9 BSD]] • [[2.10 BSD]] • [[2.11 BSD]] • [[3 BSD]] • [[4.0 BSD]] • [[4.1 BSD]] • [[4.2 BSD]] • [[4.3 BSD]] • [[NeXTSTEP]] • [[Darwin]] • [[NetBSD]] • [[OpenBSD]]

Other - [[AMIX]] • [[SunOS]] • [[Solaris]] • [[Ultrix]] • [[A/UX]] • [[Xenix]] • [[AIX]]

Clones - [[DEMOS]] • [[Coherent]]
}}

Unix Ninth Edition

2017-04-01T17:46:57Z

Darkstar: Darkstar moved page Unix Nineth Edition to Unix Ninth Edition: typo

{{Infobox OS
| image = nineth edition unix v9.png
| caption = First boot on TME
| name = Unix V9
| creator = Bell Labs
| current version = v9
| year introduced = 1986
| type = Multitasking, multiuser
| architecture = [[SUN-3]]
}}

A version of 9th Edition Unix was recently released by Alcatel-Lucent and is available [http://www.tuhs.org/Archive/Distributions/Research/Norman_v9/ here] for download. It is not a complete distribution tape, just a tar file of a running system, made by Norman Wilson.

Actually, "released" is too strong a word. They just signed a letter saying that they won't sue for the release of v8-v10 Unix. The letter can be read [http://www.tuhs.org/Archive/Distributions/Research/Dan_Cross_v8/statement_regarding_Unix_3-7-17.pdf here] (PDF).

== Notable features ==

== Getting it to run on TME ==
In order to get this running I had to install SunOS 4.x onto TME, and then follow the install instructions on setting up a disk. TME emulates a SUN3-150 with a SUN3-160 ROM, and will need the unix.75 kernel

== Games ==

The following games are included in the v9 distribution mentioned above:
<pre>
</pre>

{{Nav Unix}}
[[Category:Operating Systems]]

Unix Eighth Edition

2017-03-30T11:25:37Z

Darkstar: /* Getting it to run on SimH */ small info

{{Infobox OS
| image = eigth edition unix v8.jpg
| caption = (none yet)
| name = Unix V8
| creator = Bell Labs
| current version = v8
| year introduced = 1985
| type = Multitasking, multiuser
| architecture = [[VAX]]
}}

A version of 8th Edition Unix was recently released by Alcatel-Lucent and is available [http://www.tuhs.org/Archive/Distributions/Research/Dan_Cross_v8/ here] for download. It is not a complete distribution tape, just a tar file of a running system, made by Dan Cross.

Actually, "released" is too strong a word. They just signed a letter saying that they won't sue for the release of v8-v10 Unix. The letter can be read [http://www.tuhs.org/Archive/Distributions/Research/Dan_Cross_v8/statement_regarding_Unix_3-7-17.pdf here] (PDF).

== Notable features ==

Unix v8 includes the stream interface (in /usr/include/sys/stream.h), as opposed to the socket interface, for doing network programming.

Also included are PDP-11 cross-compilers and associated tools (assembler, linker, etc) as /usr/bin/{11cc,11as,...}

== Getting it to run on SimH ==
[http://9legacy.org/9legacy/doc/simh/v8 Here] are some instructions. Some things must be done slightly different or in a different order though. For example you either need an old(er) version of SimH to run it, like 3.8, or use "set noasync" in your configs, otherwise you ''will'' get I/O errors.

Boot messages of a v8 system running in SimH:
<pre>
Boot
: hp(0,0)unix
159316+54592+381508 start 0xf48
Unix 8th Edition Mon Mar 29 08:20:14 EST 1976
real mem = 8322048 nbuf = 254 nswbuf = 126
avail mem = 6316032
mcr0 at tr1
mcr1 at tr2
uba0 at tr3
dz0 at uba0 csr 160100 vec 0300 ipl x15
mba0 at tr8
hp0 at mba0 drive 0
hp1 at mba0 drive 1
mba1 at tr9
ht0 at mba1 drive 0
Mon Mar 29 08:20:56 EST 1976
Autoboot:
/dev/rp0a: 531 files 2316 blocks 5307 free
/dev/rrp0g: 8753 files 50554 blocks 91024 free
Mon Mar 29 08:20:59 EST 1976
not a VAX-11/750
Mounted /dev/rp0g on /usr
/tmp/dump: No such file or directory
fstyp = 2 mounted on /proc

v8generi
login: root
Welcome to Eighth Edition Unix. You may be sure that it
is suitably protected by ironclad licences, contractual agreements,
living wills, and trade secret laws of every sort. A trolley car is
certain to grow in your stomach if you violate the conditions
under which you got this tape. Consult your lawyer in case of any doubt.
If doubt persists, consult our lawyers.

Please commit this message to memory. If this is a hardcopy terminal,
tear off the paper and affix it to your machine. Otherwise
take a photo of your screen. Then delete /etc/motd.

Thank you for choosing Eighth Edition Unix. Have a nice day.
#
</pre>

== Games ==

The following games are included in the v8 distribution mentioned above:
<pre>
arithmetic
atc
back
banner
bcd
bigp
canfield
cbrogue
festoon
fish
fortune
hack
hangman
hanoi
mille
ogre
ppt
quiz
rogomatic
rogue
rogue52
rogue53
sail
say
scapegoat
snake
sread
thanks
tictactoe
tso
worm
zork
</pre>

{{Nav Unix}}
[[Category:Operating Systems]]

Unix Eighth Edition

2017-03-30T11:24:02Z

Darkstar: /* Getting it to run on SimH */

{{Infobox OS
| image = eigth edition unix v8.jpg
| caption = (none yet)
| name = Unix V8
| creator = Bell Labs
| current version = v8
| year introduced = 1985
| type = Multitasking, multiuser
| architecture = [[VAX]]
}}

A version of 8th Edition Unix was recently released by Alcatel-Lucent and is available [http://www.tuhs.org/Archive/Distributions/Research/Dan_Cross_v8/ here] for download. It is not a complete distribution tape, just a tar file of a running system, made by Dan Cross.

Actually, "released" is too strong a word. They just signed a letter saying that they won't sue for the release of v8-v10 Unix. The letter can be read [http://www.tuhs.org/Archive/Distributions/Research/Dan_Cross_v8/statement_regarding_Unix_3-7-17.pdf here] (PDF).

== Notable features ==

Unix v8 includes the stream interface (in /usr/include/sys/stream.h), as opposed to the socket interface, for doing network programming.

Also included are PDP-11 cross-compilers and associated tools (assembler, linker, etc) as /usr/bin/{11cc,11as,...}

== Getting it to run on SimH ==
[http://9legacy.org/9legacy/doc/simh/v8 Here] are some instructions (very rough; some things must be done slightly different or in a different order)

Boot messages of a v8 system running in SimH

<pre>
Boot
: hp(0,0)unix
159316+54592+381508 start 0xf48
Unix 8th Edition Mon Mar 29 08:20:14 EST 1976
real mem = 8322048 nbuf = 254 nswbuf = 126
avail mem = 6316032
mcr0 at tr1
mcr1 at tr2
uba0 at tr3
dz0 at uba0 csr 160100 vec 0300 ipl x15
mba0 at tr8
hp0 at mba0 drive 0
hp1 at mba0 drive 1
mba1 at tr9
ht0 at mba1 drive 0
Mon Mar 29 08:20:56 EST 1976
Autoboot:
/dev/rp0a: 531 files 2316 blocks 5307 free
/dev/rrp0g: 8753 files 50554 blocks 91024 free
Mon Mar 29 08:20:59 EST 1976
not a VAX-11/750
Mounted /dev/rp0g on /usr
/tmp/dump: No such file or directory
fstyp = 2 mounted on /proc

v8generi
login: root
Welcome to Eighth Edition Unix. You may be sure that it
is suitably protected by ironclad licences, contractual agreements,
living wills, and trade secret laws of every sort. A trolley car is
certain to grow in your stomach if you violate the conditions
under which you got this tape. Consult your lawyer in case of any doubt.
If doubt persists, consult our lawyers.

Please commit this message to memory. If this is a hardcopy terminal,
tear off the paper and affix it to your machine. Otherwise
take a photo of your screen. Then delete /etc/motd.

Thank you for choosing Eighth Edition Unix. Have a nice day.
#
</pre>

== Games ==

The following games are included in the v8 distribution mentioned above:
<pre>
arithmetic
atc
back
banner
bcd
bigp
canfield
cbrogue
festoon
fish
fortune
hack
hangman
hanoi
mille
ogre
ppt
quiz
rogomatic
rogue
rogue52
rogue53
sail
say
scapegoat
snake
sread
thanks
tictactoe
tso
worm
zork
</pre>

{{Nav Unix}}
[[Category:Operating Systems]]

Unix Eighth Edition

2017-03-28T21:36:58Z

Darkstar: Getting it to run

Template:Nav Unix

2017-03-28T21:24:17Z

Darkstar: add 8th edition Unix

{{Navigation
| templateName = Nav Unix
| title = [[Unix]] Versions, Vendors and Related
| body = Research Unix [[UNIX Fifth Edition]] • [[UNIX Sixth Edition]] • [[Unix Seventh Edition]] • [[Unix Eighth Edition]] • [[32v]]
AT&T - [[Unix SYSIII]] • [[Unix SYSIV]] • [[Unix SYSV]]

BSD - [[2.9 BSD]] • [[2.10 BSD]] • [[2.11 BSD]] • [[3 BSD]] • [[4.0 BSD]] • [[4.1 BSD]] • [[4.2 BSD]] • [[4.3 BSD]] • [[NeXTSTEP]] • [[Darwin]] • [[NetBSD]] • [[OpenBSD]]

Other - [[AMIX]] • [[SunOS]] • [[Solaris]] • [[Ultrix]] • [[A/UX]] • [[Xenix]] • [[AIX]]

Clones - [[DEMOS]] • [[Coherent]]
}}

Unix Eighth Edition

2017-03-28T21:23:31Z

Darkstar: initial version (stub)

Installing Ultrix 4.5 on SIMH

2017-01-22T11:21:03Z

Darkstar: /* Network configuration */ DNS/BIND updates

This WORK-IN-PROGRESS guide will be a simple guide to installing ULTRIX 4.5 for VAX on SimH.

==Requirements==
The following is a list of things required for installation
*A recent version of the [[SIMH]] emulator
**Make sure the binary you're using includes Ethernet support
**I'm using a self-compiled version (git revision 0e8c0aea)
*An ISO image of ULTRIX 4.5 for VAX
**See the "Resources" section for a download link
**It's probably also possible to install it from tape, although I don't know if any installation tapes for ULTRIX 4.5 exist
*Optional stuff (might get added to the guide later):
**Starfish Ultrix Freeware CDs from [http://musall.de/mirrors/ultrix/freeware/ here]

==SimH configuration==
The machine I'm using to run ULTRIX has the following configuration
*DEC MicroVAX 3800
*64mb memory
*DELQA network card (XQ0)
*Two [[RA90]] disk drives (with 1.2gb each) attached to an RQDX3 controller (RQ0 and RQ1)
*CD ROM drive attached to the same RQDX3 controller as unit 2 (RQ2)
*[[TK50]] tape attached as unit 0 on the first TQK50 controller (TQ0)
*DZV11 terminal multiplexer with 16 lines, attached to telnet port 1005 (DZ)
*LPT line printer attached to text file <code>printer_output.txt</code>

Here's my config file (I called it <code>simh.conf</code>)
<pre><nowiki>
;
; SimH 4.0 Configuration file for MicroVAX 3800
;
; Host System : DEC MicroVAX 3800
; Operating System : DEC Ultrix v4.5
; Memory : 64mb
; Network config : XQ: Ethernet, 08:00:2b:04:14:02
; Disks : RQ0: RA90, 1.2gb
; RQ1: RA90, 1.2gb
; CDROMs : RQ2: iso file
; Tape config : TQ0: TK50, 94mb
;

load -r ka655x.bin

; NVRAM
attach NVR nvram.bin

; CPU config
set CPU 64m
set CPU conhalt
set CPU idle=all

; configure console to 7-bit only
set TTO 7b
set TTI 7b

; Disk drives
set RQ0 ra90
attach RQ0 rq0-ra90.dsk
set RQ1 ra90
attach RQ1 rq1-ra90.dsk
set RQ2 CDROM
attach -r RQ2 ultrix-vax-os-v4.5.mode1.ufs.iso
; MD5 sum: 19df0753c27f195e9f1d2f139a3b4629 *ultrix-vax-os-v4.5.mode1.ufs.iso
set RQ3 dis

; Tape
set TQ tk50
;attach tq0 filename-to-tape-file
set TQ1 dis
set TQ2 dis
set TQ3 dis

; serial port, simulated by Telnet to port 1005
set DZ LINES=16
set DZ 8B
attach DZ 1005 NoBuffer

; printer
set LPT enable
attach LPT printer_output.txt

; Disable unused peripherals
set CR dis
set RL dis
set TS dis

; Network interface (08-00-2b is the DEC prefix, the 04-14-02 part is arbitrary)
set XQ MAC=08-00-2b-04-14-02
attach XQ0 eth0

; serial console (launch directly after booting CPU)
set console telnet=1001

; experimental
;set QVSS en

; boot the system
;boot CPU
</nowiki></pre>
Note that I'm using a telnet console (for easier copy/paste on Windows), which means that directly after running this config file (via <code>do simh.conf</code> from Simh) you will need to connect via telnet to localhost:1001 or the boot will abort. If you are on Linux, or just don't want that, remove the <code>set console telnet=1001</code> line.

Also note that you might need to attach XQ0 to a different ethernet device. Use "show ether" in SimH to list all available devices on your system and modify the <code>attach XQ0 eth0</code> line accordingly.

==Running the Emulator==
Either run <code>vax.exe simh.conf</code> from the Windows command line, or just double-click the VAX.EXE executable and type <code>do simh.conf</code>.

On the first launch it might take some time because SimH has to create the disk images (~2.5 gb total). It should look something like this
<pre><nowiki>
MicroVAX 3900 simulator V4.0-0 Beta git commit id: 0e8c0aea
NVR: buffering file in memory
RQ2: unit is read only
Listening on port 1005
WinPcap version 4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008)
Eth: opened OS device \Device\NPF_{A41A1651-DD4D-4735-A4E0-88353165C2EC}
Listening on port 1001
sim>
</nowiki></pre>

Type the following to start the emulation (note: you can also uncomment that line from the end of the config file to have the emulation start right away)
sim> boot cpu
Waiting for console Telnet connection

Now would be a good time to connect your telnet session (I use a batch file for this), otherwise the boot process will timeout.

On your console, you should see something like this:
<pre><nowiki>
Connected to the MicroVAX 3900 simulator CON-TEL device

KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>
</nowiki></pre>

This is the VAX's boot prompt. Normally you just type
>>>boot <device>
where <device> is one of the following
*MUA<num>: TK tape device number <num> (1 to 4)
*DUA<num>: RQ disk device number <num> (1 to 4)

You can use <code>show device</code> to see the installed (and detected) devices you can boot from, and <code>show boot</code> to see which device will be the default if you just type <code>boot</code> (or <code>b</code> for short):
<pre><nowiki>
>>>show device
UQSSP Disk Controller 0 (772150)
-DUA0 (RA90)
-DUA1 (RA90)
-DUA2 (RRD40)

UQSSP Tape Controller 0 (774500)
-MUA0 (TK50)

Ethernet Adapter 0 (774440)
-XQA0 (08-00-2B-04-14-02)
>>>show boot
MUA0
</nowiki></pre>

Since we want to boot from CDROM, which is unit 2, we can use
>>>boot DUA2

Note: You can add flags to boot into single user mode, or to boot in interactive mode (so-called ''conversational boot'', where the system prompts you for a kernel file name to load). For details see the Guide to ULTRIX-32 System Startup and Shutdown, linked to in the ''References'' section. To use it, add the <code>/R5:<flags></code> option to the <code>boot</code> command, where flags is 0 (default multi-user), 1 (conversational multi-user), 2 (single-user) or 3 (conversational single-user). For example
>>>boot/r5:3 dua0

Note: You can also boot from ethernet (<code>boot XQA0</code>) but this requires a DEC-specific boot server in your network (the protocol is called ''MOP'' for ''Maintenance Operations Protocol''), which is beyond the scope of this document. I did get it to work a few years ago though, but it was a bit difficult to set up.

For a list and description of all commands available in the bootloader (hint: there are lots), see the ''KA655 CPU System Maintenance'' guide mentioned in the ''References'' section..

==Bootstrapping ULTRIX==
You will see the following output on the first boot.
<pre>
>>>boot dua2
(BOOT/R5:0 DUA2

2..
-DUA2
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 945424
data = 1290240
bss = 757940
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #2: Wed Oct 18 12:06:55 EDT 1995
real mem = 67043328
avail mem = 61517824
Buffer configuration adjusted to run with small system page table
using 123 buffers containing 1007616 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
WARNING: clock gained 47 days -- CHECK AND RESET THE DATE!

*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice:
</pre>
Now we want to do an ''ADVANCED Installation'', but when we try to, it will take a few seconds until the installation program dumps us to a prompt because it couldn't find a valid device to install from and to:
<pre>
Enter your choice: 2

*** SOFTWARE DISTRIBUTION DEVICE SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of software distribution devices and which installation media you should
load on it:

No valid device is found.
Contact a DIGITAL field service representative.

#
</pre>

The problem seems to be that the hardware SimH emulates is not fully supported by ULTRIX (or is misdetected -- I'm not entirely sure myself). The good thing is that the internet has the correct solution, which is to fix some lines in the installation shell script. The fact that the basic system that is running at this point doesn't have ''vi'', or even ''cat'', makes this a bit harder ;-)

The only option you have is ''ed'', the old UNIX editor. For a quick introduction, see [http://blog.sanctum.geek.nz/actually-using-ed/ here].

To load the file in the editor, use
# '''ed install.1'''
16763

You can see the entire file with
1,$l
but be warned, the output is quite long and it'll take some time to print it all out.

To fix it, use the following commands (the lines in '''bold''' is what you type, everything else is the response from ed)
# '''ed install.1'''
16763
'''173l'''
BTD=`btd`
'''173s/`btd`/ra2/'''
'''173l'''
BTD=ra2
'''193l'''
rz* )
'''193s/rz/ra/'''
'''193l'''
ra* )
'''w'''
16761
'''q'''
#

First, we list line 173, then we change it from <code>BTD=`btd`</code> to <code>BTD=ra2</code>, which happens to be the CDROM device and unit number we're installing from (if you changed that in your config, use the correct name here!)

Then we change line 193 from <code>rz* )</code> to <code>ra* )</code> since we're trying to install on an RA type disk which was apparently not supported in ULTRIX out of the box.

After writing the file with <code>w</code> and quitting ed with <code>q</code>, we're back at the prompt, at which point we can use CTRL+D to retry the installation:

<pre>
# ^D
*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice: 2

*** SYSTEM DISK SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of system disk drives. Select one of the devices below to contain the
root file system:

SYSTEM DISK TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk drive
is on line and write-enabled (if applicable to your disk drive), then
confirm your choice.

Use RA90, ra0, for your system disk? (y/n) []: y

The installation procedure now allocates the root file system on
partition 'a' of the system disk, ra0 RA90.

Making the root file system on ra0 RA90.

The installation procedure is now restoring the root file system to
partition 'a' of the system disk, ra0 RA90.

The installation procedure now checks the root file system on partition 'a'
of the system disk, ra0 RA90.
** /dev/rra0a
** Last Mounted on /mnt
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
226 files, 4547 used, 11004 free (20 frags, 1373 blocks, 1.0% fragmentation)

*** BOOTSTRAP COMMAND SEQUENCE ***

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 8007F799
>>>
</pre>
After this, you will be back at the VAX boot prompt (if you used <code>set CPU CONHALT</code> in your config) or at the SimH emulator prompt (if you used <code>set CPU SIMHALT</code>, which is the default). In the latter case you will have to do <code>boot cpu</code> again to get to the VAX boot prompt.

==First boot==
Now we can boot the installed system from harddisk for the first time.

If you want to, now would be a good time to take a backup copy of your disk files (or just create a btrfs snapshot or something if you have the possibility ;-)

Okay, then let's boot from DUA0
<pre>
>>>boot dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 1153664
data = 281088
bss = 1043548
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #3: Wed Oct 18 11:49:00 EDT 1995
real mem = 67043328
avail mem = 62008320
Buffer configuration adjusted to run with small system page table
using 121 buffers containing 991232 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
</pre>
Here, it will seem to hang for a loooong time. A few minutes. Don't worry, it will eventually continue to boot. I guess it's probing for other devices which are not present.

You ''might'' be able to speed this up a bit by interrupting SimH (press CTRL+E in the SimH console window) and then using <code>set CPU noidle</code> followed by <code>go</code> to resume emulation.

Eventually, you will have to decide on a hostname. Note that if you want to play around with [[DECnet]] at some point, your hostname should be no longer than 6 characters.
<pre>
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)

*** SYSTEM NAME SPECIFICATION ***

Select the name of your system using alphanumeric characters.
The first character must be a letter. For example, tinker.

Enter your system name: yuki

You selected yuki as the name of your system.
Is this correct? (y/n) [y]: y
</pre>

Next up is the time configuration. Since Ultrix 4.5 is not Y2k compliant (AFAIK), I decided to set the clock back a whopping 20 years. Note that the timezone and daylight saving settings are for my location (Germany) and will probably vary for you.

<pre>
*** DATE AND TIME SPECIFICATION ***

The current date and time should be specified using the following
format:

yymmddhhmm

Use two digits for year (yy), month (mm), day (dd), hour (hh), and
minute (mm). Enter the time in 24-hour format. For example, 02:54
p.m. on Feb 2, 1993 would be entered as:

9302021454

Enter the date and time: 9512052336

*** TIME ZONE SELECTION ***

Select the time zone for your area, using the options listed in the
table below. You can also enter the number of hours (-12 to 12) in
time east of Greenwich.

Selection Time Zone
---------------------------------
e Eastern
c Central
m Mountain
p Pacific
g Greenwich
---------------------------------

Enter your choice: 1

Does your area alternate between Daylight Savings and Standard
time? (y/n) [y]: y

Select your geographic area for Daylight Savings Time, using the
options in the table below.

Selection Geographic Area
--------------------------------
u USA
a Australia
e Eastern Europe
c Central Europe
w Western Europe
--------------------------------

Enter your choice [u]: c

The current date and time is Tue Dec 5 23:36:46 EST 1995
</pre>

Next up is the root password. Note that Ultrix will not echo anything here, I added the asterisks just for this guide :)

<pre>
*** SPECIFY THE SUPERUSER PASSWORD ***
The Guide to Installing ULTRIX instructs you on how to enter
the superuser password.
Changing password for root
Enter new password: ******
Verify: ******
</pre>

Next up is the filesystem layout, which is a bit more involved than what you know from more modern systems like MS DOS ;-)

In ULTRIX, partitions are defined for each disk type in a file called <code>/etc/disktab</code>. Note that the partitions overlap, so you shouldn't use them all at the same time. The setup script actually takes care of that for you, but if you later create a new filesystem on the wrong partition you ''WILL'' lose data!

Normally, partition '''c''' is the whole disk, which is useful for add-on disk drives for example. Partitions '''a''' and '''b''' are always available and are traditionally used for the system and the swap-space respectively. The swap partition is also used for crashdumps if no separate crash-dump partition is created. The rest of the disk can be used either as a single partition (which is usually '''g''') or as 3 individual partitions ('''d''' to '''f'''). If the disk is larger than 1 gigabyte, you will get another partition, '''h''', after the g partition, probably because the filesystem cannot cope with partitions >1gig

In our case, we will have the following partitions on the first disk (RA0):
*Partition '''a''' of 32 mb for /root
*Partition '''b''' of 64 mb for swap+crashdump
*Partition '''c''' of 1.2 gig (whole-disk, not used on our setup)
*Partition '''d''' and '''e''' of 200 mb each (not used)
*Partition '''f''' of 400 mb (not used)
*Partition '''g''' of 800 mb (overlaps with d, e and f; will become /usr)
*Partition '''h''' of 256 mb (will become /usr/var)
This way we still have the whole second disk available for later use.

So here it goes:
<pre>
*** FILE SYSTEM DEFAULT OPTION ***

The following table shows the default file system layout on RA90, ra0:

partition bottom top size overlap default
a 0 32767 32768 c root
b 32768 159839 127072 c swap, dump
d 159840 580036 420197 c,g /usr

If you choose the defaults, the var area will be allocated to /usr/var.

Do you want to choose the default file system layout? (y/n): n
</pre>

No, we do not want to use the defaults...

First, we select disk 1, partition '''g''', for the /usr file system:
<pre>
*** /usr FILE SYSTEM ALLOCATION ***

You can allocate the /usr file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

/usr FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for /usr file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the /usr file system:

partition size (Kbytes) overlap
------------------------------------------------
d --- 210098 c,g
e --- 210098 c,g
f --- 420196 c,g
g --- 840393 c,d,e,f
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the /usr file system [d]: g

Making the new file system for /usr on /dev/rra0g RA90
</pre>

Next, we select disk 1, partition '''b''' for swap (only 1 swap partition) and for crashdumps:

<pre>
*** ALLOCATE THE SWAP1 SPACE ***

You can allocate the swap1 space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

SWAP1 SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for swap1 space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the swap1 space:

partition size (Kbytes) overlap
------------------------------------------------
b --- 63536 c
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the swap1 space [b]: b

*** ALLOCATE THE SWAP2 SPACE ***

Do you want to allocate a second swap space? (y/n) [n]: n

*** ALLOCATE THE CRASH DUMP SPACE ***

You can allocate the crash dump space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

CRASH DUMP SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for crash dump space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the crash dump space:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
b --- 63536 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the crash dump space [b]: b
</pre>

Finally we select partiton '''h''' for the /var file system. This might not be large enough later on but then we can always migrate the data away if we need to...

<pre>
*** ALLOCATE THE var FILE SYSTEM ***

You can allocate the var file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

var FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for var file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the var file system:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
g --- 840393 c,d,e,f
------------------------------------------------

Type the letter of the partition on which you want
to allocate the var file system [no default]: h

Making the new file system for var on /dev/rra0h RA90
</pre>

==Installing the distribution files==

Next up we have to decide what ''packages'' we want to install (yes, ULTRIX already had its own package format and corresponding installer called ''setld''. It is very basic, probably most similar to ''pkg_add'' on NetBSD). We simply install everything, since we have enough space :)

<pre>
This distribution media includes subsets for ULTRIX Worksystem
Software (UWS). A UWS license (on a workstation) or a UWS Server
License (on a timesharing machine or server) is required to install
these subsets.

Do you want to install ULTRIX Worksystem Software? y/n []: y

*** SUPPORTED SOFTWARE INSTALLATION ***

*** Select the DECwindows User Interface ***

1) DECwindows for OSF/Motif
2) X11/DECwindows (XUI)

Enter your choice [1]: 2

*** Enter Subset Selections ***

The following subsets are mandatory and will be installed automatically:
* Base System * Kernel Config Files
* TCP/IP Networking Utilities * Network File System Utilities
* Extended (Berkeley) Mailer * X11/DECwindows Servers
* X11/DECwindows User Environment * X11/DECwindows 75dpi Fonts

The subsets listed below are optional:
1) Printer Support Environment 2) RAND Mail Handler
3) Sys. Config. Mgmt. Program (SCAMP) 4) Communications Utilities
5) Unix-to-Unix Copy Facility 6) Maintenance Operations Protocol
7) Accounting Software 8) Kerberos Network Authentication
9) Enhanced Security Features 10) Prestoserve Utilities
11) System Exerciser Package 12) Bisynchronous Communications
13) Doc. Preparation for Ref. Pages 14) Doc. Preparation Extensions
15) Adobe Font Metric Files 16) Software Development Utilities
17) Source Code Control System 18) Internationalization Runtime Env.
19) Internationalization Dev. Env. 20) CDA Base System
21) CDA Software Dev Libraries 22) RPC Runtime Environment
23) RPC Development Environment 24) Pascal Development Package
25) VAX C/ULTRIX 26) Ref. Pages for Sys. Admin. & Users
27) Reference Pages for Programers 28) Programming Examples
29) Ultrix SPDS 30) X11/DECwindows 100dpi Fonts
31) VS35XX X11/DECwindows Fonts 32) Additional DECwindows Applications
33) DECwindows Mail Application 34) Worksystem Development Environment
35) X11/DECwindows System Management T 36) UWS Runtime Reference Pages
37) UWS Development Reference Pages

38) All mandatory and all optional subsets
39) Mandatory subsets only
40) Exit without installing subsets

Enter your choice(s): 38
Working....Wed Dec 6 00:14:12 EST 1995

You are installing the following subsets:
Base System Kernel Config Files
TCP/IP Networking Utilities Network File System Utilities
Extended (Berkeley) Mailer X11/DECwindows Servers
X11/DECwindows User Environment X11/DECwindows 75dpi Fonts
Printer Support Environment RAND Mail Handler
Sys. Config. Mgmt. Program (SCAMP) Communications Utilities
Unix-to-Unix Copy Facility Maintenance Operations Protocol
Accounting Software Kerberos Network Authentication
Enhanced Security Features Prestoserve Utilities
System Exerciser Package Bisynchronous Communications
Doc. Preparation for Ref. Pages Doc. Preparation Extensions
Adobe Font Metric Files Software Development Utilities
Source Code Control System Internationalization Runtime Env.
Internationalization Dev. Env. CDA Base System
CDA Software Dev Libraries RPC Runtime Environment
RPC Development Environment Pascal Development Package
VAX C/ULTRIX Ref. Pages for Sys. Admin. & Users
Reference Pages for Programers Programming Examples
Ultrix SPDS X11/DECwindows 100dpi Fonts
VS35XX X11/DECwindows Fonts Additional DECwindows Applications
DECwindows Mail Application Worksystem Development Environment
X11/DECwindows System Management To UWS Runtime Reference Pages
UWS Development Reference Pages

Is this correct? (y/n): y
</pre>

The installation will take a while (around 15-30 minutes for me), so feel free to let it run in the background for a while now. The installer will periodically print its status so you can see that it's still running...

<pre>
Base System (ULTBASE450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:14:43 EST 1995
Verifying

Kernel Config Files (ULTBIN450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:15:28 EST 1995
Verifying

...
</pre>

At some point you will have to confirm installing the generic kernel and the X11 subsystem:

<pre>
...
UWS Runtime Reference Pages (UWSMAN450)
Copying from /mnt/VAX/BASE (disk)
Verifying

UWS Development Reference Pages (UWSMANPGMR450)
Copying from /mnt/VAX/BASE (disk)
Verifying

The installation software has successfully installed the software
subsets.
Installing Upgrade subsets
The following subsets will be installed:
* X11/DECwindows Servers Upgrade * Generic Kernel
Do you wish to continue? (y/n): y

X11/DECwindows Servers Upgrade (UWSSER451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

Generic Kernel (ULTGENVMUNIX451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

The installation procedure has successfully installed the Upgrade
subsets
</pre>

That's it for the base installation, now we configure our kernel...

==Kernel configuration==
We have to select what features will be in the kernel. For anyone who has ever done a "make menuconfig" on Linux, this is ''slightly'' easier here ;-)
<pre>
*** CONFIGURATION FILE KERNEL OPTION SELECTION ***

Selection Kernel Option
---------------------------------------------------------------
1 Local Area Transport (LAT)
2 Bisynchronous Communication protocol (VAX only)
3 Computer Interconnect (CI) network
4 Diagnostic/Utilities Protocol (DUP)
5 ISO9660 File System Support (CDFS)
6 Ethernet Packet Filter
7 Enhanced Security Features
8 All of the above
9 None of the above
----------------------------------------------------------------

Enter the selection number for each kernel option you want.
For example, 1 3 :
</pre>

In our case, we don't need 2 (it is for 2780/3780 remote terminals), 3 (SimH doesn't emulate any cluster hardware) or 6 (it might cause problems with DECwindows/Motif). Everything else (<code>1 4 5 7</code>) is probably safe. This lets us play around with LAT (maybe connect an emulated Cisco router with LAT routing to it?) and DUP.

<pre>
Enter the selection number for each kernel option you want.
For example, 1 3 : 1 4 5 7

You specified the following kernel options:

Local Area Transport (LAT)
Diagnostic/Utilities Protocol (DUP)
ISO9660 File System Support (CDFS)
Enhanced Security Features

Is this correct? (y/n) [n]: y

*** SYSTEM CONFIGURATION PROCEDURE ***
The installation software found these devices in the floating
address space:

dz0 on uba0 at 0160100
dz1 on uba0 at 0160110
dz2 on uba0 at 0160120
dz3 on uba0 at 0160130

Configuration file complete.

Do you want to edit the configuration file? (y/n) [n]: n

*** PERFORMING SYSTEM CONFIGURATION ***

working ..... Wed Dec 6 02:29:10 EST 1995

*** DEVICE SPECIAL FILE CREATION ***
working ..... Wed Dec 6 02:29:53 EST 1995

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 800985B5
</pre>

Now you might want to take another backup of your disk images, since the ULTRIX installation is now basically complete.

==Adding the unsupported sets==
Now there are some more pieces of software in the CDROM, in a directory called ''unsupported''. We want to install these as well. First, let's boot our system again

<pre>
>>>b dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 747376
data = 125952
bss = 918192
Starting at 0x2c19

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
real mem = 67043328
avail mem = 56455168
using 1638 buffers containing 6712320 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
dz0 at uba0 csr 160100 vec 300, ipl 17
dz1 at uba0 csr 160110 vec 310, ipl 17
dz2 at uba0 csr 160120 vec 320, ipl 17
dz3 at uba0 csr 160130 vec 330, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
Wed Dec 6 11:25:29 MET 1995
Automatic reboot in progress...
/dev/ra0a: 644 files, 6161 used, 9390 free (166 frags, 1153 blocks, 5.0% fragmentation)
/dev/rra0g: umounted cleanly
/dev/rra0h: umounted cleanly
Warning Creating new license database
Warning creating new history file
check quotas: done.
savecore: checking for dump...dump does not exist
local daemons: syslog sendmail.
Removing remnant Opser files
preserving editor files
clearing /tmp
standard daemons: update cron accounting network snmpd printer.
start errlog daemon - elcsd
Wed Dec 6 11:25:48 MET 1995

ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
UWS V4.5 (Rev. 6)

Digital Equipment Corporation
Nashua, New Hampshire

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

#
</pre>

now, we mount the CDROM and use <code>setld</code> to install the unsupported packages. For simplicity's sake, we just (again) install everything.

<pre>
# mount -r /dev/ra2c /mnt
# cd /mnt/VAX/UNSUPPORTED
# ls
DXVUNDEMO450 ULXDOC450 ULXINGRES450 ULXRCS450 ULXUNMAN450
ULXAPL450 ULXEDIT450 ULXLEARN450 ULXSHELLS450 ULXUNMIT450
ULXBASE450 ULXF77450 ULXLISP450 ULXSPMS450 ULXVARIAN450
ULXBIB450 ULXGAMES450 ULXMAN450 ULXTERM450 instctrl
ULXCOURIER450 ULXHYPER450 ULXMOD2450 ULXTOOLS450
ULXCPM450 ULXICON450 ULXNEWS450 ULXUNEXAMP450
ULXDCMT450 ULXINET450 ULXNOTES450 ULXUNFONTS450
# setld -l .

*** Enter Subset Selections ***

The subsets listed below are optional:
1) Base Extension 2) GNU Emacs
3) TCP/IP Networking Util Extension 4) Additional Terminal Drivers
5) Document Preparation Software 6) Games and Diversions
7) Supplementary Documentation 8) Bibliographic Utilities
9) Remote Procedure Call Compiler 10) Aux. Command Line Interpreters
11) USENET News Interface Software 12) Notesfiles Package
13) Revision Control System 14) Misc. User-Contributed Utilities
15) Computer Aided System Tutor 16) Franz Lisp Development Package
17) Modula-2 Development Package 18) Raster Plotter Package
19) APL Development Package 20) CP/M 8in Diskette Utility
21) Hyperchannel Utilities 22) ICON (Language) Development Packag
23) University Ingres QUEL DBMS 24) Software Project Management System
25) Unsupported Fortran Utilities 26) Unsupported On-Line Documentation
27) Unsupported X11 Components 28) Unsupported DECwindows Examples
29) Unsupported MIT Fonts 30) Unsupported X11 Reference Pages
31) Unsupported OSF/Motif Demos

32) All mandatory and all optional subsets
33) Mandatory subsets only
34) Exit without installing subsets

Enter your choice(s): 32
Working....Wed Dec 6 11:29:48 MET 1995
Wed Dec 6 11:30:00 MET 1995

You are installing the following subsets:
Base Extension GNU Emacs
TCP/IP Networking Util Extension Additional Terminal Drivers
Document Preparation Software Games and Diversions
Supplementary Documentation Bibliographic Utilities
Remote Procedure Call Compiler Aux. Command Line Interpreters
USENET News Interface Software Notesfiles Package
Revision Control System Misc. User-Contributed Utilities
Computer Aided System Tutor Franz Lisp Development Package
Modula-2 Development Package Raster Plotter Package
APL Development Package CP/M 8in Diskette Utility
Hyperchannel Utilities ICON (Language) Development Package
University Ingres QUEL DBMS Software Project Management System
Unsupported Fortran Utilities Unsupported On-Line Documentation
Unsupported X11 Components Unsupported DECwindows Examples
Unsupported MIT Fonts Unsupported X11 Reference Pages
Unsupported OSF/Motif Demos

Is this correct? (y/n): y

Base Extension (ULXBASE450)
Copying from . (disk)
Verifying

GNU Emacs (ULXEDIT450)
Copying from . (disk)
Verifying

TCP/IP Networking Util Extension (ULXINET450)
Copying from . (disk)
Verifying
...
</pre>

Note that you could also quickly install only a single package by using for example
# setld -l . ULXINET450

After a few minutes, installation will be completed and we should unmount the CDROM
# cd /
# umount /mnt

==Network configuration==
To configure the network, you have to use a static IPv4 address and put that into the beginning of /etc/rc.local. Note that there is no <code>ifconfig -a</code> in ULTRIX, you have to use <code>netstat -i</code>

<pre>
# netstat -i
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
qe0* 1500 none none 0 0 0 0 0
lo0 1536 loop localhost 1 0 1 0 0
# ifconfig qe0 192.168.1.44 netmask 255.255.255.0 up
# route add default 192.168.1.1 1
add net default: gateway 192.168.1.1
# ping 192.168.1.1
192.168.1.1 is alive
</pre>
Note that it might actually take a while until packets are getting through. I don't know why but in my case it helped to ping ULTRIX from the outside first, e.g. from Windows, and then re-try the ping from the VM. Then it worked. I'm guessing this is some SimH/Windows issue with PCAP or something.

Then put these 2 commands at the start of <code>/etc/rc.local</code> (you'll see where). Note that you can use <code>vi</code> now!
<pre>
# @(#)rc.local 9.4 (ULTRIX) 9/21/95
/bin/hostname yuki
#/etc/ifconfig HDWR `/bin/hostname` broadcast NETNUM.0 netmask 255.0
/etc/ifconfig qe0 192.168.1.44 netmask 255.255.255.0
route add default 192.168.1.1 1
/etc/ifconfig lo0 localhost
#/etc/bscconfig dup0 bsc 1
#/etc/bscconfig dpv0 bsc 1
...
</pre>

Note that DNS lookups normally don't work out of the box. Create a basic <code>/etc/resolv.conf</code> file with the following content (or whatever is correct in your environment)
domain lan.local
nameserver 192.168.1.1

However, if you then try to do an nslookup query, you will get an error message
# nslookup www.google.com
*** Can't find server name for address 192.168.1.1: Not implemented
*** Default servers are not available
The problem is that ULTRIX sends so-called ''inverse queries'' (not to be confused with the well-known ''reverse lookups'', which are actually just regular forward lookups to a specific TLD) to map IP addresses to hostnames. Most DNS servers don't support these inverse queries anymore. Apparently, BIND8 still included an option "fake-iquery" which might be used to support these queries. Versions before BIND8 (4.x) supported IQUERY natively. I have yet to test both variants to see which (if any) of them work.

==Shutting down cleanly==
As you'd expect, you can use <code>shutdown</code> to shut the system down
<pre>
# shutdown -h now
Shutdown at 11:15 (in 0 minutes) [pid 1500]
#
System shutdown time has arrived
syncing disks... done

?06 HLT INST
PC = 80094CDD
>>>
</pre>

==Enabling outside access==
The SimH config above includes a 16-line serial multiplexer. If you connect via TELNET to port 1005, you are given the first free serial line of the emulated DZ device. However, serial login is disabled by default, so it has to be enabled first. That's what the <code>/etc/ttys</code> file is for. Edit the file and change the ''off'' to ''on'' in the lines for tty00 to tty07, as shown below
<pre>
# @(#)ttys 9.1 (ULTRIX) 4/26/94
#
#
#
# name getty type status comments
#
console "/etc/getty std.9600" vt100 on secure # console terminal
tty00 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty01 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty02 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty03 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty04 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty05 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty06 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty07 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
ttyd0 "/etc/getty std.9600" vt100 off shared secure # modem line
</pre>

If you want to be able to login as root on these terminals, you can also add the <code>secure</code> flag as well. Also note that while it seems tempting to increase the line speed to 19200 or even higher, from my experience that will cause massive lags and emulation hangs in SimH, so do that on your own risk.

After editing the file and saving it, you have to reload init:
# kill -HUP 1

Now try logging in to port 1005 via telnet, and you should be greeted with this:
<pre>
Connected to the MicroVAX 3900 simulator DZ device, line 0

ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:
Requires secure terminal
</pre>

Note that SimH will print out the serial line to which you are connected, in this case line 0 which is /dev/tty00.

Also, if your inetd is running (which it should be, if you followed this guide), you will also already be able to login remotely using telnet.
<pre>
ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:
Requires secure terminal
</pre>
To enable root access for all telnet sessions, you will have to edit the /etc/ttys file and change every line that starts with "ttyp" to include the secure flag:
ttyp0 none network
will become
ttyp0 none network secure
and so on...

==Resources==
Some of the resources I used for creating this guide:
*ULTRIX 4.5 installation ISO [http://musall.de/mirrors/ultrix/ultrix_os/vax/]
*ULTRIX-32 startup and shutdown guide [http://bitsavers.trailing-edge.com/pdf/dec/vax/ultrix-32/3.0/AA-ME91A-TE_ULTRIX-32_Guide_to_System_Shutdown_and_Startup.pdf]
*CERN guide to installing ULTRIX [https://web-docs.gsi.de/~kraemer/COLLECTION/ULTRIX/wwwpdp.web.cern.ch/wwwpdp/as/file/doc/ultrix/ultrix.pdf]
*My old guide for installing ULTRIX [https://docs.google.com/document/d/1ULRhzE0R1twarB5hfJm85yqOdTeoFCGgyPr5AxYEIbE]
*DEC KA655 CPU System Maintenance [http://bitsavers.trailing-edge.com/pdf/dec/vax/655/EK-306A-MG-001_655Mnt_Mar89.pdf]
*Some notes and links to more ULTRIX information [https://web-docs.gsi.de/~kraemer/COLLECTION/ULTRIX/docs.html]
*Ultrix Guide to Disk Maintenance [http://www.carelife.com/manuals/Ultrix_Guide_Disk_Maint.PDF]
*Some random notes about ULTRIX 4.0 (some also apply to 4.5) [http://apfelboymchen.net/gnu/UNIX/vax-ultrix.html]

[[Category:SIMH Tutorials]]

Flashterm

2016-01-29T12:00:49Z

Darkstar: update link

flashterm_ is a new & exciting [[ANSI]] terminal emulator, that is written in flash alchemy!
With the setup of a socket server, you can now quickly and easily allow people to telnet into your legacy machines!

You can read about installing it on my blog [http://virtuallyfun.superglobalmegacorp.com/2010/12/28/installing-flashterm-on-wamp/ here]. It really is simple to install.

== resources ==
*Home page http://www.flashterm.com/
*Download http://www.peternitsch.net/flashterm/files/flashterm_full.zip
*Win32 certificate server http://www.vadvbbs.com/products/utilities/downloads/index.php#flashpolicyserver

Update:
flashterm.com doesn't exist as a domain anymore.
The last sign of life was captured by the wayback machine in August 2014, with download links and all:
*https://web.archive.org/web/20140817091145/http://flashterm.com/
{{stub}}
[[Category:Terminal Emulator]]

User:Darkstar

2015-12-10T18:25:22Z

Darkstar: some info about myself

Hi

My name is Michael and I'm a retro-computer enthusiast from Germany ;-)

I have a huge collection of old computers and workstations (SGI, Sun, DEC, HP, Apple, Commodore, IBM, ...) and I try to keep them in a working condition as much as possible (replacing/fixing broken hardware, swapping batteries, etc.)

Currently I don't have as much time as I'd like for tinkering around with these old boxes so I've shifted my interest more to collecting old software and operating systems and trying out stuff in virtual machines and emulators like [[SIMH]].

I have a small(ish) but nice collection of original install media (mainly for SGI but also some IBM and DEC stuff) and dozens of gigabytes of old operating systems that I collected from every part of the internet.

Also, in my spare time, I like reverse-engineering and converting file formats, mainly for games.

I'm (semi-)active in [http://www.archiveteam.org ArchiveTeam] and it's spin-off, the [http://fileformats.archiveteam.org file-formats wiki], I founded the (now semi-defunct) [http://rewiki.awiki.org/wiki/Main_Page ReWiki] and I'm an active member of the [http://www.betaarchive.com BetaArchive Forums].

Also, I try to keep up with multiple open-source projects that have to do with retro-computing, retro-gaming and/or emulation, like ScummVM, Xoreos, Xenia, FUZIX, SimH, hercules, PCjs, PCem, DosBox and MAME.

Currently I'm trying to design a large, emulation-based retro-style network using SimH, DosBox, VirtualBox/VMware and DynaMIPS with multiple network segments, routing over different (simulated) network topologies and dozens of hosts. Linux with containers and virtual ethernet devices/bridges should make this possible...

I'm really trying to get into that whole "Mainframe" thing as well, but as someone who grew up with DOS, Windows and Linux, all the terminology and stuff turns out to be a very steep learning curve.

Netbooting a VAXstation

2015-12-10T18:06:04Z

Darkstar: found this old doc on my harddisk and slightly edited it since it might be useful for some people...

This page describes my struggles with trying to netboot a DEC VAXstation 4000/60 for installing NetBSD. I originally wrote this document in 2005, and it did work just fine back then. However, it might be difficult to get the required software nowadays, or changes in the Linux kernel could have an impact on the whole process. This is thus provided AS-IS.

Note that this might also work with [[SIMH]] but it is not tested.

==Requirements==
* Network connectivity for your VAX (normally this means you either need a transceiver for the AUI port or a hub/switch with a 10Base2 connector)
* A Linux machine for the boot-server parts (I used a physical machine with SuSE 9.3)
** This Linux server needs a network card in promiscuous mode (for a VM you might need to do a few config changes, e.g. on ESX)
** It also needs a MOP server, which is called ''mopd'' for Linux (it is a DEC specific boot protocol)
** For netbooting NetBSD (as was the original goal) you will also need a DHCP/BOOTP server, which is probably not required if you try to netboot an original DEC operating system like VMS or ULTRIX
** Also you need an NFS server (for the install packages and root filesystem) and the kernel from the NetBSD ftp server

Note that ''mopd'' does not work across routers so you need to have a flat network.

==Linux server==
First, your Linux box needs a network card in promiscuous mode. Use
lavie:/# ifconfig eth0 allmulti
to enable it. It should then look something like this
lavie:/# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:02:B3:98:9F:A1
inet addr:192.168.0.42 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: 2002:549c:e025:6:202:b3ff:fe98:9fa1/64 Scope:Global
inet6 addr: fec0::6:202:b3ff:fe98:9fa1/64 Scope:Site
inet6 addr: fe80::202:b3ff:fe98:9fa1/64 Scope:Link
UP BROADCAST RUNNING '''ALLMULTI''' MULTICAST MTU:1500 Metric:1
RX packets:870128 errors:0 dropped:0 overruns:0 frame:0
TX packets:189222 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1184340903 (1129.4 Mb) TX bytes:54007715 (51.5 Mb)
Base address:0x9000 Memory:fa040000-fa060000

===mopd===
Then you need the ''mopd'' MOP server. You can find it via google, for example [https://github.com/qu1j0t3/mopd here] is a GitHub repo which claims to be the latest release (2.5.3/2.5.4). If you use NetBSD as server, it supposedly ships with ''mopd'' on all supported platforms as noted [https://www.netbsd.org/docs/network/netboot/mop.html here]. Back in 2005 I found a prebuilt package on rpmfind.net, but it no longer exists.

You can run ''mopd'' as follows:
lavie:/ # mopd -d eth0
mopd: not running as daemon, -d given.
Just keep it running in the foreground. Of course substitute eth0 with your network interface where the VAXstation can be reached. Your syslog should now contain something like this:
Dec 25 02:32:11 lavie mopd[7854]: mopd 2.5.3 started.
Dec 25 02:32:11 lavie mopd[7854]: Initialized eth0
''mopd'' looks into <code>/tftpboot/mop/</code> by default, so you should make sure that this directory exists. We will populate it later.

===DHCP/BOOTP===
The third puzzle piece is the DHCP/BOOTP server where the NetBSD bootloader gets its configuration from. You should make sure to use a DHCP/BOOTP server which implements the BOOTP/TFTP option 17 (root path) correctly, in my case the CMU BOOTP (version bootp-DD2-4.3) did not do this correctly which made me use isc-dhcpd 3.0.2, which worked just fine. Remember this was 2005 so if you try a more recent version of either, your results may be totally different.

To configure it, create an /etc/dhcpd.conf with the following content:
subnet 192.168.0.0 netmask 255.255.255.0 {
}

host vs4k60 {
hardware ethernet 08:00:2b:xx:yy:zz;
fixed-address 192.168.0.67;
option domain-name-servers 192.168.0.1;
option domain-name "mydomain.com";
option root-path "/export/vax/root";
filename "netbsd";
}

This first tells DHCPD which subnet it's working on, and then it contains an entry which maps the VAXstation to a fixed IP address from that subnet. Important here are 2 things: First, of course replace the <code>xx:yy:zz</code> part with the MAC address of your VAXstation (which you can find out via <code>SHOW ETHER</code> from the PROM). Second, the root-path option specifies where the root filesystem will be exported. NetBSD will try to mount this when it boots (NetBSD has no initrd concept on VAX, and with 32mb RAM or so, it would be difficult to pull off anyway ;-)

The filename (in this case "netbsd") is unimportant.

===NFS server===
Create the directory <code>/export/vax/root</code> and export it via NFS to the IP address (or hostname) of your VAX
lavie:/# cat /etc/exports
/export vs4k60(rw,async)
If you use a hostname, like me, you have to create the corresponding entry in the <code>/etc/hosts</code> file of course.

==NetBSD installation files==

This guide was written for NetBSD 3.0 but it should (in theory) work the same for newer releases as well. First you will need to get this file: http://ftp.netbsd.org/pub/NetBSD-archive/NetBSD-1.5/vax/installation/netboot/boot.mop
Yes, it is from NetBSD 1.5, and yes, we will be installing a newer version. However, all newer versions don't include the ''boot.mop'' file anymore, just a file called ''boot'', which is not the same and which I couldn't get to work...

Copy this file into the following directory under exactly this name (case-sensitive):
/tftpboot/mop/MOPBOOT.SYS

Then, create a symbolic link to this file and name it like <code>aabbccddeeff.SYS</code>, where <code>aa:bb:cc:dd:ee:ff</code> is the MAC address of your VAXstation, with all letters lower-case except the .SYS at the end, which must be upper case. On my system it looks like this:
lavie:/# ls /tftpboot/mop/ -ls
total 72
0 drwxr-xr-x 2 root root 176 Dec 25 00:01 .
0 drwxr-xr-x 3 root root 136 Dec 25 01:28 ..
0 lrwxrwxrwx 1 root root 11 Dec 24 20:04 08002b30cc49.SYS -> MOPBOOT.SYS
72 -rw-r--r-- 1 root root 71168 Dec 25 00:01 MOPBOOT.SYS

Next you need the NetBSD install kernel image, which (for NetBSD 7.0) is available [http://ftp.netbsd.org/pub/NetBSD/NetBSD-7.0/vax/installation/netboot/install.ram.gz here]. It is usually called ''install.ram.gz''. Uncompress it and place it under
/export/vax/root/netbsd.vax

It should look something like this:
lavie:/# ls /export/vax/root/ -ls
total 7170
0 drwxrwxrwx 2 root root 184 Dec 25 02:43 .
0 drwxrwxrwx 3 root root 72 Dec 25 00:34 ..
2478 -rw-r--r-- 1 root root 2534976 Dec 25 01:42 netbsd.vax

The bootloader has hardcoded filenames that it tries to boot, and <code>netbsd.vax</code> is just the first one it tries.

Note: the bootloader will try other filenames if <code>netbsd.vax</code> is not found, among them for example <code>netbsd</code>, <code>netbsd.bak</code> and <code>netbsd.gz</code>. The last one seems handy to reduce boot time (the bootloader uncompresses the gz file on the fly), however on most VAXen it is probably faster to just load the uncompressed kernel from the server than uncompressing it on the VAX itself...

==Netbooting the VAXstation==
After making sure that mopd, dhcpd and nfsserver are running, boot your VAX from the PROM:
<pre>
>>> b esa0

-ESA0
>> NetBSD/vax boot [Nov 17 2000 07:23:42] > Press any key to abort autoboot 0
Trying BOOTP
Using IP address: 192.168.0.67
myip: (192.168.0.67)
root addr=192.168.0.42 path=/export/vax/root
2534184+69564]=0x27bd9c
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005
The NetBSD Foundation, Inc. All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.

NetBSD 3.0 (INSTALL) #0: Mon Dec 19 04:33:36 UTC 2005
builds@b4.netbsd.org:/home/builds/ab/netbsd-3-0-RELEASE/vax/200512182024Z-obj
/home/builds/ab/netbsd-3-0-RELEASE/src/sys/arch/vax/compile/INSTALL

VAXstation 4000/60
cpu0: KA46
cpu: turning on floating point chip
total memory = 32372 KB
avail memory = 28444 KB
mainbus0 (root)
vsbus0 at mainbus0
vsbus0: 32K entry DMA SGMAP at PA 0x3c0000 (VA 0x803c0000)
vsbus0: interrupt mask 0
le0 at vsbus0 csr 0x200e0000 vec 770 ipl 15 maskbit 1 buf 0x0-0xffff
le0: address 08:00:2b:30:cc:49
le0: 32 receive buffers, 8 transmit buffers
dz0 at vsbus0 csr 0x200a0000 vec 124 ipl 15 maskbit 4
dz0: 4 lines
lkkbd0 at dz0
wskbd0 at lkkbd0 (mux ignored)
asc0 at vsbus0 csr 0x200c0080 vec 774 ipl 15 maskbit 0
asc0: NCR53C94, 25MHz, SCSI ID 6
scsibus0 at asc0: 8 targets, 8 luns per target
md0: internal 1536 KB image area
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 2 lun 0: disk fixed
sd0: 4153 MB, 3421 cyl, 18 head, 138 sec, 512 bytes/sect x 8506782 sectors
sd0: sync (200.00ns offset 15), 8-bit (5.000MB/s) transfers, tagged queueing
sd1 at scsibus0 target 3 lun 0: disk fixed
sd1: 406 MB, 1476 cyl, 9 head, 62 sec, 512 bytes/sect x 832527 sectors
sd1: sync (200.00ns offset 15), 8-bit (5.000MB/s) transfers
boot device: le0
root on md0a dumps on md0b
root file system type: ffs
Clock has lost 13136 day(s) - CHECK AND RESET THE DATE.
</pre>
Congratulations on netbooting a VAX :)

==Troubleshooting==
On your mopd-console, you should see a lot of stuff flashing by soon after you typed <code>b esa0</code>. It should look like this:
<pre>
lavie:/# mopd -d eth0
mopd: not running as daemon, -d given.
MOP RC 802.3 8:0:2b:30:cc:49 > ab:0:0:2:0:0 len 45 code 07 SID
MOP RC 802.3 8:0:2b:30:cc:49 > ab:0:0:2:0:0 len 45 code 07 SID
MOP RC 8:0:2b:30:cc:49 > ab:0:0:2:0:0 len 37 code 07 SID
MOP DL 802.3 8:0:2b:30:cc:49 > ab:0:0:1:0:0 len 47 code 08 RPR
MOP DL 802.3 0:2:b3:98:9f:a1 > 8:0:2b:30:cc:49 len 9 code 03 ASV
MOP DL 802.3 8:0:2b:30:cc:49 > ab:0:0:1:0:0 len 47 code 08 RPR
MOP DL 802.3 0:2:b3:98:9f:a1 > 8:0:2b:30:cc:49 len 9 code 03 ASV
MOP DL 802.3 8:0:2b:30:cc:49 > 0:2:b3:98:9f:a1 len 47 code 08 RPR
Native Image (VAX)
Header Block Count: 1
Image Size: 00011400
Load Address: 00000000
Transfer Address: 00000000
MOP DL 802.3 0:2:b3:98:9f:a1 > 8:0:2b:30:cc:49 len 1498 code 02 MLD
MOP DL 802.3 8:0:2b:30:cc:49 > 0:2:b3:98:9f:a1 len 47 code 08 RPR
Native Image (VAX)
Header Block Count: 1
Image Size: 00011400
Load Address: 00000000
Transfer Address: 00000000
MOP DL 802.3 0:2:b3:98:9f:a1 > 8:0:2b:30:cc:49 len 1498 code 02 MLD
MOP DL 802.3 8:0:2b:30:cc:49 > 0:2:b3:98:9f:a1 len 11 code 0a RML
MOP DL 802.3 0:2:b3:98:9f:a1 > 8:0:2b:30:cc:49 len 1498 code 02 MLD
MOP DL 802.3 8:0:2b:30:cc:49 > 0:2:b3:98:9f:a1 len 11 code 0a RML
MOP DL 802.3 8:0:2b:30:cc:49 > 0:2:b3:98:9f:a1 len 11 code 0a RML
MOP DL 802.3 0:2:b3:98:9f:a1 > 8:0:2b:30:cc:49 len 1498 code 02 MLD
..................
</pre>

the syslog should look something like this:
Dec 25 03:17:24 lavie mopd[7961]: mopd 2.5.3 started.
Dec 25 03:17:24 lavie mopd[7961]: Initialized eth0
Dec 25 03:17:30 lavie mopd[7961]: 8:0:2b:30:cc:49 (2) Do you have 08002b30cc49? (Yes)
Dec 25 03:17:30 lavie mopd[7961]: 8:0:2b:30:cc:49 (2) Do you have 08002b30cc49? (Yes)
Dec 25 03:17:30 lavie mopd[7961]: 8:0:2b:30:cc:49 Send me 08002b30cc49
Dec 25 03:17:30 lavie mopd[7961]: 8:0:2b:30:cc:49 Send me 08002b30cc49
Dec 25 03:17:30 lavie mopd[7961]: hostname: [ipc] len: 3
Dec 25 03:17:30 lavie mopd[7961]: 8:0:2b:30:cc:49 Load completed

If you want to, you can manually specify which file to boot by typing <code>b/100 esa0</code> at the VAX console:
<pre>
>>> b/100 esa0

Bootfile: mopboot

-ESA0
>> NetBSD/vax boot [Nov 17 2000 07:23:42] > Press any key to abort autoboot 0
...
</pre>

You should also have the following entries from dhcpd in your syslog:
Dec 25 03:17:35 lavie dhcpd: DHCPDISCOVER from 08:00:2b:30:cc:49 via eth0
Dec 25 03:17:35 lavie dhcpd: DHCPOFFER on 192.168.0.67 to 08:00:2b:30:cc:49 via eth0
Dec 25 03:17:35 lavie dhcpd: DHCPREQUEST for 192.168.0.67 (192.168.0.42) from 08:00:2b:30:cc:49 via eth0
Dec 25 03:17:35 lavie dhcpd: DHCPACK on 192.168.0.67 to 08:00:2b:30:cc:49 via eth0
You should see all these 4 DHCP packets (DHCPDISCOVER, DHCPOFFER, DHCPREQUEST, DHCPACK), otherwise check your dhcpd configuration

The NFS server also prints one line in the syslog:
Dec 25 03:17:36 lavie rpc.mountd: authenticated mount request from vs4k60:1023 for /export/vax/root (/export)
If this says something like "permission denied", you probably forgot to add your VAX to /etc/hosts.

[[Category:Tutorials]]

Installing Ultrix 4.5 on SIMH

2015-12-06T16:28:32Z

Darkstar: /* Network configuration */

This WORK-IN-PROGRESS guide will be a simple guide to installing ULTRIX 4.5 for VAX on SimH.

==Requirements==
The following is a list of things required for installation
*A recent version of the [[SIMH]] emulator
**Make sure the binary you're using includes Ethernet support
**I'm using a self-compiled version (git revision 0e8c0aea)
*An ISO image of ULTRIX 4.5 for VAX
**See the "Resources" section for a download link
**It's probably also possible to install it from tape, although I don't know if any installation tapes for ULTRIX 4.5 exist
*Optional stuff (might get added to the guide later):
**Starfish Ultrix Freeware CDs from [http://musall.de/mirrors/ultrix/freeware/ here]

==SimH configuration==
The machine I'm using to run ULTRIX has the following configuration
*DEC MicroVAX 3800
*64mb memory
*DELQA network card (XQ0)
*Two [[RA90]] disk drives (with 1.2gb each) attached to an RQDX3 controller (RQ0 and RQ1)
*CD ROM drive attached to the same RQDX3 controller as unit 2 (RQ2)
*[[TK50]] tape attached as unit 0 on the first TQK50 controller (TQ0)
*DZV11 terminal multiplexer with 16 lines, attached to telnet port 1005 (DZ)
*LPT line printer attached to text file <code>printer_output.txt</code>

Here's my config file (I called it <code>simh.conf</code>)
<pre><nowiki>
;
; SimH 4.0 Configuration file for MicroVAX 3800
;
; Host System : DEC MicroVAX 3800
; Operating System : DEC Ultrix v4.5
; Memory : 64mb
; Network config : XQ: Ethernet, 08:00:2b:04:14:02
; Disks : RQ0: RA90, 1.2gb
; RQ1: RA90, 1.2gb
; CDROMs : RQ2: iso file
; Tape config : TQ0: TK50, 94mb
;

load -r ka655x.bin

; NVRAM
attach NVR nvram.bin

; CPU config
set CPU 64m
set CPU conhalt
set CPU idle=all

; configure console to 7-bit only
set TTO 7b
set TTI 7b

; Disk drives
set RQ0 ra90
attach RQ0 rq0-ra90.dsk
set RQ1 ra90
attach RQ1 rq1-ra90.dsk
set RQ2 CDROM
attach -r RQ2 ultrix-vax-os-v4.5.mode1.ufs.iso
; MD5 sum: 19df0753c27f195e9f1d2f139a3b4629 *ultrix-vax-os-v4.5.mode1.ufs.iso
set RQ3 dis

; Tape
set TQ tk50
;attach tq0 filename-to-tape-file
set TQ1 dis
set TQ2 dis
set TQ3 dis

; serial port, simulated by Telnet to port 1005
set DZ LINES=16
set DZ 8B
attach DZ 1005 NoBuffer

; printer
set LPT enable
attach LPT printer_output.txt

; Disable unused peripherals
set CR dis
set RL dis
set TS dis

; Network interface (08-00-2b is the DEC prefix, the 04-14-02 part is arbitrary)
set XQ MAC=08-00-2b-04-14-02
attach XQ0 eth0

; serial console (launch directly after booting CPU)
set console telnet=1001

; experimental
;set QVSS en

; boot the system
;boot CPU
</nowiki></pre>
Note that I'm using a telnet console (for easier copy/paste on Windows), which means that directly after running this config file (via <code>do simh.conf</code> from Simh) you will need to connect via telnet to localhost:1001 or the boot will abort. If you are on Linux, or just don't want that, remove the <code>set console telnet=1001</code> line.

Also note that you might need to attach XQ0 to a different ethernet device. Use "show ether" in SimH to list all available devices on your system and modify the <code>attach XQ0 eth0</code> line accordingly.

==Running the Emulator==
Either run <code>vax.exe simh.conf</code> from the Windows command line, or just double-click the VAX.EXE executable and type <code>do simh.conf</code>.

On the first launch it might take some time because SimH has to create the disk images (~2.5 gb total). It should look something like this
<pre><nowiki>
MicroVAX 3900 simulator V4.0-0 Beta git commit id: 0e8c0aea
NVR: buffering file in memory
RQ2: unit is read only
Listening on port 1005
WinPcap version 4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008)
Eth: opened OS device \Device\NPF_{A41A1651-DD4D-4735-A4E0-88353165C2EC}
Listening on port 1001
sim>
</nowiki></pre>

Type the following to start the emulation (note: you can also uncomment that line from the end of the config file to have the emulation start right away)
sim> boot cpu
Waiting for console Telnet connection

Now would be a good time to connect your telnet session (I use a batch file for this), otherwise the boot process will timeout.

On your console, you should see something like this:
<pre><nowiki>
Connected to the MicroVAX 3900 simulator CON-TEL device

KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>
</nowiki></pre>

This is the VAX's boot prompt. Normally you just type
>>>boot <device>
where <device> is one of the following
*MUA<num>: TK tape device number <num> (1 to 4)
*DUA<num>: RQ disk device number <num> (1 to 4)

You can use <code>show device</code> to see the installed (and detected) devices you can boot from, and <code>show boot</code> to see which device will be the default if you just type <code>boot</code> (or <code>b</code> for short):
<pre><nowiki>
>>>show device
UQSSP Disk Controller 0 (772150)
-DUA0 (RA90)
-DUA1 (RA90)
-DUA2 (RRD40)

UQSSP Tape Controller 0 (774500)
-MUA0 (TK50)

Ethernet Adapter 0 (774440)
-XQA0 (08-00-2B-04-14-02)
>>>show boot
MUA0
</nowiki></pre>

Since we want to boot from CDROM, which is unit 2, we can use
>>>boot DUA2

Note: You can add flags to boot into single user mode, or to boot in interactive mode (so-called ''conversational boot'', where the system prompts you for a kernel file name to load). For details see the Guide to ULTRIX-32 System Startup and Shutdown, linked to in the ''References'' section. To use it, add the <code>/R5:<flags></code> option to the <code>boot</code> command, where flags is 0 (default multi-user), 1 (conversational multi-user), 2 (single-user) or 3 (conversational single-user). For example
>>>boot/r5:3 dua0

Note: You can also boot from ethernet (<code>boot XQA0</code>) but this requires a DEC-specific boot server in your network (the protocol is called ''MOP'' for ''Maintenance Operations Protocol''), which is beyond the scope of this document. I did get it to work a few years ago though, but it was a bit difficult to set up.

For a list and description of all commands available in the bootloader (hint: there are lots), see the ''KA655 CPU System Maintenance'' guide mentioned in the ''References'' section..

==Bootstrapping ULTRIX==
You will see the following output on the first boot.
<pre>
>>>boot dua2
(BOOT/R5:0 DUA2

2..
-DUA2
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 945424
data = 1290240
bss = 757940
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #2: Wed Oct 18 12:06:55 EDT 1995
real mem = 67043328
avail mem = 61517824
Buffer configuration adjusted to run with small system page table
using 123 buffers containing 1007616 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
WARNING: clock gained 47 days -- CHECK AND RESET THE DATE!

*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice:
</pre>
Now we want to do an ''ADVANCED Installation'', but when we try to, it will take a few seconds until the installation program dumps us to a prompt because it couldn't find a valid device to install from and to:
<pre>
Enter your choice: 2

*** SOFTWARE DISTRIBUTION DEVICE SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of software distribution devices and which installation media you should
load on it:

No valid device is found.
Contact a DIGITAL field service representative.

#
</pre>

The problem seems to be that the hardware SimH emulates is not fully supported by ULTRIX (or is misdetected -- I'm not entirely sure myself). The good thing is that the internet has the correct solution, which is to fix some lines in the installation shell script. The fact that the basic system that is running at this point doesn't have ''vi'', or even ''cat'', makes this a bit harder ;-)

The only option you have is ''ed'', the old UNIX editor. For a quick introduction, see [http://blog.sanctum.geek.nz/actually-using-ed/ here].

To load the file in the editor, use
# '''ed install.1'''
16763

You can see the entire file with
1,$l
but be warned, the output is quite long and it'll take some time to print it all out.

To fix it, use the following commands (the lines in '''bold''' is what you type, everything else is the response from ed)
# '''ed install.1'''
16763
'''173l'''
BTD=`btd`
'''173s/`btd`/ra2/'''
'''173l'''
BTD=ra2
'''193l'''
rz* )
'''193s/rz/ra/'''
'''193l'''
ra* )
'''w'''
16761
'''q'''
#

First, we list line 173, then we change it from <code>BTD=`btd`</code> to <code>BTD=ra2</code>, which happens to be the CDROM device and unit number we're installing from (if you changed that in your config, use the correct name here!)

Then we change line 193 from <code>rz* )</code> to <code>ra* )</code> since we're trying to install on an RA type disk which was apparently not supported in ULTRIX out of the box.

After writing the file with <code>w</code> and quitting ed with <code>q</code>, we're back at the prompt, at which point we can use CTRL+D to retry the installation:

<pre>
# ^D
*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice: 2

*** SYSTEM DISK SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of system disk drives. Select one of the devices below to contain the
root file system:

SYSTEM DISK TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk drive
is on line and write-enabled (if applicable to your disk drive), then
confirm your choice.

Use RA90, ra0, for your system disk? (y/n) []: y

The installation procedure now allocates the root file system on
partition 'a' of the system disk, ra0 RA90.

Making the root file system on ra0 RA90.

The installation procedure is now restoring the root file system to
partition 'a' of the system disk, ra0 RA90.

The installation procedure now checks the root file system on partition 'a'
of the system disk, ra0 RA90.
** /dev/rra0a
** Last Mounted on /mnt
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
226 files, 4547 used, 11004 free (20 frags, 1373 blocks, 1.0% fragmentation)

*** BOOTSTRAP COMMAND SEQUENCE ***

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 8007F799
>>>
</pre>
After this, you will be back at the VAX boot prompt (if you used <code>set CPU CONHALT</code> in your config) or at the SimH emulator prompt (if you used <code>set CPU SIMHALT</code>, which is the default). In the latter case you will have to do <code>boot cpu</code> again to get to the VAX boot prompt.

==First boot==
Now we can boot the installed system from harddisk for the first time.

If you want to, now would be a good time to take a backup copy of your disk files (or just create a btrfs snapshot or something if you have the possibility ;-)

Okay, then let's boot from DUA0
<pre>
>>>boot dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 1153664
data = 281088
bss = 1043548
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #3: Wed Oct 18 11:49:00 EDT 1995
real mem = 67043328
avail mem = 62008320
Buffer configuration adjusted to run with small system page table
using 121 buffers containing 991232 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
</pre>
Here, it will seem to hang for a loooong time. A few minutes. Don't worry, it will eventually continue to boot. I guess it's probing for other devices which are not present.

You ''might'' be able to speed this up a bit by interrupting SimH (press CTRL+E in the SimH console window) and then using <code>set CPU noidle</code> followed by <code>go</code> to resume emulation.

Eventually, you will have to decide on a hostname. Note that if you want to play around with [[DECnet]] at some point, your hostname should be no longer than 6 characters.
<pre>
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)

*** SYSTEM NAME SPECIFICATION ***

Select the name of your system using alphanumeric characters.
The first character must be a letter. For example, tinker.

Enter your system name: yuki

You selected yuki as the name of your system.
Is this correct? (y/n) [y]: y
</pre>

Next up is the time configuration. Since Ultrix 4.5 is not Y2k compliant (AFAIK), I decided to set the clock back a whopping 20 years. Note that the timezone and daylight saving settings are for my location (Germany) and will probably vary for you.

<pre>
*** DATE AND TIME SPECIFICATION ***

The current date and time should be specified using the following
format:

yymmddhhmm

Use two digits for year (yy), month (mm), day (dd), hour (hh), and
minute (mm). Enter the time in 24-hour format. For example, 02:54
p.m. on Feb 2, 1993 would be entered as:

9302021454

Enter the date and time: 9512052336

*** TIME ZONE SELECTION ***

Select the time zone for your area, using the options listed in the
table below. You can also enter the number of hours (-12 to 12) in
time east of Greenwich.

Selection Time Zone
---------------------------------
e Eastern
c Central
m Mountain
p Pacific
g Greenwich
---------------------------------

Enter your choice: 1

Does your area alternate between Daylight Savings and Standard
time? (y/n) [y]: y

Select your geographic area for Daylight Savings Time, using the
options in the table below.

Selection Geographic Area
--------------------------------
u USA
a Australia
e Eastern Europe
c Central Europe
w Western Europe
--------------------------------

Enter your choice [u]: c

The current date and time is Tue Dec 5 23:36:46 EST 1995
</pre>

Next up is the root password. Note that Ultrix will not echo anything here, I added the asterisks just for this guide :)

<pre>
*** SPECIFY THE SUPERUSER PASSWORD ***
The Guide to Installing ULTRIX instructs you on how to enter
the superuser password.
Changing password for root
Enter new password: ******
Verify: ******
</pre>

Next up is the filesystem layout, which is a bit more involved than what you know from more modern systems like MS DOS ;-)

In ULTRIX, partitions are defined for each disk type in a file called <code>/etc/disktab</code>. Note that the partitions overlap, so you shouldn't use them all at the same time. The setup script actually takes care of that for you, but if you later create a new filesystem on the wrong partition you ''WILL'' lose data!

Normally, partition '''c''' is the whole disk, which is useful for add-on disk drives for example. Partitions '''a''' and '''b''' are always available and are traditionally used for the system and the swap-space respectively. The swap partition is also used for crashdumps if no separate crash-dump partition is created. The rest of the disk can be used either as a single partition (which is usually '''g''') or as 3 individual partitions ('''d''' to '''f'''). If the disk is larger than 1 gigabyte, you will get another partition, '''h''', after the g partition, probably because the filesystem cannot cope with partitions >1gig

In our case, we will have the following partitions on the first disk (RA0):
*Partition '''a''' of 32 mb for /root
*Partition '''b''' of 64 mb for swap+crashdump
*Partition '''c''' of 1.2 gig (whole-disk, not used on our setup)
*Partition '''d''' and '''e''' of 200 mb each (not used)
*Partition '''f''' of 400 mb (not used)
*Partition '''g''' of 800 mb (overlaps with d, e and f; will become /usr)
*Partition '''h''' of 256 mb (will become /usr/var)
This way we still have the whole second disk available for later use.

So here it goes:
<pre>
*** FILE SYSTEM DEFAULT OPTION ***

The following table shows the default file system layout on RA90, ra0:

partition bottom top size overlap default
a 0 32767 32768 c root
b 32768 159839 127072 c swap, dump
d 159840 580036 420197 c,g /usr

If you choose the defaults, the var area will be allocated to /usr/var.

Do you want to choose the default file system layout? (y/n): n
</pre>

No, we do not want to use the defaults...

First, we select disk 1, partition '''g''', for the /usr file system:
<pre>
*** /usr FILE SYSTEM ALLOCATION ***

You can allocate the /usr file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

/usr FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for /usr file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the /usr file system:

partition size (Kbytes) overlap
------------------------------------------------
d --- 210098 c,g
e --- 210098 c,g
f --- 420196 c,g
g --- 840393 c,d,e,f
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the /usr file system [d]: g

Making the new file system for /usr on /dev/rra0g RA90
</pre>

Next, we select disk 1, partition '''b''' for swap (only 1 swap partition) and for crashdumps:

<pre>
*** ALLOCATE THE SWAP1 SPACE ***

You can allocate the swap1 space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

SWAP1 SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for swap1 space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the swap1 space:

partition size (Kbytes) overlap
------------------------------------------------
b --- 63536 c
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the swap1 space [b]: b

*** ALLOCATE THE SWAP2 SPACE ***

Do you want to allocate a second swap space? (y/n) [n]: n

*** ALLOCATE THE CRASH DUMP SPACE ***

You can allocate the crash dump space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

CRASH DUMP SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for crash dump space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the crash dump space:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
b --- 63536 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the crash dump space [b]: b
</pre>

Finally we select partiton '''h''' for the /var file system. This might not be large enough later on but then we can always migrate the data away if we need to...

<pre>
*** ALLOCATE THE var FILE SYSTEM ***

You can allocate the var file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

var FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for var file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the var file system:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
g --- 840393 c,d,e,f
------------------------------------------------

Type the letter of the partition on which you want
to allocate the var file system [no default]: h

Making the new file system for var on /dev/rra0h RA90
</pre>

==Installing the distribution files==

Next up we have to decide what ''packages'' we want to install (yes, ULTRIX already had its own package format and corresponding installer called ''setld''. It is very basic, probably most similar to ''pkg_add'' on NetBSD). We simply install everything, since we have enough space :)

<pre>
This distribution media includes subsets for ULTRIX Worksystem
Software (UWS). A UWS license (on a workstation) or a UWS Server
License (on a timesharing machine or server) is required to install
these subsets.

Do you want to install ULTRIX Worksystem Software? y/n []: y

*** SUPPORTED SOFTWARE INSTALLATION ***

*** Select the DECwindows User Interface ***

1) DECwindows for OSF/Motif
2) X11/DECwindows (XUI)

Enter your choice [1]: 2

*** Enter Subset Selections ***

The following subsets are mandatory and will be installed automatically:
* Base System * Kernel Config Files
* TCP/IP Networking Utilities * Network File System Utilities
* Extended (Berkeley) Mailer * X11/DECwindows Servers
* X11/DECwindows User Environment * X11/DECwindows 75dpi Fonts

The subsets listed below are optional:
1) Printer Support Environment 2) RAND Mail Handler
3) Sys. Config. Mgmt. Program (SCAMP) 4) Communications Utilities
5) Unix-to-Unix Copy Facility 6) Maintenance Operations Protocol
7) Accounting Software 8) Kerberos Network Authentication
9) Enhanced Security Features 10) Prestoserve Utilities
11) System Exerciser Package 12) Bisynchronous Communications
13) Doc. Preparation for Ref. Pages 14) Doc. Preparation Extensions
15) Adobe Font Metric Files 16) Software Development Utilities
17) Source Code Control System 18) Internationalization Runtime Env.
19) Internationalization Dev. Env. 20) CDA Base System
21) CDA Software Dev Libraries 22) RPC Runtime Environment
23) RPC Development Environment 24) Pascal Development Package
25) VAX C/ULTRIX 26) Ref. Pages for Sys. Admin. & Users
27) Reference Pages for Programers 28) Programming Examples
29) Ultrix SPDS 30) X11/DECwindows 100dpi Fonts
31) VS35XX X11/DECwindows Fonts 32) Additional DECwindows Applications
33) DECwindows Mail Application 34) Worksystem Development Environment
35) X11/DECwindows System Management T 36) UWS Runtime Reference Pages
37) UWS Development Reference Pages

38) All mandatory and all optional subsets
39) Mandatory subsets only
40) Exit without installing subsets

Enter your choice(s): 38
Working....Wed Dec 6 00:14:12 EST 1995

You are installing the following subsets:
Base System Kernel Config Files
TCP/IP Networking Utilities Network File System Utilities
Extended (Berkeley) Mailer X11/DECwindows Servers
X11/DECwindows User Environment X11/DECwindows 75dpi Fonts
Printer Support Environment RAND Mail Handler
Sys. Config. Mgmt. Program (SCAMP) Communications Utilities
Unix-to-Unix Copy Facility Maintenance Operations Protocol
Accounting Software Kerberos Network Authentication
Enhanced Security Features Prestoserve Utilities
System Exerciser Package Bisynchronous Communications
Doc. Preparation for Ref. Pages Doc. Preparation Extensions
Adobe Font Metric Files Software Development Utilities
Source Code Control System Internationalization Runtime Env.
Internationalization Dev. Env. CDA Base System
CDA Software Dev Libraries RPC Runtime Environment
RPC Development Environment Pascal Development Package
VAX C/ULTRIX Ref. Pages for Sys. Admin. & Users
Reference Pages for Programers Programming Examples
Ultrix SPDS X11/DECwindows 100dpi Fonts
VS35XX X11/DECwindows Fonts Additional DECwindows Applications
DECwindows Mail Application Worksystem Development Environment
X11/DECwindows System Management To UWS Runtime Reference Pages
UWS Development Reference Pages

Is this correct? (y/n): y
</pre>

The installation will take a while (around 15-30 minutes for me), so feel free to let it run in the background for a while now. The installer will periodically print its status so you can see that it's still running...

<pre>
Base System (ULTBASE450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:14:43 EST 1995
Verifying

Kernel Config Files (ULTBIN450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:15:28 EST 1995
Verifying

...
</pre>

At some point you will have to confirm installing the generic kernel and the X11 subsystem:

<pre>
...
UWS Runtime Reference Pages (UWSMAN450)
Copying from /mnt/VAX/BASE (disk)
Verifying

UWS Development Reference Pages (UWSMANPGMR450)
Copying from /mnt/VAX/BASE (disk)
Verifying

The installation software has successfully installed the software
subsets.
Installing Upgrade subsets
The following subsets will be installed:
* X11/DECwindows Servers Upgrade * Generic Kernel
Do you wish to continue? (y/n): y

X11/DECwindows Servers Upgrade (UWSSER451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

Generic Kernel (ULTGENVMUNIX451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

The installation procedure has successfully installed the Upgrade
subsets
</pre>

That's it for the base installation, now we configure our kernel...

==Kernel configuration==
We have to select what features will be in the kernel. For anyone who has ever done a "make menuconfig" on Linux, this is ''slightly'' easier here ;-)
<pre>
*** CONFIGURATION FILE KERNEL OPTION SELECTION ***

Selection Kernel Option
---------------------------------------------------------------
1 Local Area Transport (LAT)
2 Bisynchronous Communication protocol (VAX only)
3 Computer Interconnect (CI) network
4 Diagnostic/Utilities Protocol (DUP)
5 ISO9660 File System Support (CDFS)
6 Ethernet Packet Filter
7 Enhanced Security Features
8 All of the above
9 None of the above
----------------------------------------------------------------

Enter the selection number for each kernel option you want.
For example, 1 3 :
</pre>

In our case, we don't need 2 (it is for 2780/3780 remote terminals), 3 (SimH doesn't emulate any cluster hardware) or 6 (it might cause problems with DECwindows/Motif). Everything else (<code>1 4 5 7</code>) is probably safe. This lets us play around with LAT (maybe connect an emulated Cisco router with LAT routing to it?) and DUP.

<pre>
Enter the selection number for each kernel option you want.
For example, 1 3 : 1 4 5 7

You specified the following kernel options:

Local Area Transport (LAT)
Diagnostic/Utilities Protocol (DUP)
ISO9660 File System Support (CDFS)
Enhanced Security Features

Is this correct? (y/n) [n]: y

*** SYSTEM CONFIGURATION PROCEDURE ***
The installation software found these devices in the floating
address space:

dz0 on uba0 at 0160100
dz1 on uba0 at 0160110
dz2 on uba0 at 0160120
dz3 on uba0 at 0160130

Configuration file complete.

Do you want to edit the configuration file? (y/n) [n]: n

*** PERFORMING SYSTEM CONFIGURATION ***

working ..... Wed Dec 6 02:29:10 EST 1995

*** DEVICE SPECIAL FILE CREATION ***
working ..... Wed Dec 6 02:29:53 EST 1995

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 800985B5
</pre>

Now you might want to take another backup of your disk images, since the ULTRIX installation is now basically complete.

==Adding the unsupported sets==
Now there are some more pieces of software in the CDROM, in a directory called ''unsupported''. We want to install these as well. First, let's boot our system again

<pre>
>>>b dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 747376
data = 125952
bss = 918192
Starting at 0x2c19

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
real mem = 67043328
avail mem = 56455168
using 1638 buffers containing 6712320 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
dz0 at uba0 csr 160100 vec 300, ipl 17
dz1 at uba0 csr 160110 vec 310, ipl 17
dz2 at uba0 csr 160120 vec 320, ipl 17
dz3 at uba0 csr 160130 vec 330, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
Wed Dec 6 11:25:29 MET 1995
Automatic reboot in progress...
/dev/ra0a: 644 files, 6161 used, 9390 free (166 frags, 1153 blocks, 5.0% fragmentation)
/dev/rra0g: umounted cleanly
/dev/rra0h: umounted cleanly
Warning Creating new license database
Warning creating new history file
check quotas: done.
savecore: checking for dump...dump does not exist
local daemons: syslog sendmail.
Removing remnant Opser files
preserving editor files
clearing /tmp
standard daemons: update cron accounting network snmpd printer.
start errlog daemon - elcsd
Wed Dec 6 11:25:48 MET 1995

ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
UWS V4.5 (Rev. 6)

Digital Equipment Corporation
Nashua, New Hampshire

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

#
</pre>

now, we mount the CDROM and use <code>setld</code> to install the unsupported packages. For simplicity's sake, we just (again) install everything.

<pre>
# mount -r /dev/ra2c /mnt
# cd /mnt/VAX/UNSUPPORTED
# ls
DXVUNDEMO450 ULXDOC450 ULXINGRES450 ULXRCS450 ULXUNMAN450
ULXAPL450 ULXEDIT450 ULXLEARN450 ULXSHELLS450 ULXUNMIT450
ULXBASE450 ULXF77450 ULXLISP450 ULXSPMS450 ULXVARIAN450
ULXBIB450 ULXGAMES450 ULXMAN450 ULXTERM450 instctrl
ULXCOURIER450 ULXHYPER450 ULXMOD2450 ULXTOOLS450
ULXCPM450 ULXICON450 ULXNEWS450 ULXUNEXAMP450
ULXDCMT450 ULXINET450 ULXNOTES450 ULXUNFONTS450
# setld -l .

*** Enter Subset Selections ***

The subsets listed below are optional:
1) Base Extension 2) GNU Emacs
3) TCP/IP Networking Util Extension 4) Additional Terminal Drivers
5) Document Preparation Software 6) Games and Diversions
7) Supplementary Documentation 8) Bibliographic Utilities
9) Remote Procedure Call Compiler 10) Aux. Command Line Interpreters
11) USENET News Interface Software 12) Notesfiles Package
13) Revision Control System 14) Misc. User-Contributed Utilities
15) Computer Aided System Tutor 16) Franz Lisp Development Package
17) Modula-2 Development Package 18) Raster Plotter Package
19) APL Development Package 20) CP/M 8in Diskette Utility
21) Hyperchannel Utilities 22) ICON (Language) Development Packag
23) University Ingres QUEL DBMS 24) Software Project Management System
25) Unsupported Fortran Utilities 26) Unsupported On-Line Documentation
27) Unsupported X11 Components 28) Unsupported DECwindows Examples
29) Unsupported MIT Fonts 30) Unsupported X11 Reference Pages
31) Unsupported OSF/Motif Demos

32) All mandatory and all optional subsets
33) Mandatory subsets only
34) Exit without installing subsets

Enter your choice(s): 32
Working....Wed Dec 6 11:29:48 MET 1995
Wed Dec 6 11:30:00 MET 1995

You are installing the following subsets:
Base Extension GNU Emacs
TCP/IP Networking Util Extension Additional Terminal Drivers
Document Preparation Software Games and Diversions
Supplementary Documentation Bibliographic Utilities
Remote Procedure Call Compiler Aux. Command Line Interpreters
USENET News Interface Software Notesfiles Package
Revision Control System Misc. User-Contributed Utilities
Computer Aided System Tutor Franz Lisp Development Package
Modula-2 Development Package Raster Plotter Package
APL Development Package CP/M 8in Diskette Utility
Hyperchannel Utilities ICON (Language) Development Package
University Ingres QUEL DBMS Software Project Management System
Unsupported Fortran Utilities Unsupported On-Line Documentation
Unsupported X11 Components Unsupported DECwindows Examples
Unsupported MIT Fonts Unsupported X11 Reference Pages
Unsupported OSF/Motif Demos

Is this correct? (y/n): y

Base Extension (ULXBASE450)
Copying from . (disk)
Verifying

GNU Emacs (ULXEDIT450)
Copying from . (disk)
Verifying

TCP/IP Networking Util Extension (ULXINET450)
Copying from . (disk)
Verifying
...
</pre>

Note that you could also quickly install only a single package by using for example
# setld -l . ULXINET450

After a few minutes, installation will be completed and we should unmount the CDROM
# cd /
# umount /mnt

==Network configuration==
To configure the network, you have to use a static IPv4 address and put that into the beginning of /etc/rc.local. Note that there is no <code>ifconfig -a</code> in ULTRIX, you have to use <code>netstat -i</code>

<pre>
# netstat -i
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
qe0* 1500 none none 0 0 0 0 0
lo0 1536 loop localhost 1 0 1 0 0
# ifconfig qe0 192.168.1.44 netmask 255.255.255.0 up
# route add default 192.168.1.1 1
add net default: gateway 192.168.1.1
# ping 192.168.1.1
192.168.1.1 is alive
</pre>
Note that it might actually take a while until packets are getting through. I don't know why but in my case it helped to ping ULTRIX from the outside first, e.g. from Windows, and then re-try the ping from the VM. Then it worked. I'm guessing this is some SimH/Windows issue with PCAP or something.

Then put these 2 commands at the start of <code>/etc/rc.local</code> (you'll see where). Note that you can use <code>vi</code> now!
<pre>
# @(#)rc.local 9.4 (ULTRIX) 9/21/95
/bin/hostname yuki
#/etc/ifconfig HDWR `/bin/hostname` broadcast NETNUM.0 netmask 255.0
/etc/ifconfig qe0 192.168.1.44 netmask 255.255.255.0
route add default 192.168.1.1 1
/etc/ifconfig lo0 localhost
#/etc/bscconfig dup0 bsc 1
#/etc/bscconfig dpv0 bsc 1
...
</pre>

Note that DNS lookups normally don't work out of the box. Create a basic <code>/etc/resolv.conf</code> file with the following content (or whatever is correct in your environment)
domain lan.local
nameserver 192.168.1.1

However, if you then try to do an nslookup query, you will get an error message
# nslookup www.google.com
*** Can't find server name for address 192.168.1.1: Not implemented
*** Default servers are not available
The problem is that ULTRIX sends so-called ''inverse queries'' (not to be confused with the well-known ''reverse lookups'', which are actually just regular forward lookups to a specific TLD) to map IP addresses to hostnames. Most DNS servers don't support these inverse queries anymore. I have yet to find an implementation that does. Alternatively there might be a way to disable inverse queries in ULTRIX. If anyone knows of either, let me know...

==Shutting down cleanly==
As you'd expect, you can use <code>shutdown</code> to shut the system down
<pre>
# shutdown -h now
Shutdown at 11:15 (in 0 minutes) [pid 1500]
#
System shutdown time has arrived
syncing disks... done

?06 HLT INST
PC = 80094CDD
>>>
</pre>

==Enabling outside access==
The SimH config above includes a 16-line serial multiplexer. If you connect via TELNET to port 1005, you are given the first free serial line of the emulated DZ device. However, serial login is disabled by default, so it has to be enabled first. That's what the <code>/etc/ttys</code> file is for. Edit the file and change the ''off'' to ''on'' in the lines for tty00 to tty07, as shown below
<pre>
# @(#)ttys 9.1 (ULTRIX) 4/26/94
#
#
#
# name getty type status comments
#
console "/etc/getty std.9600" vt100 on secure # console terminal
tty00 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty01 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty02 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty03 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty04 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty05 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty06 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty07 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
ttyd0 "/etc/getty std.9600" vt100 off shared secure # modem line
</pre>

If you want to be able to login as root on these terminals, you can also add the <code>secure</code> flag as well. Also note that while it seems tempting to increase the line speed to 19200 or even higher, from my experience that will cause massive lags and emulation hangs in SimH, so do that on your own risk.

After editing the file and saving it, you have to reload init:
# kill -HUP 1

Now try logging in to port 1005 via telnet, and you should be greeted with this:
<pre>
Connected to the MicroVAX 3900 simulator DZ device, line 0

ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:
Requires secure terminal
</pre>

Note that SimH will print out the serial line to which you are connected, in this case line 0 which is /dev/tty00.

Also, if your inetd is running (which it should be, if you followed this guide), you will also already be able to login remotely using telnet.
<pre>
ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:
Requires secure terminal
</pre>
To enable root access for all telnet sessions, you will have to edit the /etc/ttys file and change every line that starts with "ttyp" to include the secure flag:
ttyp0 none network
will become
ttyp0 none network secure
and so on...

==Resources==
Some of the resources I used for creating this guide:
*ULTRIX 4.5 installation ISO [http://musall.de/mirrors/ultrix/ultrix_os/vax/]
*ULTRIX-32 startup and shutdown guide [http://bitsavers.trailing-edge.com/pdf/dec/vax/ultrix-32/3.0/AA-ME91A-TE_ULTRIX-32_Guide_to_System_Shutdown_and_Startup.pdf]
*CERN guide to installing ULTRIX [https://web-docs.gsi.de/~kraemer/COLLECTION/ULTRIX/wwwpdp.web.cern.ch/wwwpdp/as/file/doc/ultrix/ultrix.pdf]
*My old guide for installing ULTRIX [https://docs.google.com/document/d/1ULRhzE0R1twarB5hfJm85yqOdTeoFCGgyPr5AxYEIbE]
*DEC KA655 CPU System Maintenance [http://bitsavers.trailing-edge.com/pdf/dec/vax/655/EK-306A-MG-001_655Mnt_Mar89.pdf]
*Some notes and links to more ULTRIX information [https://web-docs.gsi.de/~kraemer/COLLECTION/ULTRIX/docs.html]
*Ultrix Guide to Disk Maintenance [http://www.carelife.com/manuals/Ultrix_Guide_Disk_Maint.PDF]
*Some random notes about ULTRIX 4.0 (some also apply to 4.5) [http://apfelboymchen.net/gnu/UNIX/vax-ultrix.html]

[[Category:SIMH Tutorials]]

Installing Ultrix 4.5 on SIMH

2015-12-06T11:49:30Z

Darkstar: /* Resources */

This WORK-IN-PROGRESS guide will be a simple guide to installing ULTRIX 4.5 for VAX on SimH.

==Requirements==
The following is a list of things required for installation
*A recent version of the [[SIMH]] emulator
**Make sure the binary you're using includes Ethernet support
**I'm using a self-compiled version (git revision 0e8c0aea)
*An ISO image of ULTRIX 4.5 for VAX
**See the "Resources" section for a download link
**It's probably also possible to install it from tape, although I don't know if any installation tapes for ULTRIX 4.5 exist
*Optional stuff (might get added to the guide later):
**Starfish Ultrix Freeware CDs from [http://musall.de/mirrors/ultrix/freeware/ here]

==SimH configuration==
The machine I'm using to run ULTRIX has the following configuration
*DEC MicroVAX 3800
*64mb memory
*DELQA network card (XQ0)
*Two [[RA90]] disk drives (with 1.2gb each) attached to an RQDX3 controller (RQ0 and RQ1)
*CD ROM drive attached to the same RQDX3 controller as unit 2 (RQ2)
*[[TK50]] tape attached as unit 0 on the first TQK50 controller (TQ0)
*DZV11 terminal multiplexer with 16 lines, attached to telnet port 1005 (DZ)
*LPT line printer attached to text file <code>printer_output.txt</code>

Here's my config file (I called it <code>simh.conf</code>)
<pre><nowiki>
;
; SimH 4.0 Configuration file for MicroVAX 3800
;
; Host System : DEC MicroVAX 3800
; Operating System : DEC Ultrix v4.5
; Memory : 64mb
; Network config : XQ: Ethernet, 08:00:2b:04:14:02
; Disks : RQ0: RA90, 1.2gb
; RQ1: RA90, 1.2gb
; CDROMs : RQ2: iso file
; Tape config : TQ0: TK50, 94mb
;

load -r ka655x.bin

; NVRAM
attach NVR nvram.bin

; CPU config
set CPU 64m
set CPU conhalt
set CPU idle=all

; configure console to 7-bit only
set TTO 7b
set TTI 7b

; Disk drives
set RQ0 ra90
attach RQ0 rq0-ra90.dsk
set RQ1 ra90
attach RQ1 rq1-ra90.dsk
set RQ2 CDROM
attach -r RQ2 ultrix-vax-os-v4.5.mode1.ufs.iso
; MD5 sum: 19df0753c27f195e9f1d2f139a3b4629 *ultrix-vax-os-v4.5.mode1.ufs.iso
set RQ3 dis

; Tape
set TQ tk50
;attach tq0 filename-to-tape-file
set TQ1 dis
set TQ2 dis
set TQ3 dis

; serial port, simulated by Telnet to port 1005
set DZ LINES=16
set DZ 8B
attach DZ 1005 NoBuffer

; printer
set LPT enable
attach LPT printer_output.txt

; Disable unused peripherals
set CR dis
set RL dis
set TS dis

; Network interface (08-00-2b is the DEC prefix, the 04-14-02 part is arbitrary)
set XQ MAC=08-00-2b-04-14-02
attach XQ0 eth0

; serial console (launch directly after booting CPU)
set console telnet=1001

; experimental
;set QVSS en

; boot the system
;boot CPU
</nowiki></pre>
Note that I'm using a telnet console (for easier copy/paste on Windows), which means that directly after running this config file (via <code>do simh.conf</code> from Simh) you will need to connect via telnet to localhost:1001 or the boot will abort. If you are on Linux, or just don't want that, remove the <code>set console telnet=1001</code> line.

Also note that you might need to attach XQ0 to a different ethernet device. Use "show ether" in SimH to list all available devices on your system and modify the <code>attach XQ0 eth0</code> line accordingly.

==Running the Emulator==
Either run <code>vax.exe simh.conf</code> from the Windows command line, or just double-click the VAX.EXE executable and type <code>do simh.conf</code>.

On the first launch it might take some time because SimH has to create the disk images (~2.5 gb total). It should look something like this
<pre><nowiki>
MicroVAX 3900 simulator V4.0-0 Beta git commit id: 0e8c0aea
NVR: buffering file in memory
RQ2: unit is read only
Listening on port 1005
WinPcap version 4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008)
Eth: opened OS device \Device\NPF_{A41A1651-DD4D-4735-A4E0-88353165C2EC}
Listening on port 1001
sim>
</nowiki></pre>

Type the following to start the emulation (note: you can also uncomment that line from the end of the config file to have the emulation start right away)
sim> boot cpu
Waiting for console Telnet connection

Now would be a good time to connect your telnet session (I use a batch file for this), otherwise the boot process will timeout.

On your console, you should see something like this:
<pre><nowiki>
Connected to the MicroVAX 3900 simulator CON-TEL device

KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>
</nowiki></pre>

This is the VAX's boot prompt. Normally you just type
>>>boot <device>
where <device> is one of the following
*MUA<num>: TK tape device number <num> (1 to 4)
*DUA<num>: RQ disk device number <num> (1 to 4)

You can use <code>show device</code> to see the installed (and detected) devices you can boot from, and <code>show boot</code> to see which device will be the default if you just type <code>boot</code> (or <code>b</code> for short):
<pre><nowiki>
>>>show device
UQSSP Disk Controller 0 (772150)
-DUA0 (RA90)
-DUA1 (RA90)
-DUA2 (RRD40)

UQSSP Tape Controller 0 (774500)
-MUA0 (TK50)

Ethernet Adapter 0 (774440)
-XQA0 (08-00-2B-04-14-02)
>>>show boot
MUA0
</nowiki></pre>

Since we want to boot from CDROM, which is unit 2, we can use
>>>boot DUA2

Note: You can add flags to boot into single user mode, or to boot in interactive mode (so-called ''conversational boot'', where the system prompts you for a kernel file name to load). For details see the Guide to ULTRIX-32 System Startup and Shutdown, linked to in the ''References'' section. To use it, add the <code>/R5:<flags></code> option to the <code>boot</code> command, where flags is 0 (default multi-user), 1 (conversational multi-user), 2 (single-user) or 3 (conversational single-user). For example
>>>boot/r5:3 dua0

Note: You can also boot from ethernet (<code>boot XQA0</code>) but this requires a DEC-specific boot server in your network (the protocol is called ''MOP'' for ''Maintenance Operations Protocol''), which is beyond the scope of this document. I did get it to work a few years ago though, but it was a bit difficult to set up.

For a list and description of all commands available in the bootloader (hint: there are lots), see the ''KA655 CPU System Maintenance'' guide mentioned in the ''References'' section..

==Bootstrapping ULTRIX==
You will see the following output on the first boot.
<pre>
>>>boot dua2
(BOOT/R5:0 DUA2

2..
-DUA2
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 945424
data = 1290240
bss = 757940
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #2: Wed Oct 18 12:06:55 EDT 1995
real mem = 67043328
avail mem = 61517824
Buffer configuration adjusted to run with small system page table
using 123 buffers containing 1007616 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
WARNING: clock gained 47 days -- CHECK AND RESET THE DATE!

*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice:
</pre>
Now we want to do an ''ADVANCED Installation'', but when we try to, it will take a few seconds until the installation program dumps us to a prompt because it couldn't find a valid device to install from and to:
<pre>
Enter your choice: 2

*** SOFTWARE DISTRIBUTION DEVICE SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of software distribution devices and which installation media you should
load on it:

No valid device is found.
Contact a DIGITAL field service representative.

#
</pre>

The problem seems to be that the hardware SimH emulates is not fully supported by ULTRIX (or is misdetected -- I'm not entirely sure myself). The good thing is that the internet has the correct solution, which is to fix some lines in the installation shell script. The fact that the basic system that is running at this point doesn't have ''vi'', or even ''cat'', makes this a bit harder ;-)

The only option you have is ''ed'', the old UNIX editor. For a quick introduction, see [http://blog.sanctum.geek.nz/actually-using-ed/ here].

To load the file in the editor, use
# '''ed install.1'''
16763

You can see the entire file with
1,$l
but be warned, the output is quite long and it'll take some time to print it all out.

To fix it, use the following commands (the lines in '''bold''' is what you type, everything else is the response from ed)
# '''ed install.1'''
16763
'''173l'''
BTD=`btd`
'''173s/`btd`/ra2/'''
'''173l'''
BTD=ra2
'''193l'''
rz* )
'''193s/rz/ra/'''
'''193l'''
ra* )
'''w'''
16761
'''q'''
#

First, we list line 173, then we change it from <code>BTD=`btd`</code> to <code>BTD=ra2</code>, which happens to be the CDROM device and unit number we're installing from (if you changed that in your config, use the correct name here!)

Then we change line 193 from <code>rz* )</code> to <code>ra* )</code> since we're trying to install on an RA type disk which was apparently not supported in ULTRIX out of the box.

After writing the file with <code>w</code> and quitting ed with <code>q</code>, we're back at the prompt, at which point we can use CTRL+D to retry the installation:

<pre>
# ^D
*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice: 2

*** SYSTEM DISK SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of system disk drives. Select one of the devices below to contain the
root file system:

SYSTEM DISK TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk drive
is on line and write-enabled (if applicable to your disk drive), then
confirm your choice.

Use RA90, ra0, for your system disk? (y/n) []: y

The installation procedure now allocates the root file system on
partition 'a' of the system disk, ra0 RA90.

Making the root file system on ra0 RA90.

The installation procedure is now restoring the root file system to
partition 'a' of the system disk, ra0 RA90.

The installation procedure now checks the root file system on partition 'a'
of the system disk, ra0 RA90.
** /dev/rra0a
** Last Mounted on /mnt
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
226 files, 4547 used, 11004 free (20 frags, 1373 blocks, 1.0% fragmentation)

*** BOOTSTRAP COMMAND SEQUENCE ***

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 8007F799
>>>
</pre>
After this, you will be back at the VAX boot prompt (if you used <code>set CPU CONHALT</code> in your config) or at the SimH emulator prompt (if you used <code>set CPU SIMHALT</code>, which is the default). In the latter case you will have to do <code>boot cpu</code> again to get to the VAX boot prompt.

==First boot==
Now we can boot the installed system from harddisk for the first time.

If you want to, now would be a good time to take a backup copy of your disk files (or just create a btrfs snapshot or something if you have the possibility ;-)

Okay, then let's boot from DUA0
<pre>
>>>boot dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 1153664
data = 281088
bss = 1043548
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #3: Wed Oct 18 11:49:00 EDT 1995
real mem = 67043328
avail mem = 62008320
Buffer configuration adjusted to run with small system page table
using 121 buffers containing 991232 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
</pre>
Here, it will seem to hang for a loooong time. A few minutes. Don't worry, it will eventually continue to boot. I guess it's probing for other devices which are not present.

You ''might'' be able to speed this up a bit by interrupting SimH (press CTRL+E in the SimH console window) and then using <code>set CPU noidle</code> followed by <code>go</code> to resume emulation.

Eventually, you will have to decide on a hostname. Note that if you want to play around with [[DECnet]] at some point, your hostname should be no longer than 6 characters.
<pre>
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)

*** SYSTEM NAME SPECIFICATION ***

Select the name of your system using alphanumeric characters.
The first character must be a letter. For example, tinker.

Enter your system name: yuki

You selected yuki as the name of your system.
Is this correct? (y/n) [y]: y
</pre>

Next up is the time configuration. Since Ultrix 4.5 is not Y2k compliant (AFAIK), I decided to set the clock back a whopping 20 years. Note that the timezone and daylight saving settings are for my location (Germany) and will probably vary for you.

<pre>
*** DATE AND TIME SPECIFICATION ***

The current date and time should be specified using the following
format:

yymmddhhmm

Use two digits for year (yy), month (mm), day (dd), hour (hh), and
minute (mm). Enter the time in 24-hour format. For example, 02:54
p.m. on Feb 2, 1993 would be entered as:

9302021454

Enter the date and time: 9512052336

*** TIME ZONE SELECTION ***

Select the time zone for your area, using the options listed in the
table below. You can also enter the number of hours (-12 to 12) in
time east of Greenwich.

Selection Time Zone
---------------------------------
e Eastern
c Central
m Mountain
p Pacific
g Greenwich
---------------------------------

Enter your choice: 1

Does your area alternate between Daylight Savings and Standard
time? (y/n) [y]: y

Select your geographic area for Daylight Savings Time, using the
options in the table below.

Selection Geographic Area
--------------------------------
u USA
a Australia
e Eastern Europe
c Central Europe
w Western Europe
--------------------------------

Enter your choice [u]: c

The current date and time is Tue Dec 5 23:36:46 EST 1995
</pre>

Next up is the root password. Note that Ultrix will not echo anything here, I added the asterisks just for this guide :)

<pre>
*** SPECIFY THE SUPERUSER PASSWORD ***
The Guide to Installing ULTRIX instructs you on how to enter
the superuser password.
Changing password for root
Enter new password: ******
Verify: ******
</pre>

Next up is the filesystem layout, which is a bit more involved than what you know from more modern systems like MS DOS ;-)

In ULTRIX, partitions are defined for each disk type in a file called <code>/etc/disktab</code>. Note that the partitions overlap, so you shouldn't use them all at the same time. The setup script actually takes care of that for you, but if you later create a new filesystem on the wrong partition you ''WILL'' lose data!

Normally, partition '''c''' is the whole disk, which is useful for add-on disk drives for example. Partitions '''a''' and '''b''' are always available and are traditionally used for the system and the swap-space respectively. The swap partition is also used for crashdumps if no separate crash-dump partition is created. The rest of the disk can be used either as a single partition (which is usually '''g''') or as 3 individual partitions ('''d''' to '''f'''). If the disk is larger than 1 gigabyte, you will get another partition, '''h''', after the g partition, probably because the filesystem cannot cope with partitions >1gig

In our case, we will have the following partitions on the first disk (RA0):
*Partition '''a''' of 32 mb for /root
*Partition '''b''' of 64 mb for swap+crashdump
*Partition '''c''' of 1.2 gig (whole-disk, not used on our setup)
*Partition '''d''' and '''e''' of 200 mb each (not used)
*Partition '''f''' of 400 mb (not used)
*Partition '''g''' of 800 mb (overlaps with d, e and f; will become /usr)
*Partition '''h''' of 256 mb (will become /usr/var)
This way we still have the whole second disk available for later use.

So here it goes:
<pre>
*** FILE SYSTEM DEFAULT OPTION ***

The following table shows the default file system layout on RA90, ra0:

partition bottom top size overlap default
a 0 32767 32768 c root
b 32768 159839 127072 c swap, dump
d 159840 580036 420197 c,g /usr

If you choose the defaults, the var area will be allocated to /usr/var.

Do you want to choose the default file system layout? (y/n): n
</pre>

No, we do not want to use the defaults...

First, we select disk 1, partition '''g''', for the /usr file system:
<pre>
*** /usr FILE SYSTEM ALLOCATION ***

You can allocate the /usr file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

/usr FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for /usr file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the /usr file system:

partition size (Kbytes) overlap
------------------------------------------------
d --- 210098 c,g
e --- 210098 c,g
f --- 420196 c,g
g --- 840393 c,d,e,f
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the /usr file system [d]: g

Making the new file system for /usr on /dev/rra0g RA90
</pre>

Next, we select disk 1, partition '''b''' for swap (only 1 swap partition) and for crashdumps:

<pre>
*** ALLOCATE THE SWAP1 SPACE ***

You can allocate the swap1 space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

SWAP1 SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for swap1 space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the swap1 space:

partition size (Kbytes) overlap
------------------------------------------------
b --- 63536 c
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the swap1 space [b]: b

*** ALLOCATE THE SWAP2 SPACE ***

Do you want to allocate a second swap space? (y/n) [n]: n

*** ALLOCATE THE CRASH DUMP SPACE ***

You can allocate the crash dump space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

CRASH DUMP SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for crash dump space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the crash dump space:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
b --- 63536 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the crash dump space [b]: b
</pre>

Finally we select partiton '''h''' for the /var file system. This might not be large enough later on but then we can always migrate the data away if we need to...

<pre>
*** ALLOCATE THE var FILE SYSTEM ***

You can allocate the var file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

var FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for var file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the var file system:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
g --- 840393 c,d,e,f
------------------------------------------------

Type the letter of the partition on which you want
to allocate the var file system [no default]: h

Making the new file system for var on /dev/rra0h RA90
</pre>

==Installing the distribution files==

Next up we have to decide what ''packages'' we want to install (yes, ULTRIX already had its own package format and corresponding installer called ''setld''. It is very basic, probably most similar to ''pkg_add'' on NetBSD). We simply install everything, since we have enough space :)

<pre>
This distribution media includes subsets for ULTRIX Worksystem
Software (UWS). A UWS license (on a workstation) or a UWS Server
License (on a timesharing machine or server) is required to install
these subsets.

Do you want to install ULTRIX Worksystem Software? y/n []: y

*** SUPPORTED SOFTWARE INSTALLATION ***

*** Select the DECwindows User Interface ***

1) DECwindows for OSF/Motif
2) X11/DECwindows (XUI)

Enter your choice [1]: 2

*** Enter Subset Selections ***

The following subsets are mandatory and will be installed automatically:
* Base System * Kernel Config Files
* TCP/IP Networking Utilities * Network File System Utilities
* Extended (Berkeley) Mailer * X11/DECwindows Servers
* X11/DECwindows User Environment * X11/DECwindows 75dpi Fonts

The subsets listed below are optional:
1) Printer Support Environment 2) RAND Mail Handler
3) Sys. Config. Mgmt. Program (SCAMP) 4) Communications Utilities
5) Unix-to-Unix Copy Facility 6) Maintenance Operations Protocol
7) Accounting Software 8) Kerberos Network Authentication
9) Enhanced Security Features 10) Prestoserve Utilities
11) System Exerciser Package 12) Bisynchronous Communications
13) Doc. Preparation for Ref. Pages 14) Doc. Preparation Extensions
15) Adobe Font Metric Files 16) Software Development Utilities
17) Source Code Control System 18) Internationalization Runtime Env.
19) Internationalization Dev. Env. 20) CDA Base System
21) CDA Software Dev Libraries 22) RPC Runtime Environment
23) RPC Development Environment 24) Pascal Development Package
25) VAX C/ULTRIX 26) Ref. Pages for Sys. Admin. & Users
27) Reference Pages for Programers 28) Programming Examples
29) Ultrix SPDS 30) X11/DECwindows 100dpi Fonts
31) VS35XX X11/DECwindows Fonts 32) Additional DECwindows Applications
33) DECwindows Mail Application 34) Worksystem Development Environment
35) X11/DECwindows System Management T 36) UWS Runtime Reference Pages
37) UWS Development Reference Pages

38) All mandatory and all optional subsets
39) Mandatory subsets only
40) Exit without installing subsets

Enter your choice(s): 38
Working....Wed Dec 6 00:14:12 EST 1995

You are installing the following subsets:
Base System Kernel Config Files
TCP/IP Networking Utilities Network File System Utilities
Extended (Berkeley) Mailer X11/DECwindows Servers
X11/DECwindows User Environment X11/DECwindows 75dpi Fonts
Printer Support Environment RAND Mail Handler
Sys. Config. Mgmt. Program (SCAMP) Communications Utilities
Unix-to-Unix Copy Facility Maintenance Operations Protocol
Accounting Software Kerberos Network Authentication
Enhanced Security Features Prestoserve Utilities
System Exerciser Package Bisynchronous Communications
Doc. Preparation for Ref. Pages Doc. Preparation Extensions
Adobe Font Metric Files Software Development Utilities
Source Code Control System Internationalization Runtime Env.
Internationalization Dev. Env. CDA Base System
CDA Software Dev Libraries RPC Runtime Environment
RPC Development Environment Pascal Development Package
VAX C/ULTRIX Ref. Pages for Sys. Admin. & Users
Reference Pages for Programers Programming Examples
Ultrix SPDS X11/DECwindows 100dpi Fonts
VS35XX X11/DECwindows Fonts Additional DECwindows Applications
DECwindows Mail Application Worksystem Development Environment
X11/DECwindows System Management To UWS Runtime Reference Pages
UWS Development Reference Pages

Is this correct? (y/n): y
</pre>

The installation will take a while (around 15-30 minutes for me), so feel free to let it run in the background for a while now. The installer will periodically print its status so you can see that it's still running...

<pre>
Base System (ULTBASE450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:14:43 EST 1995
Verifying

Kernel Config Files (ULTBIN450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:15:28 EST 1995
Verifying

...
</pre>

At some point you will have to confirm installing the generic kernel and the X11 subsystem:

<pre>
...
UWS Runtime Reference Pages (UWSMAN450)
Copying from /mnt/VAX/BASE (disk)
Verifying

UWS Development Reference Pages (UWSMANPGMR450)
Copying from /mnt/VAX/BASE (disk)
Verifying

The installation software has successfully installed the software
subsets.
Installing Upgrade subsets
The following subsets will be installed:
* X11/DECwindows Servers Upgrade * Generic Kernel
Do you wish to continue? (y/n): y

X11/DECwindows Servers Upgrade (UWSSER451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

Generic Kernel (ULTGENVMUNIX451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

The installation procedure has successfully installed the Upgrade
subsets
</pre>

That's it for the base installation, now we configure our kernel...

==Kernel configuration==
We have to select what features will be in the kernel. For anyone who has ever done a "make menuconfig" on Linux, this is ''slightly'' easier here ;-)
<pre>
*** CONFIGURATION FILE KERNEL OPTION SELECTION ***

Selection Kernel Option
---------------------------------------------------------------
1 Local Area Transport (LAT)
2 Bisynchronous Communication protocol (VAX only)
3 Computer Interconnect (CI) network
4 Diagnostic/Utilities Protocol (DUP)
5 ISO9660 File System Support (CDFS)
6 Ethernet Packet Filter
7 Enhanced Security Features
8 All of the above
9 None of the above
----------------------------------------------------------------

Enter the selection number for each kernel option you want.
For example, 1 3 :
</pre>

In our case, we don't need 2 (it is for 2780/3780 remote terminals), 3 (SimH doesn't emulate any cluster hardware) or 6 (it might cause problems with DECwindows/Motif). Everything else (<code>1 4 5 7</code>) is probably safe. This lets us play around with LAT (maybe connect an emulated Cisco router with LAT routing to it?) and DUP.

<pre>
Enter the selection number for each kernel option you want.
For example, 1 3 : 1 4 5 7

You specified the following kernel options:

Local Area Transport (LAT)
Diagnostic/Utilities Protocol (DUP)
ISO9660 File System Support (CDFS)
Enhanced Security Features

Is this correct? (y/n) [n]: y

*** SYSTEM CONFIGURATION PROCEDURE ***
The installation software found these devices in the floating
address space:

dz0 on uba0 at 0160100
dz1 on uba0 at 0160110
dz2 on uba0 at 0160120
dz3 on uba0 at 0160130

Configuration file complete.

Do you want to edit the configuration file? (y/n) [n]: n

*** PERFORMING SYSTEM CONFIGURATION ***

working ..... Wed Dec 6 02:29:10 EST 1995

*** DEVICE SPECIAL FILE CREATION ***
working ..... Wed Dec 6 02:29:53 EST 1995

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 800985B5
</pre>

Now you might want to take another backup of your disk images, since the ULTRIX installation is now basically complete.

==Adding the unsupported sets==
Now there are some more pieces of software in the CDROM, in a directory called ''unsupported''. We want to install these as well. First, let's boot our system again

<pre>
>>>b dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 747376
data = 125952
bss = 918192
Starting at 0x2c19

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
real mem = 67043328
avail mem = 56455168
using 1638 buffers containing 6712320 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
dz0 at uba0 csr 160100 vec 300, ipl 17
dz1 at uba0 csr 160110 vec 310, ipl 17
dz2 at uba0 csr 160120 vec 320, ipl 17
dz3 at uba0 csr 160130 vec 330, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
Wed Dec 6 11:25:29 MET 1995
Automatic reboot in progress...
/dev/ra0a: 644 files, 6161 used, 9390 free (166 frags, 1153 blocks, 5.0% fragmentation)
/dev/rra0g: umounted cleanly
/dev/rra0h: umounted cleanly
Warning Creating new license database
Warning creating new history file
check quotas: done.
savecore: checking for dump...dump does not exist
local daemons: syslog sendmail.
Removing remnant Opser files
preserving editor files
clearing /tmp
standard daemons: update cron accounting network snmpd printer.
start errlog daemon - elcsd
Wed Dec 6 11:25:48 MET 1995

ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
UWS V4.5 (Rev. 6)

Digital Equipment Corporation
Nashua, New Hampshire

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

#
</pre>

now, we mount the CDROM and use <code>setld</code> to install the unsupported packages. For simplicity's sake, we just (again) install everything.

<pre>
# mount -r /dev/ra2c /mnt
# cd /mnt/VAX/UNSUPPORTED
# ls
DXVUNDEMO450 ULXDOC450 ULXINGRES450 ULXRCS450 ULXUNMAN450
ULXAPL450 ULXEDIT450 ULXLEARN450 ULXSHELLS450 ULXUNMIT450
ULXBASE450 ULXF77450 ULXLISP450 ULXSPMS450 ULXVARIAN450
ULXBIB450 ULXGAMES450 ULXMAN450 ULXTERM450 instctrl
ULXCOURIER450 ULXHYPER450 ULXMOD2450 ULXTOOLS450
ULXCPM450 ULXICON450 ULXNEWS450 ULXUNEXAMP450
ULXDCMT450 ULXINET450 ULXNOTES450 ULXUNFONTS450
# setld -l .

*** Enter Subset Selections ***

The subsets listed below are optional:
1) Base Extension 2) GNU Emacs
3) TCP/IP Networking Util Extension 4) Additional Terminal Drivers
5) Document Preparation Software 6) Games and Diversions
7) Supplementary Documentation 8) Bibliographic Utilities
9) Remote Procedure Call Compiler 10) Aux. Command Line Interpreters
11) USENET News Interface Software 12) Notesfiles Package
13) Revision Control System 14) Misc. User-Contributed Utilities
15) Computer Aided System Tutor 16) Franz Lisp Development Package
17) Modula-2 Development Package 18) Raster Plotter Package
19) APL Development Package 20) CP/M 8in Diskette Utility
21) Hyperchannel Utilities 22) ICON (Language) Development Packag
23) University Ingres QUEL DBMS 24) Software Project Management System
25) Unsupported Fortran Utilities 26) Unsupported On-Line Documentation
27) Unsupported X11 Components 28) Unsupported DECwindows Examples
29) Unsupported MIT Fonts 30) Unsupported X11 Reference Pages
31) Unsupported OSF/Motif Demos

32) All mandatory and all optional subsets
33) Mandatory subsets only
34) Exit without installing subsets

Enter your choice(s): 32
Working....Wed Dec 6 11:29:48 MET 1995
Wed Dec 6 11:30:00 MET 1995

You are installing the following subsets:
Base Extension GNU Emacs
TCP/IP Networking Util Extension Additional Terminal Drivers
Document Preparation Software Games and Diversions
Supplementary Documentation Bibliographic Utilities
Remote Procedure Call Compiler Aux. Command Line Interpreters
USENET News Interface Software Notesfiles Package
Revision Control System Misc. User-Contributed Utilities
Computer Aided System Tutor Franz Lisp Development Package
Modula-2 Development Package Raster Plotter Package
APL Development Package CP/M 8in Diskette Utility
Hyperchannel Utilities ICON (Language) Development Package
University Ingres QUEL DBMS Software Project Management System
Unsupported Fortran Utilities Unsupported On-Line Documentation
Unsupported X11 Components Unsupported DECwindows Examples
Unsupported MIT Fonts Unsupported X11 Reference Pages
Unsupported OSF/Motif Demos

Is this correct? (y/n): y

Base Extension (ULXBASE450)
Copying from . (disk)
Verifying

GNU Emacs (ULXEDIT450)
Copying from . (disk)
Verifying

TCP/IP Networking Util Extension (ULXINET450)
Copying from . (disk)
Verifying
...
</pre>

Note that you could also quickly install only a single package by using for example
# setld -l . ULXINET450

After a few minutes, installation will be completed and we should unmount the CDROM
# cd /
# umount /mnt

==Network configuration==
To configure the network, you have to use a static IPv4 address and put that into the beginning of /etc/rc.local. Note that there is no <code>ifconfig -a</code> in ULTRIX, you have to use <code>netstat -i</code>

<pre>
# netstat -i
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
qe0* 1500 none none 0 0 0 0 0
lo0 1536 loop localhost 1 0 1 0 0
# ifconfig qe0 192.168.1.44 netmask 255.255.255.0 up
# route add default 192.168.1.1 1
add net default: gateway 192.168.1.1
# ping 192.168.1.1
192.168.1.1 is alive
</pre>
Note that it might actually take a while until packets are getting through. I don't know why but in my case it helped to ping ULTRIX from the outside first, e.g. from Windows, and then re-try the ping from the VM. Then it worked. I'm guessing this is some SimH/Windows issue with PCAP or something.

Then put these 2 commands at the start of <code>/etc/rc.local</code> (you'll see where). Note that you can use <code>vi</code> now!
<pre>
# @(#)rc.local 9.4 (ULTRIX) 9/21/95
/bin/hostname yuki
#/etc/ifconfig HDWR `/bin/hostname` broadcast NETNUM.0 netmask 255.0
/etc/ifconfig qe0 192.168.1.44 netmask 255.255.255.0
route add default 192.168.1.1 1
/etc/ifconfig lo0 localhost
#/etc/bscconfig dup0 bsc 1
#/etc/bscconfig dpv0 bsc 1
...
</pre>

==Shutting down cleanly==
As you'd expect, you can use <code>shutdown</code> to shut the system down
<pre>
# shutdown -h now
Shutdown at 11:15 (in 0 minutes) [pid 1500]
#
System shutdown time has arrived
syncing disks... done

?06 HLT INST
PC = 80094CDD
>>>
</pre>

==Enabling outside access==
The SimH config above includes a 16-line serial multiplexer. If you connect via TELNET to port 1005, you are given the first free serial line of the emulated DZ device. However, serial login is disabled by default, so it has to be enabled first. That's what the <code>/etc/ttys</code> file is for. Edit the file and change the ''off'' to ''on'' in the lines for tty00 to tty07, as shown below
<pre>
# @(#)ttys 9.1 (ULTRIX) 4/26/94
#
#
#
# name getty type status comments
#
console "/etc/getty std.9600" vt100 on secure # console terminal
tty00 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty01 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty02 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty03 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty04 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty05 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty06 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty07 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
ttyd0 "/etc/getty std.9600" vt100 off shared secure # modem line
</pre>

If you want to be able to login as root on these terminals, you can also add the <code>secure</code> flag as well. Also note that while it seems tempting to increase the line speed to 19200 or even higher, from my experience that will cause massive lags and emulation hangs in SimH, so do that on your own risk.

After editing the file and saving it, you have to reload init:
# kill -HUP 1

Now try logging in to port 1005 via telnet, and you should be greeted with this:
<pre>
Connected to the MicroVAX 3900 simulator DZ device, line 0

ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:
Requires secure terminal
</pre>

Note that SimH will print out the serial line to which you are connected, in this case line 0 which is /dev/tty00.

Also, if your inetd is running (which it should be, if you followed this guide), you will also already be able to login remotely using telnet.
<pre>
ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:
Requires secure terminal
</pre>
To enable root access for all telnet sessions, you will have to edit the /etc/ttys file and change every line that starts with "ttyp" to include the secure flag:
ttyp0 none network
will become
ttyp0 none network secure
and so on...

==Resources==
Some of the resources I used for creating this guide:
*ULTRIX 4.5 installation ISO [http://musall.de/mirrors/ultrix/ultrix_os/vax/]
*ULTRIX-32 startup and shutdown guide [http://bitsavers.trailing-edge.com/pdf/dec/vax/ultrix-32/3.0/AA-ME91A-TE_ULTRIX-32_Guide_to_System_Shutdown_and_Startup.pdf]
*CERN guide to installing ULTRIX [https://web-docs.gsi.de/~kraemer/COLLECTION/ULTRIX/wwwpdp.web.cern.ch/wwwpdp/as/file/doc/ultrix/ultrix.pdf]
*My old guide for installing ULTRIX [https://docs.google.com/document/d/1ULRhzE0R1twarB5hfJm85yqOdTeoFCGgyPr5AxYEIbE]
*DEC KA655 CPU System Maintenance [http://bitsavers.trailing-edge.com/pdf/dec/vax/655/EK-306A-MG-001_655Mnt_Mar89.pdf]
*Some notes and links to more ULTRIX information [https://web-docs.gsi.de/~kraemer/COLLECTION/ULTRIX/docs.html]
*Ultrix Guide to Disk Maintenance [http://www.carelife.com/manuals/Ultrix_Guide_Disk_Maint.PDF]
*Some random notes about ULTRIX 4.0 (some also apply to 4.5) [http://apfelboymchen.net/gnu/UNIX/vax-ultrix.html]

[[Category:SIMH Tutorials]]

Installing Ultrix 4.5 on SIMH

2015-12-06T10:56:36Z

Darkstar: /* Enabling outside access */

This WORK-IN-PROGRESS guide will be a simple guide to installing ULTRIX 4.5 for VAX on SimH.

==Requirements==
The following is a list of things required for installation
*A recent version of the [[SIMH]] emulator
**Make sure the binary you're using includes Ethernet support
**I'm using a self-compiled version (git revision 0e8c0aea)
*An ISO image of ULTRIX 4.5 for VAX
**See the "Resources" section for a download link
**It's probably also possible to install it from tape, although I don't know if any installation tapes for ULTRIX 4.5 exist
*Optional stuff (might get added to the guide later):
**Starfish Ultrix Freeware CDs from [http://musall.de/mirrors/ultrix/freeware/ here]

==SimH configuration==
The machine I'm using to run ULTRIX has the following configuration
*DEC MicroVAX 3800
*64mb memory
*DELQA network card (XQ0)
*Two [[RA90]] disk drives (with 1.2gb each) attached to an RQDX3 controller (RQ0 and RQ1)
*CD ROM drive attached to the same RQDX3 controller as unit 2 (RQ2)
*[[TK50]] tape attached as unit 0 on the first TQK50 controller (TQ0)
*DZV11 terminal multiplexer with 16 lines, attached to telnet port 1005 (DZ)
*LPT line printer attached to text file <code>printer_output.txt</code>

Here's my config file (I called it <code>simh.conf</code>)
<pre><nowiki>
;
; SimH 4.0 Configuration file for MicroVAX 3800
;
; Host System : DEC MicroVAX 3800
; Operating System : DEC Ultrix v4.5
; Memory : 64mb
; Network config : XQ: Ethernet, 08:00:2b:04:14:02
; Disks : RQ0: RA90, 1.2gb
; RQ1: RA90, 1.2gb
; CDROMs : RQ2: iso file
; Tape config : TQ0: TK50, 94mb
;

load -r ka655x.bin

; NVRAM
attach NVR nvram.bin

; CPU config
set CPU 64m
set CPU conhalt
set CPU idle=all

; configure console to 7-bit only
set TTO 7b
set TTI 7b

; Disk drives
set RQ0 ra90
attach RQ0 rq0-ra90.dsk
set RQ1 ra90
attach RQ1 rq1-ra90.dsk
set RQ2 CDROM
attach -r RQ2 ultrix-vax-os-v4.5.mode1.ufs.iso
; MD5 sum: 19df0753c27f195e9f1d2f139a3b4629 *ultrix-vax-os-v4.5.mode1.ufs.iso
set RQ3 dis

; Tape
set TQ tk50
;attach tq0 filename-to-tape-file
set TQ1 dis
set TQ2 dis
set TQ3 dis

; serial port, simulated by Telnet to port 1005
set DZ LINES=16
set DZ 8B
attach DZ 1005 NoBuffer

; printer
set LPT enable
attach LPT printer_output.txt

; Disable unused peripherals
set CR dis
set RL dis
set TS dis

; Network interface (08-00-2b is the DEC prefix, the 04-14-02 part is arbitrary)
set XQ MAC=08-00-2b-04-14-02
attach XQ0 eth0

; serial console (launch directly after booting CPU)
set console telnet=1001

; experimental
;set QVSS en

; boot the system
;boot CPU
</nowiki></pre>
Note that I'm using a telnet console (for easier copy/paste on Windows), which means that directly after running this config file (via <code>do simh.conf</code> from Simh) you will need to connect via telnet to localhost:1001 or the boot will abort. If you are on Linux, or just don't want that, remove the <code>set console telnet=1001</code> line.

Also note that you might need to attach XQ0 to a different ethernet device. Use "show ether" in SimH to list all available devices on your system and modify the <code>attach XQ0 eth0</code> line accordingly.

==Running the Emulator==
Either run <code>vax.exe simh.conf</code> from the Windows command line, or just double-click the VAX.EXE executable and type <code>do simh.conf</code>.

On the first launch it might take some time because SimH has to create the disk images (~2.5 gb total). It should look something like this
<pre><nowiki>
MicroVAX 3900 simulator V4.0-0 Beta git commit id: 0e8c0aea
NVR: buffering file in memory
RQ2: unit is read only
Listening on port 1005
WinPcap version 4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008)
Eth: opened OS device \Device\NPF_{A41A1651-DD4D-4735-A4E0-88353165C2EC}
Listening on port 1001
sim>
</nowiki></pre>

Type the following to start the emulation (note: you can also uncomment that line from the end of the config file to have the emulation start right away)
sim> boot cpu
Waiting for console Telnet connection

Now would be a good time to connect your telnet session (I use a batch file for this), otherwise the boot process will timeout.

On your console, you should see something like this:
<pre><nowiki>
Connected to the MicroVAX 3900 simulator CON-TEL device

KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>
</nowiki></pre>

This is the VAX's boot prompt. Normally you just type
>>>boot <device>
where <device> is one of the following
*MUA<num>: TK tape device number <num> (1 to 4)
*DUA<num>: RQ disk device number <num> (1 to 4)

You can use <code>show device</code> to see the installed (and detected) devices you can boot from, and <code>show boot</code> to see which device will be the default if you just type <code>boot</code> (or <code>b</code> for short):
<pre><nowiki>
>>>show device
UQSSP Disk Controller 0 (772150)
-DUA0 (RA90)
-DUA1 (RA90)
-DUA2 (RRD40)

UQSSP Tape Controller 0 (774500)
-MUA0 (TK50)

Ethernet Adapter 0 (774440)
-XQA0 (08-00-2B-04-14-02)
>>>show boot
MUA0
</nowiki></pre>

Since we want to boot from CDROM, which is unit 2, we can use
>>>boot DUA2

Note: You can add flags to boot into single user mode, or to boot in interactive mode (so-called ''conversational boot'', where the system prompts you for a kernel file name to load). For details see the Guide to ULTRIX-32 System Startup and Shutdown, linked to in the ''References'' section. To use it, add the <code>/R5:<flags></code> option to the <code>boot</code> command, where flags is 0 (default multi-user), 1 (conversational multi-user), 2 (single-user) or 3 (conversational single-user). For example
>>>boot/r5:3 dua0

Note: You can also boot from ethernet (<code>boot XQA0</code>) but this requires a DEC-specific boot server in your network (the protocol is called ''MOP'' for ''Maintenance Operations Protocol''), which is beyond the scope of this document. I did get it to work a few years ago though, but it was a bit difficult to set up.

For a list and description of all commands available in the bootloader (hint: there are lots), see the ''KA655 CPU System Maintenance'' guide mentioned in the ''References'' section..

==Bootstrapping ULTRIX==
You will see the following output on the first boot.
<pre>
>>>boot dua2
(BOOT/R5:0 DUA2

2..
-DUA2
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 945424
data = 1290240
bss = 757940
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #2: Wed Oct 18 12:06:55 EDT 1995
real mem = 67043328
avail mem = 61517824
Buffer configuration adjusted to run with small system page table
using 123 buffers containing 1007616 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
WARNING: clock gained 47 days -- CHECK AND RESET THE DATE!

*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice:
</pre>
Now we want to do an ''ADVANCED Installation'', but when we try to, it will take a few seconds until the installation program dumps us to a prompt because it couldn't find a valid device to install from and to:
<pre>
Enter your choice: 2

*** SOFTWARE DISTRIBUTION DEVICE SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of software distribution devices and which installation media you should
load on it:

No valid device is found.
Contact a DIGITAL field service representative.

#
</pre>

The problem seems to be that the hardware SimH emulates is not fully supported by ULTRIX (or is misdetected -- I'm not entirely sure myself). The good thing is that the internet has the correct solution, which is to fix some lines in the installation shell script. The fact that the basic system that is running at this point doesn't have ''vi'', or even ''cat'', makes this a bit harder ;-)

The only option you have is ''ed'', the old UNIX editor. For a quick introduction, see [http://blog.sanctum.geek.nz/actually-using-ed/ here].

To load the file in the editor, use
# '''ed install.1'''
16763

You can see the entire file with
1,$l
but be warned, the output is quite long and it'll take some time to print it all out.

To fix it, use the following commands (the lines in '''bold''' is what you type, everything else is the response from ed)
# '''ed install.1'''
16763
'''173l'''
BTD=`btd`
'''173s/`btd`/ra2/'''
'''173l'''
BTD=ra2
'''193l'''
rz* )
'''193s/rz/ra/'''
'''193l'''
ra* )
'''w'''
16761
'''q'''
#

First, we list line 173, then we change it from <code>BTD=`btd`</code> to <code>BTD=ra2</code>, which happens to be the CDROM device and unit number we're installing from (if you changed that in your config, use the correct name here!)

Then we change line 193 from <code>rz* )</code> to <code>ra* )</code> since we're trying to install on an RA type disk which was apparently not supported in ULTRIX out of the box.

After writing the file with <code>w</code> and quitting ed with <code>q</code>, we're back at the prompt, at which point we can use CTRL+D to retry the installation:

<pre>
# ^D
*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice: 2

*** SYSTEM DISK SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of system disk drives. Select one of the devices below to contain the
root file system:

SYSTEM DISK TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk drive
is on line and write-enabled (if applicable to your disk drive), then
confirm your choice.

Use RA90, ra0, for your system disk? (y/n) []: y

The installation procedure now allocates the root file system on
partition 'a' of the system disk, ra0 RA90.

Making the root file system on ra0 RA90.

The installation procedure is now restoring the root file system to
partition 'a' of the system disk, ra0 RA90.

The installation procedure now checks the root file system on partition 'a'
of the system disk, ra0 RA90.
** /dev/rra0a
** Last Mounted on /mnt
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
226 files, 4547 used, 11004 free (20 frags, 1373 blocks, 1.0% fragmentation)

*** BOOTSTRAP COMMAND SEQUENCE ***

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 8007F799
>>>
</pre>
After this, you will be back at the VAX boot prompt (if you used <code>set CPU CONHALT</code> in your config) or at the SimH emulator prompt (if you used <code>set CPU SIMHALT</code>, which is the default). In the latter case you will have to do <code>boot cpu</code> again to get to the VAX boot prompt.

==First boot==
Now we can boot the installed system from harddisk for the first time.

If you want to, now would be a good time to take a backup copy of your disk files (or just create a btrfs snapshot or something if you have the possibility ;-)

Okay, then let's boot from DUA0
<pre>
>>>boot dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 1153664
data = 281088
bss = 1043548
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #3: Wed Oct 18 11:49:00 EDT 1995
real mem = 67043328
avail mem = 62008320
Buffer configuration adjusted to run with small system page table
using 121 buffers containing 991232 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
</pre>
Here, it will seem to hang for a loooong time. A few minutes. Don't worry, it will eventually continue to boot. I guess it's probing for other devices which are not present.

You ''might'' be able to speed this up a bit by interrupting SimH (press CTRL+E in the SimH console window) and then using <code>set CPU noidle</code> followed by <code>go</code> to resume emulation.

Eventually, you will have to decide on a hostname. Note that if you want to play around with [[DECnet]] at some point, your hostname should be no longer than 6 characters.
<pre>
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)

*** SYSTEM NAME SPECIFICATION ***

Select the name of your system using alphanumeric characters.
The first character must be a letter. For example, tinker.

Enter your system name: yuki

You selected yuki as the name of your system.
Is this correct? (y/n) [y]: y
</pre>

Next up is the time configuration. Since Ultrix 4.5 is not Y2k compliant (AFAIK), I decided to set the clock back a whopping 20 years. Note that the timezone and daylight saving settings are for my location (Germany) and will probably vary for you.

<pre>
*** DATE AND TIME SPECIFICATION ***

The current date and time should be specified using the following
format:

yymmddhhmm

Use two digits for year (yy), month (mm), day (dd), hour (hh), and
minute (mm). Enter the time in 24-hour format. For example, 02:54
p.m. on Feb 2, 1993 would be entered as:

9302021454

Enter the date and time: 9512052336

*** TIME ZONE SELECTION ***

Select the time zone for your area, using the options listed in the
table below. You can also enter the number of hours (-12 to 12) in
time east of Greenwich.

Selection Time Zone
---------------------------------
e Eastern
c Central
m Mountain
p Pacific
g Greenwich
---------------------------------

Enter your choice: 1

Does your area alternate between Daylight Savings and Standard
time? (y/n) [y]: y

Select your geographic area for Daylight Savings Time, using the
options in the table below.

Selection Geographic Area
--------------------------------
u USA
a Australia
e Eastern Europe
c Central Europe
w Western Europe
--------------------------------

Enter your choice [u]: c

The current date and time is Tue Dec 5 23:36:46 EST 1995
</pre>

Next up is the root password. Note that Ultrix will not echo anything here, I added the asterisks just for this guide :)

<pre>
*** SPECIFY THE SUPERUSER PASSWORD ***
The Guide to Installing ULTRIX instructs you on how to enter
the superuser password.
Changing password for root
Enter new password: ******
Verify: ******
</pre>

Next up is the filesystem layout, which is a bit more involved than what you know from more modern systems like MS DOS ;-)

In ULTRIX, partitions are defined for each disk type in a file called <code>/etc/disktab</code>. Note that the partitions overlap, so you shouldn't use them all at the same time. The setup script actually takes care of that for you, but if you later create a new filesystem on the wrong partition you ''WILL'' lose data!

Normally, partition '''c''' is the whole disk, which is useful for add-on disk drives for example. Partitions '''a''' and '''b''' are always available and are traditionally used for the system and the swap-space respectively. The swap partition is also used for crashdumps if no separate crash-dump partition is created. The rest of the disk can be used either as a single partition (which is usually '''g''') or as 3 individual partitions ('''d''' to '''f'''). If the disk is larger than 1 gigabyte, you will get another partition, '''h''', after the g partition, probably because the filesystem cannot cope with partitions >1gig

In our case, we will have the following partitions on the first disk (RA0):
*Partition '''a''' of 32 mb for /root
*Partition '''b''' of 64 mb for swap+crashdump
*Partition '''c''' of 1.2 gig (whole-disk, not used on our setup)
*Partition '''d''' and '''e''' of 200 mb each (not used)
*Partition '''f''' of 400 mb (not used)
*Partition '''g''' of 800 mb (overlaps with d, e and f; will become /usr)
*Partition '''h''' of 256 mb (will become /usr/var)
This way we still have the whole second disk available for later use.

So here it goes:
<pre>
*** FILE SYSTEM DEFAULT OPTION ***

The following table shows the default file system layout on RA90, ra0:

partition bottom top size overlap default
a 0 32767 32768 c root
b 32768 159839 127072 c swap, dump
d 159840 580036 420197 c,g /usr

If you choose the defaults, the var area will be allocated to /usr/var.

Do you want to choose the default file system layout? (y/n): n
</pre>

No, we do not want to use the defaults...

First, we select disk 1, partition '''g''', for the /usr file system:
<pre>
*** /usr FILE SYSTEM ALLOCATION ***

You can allocate the /usr file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

/usr FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for /usr file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the /usr file system:

partition size (Kbytes) overlap
------------------------------------------------
d --- 210098 c,g
e --- 210098 c,g
f --- 420196 c,g
g --- 840393 c,d,e,f
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the /usr file system [d]: g

Making the new file system for /usr on /dev/rra0g RA90
</pre>

Next, we select disk 1, partition '''b''' for swap (only 1 swap partition) and for crashdumps:

<pre>
*** ALLOCATE THE SWAP1 SPACE ***

You can allocate the swap1 space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

SWAP1 SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for swap1 space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the swap1 space:

partition size (Kbytes) overlap
------------------------------------------------
b --- 63536 c
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the swap1 space [b]: b

*** ALLOCATE THE SWAP2 SPACE ***

Do you want to allocate a second swap space? (y/n) [n]: n

*** ALLOCATE THE CRASH DUMP SPACE ***

You can allocate the crash dump space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

CRASH DUMP SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for crash dump space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the crash dump space:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
b --- 63536 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the crash dump space [b]: b
</pre>

Finally we select partiton '''h''' for the /var file system. This might not be large enough later on but then we can always migrate the data away if we need to...

<pre>
*** ALLOCATE THE var FILE SYSTEM ***

You can allocate the var file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

var FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for var file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the var file system:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
g --- 840393 c,d,e,f
------------------------------------------------

Type the letter of the partition on which you want
to allocate the var file system [no default]: h

Making the new file system for var on /dev/rra0h RA90
</pre>

==Installing the distribution files==

Next up we have to decide what ''packages'' we want to install (yes, ULTRIX already had its own package format and corresponding installer called ''setld''. It is very basic, probably most similar to ''pkg_add'' on NetBSD). We simply install everything, since we have enough space :)

<pre>
This distribution media includes subsets for ULTRIX Worksystem
Software (UWS). A UWS license (on a workstation) or a UWS Server
License (on a timesharing machine or server) is required to install
these subsets.

Do you want to install ULTRIX Worksystem Software? y/n []: y

*** SUPPORTED SOFTWARE INSTALLATION ***

*** Select the DECwindows User Interface ***

1) DECwindows for OSF/Motif
2) X11/DECwindows (XUI)

Enter your choice [1]: 2

*** Enter Subset Selections ***

The following subsets are mandatory and will be installed automatically:
* Base System * Kernel Config Files
* TCP/IP Networking Utilities * Network File System Utilities
* Extended (Berkeley) Mailer * X11/DECwindows Servers
* X11/DECwindows User Environment * X11/DECwindows 75dpi Fonts

The subsets listed below are optional:
1) Printer Support Environment 2) RAND Mail Handler
3) Sys. Config. Mgmt. Program (SCAMP) 4) Communications Utilities
5) Unix-to-Unix Copy Facility 6) Maintenance Operations Protocol
7) Accounting Software 8) Kerberos Network Authentication
9) Enhanced Security Features 10) Prestoserve Utilities
11) System Exerciser Package 12) Bisynchronous Communications
13) Doc. Preparation for Ref. Pages 14) Doc. Preparation Extensions
15) Adobe Font Metric Files 16) Software Development Utilities
17) Source Code Control System 18) Internationalization Runtime Env.
19) Internationalization Dev. Env. 20) CDA Base System
21) CDA Software Dev Libraries 22) RPC Runtime Environment
23) RPC Development Environment 24) Pascal Development Package
25) VAX C/ULTRIX 26) Ref. Pages for Sys. Admin. & Users
27) Reference Pages for Programers 28) Programming Examples
29) Ultrix SPDS 30) X11/DECwindows 100dpi Fonts
31) VS35XX X11/DECwindows Fonts 32) Additional DECwindows Applications
33) DECwindows Mail Application 34) Worksystem Development Environment
35) X11/DECwindows System Management T 36) UWS Runtime Reference Pages
37) UWS Development Reference Pages

38) All mandatory and all optional subsets
39) Mandatory subsets only
40) Exit without installing subsets

Enter your choice(s): 38
Working....Wed Dec 6 00:14:12 EST 1995

You are installing the following subsets:
Base System Kernel Config Files
TCP/IP Networking Utilities Network File System Utilities
Extended (Berkeley) Mailer X11/DECwindows Servers
X11/DECwindows User Environment X11/DECwindows 75dpi Fonts
Printer Support Environment RAND Mail Handler
Sys. Config. Mgmt. Program (SCAMP) Communications Utilities
Unix-to-Unix Copy Facility Maintenance Operations Protocol
Accounting Software Kerberos Network Authentication
Enhanced Security Features Prestoserve Utilities
System Exerciser Package Bisynchronous Communications
Doc. Preparation for Ref. Pages Doc. Preparation Extensions
Adobe Font Metric Files Software Development Utilities
Source Code Control System Internationalization Runtime Env.
Internationalization Dev. Env. CDA Base System
CDA Software Dev Libraries RPC Runtime Environment
RPC Development Environment Pascal Development Package
VAX C/ULTRIX Ref. Pages for Sys. Admin. & Users
Reference Pages for Programers Programming Examples
Ultrix SPDS X11/DECwindows 100dpi Fonts
VS35XX X11/DECwindows Fonts Additional DECwindows Applications
DECwindows Mail Application Worksystem Development Environment
X11/DECwindows System Management To UWS Runtime Reference Pages
UWS Development Reference Pages

Is this correct? (y/n): y
</pre>

The installation will take a while (around 15-30 minutes for me), so feel free to let it run in the background for a while now. The installer will periodically print its status so you can see that it's still running...

<pre>
Base System (ULTBASE450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:14:43 EST 1995
Verifying

Kernel Config Files (ULTBIN450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:15:28 EST 1995
Verifying

...
</pre>

At some point you will have to confirm installing the generic kernel and the X11 subsystem:

<pre>
...
UWS Runtime Reference Pages (UWSMAN450)
Copying from /mnt/VAX/BASE (disk)
Verifying

UWS Development Reference Pages (UWSMANPGMR450)
Copying from /mnt/VAX/BASE (disk)
Verifying

The installation software has successfully installed the software
subsets.
Installing Upgrade subsets
The following subsets will be installed:
* X11/DECwindows Servers Upgrade * Generic Kernel
Do you wish to continue? (y/n): y

X11/DECwindows Servers Upgrade (UWSSER451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

Generic Kernel (ULTGENVMUNIX451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

The installation procedure has successfully installed the Upgrade
subsets
</pre>

That's it for the base installation, now we configure our kernel...

==Kernel configuration==
We have to select what features will be in the kernel. For anyone who has ever done a "make menuconfig" on Linux, this is ''slightly'' easier here ;-)
<pre>
*** CONFIGURATION FILE KERNEL OPTION SELECTION ***

Selection Kernel Option
---------------------------------------------------------------
1 Local Area Transport (LAT)
2 Bisynchronous Communication protocol (VAX only)
3 Computer Interconnect (CI) network
4 Diagnostic/Utilities Protocol (DUP)
5 ISO9660 File System Support (CDFS)
6 Ethernet Packet Filter
7 Enhanced Security Features
8 All of the above
9 None of the above
----------------------------------------------------------------

Enter the selection number for each kernel option you want.
For example, 1 3 :
</pre>

In our case, we don't need 2 (it is for 2780/3780 remote terminals), 3 (SimH doesn't emulate any cluster hardware) or 6 (it might cause problems with DECwindows/Motif). Everything else (<code>1 4 5 7</code>) is probably safe. This lets us play around with LAT (maybe connect an emulated Cisco router with LAT routing to it?) and DUP.

<pre>
Enter the selection number for each kernel option you want.
For example, 1 3 : 1 4 5 7

You specified the following kernel options:

Local Area Transport (LAT)
Diagnostic/Utilities Protocol (DUP)
ISO9660 File System Support (CDFS)
Enhanced Security Features

Is this correct? (y/n) [n]: y

*** SYSTEM CONFIGURATION PROCEDURE ***
The installation software found these devices in the floating
address space:

dz0 on uba0 at 0160100
dz1 on uba0 at 0160110
dz2 on uba0 at 0160120
dz3 on uba0 at 0160130

Configuration file complete.

Do you want to edit the configuration file? (y/n) [n]: n

*** PERFORMING SYSTEM CONFIGURATION ***

working ..... Wed Dec 6 02:29:10 EST 1995

*** DEVICE SPECIAL FILE CREATION ***
working ..... Wed Dec 6 02:29:53 EST 1995

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 800985B5
</pre>

Now you might want to take another backup of your disk images, since the ULTRIX installation is now basically complete.

==Adding the unsupported sets==
Now there are some more pieces of software in the CDROM, in a directory called ''unsupported''. We want to install these as well. First, let's boot our system again

<pre>
>>>b dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 747376
data = 125952
bss = 918192
Starting at 0x2c19

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
real mem = 67043328
avail mem = 56455168
using 1638 buffers containing 6712320 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
dz0 at uba0 csr 160100 vec 300, ipl 17
dz1 at uba0 csr 160110 vec 310, ipl 17
dz2 at uba0 csr 160120 vec 320, ipl 17
dz3 at uba0 csr 160130 vec 330, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
Wed Dec 6 11:25:29 MET 1995
Automatic reboot in progress...
/dev/ra0a: 644 files, 6161 used, 9390 free (166 frags, 1153 blocks, 5.0% fragmentation)
/dev/rra0g: umounted cleanly
/dev/rra0h: umounted cleanly
Warning Creating new license database
Warning creating new history file
check quotas: done.
savecore: checking for dump...dump does not exist
local daemons: syslog sendmail.
Removing remnant Opser files
preserving editor files
clearing /tmp
standard daemons: update cron accounting network snmpd printer.
start errlog daemon - elcsd
Wed Dec 6 11:25:48 MET 1995

ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
UWS V4.5 (Rev. 6)

Digital Equipment Corporation
Nashua, New Hampshire

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

#
</pre>

now, we mount the CDROM and use <code>setld</code> to install the unsupported packages. For simplicity's sake, we just (again) install everything.

<pre>
# mount -r /dev/ra2c /mnt
# cd /mnt/VAX/UNSUPPORTED
# ls
DXVUNDEMO450 ULXDOC450 ULXINGRES450 ULXRCS450 ULXUNMAN450
ULXAPL450 ULXEDIT450 ULXLEARN450 ULXSHELLS450 ULXUNMIT450
ULXBASE450 ULXF77450 ULXLISP450 ULXSPMS450 ULXVARIAN450
ULXBIB450 ULXGAMES450 ULXMAN450 ULXTERM450 instctrl
ULXCOURIER450 ULXHYPER450 ULXMOD2450 ULXTOOLS450
ULXCPM450 ULXICON450 ULXNEWS450 ULXUNEXAMP450
ULXDCMT450 ULXINET450 ULXNOTES450 ULXUNFONTS450
# setld -l .

*** Enter Subset Selections ***

The subsets listed below are optional:
1) Base Extension 2) GNU Emacs
3) TCP/IP Networking Util Extension 4) Additional Terminal Drivers
5) Document Preparation Software 6) Games and Diversions
7) Supplementary Documentation 8) Bibliographic Utilities
9) Remote Procedure Call Compiler 10) Aux. Command Line Interpreters
11) USENET News Interface Software 12) Notesfiles Package
13) Revision Control System 14) Misc. User-Contributed Utilities
15) Computer Aided System Tutor 16) Franz Lisp Development Package
17) Modula-2 Development Package 18) Raster Plotter Package
19) APL Development Package 20) CP/M 8in Diskette Utility
21) Hyperchannel Utilities 22) ICON (Language) Development Packag
23) University Ingres QUEL DBMS 24) Software Project Management System
25) Unsupported Fortran Utilities 26) Unsupported On-Line Documentation
27) Unsupported X11 Components 28) Unsupported DECwindows Examples
29) Unsupported MIT Fonts 30) Unsupported X11 Reference Pages
31) Unsupported OSF/Motif Demos

32) All mandatory and all optional subsets
33) Mandatory subsets only
34) Exit without installing subsets

Enter your choice(s): 32
Working....Wed Dec 6 11:29:48 MET 1995
Wed Dec 6 11:30:00 MET 1995

You are installing the following subsets:
Base Extension GNU Emacs
TCP/IP Networking Util Extension Additional Terminal Drivers
Document Preparation Software Games and Diversions
Supplementary Documentation Bibliographic Utilities
Remote Procedure Call Compiler Aux. Command Line Interpreters
USENET News Interface Software Notesfiles Package
Revision Control System Misc. User-Contributed Utilities
Computer Aided System Tutor Franz Lisp Development Package
Modula-2 Development Package Raster Plotter Package
APL Development Package CP/M 8in Diskette Utility
Hyperchannel Utilities ICON (Language) Development Package
University Ingres QUEL DBMS Software Project Management System
Unsupported Fortran Utilities Unsupported On-Line Documentation
Unsupported X11 Components Unsupported DECwindows Examples
Unsupported MIT Fonts Unsupported X11 Reference Pages
Unsupported OSF/Motif Demos

Is this correct? (y/n): y

Base Extension (ULXBASE450)
Copying from . (disk)
Verifying

GNU Emacs (ULXEDIT450)
Copying from . (disk)
Verifying

TCP/IP Networking Util Extension (ULXINET450)
Copying from . (disk)
Verifying
...
</pre>

Note that you could also quickly install only a single package by using for example
# setld -l . ULXINET450

After a few minutes, installation will be completed and we should unmount the CDROM
# cd /
# umount /mnt

==Network configuration==
To configure the network, you have to use a static IPv4 address and put that into the beginning of /etc/rc.local. Note that there is no <code>ifconfig -a</code> in ULTRIX, you have to use <code>netstat -i</code>

<pre>
# netstat -i
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
qe0* 1500 none none 0 0 0 0 0
lo0 1536 loop localhost 1 0 1 0 0
# ifconfig qe0 192.168.1.44 netmask 255.255.255.0 up
# route add default 192.168.1.1 1
add net default: gateway 192.168.1.1
# ping 192.168.1.1
192.168.1.1 is alive
</pre>
Note that it might actually take a while until packets are getting through. I don't know why but in my case it helped to ping ULTRIX from the outside first, e.g. from Windows, and then re-try the ping from the VM. Then it worked. I'm guessing this is some SimH/Windows issue with PCAP or something.

Then put these 2 commands at the start of <code>/etc/rc.local</code> (you'll see where). Note that you can use <code>vi</code> now!
<pre>
# @(#)rc.local 9.4 (ULTRIX) 9/21/95
/bin/hostname yuki
#/etc/ifconfig HDWR `/bin/hostname` broadcast NETNUM.0 netmask 255.0
/etc/ifconfig qe0 192.168.1.44 netmask 255.255.255.0
route add default 192.168.1.1 1
/etc/ifconfig lo0 localhost
#/etc/bscconfig dup0 bsc 1
#/etc/bscconfig dpv0 bsc 1
...
</pre>

==Shutting down cleanly==
As you'd expect, you can use <code>shutdown</code> to shut the system down
<pre>
# shutdown -h now
Shutdown at 11:15 (in 0 minutes) [pid 1500]
#
System shutdown time has arrived
syncing disks... done

?06 HLT INST
PC = 80094CDD
>>>
</pre>

==Enabling outside access==
The SimH config above includes a 16-line serial multiplexer. If you connect via TELNET to port 1005, you are given the first free serial line of the emulated DZ device. However, serial login is disabled by default, so it has to be enabled first. That's what the <code>/etc/ttys</code> file is for. Edit the file and change the ''off'' to ''on'' in the lines for tty00 to tty07, as shown below
<pre>
# @(#)ttys 9.1 (ULTRIX) 4/26/94
#
#
#
# name getty type status comments
#
console "/etc/getty std.9600" vt100 on secure # console terminal
tty00 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty01 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty02 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty03 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty04 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty05 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty06 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty07 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
ttyd0 "/etc/getty std.9600" vt100 off shared secure # modem line
</pre>

If you want to be able to login as root on these terminals, you can also add the <code>secure</code> flag as well. Also note that while it seems tempting to increase the line speed to 19200 or even higher, from my experience that will cause massive lags and emulation hangs in SimH, so do that on your own risk.

After editing the file and saving it, you have to reload init:
# kill -HUP 1

Now try logging in to port 1005 via telnet, and you should be greeted with this:
<pre>
Connected to the MicroVAX 3900 simulator DZ device, line 0

ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:
Requires secure terminal
</pre>

Note that SimH will print out the serial line to which you are connected, in this case line 0 which is /dev/tty00.

Also, if your inetd is running (which it should be, if you followed this guide), you will also already be able to login remotely using telnet.
<pre>
ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:
Requires secure terminal
</pre>
To enable root access for all telnet sessions, you will have to edit the /etc/ttys file and change every line that starts with "ttyp" to include the secure flag:
ttyp0 none network
will become
ttyp0 none network secure
and so on...

==Resources==
Some of the resources I used for creating this guide:
*ULTRIX 4.5 installation ISO [http://musall.de/mirrors/ultrix/ultrix_os/vax/]
*ULTRIX-32 startup and shutdown guide [http://bitsavers.trailing-edge.com/pdf/dec/vax/ultrix-32/3.0/AA-ME91A-TE_ULTRIX-32_Guide_to_System_Shutdown_and_Startup.pdf]
*CERN guide to installing ULTRIX [https://web-docs.gsi.de/~kraemer/COLLECTION/ULTRIX/wwwpdp.web.cern.ch/wwwpdp/as/file/doc/ultrix/ultrix.pdf]
*My old guide for installing ULTRIX [https://docs.google.com/document/d/1ULRhzE0R1twarB5hfJm85yqOdTeoFCGgyPr5AxYEIbE]
*DEC KA655 CPU System Maintenance [http://bitsavers.trailing-edge.com/pdf/dec/vax/655/EK-306A-MG-001_655Mnt_Mar89.pdf]
*Some notes and links to more ULTRIX information [https://web-docs.gsi.de/~kraemer/COLLECTION/ULTRIX/docs.html]

[[Category:SIMH Tutorials]]

Installing Ultrix 4.5 on SIMH

2015-12-06T10:55:19Z

Darkstar: /* Resources */

This WORK-IN-PROGRESS guide will be a simple guide to installing ULTRIX 4.5 for VAX on SimH.

==Requirements==
The following is a list of things required for installation
*A recent version of the [[SIMH]] emulator
**Make sure the binary you're using includes Ethernet support
**I'm using a self-compiled version (git revision 0e8c0aea)
*An ISO image of ULTRIX 4.5 for VAX
**See the "Resources" section for a download link
**It's probably also possible to install it from tape, although I don't know if any installation tapes for ULTRIX 4.5 exist
*Optional stuff (might get added to the guide later):
**Starfish Ultrix Freeware CDs from [http://musall.de/mirrors/ultrix/freeware/ here]

==SimH configuration==
The machine I'm using to run ULTRIX has the following configuration
*DEC MicroVAX 3800
*64mb memory
*DELQA network card (XQ0)
*Two [[RA90]] disk drives (with 1.2gb each) attached to an RQDX3 controller (RQ0 and RQ1)
*CD ROM drive attached to the same RQDX3 controller as unit 2 (RQ2)
*[[TK50]] tape attached as unit 0 on the first TQK50 controller (TQ0)
*DZV11 terminal multiplexer with 16 lines, attached to telnet port 1005 (DZ)
*LPT line printer attached to text file <code>printer_output.txt</code>

Here's my config file (I called it <code>simh.conf</code>)
<pre><nowiki>
;
; SimH 4.0 Configuration file for MicroVAX 3800
;
; Host System : DEC MicroVAX 3800
; Operating System : DEC Ultrix v4.5
; Memory : 64mb
; Network config : XQ: Ethernet, 08:00:2b:04:14:02
; Disks : RQ0: RA90, 1.2gb
; RQ1: RA90, 1.2gb
; CDROMs : RQ2: iso file
; Tape config : TQ0: TK50, 94mb
;

load -r ka655x.bin

; NVRAM
attach NVR nvram.bin

; CPU config
set CPU 64m
set CPU conhalt
set CPU idle=all

; configure console to 7-bit only
set TTO 7b
set TTI 7b

; Disk drives
set RQ0 ra90
attach RQ0 rq0-ra90.dsk
set RQ1 ra90
attach RQ1 rq1-ra90.dsk
set RQ2 CDROM
attach -r RQ2 ultrix-vax-os-v4.5.mode1.ufs.iso
; MD5 sum: 19df0753c27f195e9f1d2f139a3b4629 *ultrix-vax-os-v4.5.mode1.ufs.iso
set RQ3 dis

; Tape
set TQ tk50
;attach tq0 filename-to-tape-file
set TQ1 dis
set TQ2 dis
set TQ3 dis

; serial port, simulated by Telnet to port 1005
set DZ LINES=16
set DZ 8B
attach DZ 1005 NoBuffer

; printer
set LPT enable
attach LPT printer_output.txt

; Disable unused peripherals
set CR dis
set RL dis
set TS dis

; Network interface (08-00-2b is the DEC prefix, the 04-14-02 part is arbitrary)
set XQ MAC=08-00-2b-04-14-02
attach XQ0 eth0

; serial console (launch directly after booting CPU)
set console telnet=1001

; experimental
;set QVSS en

; boot the system
;boot CPU
</nowiki></pre>
Note that I'm using a telnet console (for easier copy/paste on Windows), which means that directly after running this config file (via <code>do simh.conf</code> from Simh) you will need to connect via telnet to localhost:1001 or the boot will abort. If you are on Linux, or just don't want that, remove the <code>set console telnet=1001</code> line.

Also note that you might need to attach XQ0 to a different ethernet device. Use "show ether" in SimH to list all available devices on your system and modify the <code>attach XQ0 eth0</code> line accordingly.

==Running the Emulator==
Either run <code>vax.exe simh.conf</code> from the Windows command line, or just double-click the VAX.EXE executable and type <code>do simh.conf</code>.

On the first launch it might take some time because SimH has to create the disk images (~2.5 gb total). It should look something like this
<pre><nowiki>
MicroVAX 3900 simulator V4.0-0 Beta git commit id: 0e8c0aea
NVR: buffering file in memory
RQ2: unit is read only
Listening on port 1005
WinPcap version 4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008)
Eth: opened OS device \Device\NPF_{A41A1651-DD4D-4735-A4E0-88353165C2EC}
Listening on port 1001
sim>
</nowiki></pre>

Type the following to start the emulation (note: you can also uncomment that line from the end of the config file to have the emulation start right away)
sim> boot cpu
Waiting for console Telnet connection

Now would be a good time to connect your telnet session (I use a batch file for this), otherwise the boot process will timeout.

On your console, you should see something like this:
<pre><nowiki>
Connected to the MicroVAX 3900 simulator CON-TEL device

KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>
</nowiki></pre>

This is the VAX's boot prompt. Normally you just type
>>>boot <device>
where <device> is one of the following
*MUA<num>: TK tape device number <num> (1 to 4)
*DUA<num>: RQ disk device number <num> (1 to 4)

You can use <code>show device</code> to see the installed (and detected) devices you can boot from, and <code>show boot</code> to see which device will be the default if you just type <code>boot</code> (or <code>b</code> for short):
<pre><nowiki>
>>>show device
UQSSP Disk Controller 0 (772150)
-DUA0 (RA90)
-DUA1 (RA90)
-DUA2 (RRD40)

UQSSP Tape Controller 0 (774500)
-MUA0 (TK50)

Ethernet Adapter 0 (774440)
-XQA0 (08-00-2B-04-14-02)
>>>show boot
MUA0
</nowiki></pre>

Since we want to boot from CDROM, which is unit 2, we can use
>>>boot DUA2

Note: You can add flags to boot into single user mode, or to boot in interactive mode (so-called ''conversational boot'', where the system prompts you for a kernel file name to load). For details see the Guide to ULTRIX-32 System Startup and Shutdown, linked to in the ''References'' section. To use it, add the <code>/R5:<flags></code> option to the <code>boot</code> command, where flags is 0 (default multi-user), 1 (conversational multi-user), 2 (single-user) or 3 (conversational single-user). For example
>>>boot/r5:3 dua0

Note: You can also boot from ethernet (<code>boot XQA0</code>) but this requires a DEC-specific boot server in your network (the protocol is called ''MOP'' for ''Maintenance Operations Protocol''), which is beyond the scope of this document. I did get it to work a few years ago though, but it was a bit difficult to set up.

For a list and description of all commands available in the bootloader (hint: there are lots), see the ''KA655 CPU System Maintenance'' guide mentioned in the ''References'' section..

==Bootstrapping ULTRIX==
You will see the following output on the first boot.
<pre>
>>>boot dua2
(BOOT/R5:0 DUA2

2..
-DUA2
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 945424
data = 1290240
bss = 757940
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #2: Wed Oct 18 12:06:55 EDT 1995
real mem = 67043328
avail mem = 61517824
Buffer configuration adjusted to run with small system page table
using 123 buffers containing 1007616 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
WARNING: clock gained 47 days -- CHECK AND RESET THE DATE!

*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice:
</pre>
Now we want to do an ''ADVANCED Installation'', but when we try to, it will take a few seconds until the installation program dumps us to a prompt because it couldn't find a valid device to install from and to:
<pre>
Enter your choice: 2

*** SOFTWARE DISTRIBUTION DEVICE SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of software distribution devices and which installation media you should
load on it:

No valid device is found.
Contact a DIGITAL field service representative.

#
</pre>

The problem seems to be that the hardware SimH emulates is not fully supported by ULTRIX (or is misdetected -- I'm not entirely sure myself). The good thing is that the internet has the correct solution, which is to fix some lines in the installation shell script. The fact that the basic system that is running at this point doesn't have ''vi'', or even ''cat'', makes this a bit harder ;-)

The only option you have is ''ed'', the old UNIX editor. For a quick introduction, see [http://blog.sanctum.geek.nz/actually-using-ed/ here].

To load the file in the editor, use
# '''ed install.1'''
16763

You can see the entire file with
1,$l
but be warned, the output is quite long and it'll take some time to print it all out.

To fix it, use the following commands (the lines in '''bold''' is what you type, everything else is the response from ed)
# '''ed install.1'''
16763
'''173l'''
BTD=`btd`
'''173s/`btd`/ra2/'''
'''173l'''
BTD=ra2
'''193l'''
rz* )
'''193s/rz/ra/'''
'''193l'''
ra* )
'''w'''
16761
'''q'''
#

First, we list line 173, then we change it from <code>BTD=`btd`</code> to <code>BTD=ra2</code>, which happens to be the CDROM device and unit number we're installing from (if you changed that in your config, use the correct name here!)

Then we change line 193 from <code>rz* )</code> to <code>ra* )</code> since we're trying to install on an RA type disk which was apparently not supported in ULTRIX out of the box.

After writing the file with <code>w</code> and quitting ed with <code>q</code>, we're back at the prompt, at which point we can use CTRL+D to retry the installation:

<pre>
# ^D
*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice: 2

*** SYSTEM DISK SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of system disk drives. Select one of the devices below to contain the
root file system:

SYSTEM DISK TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk drive
is on line and write-enabled (if applicable to your disk drive), then
confirm your choice.

Use RA90, ra0, for your system disk? (y/n) []: y

The installation procedure now allocates the root file system on
partition 'a' of the system disk, ra0 RA90.

Making the root file system on ra0 RA90.

The installation procedure is now restoring the root file system to
partition 'a' of the system disk, ra0 RA90.

The installation procedure now checks the root file system on partition 'a'
of the system disk, ra0 RA90.
** /dev/rra0a
** Last Mounted on /mnt
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
226 files, 4547 used, 11004 free (20 frags, 1373 blocks, 1.0% fragmentation)

*** BOOTSTRAP COMMAND SEQUENCE ***

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 8007F799
>>>
</pre>
After this, you will be back at the VAX boot prompt (if you used <code>set CPU CONHALT</code> in your config) or at the SimH emulator prompt (if you used <code>set CPU SIMHALT</code>, which is the default). In the latter case you will have to do <code>boot cpu</code> again to get to the VAX boot prompt.

==First boot==
Now we can boot the installed system from harddisk for the first time.

If you want to, now would be a good time to take a backup copy of your disk files (or just create a btrfs snapshot or something if you have the possibility ;-)

Okay, then let's boot from DUA0
<pre>
>>>boot dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 1153664
data = 281088
bss = 1043548
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #3: Wed Oct 18 11:49:00 EDT 1995
real mem = 67043328
avail mem = 62008320
Buffer configuration adjusted to run with small system page table
using 121 buffers containing 991232 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
</pre>
Here, it will seem to hang for a loooong time. A few minutes. Don't worry, it will eventually continue to boot. I guess it's probing for other devices which are not present.

You ''might'' be able to speed this up a bit by interrupting SimH (press CTRL+E in the SimH console window) and then using <code>set CPU noidle</code> followed by <code>go</code> to resume emulation.

Eventually, you will have to decide on a hostname. Note that if you want to play around with [[DECnet]] at some point, your hostname should be no longer than 6 characters.
<pre>
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)

*** SYSTEM NAME SPECIFICATION ***

Select the name of your system using alphanumeric characters.
The first character must be a letter. For example, tinker.

Enter your system name: yuki

You selected yuki as the name of your system.
Is this correct? (y/n) [y]: y
</pre>

Next up is the time configuration. Since Ultrix 4.5 is not Y2k compliant (AFAIK), I decided to set the clock back a whopping 20 years. Note that the timezone and daylight saving settings are for my location (Germany) and will probably vary for you.

<pre>
*** DATE AND TIME SPECIFICATION ***

The current date and time should be specified using the following
format:

yymmddhhmm

Use two digits for year (yy), month (mm), day (dd), hour (hh), and
minute (mm). Enter the time in 24-hour format. For example, 02:54
p.m. on Feb 2, 1993 would be entered as:

9302021454

Enter the date and time: 9512052336

*** TIME ZONE SELECTION ***

Select the time zone for your area, using the options listed in the
table below. You can also enter the number of hours (-12 to 12) in
time east of Greenwich.

Selection Time Zone
---------------------------------
e Eastern
c Central
m Mountain
p Pacific
g Greenwich
---------------------------------

Enter your choice: 1

Does your area alternate between Daylight Savings and Standard
time? (y/n) [y]: y

Select your geographic area for Daylight Savings Time, using the
options in the table below.

Selection Geographic Area
--------------------------------
u USA
a Australia
e Eastern Europe
c Central Europe
w Western Europe
--------------------------------

Enter your choice [u]: c

The current date and time is Tue Dec 5 23:36:46 EST 1995
</pre>

Next up is the root password. Note that Ultrix will not echo anything here, I added the asterisks just for this guide :)

<pre>
*** SPECIFY THE SUPERUSER PASSWORD ***
The Guide to Installing ULTRIX instructs you on how to enter
the superuser password.
Changing password for root
Enter new password: ******
Verify: ******
</pre>

Next up is the filesystem layout, which is a bit more involved than what you know from more modern systems like MS DOS ;-)

In ULTRIX, partitions are defined for each disk type in a file called <code>/etc/disktab</code>. Note that the partitions overlap, so you shouldn't use them all at the same time. The setup script actually takes care of that for you, but if you later create a new filesystem on the wrong partition you ''WILL'' lose data!

Normally, partition '''c''' is the whole disk, which is useful for add-on disk drives for example. Partitions '''a''' and '''b''' are always available and are traditionally used for the system and the swap-space respectively. The swap partition is also used for crashdumps if no separate crash-dump partition is created. The rest of the disk can be used either as a single partition (which is usually '''g''') or as 3 individual partitions ('''d''' to '''f'''). If the disk is larger than 1 gigabyte, you will get another partition, '''h''', after the g partition, probably because the filesystem cannot cope with partitions >1gig

In our case, we will have the following partitions on the first disk (RA0):
*Partition '''a''' of 32 mb for /root
*Partition '''b''' of 64 mb for swap+crashdump
*Partition '''c''' of 1.2 gig (whole-disk, not used on our setup)
*Partition '''d''' and '''e''' of 200 mb each (not used)
*Partition '''f''' of 400 mb (not used)
*Partition '''g''' of 800 mb (overlaps with d, e and f; will become /usr)
*Partition '''h''' of 256 mb (will become /usr/var)
This way we still have the whole second disk available for later use.

So here it goes:
<pre>
*** FILE SYSTEM DEFAULT OPTION ***

The following table shows the default file system layout on RA90, ra0:

partition bottom top size overlap default
a 0 32767 32768 c root
b 32768 159839 127072 c swap, dump
d 159840 580036 420197 c,g /usr

If you choose the defaults, the var area will be allocated to /usr/var.

Do you want to choose the default file system layout? (y/n): n
</pre>

No, we do not want to use the defaults...

First, we select disk 1, partition '''g''', for the /usr file system:
<pre>
*** /usr FILE SYSTEM ALLOCATION ***

You can allocate the /usr file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

/usr FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for /usr file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the /usr file system:

partition size (Kbytes) overlap
------------------------------------------------
d --- 210098 c,g
e --- 210098 c,g
f --- 420196 c,g
g --- 840393 c,d,e,f
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the /usr file system [d]: g

Making the new file system for /usr on /dev/rra0g RA90
</pre>

Next, we select disk 1, partition '''b''' for swap (only 1 swap partition) and for crashdumps:

<pre>
*** ALLOCATE THE SWAP1 SPACE ***

You can allocate the swap1 space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

SWAP1 SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for swap1 space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the swap1 space:

partition size (Kbytes) overlap
------------------------------------------------
b --- 63536 c
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the swap1 space [b]: b

*** ALLOCATE THE SWAP2 SPACE ***

Do you want to allocate a second swap space? (y/n) [n]: n

*** ALLOCATE THE CRASH DUMP SPACE ***

You can allocate the crash dump space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

CRASH DUMP SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for crash dump space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the crash dump space:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
b --- 63536 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the crash dump space [b]: b
</pre>

Finally we select partiton '''h''' for the /var file system. This might not be large enough later on but then we can always migrate the data away if we need to...

<pre>
*** ALLOCATE THE var FILE SYSTEM ***

You can allocate the var file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

var FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for var file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the var file system:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
g --- 840393 c,d,e,f
------------------------------------------------

Type the letter of the partition on which you want
to allocate the var file system [no default]: h

Making the new file system for var on /dev/rra0h RA90
</pre>

==Installing the distribution files==

Next up we have to decide what ''packages'' we want to install (yes, ULTRIX already had its own package format and corresponding installer called ''setld''. It is very basic, probably most similar to ''pkg_add'' on NetBSD). We simply install everything, since we have enough space :)

<pre>
This distribution media includes subsets for ULTRIX Worksystem
Software (UWS). A UWS license (on a workstation) or a UWS Server
License (on a timesharing machine or server) is required to install
these subsets.

Do you want to install ULTRIX Worksystem Software? y/n []: y

*** SUPPORTED SOFTWARE INSTALLATION ***

*** Select the DECwindows User Interface ***

1) DECwindows for OSF/Motif
2) X11/DECwindows (XUI)

Enter your choice [1]: 2

*** Enter Subset Selections ***

The following subsets are mandatory and will be installed automatically:
* Base System * Kernel Config Files
* TCP/IP Networking Utilities * Network File System Utilities
* Extended (Berkeley) Mailer * X11/DECwindows Servers
* X11/DECwindows User Environment * X11/DECwindows 75dpi Fonts

The subsets listed below are optional:
1) Printer Support Environment 2) RAND Mail Handler
3) Sys. Config. Mgmt. Program (SCAMP) 4) Communications Utilities
5) Unix-to-Unix Copy Facility 6) Maintenance Operations Protocol
7) Accounting Software 8) Kerberos Network Authentication
9) Enhanced Security Features 10) Prestoserve Utilities
11) System Exerciser Package 12) Bisynchronous Communications
13) Doc. Preparation for Ref. Pages 14) Doc. Preparation Extensions
15) Adobe Font Metric Files 16) Software Development Utilities
17) Source Code Control System 18) Internationalization Runtime Env.
19) Internationalization Dev. Env. 20) CDA Base System
21) CDA Software Dev Libraries 22) RPC Runtime Environment
23) RPC Development Environment 24) Pascal Development Package
25) VAX C/ULTRIX 26) Ref. Pages for Sys. Admin. & Users
27) Reference Pages for Programers 28) Programming Examples
29) Ultrix SPDS 30) X11/DECwindows 100dpi Fonts
31) VS35XX X11/DECwindows Fonts 32) Additional DECwindows Applications
33) DECwindows Mail Application 34) Worksystem Development Environment
35) X11/DECwindows System Management T 36) UWS Runtime Reference Pages
37) UWS Development Reference Pages

38) All mandatory and all optional subsets
39) Mandatory subsets only
40) Exit without installing subsets

Enter your choice(s): 38
Working....Wed Dec 6 00:14:12 EST 1995

You are installing the following subsets:
Base System Kernel Config Files
TCP/IP Networking Utilities Network File System Utilities
Extended (Berkeley) Mailer X11/DECwindows Servers
X11/DECwindows User Environment X11/DECwindows 75dpi Fonts
Printer Support Environment RAND Mail Handler
Sys. Config. Mgmt. Program (SCAMP) Communications Utilities
Unix-to-Unix Copy Facility Maintenance Operations Protocol
Accounting Software Kerberos Network Authentication
Enhanced Security Features Prestoserve Utilities
System Exerciser Package Bisynchronous Communications
Doc. Preparation for Ref. Pages Doc. Preparation Extensions
Adobe Font Metric Files Software Development Utilities
Source Code Control System Internationalization Runtime Env.
Internationalization Dev. Env. CDA Base System
CDA Software Dev Libraries RPC Runtime Environment
RPC Development Environment Pascal Development Package
VAX C/ULTRIX Ref. Pages for Sys. Admin. & Users
Reference Pages for Programers Programming Examples
Ultrix SPDS X11/DECwindows 100dpi Fonts
VS35XX X11/DECwindows Fonts Additional DECwindows Applications
DECwindows Mail Application Worksystem Development Environment
X11/DECwindows System Management To UWS Runtime Reference Pages
UWS Development Reference Pages

Is this correct? (y/n): y
</pre>

The installation will take a while (around 15-30 minutes for me), so feel free to let it run in the background for a while now. The installer will periodically print its status so you can see that it's still running...

<pre>
Base System (ULTBASE450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:14:43 EST 1995
Verifying

Kernel Config Files (ULTBIN450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:15:28 EST 1995
Verifying

...
</pre>

At some point you will have to confirm installing the generic kernel and the X11 subsystem:

<pre>
...
UWS Runtime Reference Pages (UWSMAN450)
Copying from /mnt/VAX/BASE (disk)
Verifying

UWS Development Reference Pages (UWSMANPGMR450)
Copying from /mnt/VAX/BASE (disk)
Verifying

The installation software has successfully installed the software
subsets.
Installing Upgrade subsets
The following subsets will be installed:
* X11/DECwindows Servers Upgrade * Generic Kernel
Do you wish to continue? (y/n): y

X11/DECwindows Servers Upgrade (UWSSER451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

Generic Kernel (ULTGENVMUNIX451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

The installation procedure has successfully installed the Upgrade
subsets
</pre>

That's it for the base installation, now we configure our kernel...

==Kernel configuration==
We have to select what features will be in the kernel. For anyone who has ever done a "make menuconfig" on Linux, this is ''slightly'' easier here ;-)
<pre>
*** CONFIGURATION FILE KERNEL OPTION SELECTION ***

Selection Kernel Option
---------------------------------------------------------------
1 Local Area Transport (LAT)
2 Bisynchronous Communication protocol (VAX only)
3 Computer Interconnect (CI) network
4 Diagnostic/Utilities Protocol (DUP)
5 ISO9660 File System Support (CDFS)
6 Ethernet Packet Filter
7 Enhanced Security Features
8 All of the above
9 None of the above
----------------------------------------------------------------

Enter the selection number for each kernel option you want.
For example, 1 3 :
</pre>

In our case, we don't need 2 (it is for 2780/3780 remote terminals), 3 (SimH doesn't emulate any cluster hardware) or 6 (it might cause problems with DECwindows/Motif). Everything else (<code>1 4 5 7</code>) is probably safe. This lets us play around with LAT (maybe connect an emulated Cisco router with LAT routing to it?) and DUP.

<pre>
Enter the selection number for each kernel option you want.
For example, 1 3 : 1 4 5 7

You specified the following kernel options:

Local Area Transport (LAT)
Diagnostic/Utilities Protocol (DUP)
ISO9660 File System Support (CDFS)
Enhanced Security Features

Is this correct? (y/n) [n]: y

*** SYSTEM CONFIGURATION PROCEDURE ***
The installation software found these devices in the floating
address space:

dz0 on uba0 at 0160100
dz1 on uba0 at 0160110
dz2 on uba0 at 0160120
dz3 on uba0 at 0160130

Configuration file complete.

Do you want to edit the configuration file? (y/n) [n]: n

*** PERFORMING SYSTEM CONFIGURATION ***

working ..... Wed Dec 6 02:29:10 EST 1995

*** DEVICE SPECIAL FILE CREATION ***
working ..... Wed Dec 6 02:29:53 EST 1995

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 800985B5
</pre>

Now you might want to take another backup of your disk images, since the ULTRIX installation is now basically complete.

==Adding the unsupported sets==
Now there are some more pieces of software in the CDROM, in a directory called ''unsupported''. We want to install these as well. First, let's boot our system again

<pre>
>>>b dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 747376
data = 125952
bss = 918192
Starting at 0x2c19

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
real mem = 67043328
avail mem = 56455168
using 1638 buffers containing 6712320 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
dz0 at uba0 csr 160100 vec 300, ipl 17
dz1 at uba0 csr 160110 vec 310, ipl 17
dz2 at uba0 csr 160120 vec 320, ipl 17
dz3 at uba0 csr 160130 vec 330, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
Wed Dec 6 11:25:29 MET 1995
Automatic reboot in progress...
/dev/ra0a: 644 files, 6161 used, 9390 free (166 frags, 1153 blocks, 5.0% fragmentation)
/dev/rra0g: umounted cleanly
/dev/rra0h: umounted cleanly
Warning Creating new license database
Warning creating new history file
check quotas: done.
savecore: checking for dump...dump does not exist
local daemons: syslog sendmail.
Removing remnant Opser files
preserving editor files
clearing /tmp
standard daemons: update cron accounting network snmpd printer.
start errlog daemon - elcsd
Wed Dec 6 11:25:48 MET 1995

ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
UWS V4.5 (Rev. 6)

Digital Equipment Corporation
Nashua, New Hampshire

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

#
</pre>

now, we mount the CDROM and use <code>setld</code> to install the unsupported packages. For simplicity's sake, we just (again) install everything.

<pre>
# mount -r /dev/ra2c /mnt
# cd /mnt/VAX/UNSUPPORTED
# ls
DXVUNDEMO450 ULXDOC450 ULXINGRES450 ULXRCS450 ULXUNMAN450
ULXAPL450 ULXEDIT450 ULXLEARN450 ULXSHELLS450 ULXUNMIT450
ULXBASE450 ULXF77450 ULXLISP450 ULXSPMS450 ULXVARIAN450
ULXBIB450 ULXGAMES450 ULXMAN450 ULXTERM450 instctrl
ULXCOURIER450 ULXHYPER450 ULXMOD2450 ULXTOOLS450
ULXCPM450 ULXICON450 ULXNEWS450 ULXUNEXAMP450
ULXDCMT450 ULXINET450 ULXNOTES450 ULXUNFONTS450
# setld -l .

*** Enter Subset Selections ***

The subsets listed below are optional:
1) Base Extension 2) GNU Emacs
3) TCP/IP Networking Util Extension 4) Additional Terminal Drivers
5) Document Preparation Software 6) Games and Diversions
7) Supplementary Documentation 8) Bibliographic Utilities
9) Remote Procedure Call Compiler 10) Aux. Command Line Interpreters
11) USENET News Interface Software 12) Notesfiles Package
13) Revision Control System 14) Misc. User-Contributed Utilities
15) Computer Aided System Tutor 16) Franz Lisp Development Package
17) Modula-2 Development Package 18) Raster Plotter Package
19) APL Development Package 20) CP/M 8in Diskette Utility
21) Hyperchannel Utilities 22) ICON (Language) Development Packag
23) University Ingres QUEL DBMS 24) Software Project Management System
25) Unsupported Fortran Utilities 26) Unsupported On-Line Documentation
27) Unsupported X11 Components 28) Unsupported DECwindows Examples
29) Unsupported MIT Fonts 30) Unsupported X11 Reference Pages
31) Unsupported OSF/Motif Demos

32) All mandatory and all optional subsets
33) Mandatory subsets only
34) Exit without installing subsets

Enter your choice(s): 32
Working....Wed Dec 6 11:29:48 MET 1995
Wed Dec 6 11:30:00 MET 1995

You are installing the following subsets:
Base Extension GNU Emacs
TCP/IP Networking Util Extension Additional Terminal Drivers
Document Preparation Software Games and Diversions
Supplementary Documentation Bibliographic Utilities
Remote Procedure Call Compiler Aux. Command Line Interpreters
USENET News Interface Software Notesfiles Package
Revision Control System Misc. User-Contributed Utilities
Computer Aided System Tutor Franz Lisp Development Package
Modula-2 Development Package Raster Plotter Package
APL Development Package CP/M 8in Diskette Utility
Hyperchannel Utilities ICON (Language) Development Package
University Ingres QUEL DBMS Software Project Management System
Unsupported Fortran Utilities Unsupported On-Line Documentation
Unsupported X11 Components Unsupported DECwindows Examples
Unsupported MIT Fonts Unsupported X11 Reference Pages
Unsupported OSF/Motif Demos

Is this correct? (y/n): y

Base Extension (ULXBASE450)
Copying from . (disk)
Verifying

GNU Emacs (ULXEDIT450)
Copying from . (disk)
Verifying

TCP/IP Networking Util Extension (ULXINET450)
Copying from . (disk)
Verifying
...
</pre>

Note that you could also quickly install only a single package by using for example
# setld -l . ULXINET450

After a few minutes, installation will be completed and we should unmount the CDROM
# cd /
# umount /mnt

==Network configuration==
To configure the network, you have to use a static IPv4 address and put that into the beginning of /etc/rc.local. Note that there is no <code>ifconfig -a</code> in ULTRIX, you have to use <code>netstat -i</code>

<pre>
# netstat -i
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
qe0* 1500 none none 0 0 0 0 0
lo0 1536 loop localhost 1 0 1 0 0
# ifconfig qe0 192.168.1.44 netmask 255.255.255.0 up
# route add default 192.168.1.1 1
add net default: gateway 192.168.1.1
# ping 192.168.1.1
192.168.1.1 is alive
</pre>
Note that it might actually take a while until packets are getting through. I don't know why but in my case it helped to ping ULTRIX from the outside first, e.g. from Windows, and then re-try the ping from the VM. Then it worked. I'm guessing this is some SimH/Windows issue with PCAP or something.

Then put these 2 commands at the start of <code>/etc/rc.local</code> (you'll see where). Note that you can use <code>vi</code> now!
<pre>
# @(#)rc.local 9.4 (ULTRIX) 9/21/95
/bin/hostname yuki
#/etc/ifconfig HDWR `/bin/hostname` broadcast NETNUM.0 netmask 255.0
/etc/ifconfig qe0 192.168.1.44 netmask 255.255.255.0
route add default 192.168.1.1 1
/etc/ifconfig lo0 localhost
#/etc/bscconfig dup0 bsc 1
#/etc/bscconfig dpv0 bsc 1
...
</pre>

==Shutting down cleanly==
As you'd expect, you can use <code>shutdown</code> to shut the system down
<pre>
# shutdown -h now
Shutdown at 11:15 (in 0 minutes) [pid 1500]
#
System shutdown time has arrived
syncing disks... done

?06 HLT INST
PC = 80094CDD
>>>
</pre>

==Enabling outside access==
The SimH config above includes a 16-line serial multiplexer. If you connect via TELNET to port 1005, you are given the first free serial line of the emulated DZ device. However, serial login is disabled by default, so it has to be enabled first. That's what the <code>/etc/ttys</code> file is for. Edit the file and change the ''off'' to ''on'' in the lines for tty00 to tty07, as shown below
<pre>
# @(#)ttys 9.1 (ULTRIX) 4/26/94
#
#
#
# name getty type status comments
#
console "/etc/getty std.9600" vt100 on secure # console terminal
tty00 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty01 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty02 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty03 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty04 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty05 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty06 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty07 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
ttyd0 "/etc/getty std.9600" vt100 off shared secure # modem line
</pre>

If you want to be able to login as root on these terminals, you can also add the <code>secure</code> flag as well. Also note that while it seems tempting to increase the line speed to 19200 or even higher, from my experience that will cause massive lags and emulation hangs in SimH, so do that on your own risk.

After editing the file and saving it, you have to reload init:
# kill -HUP 1

Now try logging in to port 1005 via telnet, and you should be greeted with this:
<pre>
Connected to the MicroVAX 3900 simulator DZ device, line 0

ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:
Requires secure terminal
</pre>

Note that SimH will print out the serial line to which you are connected, in this case line 0 which is /dev/tty00.

Also, if your inetd is running (which it should be, if you followed this guide), you will also already be able to login remotely using telnet.
<pre>
ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:
Requires secure terminal
</pre>
I still have to figure out what to change so that root access is permitted through telnet... But it's no big deal for now

==Resources==
Some of the resources I used for creating this guide:
*ULTRIX 4.5 installation ISO [http://musall.de/mirrors/ultrix/ultrix_os/vax/]
*ULTRIX-32 startup and shutdown guide [http://bitsavers.trailing-edge.com/pdf/dec/vax/ultrix-32/3.0/AA-ME91A-TE_ULTRIX-32_Guide_to_System_Shutdown_and_Startup.pdf]
*CERN guide to installing ULTRIX [https://web-docs.gsi.de/~kraemer/COLLECTION/ULTRIX/wwwpdp.web.cern.ch/wwwpdp/as/file/doc/ultrix/ultrix.pdf]
*My old guide for installing ULTRIX [https://docs.google.com/document/d/1ULRhzE0R1twarB5hfJm85yqOdTeoFCGgyPr5AxYEIbE]
*DEC KA655 CPU System Maintenance [http://bitsavers.trailing-edge.com/pdf/dec/vax/655/EK-306A-MG-001_655Mnt_Mar89.pdf]
*Some notes and links to more ULTRIX information [https://web-docs.gsi.de/~kraemer/COLLECTION/ULTRIX/docs.html]

[[Category:SIMH Tutorials]]

Installing Ultrix 4.5 on SIMH

2015-12-06T10:46:38Z

Darkstar: /* Enabling outside access */

This WORK-IN-PROGRESS guide will be a simple guide to installing ULTRIX 4.5 for VAX on SimH.

==Requirements==
The following is a list of things required for installation
*A recent version of the [[SIMH]] emulator
**Make sure the binary you're using includes Ethernet support
**I'm using a self-compiled version (git revision 0e8c0aea)
*An ISO image of ULTRIX 4.5 for VAX
**See the "Resources" section for a download link
**It's probably also possible to install it from tape, although I don't know if any installation tapes for ULTRIX 4.5 exist
*Optional stuff (might get added to the guide later):
**Starfish Ultrix Freeware CDs from [http://musall.de/mirrors/ultrix/freeware/ here]

==SimH configuration==
The machine I'm using to run ULTRIX has the following configuration
*DEC MicroVAX 3800
*64mb memory
*DELQA network card (XQ0)
*Two [[RA90]] disk drives (with 1.2gb each) attached to an RQDX3 controller (RQ0 and RQ1)
*CD ROM drive attached to the same RQDX3 controller as unit 2 (RQ2)
*[[TK50]] tape attached as unit 0 on the first TQK50 controller (TQ0)
*DZV11 terminal multiplexer with 16 lines, attached to telnet port 1005 (DZ)
*LPT line printer attached to text file <code>printer_output.txt</code>

Here's my config file (I called it <code>simh.conf</code>)
<pre><nowiki>
;
; SimH 4.0 Configuration file for MicroVAX 3800
;
; Host System : DEC MicroVAX 3800
; Operating System : DEC Ultrix v4.5
; Memory : 64mb
; Network config : XQ: Ethernet, 08:00:2b:04:14:02
; Disks : RQ0: RA90, 1.2gb
; RQ1: RA90, 1.2gb
; CDROMs : RQ2: iso file
; Tape config : TQ0: TK50, 94mb
;

load -r ka655x.bin

; NVRAM
attach NVR nvram.bin

; CPU config
set CPU 64m
set CPU conhalt
set CPU idle=all

; configure console to 7-bit only
set TTO 7b
set TTI 7b

; Disk drives
set RQ0 ra90
attach RQ0 rq0-ra90.dsk
set RQ1 ra90
attach RQ1 rq1-ra90.dsk
set RQ2 CDROM
attach -r RQ2 ultrix-vax-os-v4.5.mode1.ufs.iso
; MD5 sum: 19df0753c27f195e9f1d2f139a3b4629 *ultrix-vax-os-v4.5.mode1.ufs.iso
set RQ3 dis

; Tape
set TQ tk50
;attach tq0 filename-to-tape-file
set TQ1 dis
set TQ2 dis
set TQ3 dis

; serial port, simulated by Telnet to port 1005
set DZ LINES=16
set DZ 8B
attach DZ 1005 NoBuffer

; printer
set LPT enable
attach LPT printer_output.txt

; Disable unused peripherals
set CR dis
set RL dis
set TS dis

; Network interface (08-00-2b is the DEC prefix, the 04-14-02 part is arbitrary)
set XQ MAC=08-00-2b-04-14-02
attach XQ0 eth0

; serial console (launch directly after booting CPU)
set console telnet=1001

; experimental
;set QVSS en

; boot the system
;boot CPU
</nowiki></pre>
Note that I'm using a telnet console (for easier copy/paste on Windows), which means that directly after running this config file (via <code>do simh.conf</code> from Simh) you will need to connect via telnet to localhost:1001 or the boot will abort. If you are on Linux, or just don't want that, remove the <code>set console telnet=1001</code> line.

Also note that you might need to attach XQ0 to a different ethernet device. Use "show ether" in SimH to list all available devices on your system and modify the <code>attach XQ0 eth0</code> line accordingly.

==Running the Emulator==
Either run <code>vax.exe simh.conf</code> from the Windows command line, or just double-click the VAX.EXE executable and type <code>do simh.conf</code>.

On the first launch it might take some time because SimH has to create the disk images (~2.5 gb total). It should look something like this
<pre><nowiki>
MicroVAX 3900 simulator V4.0-0 Beta git commit id: 0e8c0aea
NVR: buffering file in memory
RQ2: unit is read only
Listening on port 1005
WinPcap version 4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008)
Eth: opened OS device \Device\NPF_{A41A1651-DD4D-4735-A4E0-88353165C2EC}
Listening on port 1001
sim>
</nowiki></pre>

Type the following to start the emulation (note: you can also uncomment that line from the end of the config file to have the emulation start right away)
sim> boot cpu
Waiting for console Telnet connection

Now would be a good time to connect your telnet session (I use a batch file for this), otherwise the boot process will timeout.

On your console, you should see something like this:
<pre><nowiki>
Connected to the MicroVAX 3900 simulator CON-TEL device

KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>
</nowiki></pre>

This is the VAX's boot prompt. Normally you just type
>>>boot <device>
where <device> is one of the following
*MUA<num>: TK tape device number <num> (1 to 4)
*DUA<num>: RQ disk device number <num> (1 to 4)

You can use <code>show device</code> to see the installed (and detected) devices you can boot from, and <code>show boot</code> to see which device will be the default if you just type <code>boot</code> (or <code>b</code> for short):
<pre><nowiki>
>>>show device
UQSSP Disk Controller 0 (772150)
-DUA0 (RA90)
-DUA1 (RA90)
-DUA2 (RRD40)

UQSSP Tape Controller 0 (774500)
-MUA0 (TK50)

Ethernet Adapter 0 (774440)
-XQA0 (08-00-2B-04-14-02)
>>>show boot
MUA0
</nowiki></pre>

Since we want to boot from CDROM, which is unit 2, we can use
>>>boot DUA2

Note: You can add flags to boot into single user mode, or to boot in interactive mode (so-called ''conversational boot'', where the system prompts you for a kernel file name to load). For details see the Guide to ULTRIX-32 System Startup and Shutdown, linked to in the ''References'' section. To use it, add the <code>/R5:<flags></code> option to the <code>boot</code> command, where flags is 0 (default multi-user), 1 (conversational multi-user), 2 (single-user) or 3 (conversational single-user). For example
>>>boot/r5:3 dua0

Note: You can also boot from ethernet (<code>boot XQA0</code>) but this requires a DEC-specific boot server in your network (the protocol is called ''MOP'' for ''Maintenance Operations Protocol''), which is beyond the scope of this document. I did get it to work a few years ago though, but it was a bit difficult to set up.

For a list and description of all commands available in the bootloader (hint: there are lots), see the ''KA655 CPU System Maintenance'' guide mentioned in the ''References'' section..

==Bootstrapping ULTRIX==
You will see the following output on the first boot.
<pre>
>>>boot dua2
(BOOT/R5:0 DUA2

2..
-DUA2
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 945424
data = 1290240
bss = 757940
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #2: Wed Oct 18 12:06:55 EDT 1995
real mem = 67043328
avail mem = 61517824
Buffer configuration adjusted to run with small system page table
using 123 buffers containing 1007616 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
WARNING: clock gained 47 days -- CHECK AND RESET THE DATE!

*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice:
</pre>
Now we want to do an ''ADVANCED Installation'', but when we try to, it will take a few seconds until the installation program dumps us to a prompt because it couldn't find a valid device to install from and to:
<pre>
Enter your choice: 2

*** SOFTWARE DISTRIBUTION DEVICE SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of software distribution devices and which installation media you should
load on it:

No valid device is found.
Contact a DIGITAL field service representative.

#
</pre>

The problem seems to be that the hardware SimH emulates is not fully supported by ULTRIX (or is misdetected -- I'm not entirely sure myself). The good thing is that the internet has the correct solution, which is to fix some lines in the installation shell script. The fact that the basic system that is running at this point doesn't have ''vi'', or even ''cat'', makes this a bit harder ;-)

The only option you have is ''ed'', the old UNIX editor. For a quick introduction, see [http://blog.sanctum.geek.nz/actually-using-ed/ here].

To load the file in the editor, use
# '''ed install.1'''
16763

You can see the entire file with
1,$l
but be warned, the output is quite long and it'll take some time to print it all out.

To fix it, use the following commands (the lines in '''bold''' is what you type, everything else is the response from ed)
# '''ed install.1'''
16763
'''173l'''
BTD=`btd`
'''173s/`btd`/ra2/'''
'''173l'''
BTD=ra2
'''193l'''
rz* )
'''193s/rz/ra/'''
'''193l'''
ra* )
'''w'''
16761
'''q'''
#

First, we list line 173, then we change it from <code>BTD=`btd`</code> to <code>BTD=ra2</code>, which happens to be the CDROM device and unit number we're installing from (if you changed that in your config, use the correct name here!)

Then we change line 193 from <code>rz* )</code> to <code>ra* )</code> since we're trying to install on an RA type disk which was apparently not supported in ULTRIX out of the box.

After writing the file with <code>w</code> and quitting ed with <code>q</code>, we're back at the prompt, at which point we can use CTRL+D to retry the installation:

<pre>
# ^D
*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice: 2

*** SYSTEM DISK SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of system disk drives. Select one of the devices below to contain the
root file system:

SYSTEM DISK TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk drive
is on line and write-enabled (if applicable to your disk drive), then
confirm your choice.

Use RA90, ra0, for your system disk? (y/n) []: y

The installation procedure now allocates the root file system on
partition 'a' of the system disk, ra0 RA90.

Making the root file system on ra0 RA90.

The installation procedure is now restoring the root file system to
partition 'a' of the system disk, ra0 RA90.

The installation procedure now checks the root file system on partition 'a'
of the system disk, ra0 RA90.
** /dev/rra0a
** Last Mounted on /mnt
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
226 files, 4547 used, 11004 free (20 frags, 1373 blocks, 1.0% fragmentation)

*** BOOTSTRAP COMMAND SEQUENCE ***

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 8007F799
>>>
</pre>
After this, you will be back at the VAX boot prompt (if you used <code>set CPU CONHALT</code> in your config) or at the SimH emulator prompt (if you used <code>set CPU SIMHALT</code>, which is the default). In the latter case you will have to do <code>boot cpu</code> again to get to the VAX boot prompt.

==First boot==
Now we can boot the installed system from harddisk for the first time.

If you want to, now would be a good time to take a backup copy of your disk files (or just create a btrfs snapshot or something if you have the possibility ;-)

Okay, then let's boot from DUA0
<pre>
>>>boot dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 1153664
data = 281088
bss = 1043548
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #3: Wed Oct 18 11:49:00 EDT 1995
real mem = 67043328
avail mem = 62008320
Buffer configuration adjusted to run with small system page table
using 121 buffers containing 991232 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
</pre>
Here, it will seem to hang for a loooong time. A few minutes. Don't worry, it will eventually continue to boot. I guess it's probing for other devices which are not present.

You ''might'' be able to speed this up a bit by interrupting SimH (press CTRL+E in the SimH console window) and then using <code>set CPU noidle</code> followed by <code>go</code> to resume emulation.

Eventually, you will have to decide on a hostname. Note that if you want to play around with [[DECnet]] at some point, your hostname should be no longer than 6 characters.
<pre>
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)

*** SYSTEM NAME SPECIFICATION ***

Select the name of your system using alphanumeric characters.
The first character must be a letter. For example, tinker.

Enter your system name: yuki

You selected yuki as the name of your system.
Is this correct? (y/n) [y]: y
</pre>

Next up is the time configuration. Since Ultrix 4.5 is not Y2k compliant (AFAIK), I decided to set the clock back a whopping 20 years. Note that the timezone and daylight saving settings are for my location (Germany) and will probably vary for you.

<pre>
*** DATE AND TIME SPECIFICATION ***

The current date and time should be specified using the following
format:

yymmddhhmm

Use two digits for year (yy), month (mm), day (dd), hour (hh), and
minute (mm). Enter the time in 24-hour format. For example, 02:54
p.m. on Feb 2, 1993 would be entered as:

9302021454

Enter the date and time: 9512052336

*** TIME ZONE SELECTION ***

Select the time zone for your area, using the options listed in the
table below. You can also enter the number of hours (-12 to 12) in
time east of Greenwich.

Selection Time Zone
---------------------------------
e Eastern
c Central
m Mountain
p Pacific
g Greenwich
---------------------------------

Enter your choice: 1

Does your area alternate between Daylight Savings and Standard
time? (y/n) [y]: y

Select your geographic area for Daylight Savings Time, using the
options in the table below.

Selection Geographic Area
--------------------------------
u USA
a Australia
e Eastern Europe
c Central Europe
w Western Europe
--------------------------------

Enter your choice [u]: c

The current date and time is Tue Dec 5 23:36:46 EST 1995
</pre>

Next up is the root password. Note that Ultrix will not echo anything here, I added the asterisks just for this guide :)

<pre>
*** SPECIFY THE SUPERUSER PASSWORD ***
The Guide to Installing ULTRIX instructs you on how to enter
the superuser password.
Changing password for root
Enter new password: ******
Verify: ******
</pre>

Next up is the filesystem layout, which is a bit more involved than what you know from more modern systems like MS DOS ;-)

In ULTRIX, partitions are defined for each disk type in a file called <code>/etc/disktab</code>. Note that the partitions overlap, so you shouldn't use them all at the same time. The setup script actually takes care of that for you, but if you later create a new filesystem on the wrong partition you ''WILL'' lose data!

Normally, partition '''c''' is the whole disk, which is useful for add-on disk drives for example. Partitions '''a''' and '''b''' are always available and are traditionally used for the system and the swap-space respectively. The swap partition is also used for crashdumps if no separate crash-dump partition is created. The rest of the disk can be used either as a single partition (which is usually '''g''') or as 3 individual partitions ('''d''' to '''f'''). If the disk is larger than 1 gigabyte, you will get another partition, '''h''', after the g partition, probably because the filesystem cannot cope with partitions >1gig

In our case, we will have the following partitions on the first disk (RA0):
*Partition '''a''' of 32 mb for /root
*Partition '''b''' of 64 mb for swap+crashdump
*Partition '''c''' of 1.2 gig (whole-disk, not used on our setup)
*Partition '''d''' and '''e''' of 200 mb each (not used)
*Partition '''f''' of 400 mb (not used)
*Partition '''g''' of 800 mb (overlaps with d, e and f; will become /usr)
*Partition '''h''' of 256 mb (will become /usr/var)
This way we still have the whole second disk available for later use.

So here it goes:
<pre>
*** FILE SYSTEM DEFAULT OPTION ***

The following table shows the default file system layout on RA90, ra0:

partition bottom top size overlap default
a 0 32767 32768 c root
b 32768 159839 127072 c swap, dump
d 159840 580036 420197 c,g /usr

If you choose the defaults, the var area will be allocated to /usr/var.

Do you want to choose the default file system layout? (y/n): n
</pre>

No, we do not want to use the defaults...

First, we select disk 1, partition '''g''', for the /usr file system:
<pre>
*** /usr FILE SYSTEM ALLOCATION ***

You can allocate the /usr file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

/usr FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for /usr file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the /usr file system:

partition size (Kbytes) overlap
------------------------------------------------
d --- 210098 c,g
e --- 210098 c,g
f --- 420196 c,g
g --- 840393 c,d,e,f
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the /usr file system [d]: g

Making the new file system for /usr on /dev/rra0g RA90
</pre>

Next, we select disk 1, partition '''b''' for swap (only 1 swap partition) and for crashdumps:

<pre>
*** ALLOCATE THE SWAP1 SPACE ***

You can allocate the swap1 space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

SWAP1 SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for swap1 space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the swap1 space:

partition size (Kbytes) overlap
------------------------------------------------
b --- 63536 c
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the swap1 space [b]: b

*** ALLOCATE THE SWAP2 SPACE ***

Do you want to allocate a second swap space? (y/n) [n]: n

*** ALLOCATE THE CRASH DUMP SPACE ***

You can allocate the crash dump space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

CRASH DUMP SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for crash dump space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the crash dump space:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
b --- 63536 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the crash dump space [b]: b
</pre>

Finally we select partiton '''h''' for the /var file system. This might not be large enough later on but then we can always migrate the data away if we need to...

<pre>
*** ALLOCATE THE var FILE SYSTEM ***

You can allocate the var file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

var FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for var file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the var file system:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
g --- 840393 c,d,e,f
------------------------------------------------

Type the letter of the partition on which you want
to allocate the var file system [no default]: h

Making the new file system for var on /dev/rra0h RA90
</pre>

==Installing the distribution files==

Next up we have to decide what ''packages'' we want to install (yes, ULTRIX already had its own package format and corresponding installer called ''setld''. It is very basic, probably most similar to ''pkg_add'' on NetBSD). We simply install everything, since we have enough space :)

<pre>
This distribution media includes subsets for ULTRIX Worksystem
Software (UWS). A UWS license (on a workstation) or a UWS Server
License (on a timesharing machine or server) is required to install
these subsets.

Do you want to install ULTRIX Worksystem Software? y/n []: y

*** SUPPORTED SOFTWARE INSTALLATION ***

*** Select the DECwindows User Interface ***

1) DECwindows for OSF/Motif
2) X11/DECwindows (XUI)

Enter your choice [1]: 2

*** Enter Subset Selections ***

The following subsets are mandatory and will be installed automatically:
* Base System * Kernel Config Files
* TCP/IP Networking Utilities * Network File System Utilities
* Extended (Berkeley) Mailer * X11/DECwindows Servers
* X11/DECwindows User Environment * X11/DECwindows 75dpi Fonts

The subsets listed below are optional:
1) Printer Support Environment 2) RAND Mail Handler
3) Sys. Config. Mgmt. Program (SCAMP) 4) Communications Utilities
5) Unix-to-Unix Copy Facility 6) Maintenance Operations Protocol
7) Accounting Software 8) Kerberos Network Authentication
9) Enhanced Security Features 10) Prestoserve Utilities
11) System Exerciser Package 12) Bisynchronous Communications
13) Doc. Preparation for Ref. Pages 14) Doc. Preparation Extensions
15) Adobe Font Metric Files 16) Software Development Utilities
17) Source Code Control System 18) Internationalization Runtime Env.
19) Internationalization Dev. Env. 20) CDA Base System
21) CDA Software Dev Libraries 22) RPC Runtime Environment
23) RPC Development Environment 24) Pascal Development Package
25) VAX C/ULTRIX 26) Ref. Pages for Sys. Admin. & Users
27) Reference Pages for Programers 28) Programming Examples
29) Ultrix SPDS 30) X11/DECwindows 100dpi Fonts
31) VS35XX X11/DECwindows Fonts 32) Additional DECwindows Applications
33) DECwindows Mail Application 34) Worksystem Development Environment
35) X11/DECwindows System Management T 36) UWS Runtime Reference Pages
37) UWS Development Reference Pages

38) All mandatory and all optional subsets
39) Mandatory subsets only
40) Exit without installing subsets

Enter your choice(s): 38
Working....Wed Dec 6 00:14:12 EST 1995

You are installing the following subsets:
Base System Kernel Config Files
TCP/IP Networking Utilities Network File System Utilities
Extended (Berkeley) Mailer X11/DECwindows Servers
X11/DECwindows User Environment X11/DECwindows 75dpi Fonts
Printer Support Environment RAND Mail Handler
Sys. Config. Mgmt. Program (SCAMP) Communications Utilities
Unix-to-Unix Copy Facility Maintenance Operations Protocol
Accounting Software Kerberos Network Authentication
Enhanced Security Features Prestoserve Utilities
System Exerciser Package Bisynchronous Communications
Doc. Preparation for Ref. Pages Doc. Preparation Extensions
Adobe Font Metric Files Software Development Utilities
Source Code Control System Internationalization Runtime Env.
Internationalization Dev. Env. CDA Base System
CDA Software Dev Libraries RPC Runtime Environment
RPC Development Environment Pascal Development Package
VAX C/ULTRIX Ref. Pages for Sys. Admin. & Users
Reference Pages for Programers Programming Examples
Ultrix SPDS X11/DECwindows 100dpi Fonts
VS35XX X11/DECwindows Fonts Additional DECwindows Applications
DECwindows Mail Application Worksystem Development Environment
X11/DECwindows System Management To UWS Runtime Reference Pages
UWS Development Reference Pages

Is this correct? (y/n): y
</pre>

The installation will take a while (around 15-30 minutes for me), so feel free to let it run in the background for a while now. The installer will periodically print its status so you can see that it's still running...

<pre>
Base System (ULTBASE450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:14:43 EST 1995
Verifying

Kernel Config Files (ULTBIN450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:15:28 EST 1995
Verifying

...
</pre>

At some point you will have to confirm installing the generic kernel and the X11 subsystem:

<pre>
...
UWS Runtime Reference Pages (UWSMAN450)
Copying from /mnt/VAX/BASE (disk)
Verifying

UWS Development Reference Pages (UWSMANPGMR450)
Copying from /mnt/VAX/BASE (disk)
Verifying

The installation software has successfully installed the software
subsets.
Installing Upgrade subsets
The following subsets will be installed:
* X11/DECwindows Servers Upgrade * Generic Kernel
Do you wish to continue? (y/n): y

X11/DECwindows Servers Upgrade (UWSSER451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

Generic Kernel (ULTGENVMUNIX451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

The installation procedure has successfully installed the Upgrade
subsets
</pre>

That's it for the base installation, now we configure our kernel...

==Kernel configuration==
We have to select what features will be in the kernel. For anyone who has ever done a "make menuconfig" on Linux, this is ''slightly'' easier here ;-)
<pre>
*** CONFIGURATION FILE KERNEL OPTION SELECTION ***

Selection Kernel Option
---------------------------------------------------------------
1 Local Area Transport (LAT)
2 Bisynchronous Communication protocol (VAX only)
3 Computer Interconnect (CI) network
4 Diagnostic/Utilities Protocol (DUP)
5 ISO9660 File System Support (CDFS)
6 Ethernet Packet Filter
7 Enhanced Security Features
8 All of the above
9 None of the above
----------------------------------------------------------------

Enter the selection number for each kernel option you want.
For example, 1 3 :
</pre>

In our case, we don't need 2 (it is for 2780/3780 remote terminals), 3 (SimH doesn't emulate any cluster hardware) or 6 (it might cause problems with DECwindows/Motif). Everything else (<code>1 4 5 7</code>) is probably safe. This lets us play around with LAT (maybe connect an emulated Cisco router with LAT routing to it?) and DUP.

<pre>
Enter the selection number for each kernel option you want.
For example, 1 3 : 1 4 5 7

You specified the following kernel options:

Local Area Transport (LAT)
Diagnostic/Utilities Protocol (DUP)
ISO9660 File System Support (CDFS)
Enhanced Security Features

Is this correct? (y/n) [n]: y

*** SYSTEM CONFIGURATION PROCEDURE ***
The installation software found these devices in the floating
address space:

dz0 on uba0 at 0160100
dz1 on uba0 at 0160110
dz2 on uba0 at 0160120
dz3 on uba0 at 0160130

Configuration file complete.

Do you want to edit the configuration file? (y/n) [n]: n

*** PERFORMING SYSTEM CONFIGURATION ***

working ..... Wed Dec 6 02:29:10 EST 1995

*** DEVICE SPECIAL FILE CREATION ***
working ..... Wed Dec 6 02:29:53 EST 1995

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 800985B5
</pre>

Now you might want to take another backup of your disk images, since the ULTRIX installation is now basically complete.

==Adding the unsupported sets==
Now there are some more pieces of software in the CDROM, in a directory called ''unsupported''. We want to install these as well. First, let's boot our system again

<pre>
>>>b dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 747376
data = 125952
bss = 918192
Starting at 0x2c19

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
real mem = 67043328
avail mem = 56455168
using 1638 buffers containing 6712320 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
dz0 at uba0 csr 160100 vec 300, ipl 17
dz1 at uba0 csr 160110 vec 310, ipl 17
dz2 at uba0 csr 160120 vec 320, ipl 17
dz3 at uba0 csr 160130 vec 330, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
Wed Dec 6 11:25:29 MET 1995
Automatic reboot in progress...
/dev/ra0a: 644 files, 6161 used, 9390 free (166 frags, 1153 blocks, 5.0% fragmentation)
/dev/rra0g: umounted cleanly
/dev/rra0h: umounted cleanly
Warning Creating new license database
Warning creating new history file
check quotas: done.
savecore: checking for dump...dump does not exist
local daemons: syslog sendmail.
Removing remnant Opser files
preserving editor files
clearing /tmp
standard daemons: update cron accounting network snmpd printer.
start errlog daemon - elcsd
Wed Dec 6 11:25:48 MET 1995

ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
UWS V4.5 (Rev. 6)

Digital Equipment Corporation
Nashua, New Hampshire

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

#
</pre>

now, we mount the CDROM and use <code>setld</code> to install the unsupported packages. For simplicity's sake, we just (again) install everything.

<pre>
# mount -r /dev/ra2c /mnt
# cd /mnt/VAX/UNSUPPORTED
# ls
DXVUNDEMO450 ULXDOC450 ULXINGRES450 ULXRCS450 ULXUNMAN450
ULXAPL450 ULXEDIT450 ULXLEARN450 ULXSHELLS450 ULXUNMIT450
ULXBASE450 ULXF77450 ULXLISP450 ULXSPMS450 ULXVARIAN450
ULXBIB450 ULXGAMES450 ULXMAN450 ULXTERM450 instctrl
ULXCOURIER450 ULXHYPER450 ULXMOD2450 ULXTOOLS450
ULXCPM450 ULXICON450 ULXNEWS450 ULXUNEXAMP450
ULXDCMT450 ULXINET450 ULXNOTES450 ULXUNFONTS450
# setld -l .

*** Enter Subset Selections ***

The subsets listed below are optional:
1) Base Extension 2) GNU Emacs
3) TCP/IP Networking Util Extension 4) Additional Terminal Drivers
5) Document Preparation Software 6) Games and Diversions
7) Supplementary Documentation 8) Bibliographic Utilities
9) Remote Procedure Call Compiler 10) Aux. Command Line Interpreters
11) USENET News Interface Software 12) Notesfiles Package
13) Revision Control System 14) Misc. User-Contributed Utilities
15) Computer Aided System Tutor 16) Franz Lisp Development Package
17) Modula-2 Development Package 18) Raster Plotter Package
19) APL Development Package 20) CP/M 8in Diskette Utility
21) Hyperchannel Utilities 22) ICON (Language) Development Packag
23) University Ingres QUEL DBMS 24) Software Project Management System
25) Unsupported Fortran Utilities 26) Unsupported On-Line Documentation
27) Unsupported X11 Components 28) Unsupported DECwindows Examples
29) Unsupported MIT Fonts 30) Unsupported X11 Reference Pages
31) Unsupported OSF/Motif Demos

32) All mandatory and all optional subsets
33) Mandatory subsets only
34) Exit without installing subsets

Enter your choice(s): 32
Working....Wed Dec 6 11:29:48 MET 1995
Wed Dec 6 11:30:00 MET 1995

You are installing the following subsets:
Base Extension GNU Emacs
TCP/IP Networking Util Extension Additional Terminal Drivers
Document Preparation Software Games and Diversions
Supplementary Documentation Bibliographic Utilities
Remote Procedure Call Compiler Aux. Command Line Interpreters
USENET News Interface Software Notesfiles Package
Revision Control System Misc. User-Contributed Utilities
Computer Aided System Tutor Franz Lisp Development Package
Modula-2 Development Package Raster Plotter Package
APL Development Package CP/M 8in Diskette Utility
Hyperchannel Utilities ICON (Language) Development Package
University Ingres QUEL DBMS Software Project Management System
Unsupported Fortran Utilities Unsupported On-Line Documentation
Unsupported X11 Components Unsupported DECwindows Examples
Unsupported MIT Fonts Unsupported X11 Reference Pages
Unsupported OSF/Motif Demos

Is this correct? (y/n): y

Base Extension (ULXBASE450)
Copying from . (disk)
Verifying

GNU Emacs (ULXEDIT450)
Copying from . (disk)
Verifying

TCP/IP Networking Util Extension (ULXINET450)
Copying from . (disk)
Verifying
...
</pre>

Note that you could also quickly install only a single package by using for example
# setld -l . ULXINET450

After a few minutes, installation will be completed and we should unmount the CDROM
# cd /
# umount /mnt

==Network configuration==
To configure the network, you have to use a static IPv4 address and put that into the beginning of /etc/rc.local. Note that there is no <code>ifconfig -a</code> in ULTRIX, you have to use <code>netstat -i</code>

<pre>
# netstat -i
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
qe0* 1500 none none 0 0 0 0 0
lo0 1536 loop localhost 1 0 1 0 0
# ifconfig qe0 192.168.1.44 netmask 255.255.255.0 up
# route add default 192.168.1.1 1
add net default: gateway 192.168.1.1
# ping 192.168.1.1
192.168.1.1 is alive
</pre>
Note that it might actually take a while until packets are getting through. I don't know why but in my case it helped to ping ULTRIX from the outside first, e.g. from Windows, and then re-try the ping from the VM. Then it worked. I'm guessing this is some SimH/Windows issue with PCAP or something.

Then put these 2 commands at the start of <code>/etc/rc.local</code> (you'll see where). Note that you can use <code>vi</code> now!
<pre>
# @(#)rc.local 9.4 (ULTRIX) 9/21/95
/bin/hostname yuki
#/etc/ifconfig HDWR `/bin/hostname` broadcast NETNUM.0 netmask 255.0
/etc/ifconfig qe0 192.168.1.44 netmask 255.255.255.0
route add default 192.168.1.1 1
/etc/ifconfig lo0 localhost
#/etc/bscconfig dup0 bsc 1
#/etc/bscconfig dpv0 bsc 1
...
</pre>

==Shutting down cleanly==
As you'd expect, you can use <code>shutdown</code> to shut the system down
<pre>
# shutdown -h now
Shutdown at 11:15 (in 0 minutes) [pid 1500]
#
System shutdown time has arrived
syncing disks... done

?06 HLT INST
PC = 80094CDD
>>>
</pre>

==Enabling outside access==
The SimH config above includes a 16-line serial multiplexer. If you connect via TELNET to port 1005, you are given the first free serial line of the emulated DZ device. However, serial login is disabled by default, so it has to be enabled first. That's what the <code>/etc/ttys</code> file is for. Edit the file and change the ''off'' to ''on'' in the lines for tty00 to tty07, as shown below
<pre>
# @(#)ttys 9.1 (ULTRIX) 4/26/94
#
#
#
# name getty type status comments
#
console "/etc/getty std.9600" vt100 on secure # console terminal
tty00 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty01 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty02 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty03 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty04 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty05 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty06 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty07 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
ttyd0 "/etc/getty std.9600" vt100 off shared secure # modem line
</pre>

If you want to be able to login as root on these terminals, you can also add the <code>secure</code> flag as well. Also note that while it seems tempting to increase the line speed to 19200 or even higher, from my experience that will cause massive lags and emulation hangs in SimH, so do that on your own risk.

After editing the file and saving it, you have to reload init:
# kill -HUP 1

Now try logging in to port 1005 via telnet, and you should be greeted with this:
<pre>
Connected to the MicroVAX 3900 simulator DZ device, line 0

ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:
Requires secure terminal
</pre>

Note that SimH will print out the serial line to which you are connected, in this case line 0 which is /dev/tty00.

Also, if your inetd is running (which it should be, if you followed this guide), you will also already be able to login remotely using telnet.
<pre>
ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:
Requires secure terminal
</pre>
I still have to figure out what to change so that root access is permitted through telnet... But it's no big deal for now

==Resources==
Some of the resources I used for creating this guide:
*ULTRIX 4.5 installation ISO [http://musall.de/mirrors/ultrix/ultrix_os/vax/]
*ULTRIX-32 startup and shutdown guide [http://bitsavers.trailing-edge.com/pdf/dec/vax/ultrix-32/3.0/AA-ME91A-TE_ULTRIX-32_Guide_to_System_Shutdown_and_Startup.pdf]
*CERN guide to installing ULTRIX [https://web-docs.gsi.de/~kraemer/COLLECTION/ULTRIX/wwwpdp.web.cern.ch/wwwpdp/as/file/doc/ultrix/ultrix.pdf]
*My old guide for installing ULTRIX [https://docs.google.com/document/d/1ULRhzE0R1twarB5hfJm85yqOdTeoFCGgyPr5AxYEIbE]
*DEC KA655 CPU System Maintenance [http://bitsavers.trailing-edge.com/pdf/dec/vax/655/EK-306A-MG-001_655Mnt_Mar89.pdf]
[[Category:SIMH Tutorials]]

Installing Ultrix 4.5 on SIMH

2015-12-06T10:43:00Z

Darkstar: Enabling terminal access

This WORK-IN-PROGRESS guide will be a simple guide to installing ULTRIX 4.5 for VAX on SimH.

==Requirements==
The following is a list of things required for installation
*A recent version of the [[SIMH]] emulator
**Make sure the binary you're using includes Ethernet support
**I'm using a self-compiled version (git revision 0e8c0aea)
*An ISO image of ULTRIX 4.5 for VAX
**See the "Resources" section for a download link
**It's probably also possible to install it from tape, although I don't know if any installation tapes for ULTRIX 4.5 exist
*Optional stuff (might get added to the guide later):
**Starfish Ultrix Freeware CDs from [http://musall.de/mirrors/ultrix/freeware/ here]

==SimH configuration==
The machine I'm using to run ULTRIX has the following configuration
*DEC MicroVAX 3800
*64mb memory
*DELQA network card (XQ0)
*Two [[RA90]] disk drives (with 1.2gb each) attached to an RQDX3 controller (RQ0 and RQ1)
*CD ROM drive attached to the same RQDX3 controller as unit 2 (RQ2)
*[[TK50]] tape attached as unit 0 on the first TQK50 controller (TQ0)
*DZV11 terminal multiplexer with 16 lines, attached to telnet port 1005 (DZ)
*LPT line printer attached to text file <code>printer_output.txt</code>

Here's my config file (I called it <code>simh.conf</code>)
<pre><nowiki>
;
; SimH 4.0 Configuration file for MicroVAX 3800
;
; Host System : DEC MicroVAX 3800
; Operating System : DEC Ultrix v4.5
; Memory : 64mb
; Network config : XQ: Ethernet, 08:00:2b:04:14:02
; Disks : RQ0: RA90, 1.2gb
; RQ1: RA90, 1.2gb
; CDROMs : RQ2: iso file
; Tape config : TQ0: TK50, 94mb
;

load -r ka655x.bin

; NVRAM
attach NVR nvram.bin

; CPU config
set CPU 64m
set CPU conhalt
set CPU idle=all

; configure console to 7-bit only
set TTO 7b
set TTI 7b

; Disk drives
set RQ0 ra90
attach RQ0 rq0-ra90.dsk
set RQ1 ra90
attach RQ1 rq1-ra90.dsk
set RQ2 CDROM
attach -r RQ2 ultrix-vax-os-v4.5.mode1.ufs.iso
; MD5 sum: 19df0753c27f195e9f1d2f139a3b4629 *ultrix-vax-os-v4.5.mode1.ufs.iso
set RQ3 dis

; Tape
set TQ tk50
;attach tq0 filename-to-tape-file
set TQ1 dis
set TQ2 dis
set TQ3 dis

; serial port, simulated by Telnet to port 1005
set DZ LINES=16
set DZ 8B
attach DZ 1005 NoBuffer

; printer
set LPT enable
attach LPT printer_output.txt

; Disable unused peripherals
set CR dis
set RL dis
set TS dis

; Network interface (08-00-2b is the DEC prefix, the 04-14-02 part is arbitrary)
set XQ MAC=08-00-2b-04-14-02
attach XQ0 eth0

; serial console (launch directly after booting CPU)
set console telnet=1001

; experimental
;set QVSS en

; boot the system
;boot CPU
</nowiki></pre>
Note that I'm using a telnet console (for easier copy/paste on Windows), which means that directly after running this config file (via <code>do simh.conf</code> from Simh) you will need to connect via telnet to localhost:1001 or the boot will abort. If you are on Linux, or just don't want that, remove the <code>set console telnet=1001</code> line.

Also note that you might need to attach XQ0 to a different ethernet device. Use "show ether" in SimH to list all available devices on your system and modify the <code>attach XQ0 eth0</code> line accordingly.

==Running the Emulator==
Either run <code>vax.exe simh.conf</code> from the Windows command line, or just double-click the VAX.EXE executable and type <code>do simh.conf</code>.

On the first launch it might take some time because SimH has to create the disk images (~2.5 gb total). It should look something like this
<pre><nowiki>
MicroVAX 3900 simulator V4.0-0 Beta git commit id: 0e8c0aea
NVR: buffering file in memory
RQ2: unit is read only
Listening on port 1005
WinPcap version 4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008)
Eth: opened OS device \Device\NPF_{A41A1651-DD4D-4735-A4E0-88353165C2EC}
Listening on port 1001
sim>
</nowiki></pre>

Type the following to start the emulation (note: you can also uncomment that line from the end of the config file to have the emulation start right away)
sim> boot cpu
Waiting for console Telnet connection

Now would be a good time to connect your telnet session (I use a batch file for this), otherwise the boot process will timeout.

On your console, you should see something like this:
<pre><nowiki>
Connected to the MicroVAX 3900 simulator CON-TEL device

KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>
</nowiki></pre>

This is the VAX's boot prompt. Normally you just type
>>>boot <device>
where <device> is one of the following
*MUA<num>: TK tape device number <num> (1 to 4)
*DUA<num>: RQ disk device number <num> (1 to 4)

You can use <code>show device</code> to see the installed (and detected) devices you can boot from, and <code>show boot</code> to see which device will be the default if you just type <code>boot</code> (or <code>b</code> for short):
<pre><nowiki>
>>>show device
UQSSP Disk Controller 0 (772150)
-DUA0 (RA90)
-DUA1 (RA90)
-DUA2 (RRD40)

UQSSP Tape Controller 0 (774500)
-MUA0 (TK50)

Ethernet Adapter 0 (774440)
-XQA0 (08-00-2B-04-14-02)
>>>show boot
MUA0
</nowiki></pre>

Since we want to boot from CDROM, which is unit 2, we can use
>>>boot DUA2

Note: You can add flags to boot into single user mode, or to boot in interactive mode (so-called ''conversational boot'', where the system prompts you for a kernel file name to load). For details see the Guide to ULTRIX-32 System Startup and Shutdown, linked to in the ''References'' section. To use it, add the <code>/R5:<flags></code> option to the <code>boot</code> command, where flags is 0 (default multi-user), 1 (conversational multi-user), 2 (single-user) or 3 (conversational single-user). For example
>>>boot/r5:3 dua0

Note: You can also boot from ethernet (<code>boot XQA0</code>) but this requires a DEC-specific boot server in your network (the protocol is called ''MOP'' for ''Maintenance Operations Protocol''), which is beyond the scope of this document. I did get it to work a few years ago though, but it was a bit difficult to set up.

For a list and description of all commands available in the bootloader (hint: there are lots), see the ''KA655 CPU System Maintenance'' guide mentioned in the ''References'' section..

==Bootstrapping ULTRIX==
You will see the following output on the first boot.
<pre>
>>>boot dua2
(BOOT/R5:0 DUA2

2..
-DUA2
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 945424
data = 1290240
bss = 757940
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #2: Wed Oct 18 12:06:55 EDT 1995
real mem = 67043328
avail mem = 61517824
Buffer configuration adjusted to run with small system page table
using 123 buffers containing 1007616 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
WARNING: clock gained 47 days -- CHECK AND RESET THE DATE!

*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice:
</pre>
Now we want to do an ''ADVANCED Installation'', but when we try to, it will take a few seconds until the installation program dumps us to a prompt because it couldn't find a valid device to install from and to:
<pre>
Enter your choice: 2

*** SOFTWARE DISTRIBUTION DEVICE SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of software distribution devices and which installation media you should
load on it:

No valid device is found.
Contact a DIGITAL field service representative.

#
</pre>

The problem seems to be that the hardware SimH emulates is not fully supported by ULTRIX (or is misdetected -- I'm not entirely sure myself). The good thing is that the internet has the correct solution, which is to fix some lines in the installation shell script. The fact that the basic system that is running at this point doesn't have ''vi'', or even ''cat'', makes this a bit harder ;-)

The only option you have is ''ed'', the old UNIX editor. For a quick introduction, see [http://blog.sanctum.geek.nz/actually-using-ed/ here].

To load the file in the editor, use
# '''ed install.1'''
16763

You can see the entire file with
1,$l
but be warned, the output is quite long and it'll take some time to print it all out.

To fix it, use the following commands (the lines in '''bold''' is what you type, everything else is the response from ed)
# '''ed install.1'''
16763
'''173l'''
BTD=`btd`
'''173s/`btd`/ra2/'''
'''173l'''
BTD=ra2
'''193l'''
rz* )
'''193s/rz/ra/'''
'''193l'''
ra* )
'''w'''
16761
'''q'''
#

First, we list line 173, then we change it from <code>BTD=`btd`</code> to <code>BTD=ra2</code>, which happens to be the CDROM device and unit number we're installing from (if you changed that in your config, use the correct name here!)

Then we change line 193 from <code>rz* )</code> to <code>ra* )</code> since we're trying to install on an RA type disk which was apparently not supported in ULTRIX out of the box.

After writing the file with <code>w</code> and quitting ed with <code>q</code>, we're back at the prompt, at which point we can use CTRL+D to retry the installation:

<pre>
# ^D
*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice: 2

*** SYSTEM DISK SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of system disk drives. Select one of the devices below to contain the
root file system:

SYSTEM DISK TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk drive
is on line and write-enabled (if applicable to your disk drive), then
confirm your choice.

Use RA90, ra0, for your system disk? (y/n) []: y

The installation procedure now allocates the root file system on
partition 'a' of the system disk, ra0 RA90.

Making the root file system on ra0 RA90.

The installation procedure is now restoring the root file system to
partition 'a' of the system disk, ra0 RA90.

The installation procedure now checks the root file system on partition 'a'
of the system disk, ra0 RA90.
** /dev/rra0a
** Last Mounted on /mnt
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
226 files, 4547 used, 11004 free (20 frags, 1373 blocks, 1.0% fragmentation)

*** BOOTSTRAP COMMAND SEQUENCE ***

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 8007F799
>>>
</pre>
After this, you will be back at the VAX boot prompt (if you used <code>set CPU CONHALT</code> in your config) or at the SimH emulator prompt (if you used <code>set CPU SIMHALT</code>, which is the default). In the latter case you will have to do <code>boot cpu</code> again to get to the VAX boot prompt.

==First boot==
Now we can boot the installed system from harddisk for the first time.

If you want to, now would be a good time to take a backup copy of your disk files (or just create a btrfs snapshot or something if you have the possibility ;-)

Okay, then let's boot from DUA0
<pre>
>>>boot dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 1153664
data = 281088
bss = 1043548
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #3: Wed Oct 18 11:49:00 EDT 1995
real mem = 67043328
avail mem = 62008320
Buffer configuration adjusted to run with small system page table
using 121 buffers containing 991232 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
</pre>
Here, it will seem to hang for a loooong time. A few minutes. Don't worry, it will eventually continue to boot. I guess it's probing for other devices which are not present.

You ''might'' be able to speed this up a bit by interrupting SimH (press CTRL+E in the SimH console window) and then using <code>set CPU noidle</code> followed by <code>go</code> to resume emulation.

Eventually, you will have to decide on a hostname. Note that if you want to play around with [[DECnet]] at some point, your hostname should be no longer than 6 characters.
<pre>
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)

*** SYSTEM NAME SPECIFICATION ***

Select the name of your system using alphanumeric characters.
The first character must be a letter. For example, tinker.

Enter your system name: yuki

You selected yuki as the name of your system.
Is this correct? (y/n) [y]: y
</pre>

Next up is the time configuration. Since Ultrix 4.5 is not Y2k compliant (AFAIK), I decided to set the clock back a whopping 20 years. Note that the timezone and daylight saving settings are for my location (Germany) and will probably vary for you.

<pre>
*** DATE AND TIME SPECIFICATION ***

The current date and time should be specified using the following
format:

yymmddhhmm

Use two digits for year (yy), month (mm), day (dd), hour (hh), and
minute (mm). Enter the time in 24-hour format. For example, 02:54
p.m. on Feb 2, 1993 would be entered as:

9302021454

Enter the date and time: 9512052336

*** TIME ZONE SELECTION ***

Select the time zone for your area, using the options listed in the
table below. You can also enter the number of hours (-12 to 12) in
time east of Greenwich.

Selection Time Zone
---------------------------------
e Eastern
c Central
m Mountain
p Pacific
g Greenwich
---------------------------------

Enter your choice: 1

Does your area alternate between Daylight Savings and Standard
time? (y/n) [y]: y

Select your geographic area for Daylight Savings Time, using the
options in the table below.

Selection Geographic Area
--------------------------------
u USA
a Australia
e Eastern Europe
c Central Europe
w Western Europe
--------------------------------

Enter your choice [u]: c

The current date and time is Tue Dec 5 23:36:46 EST 1995
</pre>

Next up is the root password. Note that Ultrix will not echo anything here, I added the asterisks just for this guide :)

<pre>
*** SPECIFY THE SUPERUSER PASSWORD ***
The Guide to Installing ULTRIX instructs you on how to enter
the superuser password.
Changing password for root
Enter new password: ******
Verify: ******
</pre>

Next up is the filesystem layout, which is a bit more involved than what you know from more modern systems like MS DOS ;-)

In ULTRIX, partitions are defined for each disk type in a file called <code>/etc/disktab</code>. Note that the partitions overlap, so you shouldn't use them all at the same time. The setup script actually takes care of that for you, but if you later create a new filesystem on the wrong partition you ''WILL'' lose data!

Normally, partition '''c''' is the whole disk, which is useful for add-on disk drives for example. Partitions '''a''' and '''b''' are always available and are traditionally used for the system and the swap-space respectively. The swap partition is also used for crashdumps if no separate crash-dump partition is created. The rest of the disk can be used either as a single partition (which is usually '''g''') or as 3 individual partitions ('''d''' to '''f'''). If the disk is larger than 1 gigabyte, you will get another partition, '''h''', after the g partition, probably because the filesystem cannot cope with partitions >1gig

In our case, we will have the following partitions on the first disk (RA0):
*Partition '''a''' of 32 mb for /root
*Partition '''b''' of 64 mb for swap+crashdump
*Partition '''c''' of 1.2 gig (whole-disk, not used on our setup)
*Partition '''d''' and '''e''' of 200 mb each (not used)
*Partition '''f''' of 400 mb (not used)
*Partition '''g''' of 800 mb (overlaps with d, e and f; will become /usr)
*Partition '''h''' of 256 mb (will become /usr/var)
This way we still have the whole second disk available for later use.

So here it goes:
<pre>
*** FILE SYSTEM DEFAULT OPTION ***

The following table shows the default file system layout on RA90, ra0:

partition bottom top size overlap default
a 0 32767 32768 c root
b 32768 159839 127072 c swap, dump
d 159840 580036 420197 c,g /usr

If you choose the defaults, the var area will be allocated to /usr/var.

Do you want to choose the default file system layout? (y/n): n
</pre>

No, we do not want to use the defaults...

First, we select disk 1, partition '''g''', for the /usr file system:
<pre>
*** /usr FILE SYSTEM ALLOCATION ***

You can allocate the /usr file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

/usr FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for /usr file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the /usr file system:

partition size (Kbytes) overlap
------------------------------------------------
d --- 210098 c,g
e --- 210098 c,g
f --- 420196 c,g
g --- 840393 c,d,e,f
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the /usr file system [d]: g

Making the new file system for /usr on /dev/rra0g RA90
</pre>

Next, we select disk 1, partition '''b''' for swap (only 1 swap partition) and for crashdumps:

<pre>
*** ALLOCATE THE SWAP1 SPACE ***

You can allocate the swap1 space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

SWAP1 SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for swap1 space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the swap1 space:

partition size (Kbytes) overlap
------------------------------------------------
b --- 63536 c
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the swap1 space [b]: b

*** ALLOCATE THE SWAP2 SPACE ***

Do you want to allocate a second swap space? (y/n) [n]: n

*** ALLOCATE THE CRASH DUMP SPACE ***

You can allocate the crash dump space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

CRASH DUMP SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for crash dump space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the crash dump space:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
b --- 63536 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the crash dump space [b]: b
</pre>

Finally we select partiton '''h''' for the /var file system. This might not be large enough later on but then we can always migrate the data away if we need to...

<pre>
*** ALLOCATE THE var FILE SYSTEM ***

You can allocate the var file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

var FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for var file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the var file system:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
g --- 840393 c,d,e,f
------------------------------------------------

Type the letter of the partition on which you want
to allocate the var file system [no default]: h

Making the new file system for var on /dev/rra0h RA90
</pre>

==Installing the distribution files==

Next up we have to decide what ''packages'' we want to install (yes, ULTRIX already had its own package format and corresponding installer called ''setld''. It is very basic, probably most similar to ''pkg_add'' on NetBSD). We simply install everything, since we have enough space :)

<pre>
This distribution media includes subsets for ULTRIX Worksystem
Software (UWS). A UWS license (on a workstation) or a UWS Server
License (on a timesharing machine or server) is required to install
these subsets.

Do you want to install ULTRIX Worksystem Software? y/n []: y

*** SUPPORTED SOFTWARE INSTALLATION ***

*** Select the DECwindows User Interface ***

1) DECwindows for OSF/Motif
2) X11/DECwindows (XUI)

Enter your choice [1]: 2

*** Enter Subset Selections ***

The following subsets are mandatory and will be installed automatically:
* Base System * Kernel Config Files
* TCP/IP Networking Utilities * Network File System Utilities
* Extended (Berkeley) Mailer * X11/DECwindows Servers
* X11/DECwindows User Environment * X11/DECwindows 75dpi Fonts

The subsets listed below are optional:
1) Printer Support Environment 2) RAND Mail Handler
3) Sys. Config. Mgmt. Program (SCAMP) 4) Communications Utilities
5) Unix-to-Unix Copy Facility 6) Maintenance Operations Protocol
7) Accounting Software 8) Kerberos Network Authentication
9) Enhanced Security Features 10) Prestoserve Utilities
11) System Exerciser Package 12) Bisynchronous Communications
13) Doc. Preparation for Ref. Pages 14) Doc. Preparation Extensions
15) Adobe Font Metric Files 16) Software Development Utilities
17) Source Code Control System 18) Internationalization Runtime Env.
19) Internationalization Dev. Env. 20) CDA Base System
21) CDA Software Dev Libraries 22) RPC Runtime Environment
23) RPC Development Environment 24) Pascal Development Package
25) VAX C/ULTRIX 26) Ref. Pages for Sys. Admin. & Users
27) Reference Pages for Programers 28) Programming Examples
29) Ultrix SPDS 30) X11/DECwindows 100dpi Fonts
31) VS35XX X11/DECwindows Fonts 32) Additional DECwindows Applications
33) DECwindows Mail Application 34) Worksystem Development Environment
35) X11/DECwindows System Management T 36) UWS Runtime Reference Pages
37) UWS Development Reference Pages

38) All mandatory and all optional subsets
39) Mandatory subsets only
40) Exit without installing subsets

Enter your choice(s): 38
Working....Wed Dec 6 00:14:12 EST 1995

You are installing the following subsets:
Base System Kernel Config Files
TCP/IP Networking Utilities Network File System Utilities
Extended (Berkeley) Mailer X11/DECwindows Servers
X11/DECwindows User Environment X11/DECwindows 75dpi Fonts
Printer Support Environment RAND Mail Handler
Sys. Config. Mgmt. Program (SCAMP) Communications Utilities
Unix-to-Unix Copy Facility Maintenance Operations Protocol
Accounting Software Kerberos Network Authentication
Enhanced Security Features Prestoserve Utilities
System Exerciser Package Bisynchronous Communications
Doc. Preparation for Ref. Pages Doc. Preparation Extensions
Adobe Font Metric Files Software Development Utilities
Source Code Control System Internationalization Runtime Env.
Internationalization Dev. Env. CDA Base System
CDA Software Dev Libraries RPC Runtime Environment
RPC Development Environment Pascal Development Package
VAX C/ULTRIX Ref. Pages for Sys. Admin. & Users
Reference Pages for Programers Programming Examples
Ultrix SPDS X11/DECwindows 100dpi Fonts
VS35XX X11/DECwindows Fonts Additional DECwindows Applications
DECwindows Mail Application Worksystem Development Environment
X11/DECwindows System Management To UWS Runtime Reference Pages
UWS Development Reference Pages

Is this correct? (y/n): y
</pre>

The installation will take a while (around 15-30 minutes for me), so feel free to let it run in the background for a while now. The installer will periodically print its status so you can see that it's still running...

<pre>
Base System (ULTBASE450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:14:43 EST 1995
Verifying

Kernel Config Files (ULTBIN450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:15:28 EST 1995
Verifying

...
</pre>

At some point you will have to confirm installing the generic kernel and the X11 subsystem:

<pre>
...
UWS Runtime Reference Pages (UWSMAN450)
Copying from /mnt/VAX/BASE (disk)
Verifying

UWS Development Reference Pages (UWSMANPGMR450)
Copying from /mnt/VAX/BASE (disk)
Verifying

The installation software has successfully installed the software
subsets.
Installing Upgrade subsets
The following subsets will be installed:
* X11/DECwindows Servers Upgrade * Generic Kernel
Do you wish to continue? (y/n): y

X11/DECwindows Servers Upgrade (UWSSER451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

Generic Kernel (ULTGENVMUNIX451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

The installation procedure has successfully installed the Upgrade
subsets
</pre>

That's it for the base installation, now we configure our kernel...

==Kernel configuration==
We have to select what features will be in the kernel. For anyone who has ever done a "make menuconfig" on Linux, this is ''slightly'' easier here ;-)
<pre>
*** CONFIGURATION FILE KERNEL OPTION SELECTION ***

Selection Kernel Option
---------------------------------------------------------------
1 Local Area Transport (LAT)
2 Bisynchronous Communication protocol (VAX only)
3 Computer Interconnect (CI) network
4 Diagnostic/Utilities Protocol (DUP)
5 ISO9660 File System Support (CDFS)
6 Ethernet Packet Filter
7 Enhanced Security Features
8 All of the above
9 None of the above
----------------------------------------------------------------

Enter the selection number for each kernel option you want.
For example, 1 3 :
</pre>

In our case, we don't need 2 (it is for 2780/3780 remote terminals), 3 (SimH doesn't emulate any cluster hardware) or 6 (it might cause problems with DECwindows/Motif). Everything else (<code>1 4 5 7</code>) is probably safe. This lets us play around with LAT (maybe connect an emulated Cisco router with LAT routing to it?) and DUP.

<pre>
Enter the selection number for each kernel option you want.
For example, 1 3 : 1 4 5 7

You specified the following kernel options:

Local Area Transport (LAT)
Diagnostic/Utilities Protocol (DUP)
ISO9660 File System Support (CDFS)
Enhanced Security Features

Is this correct? (y/n) [n]: y

*** SYSTEM CONFIGURATION PROCEDURE ***
The installation software found these devices in the floating
address space:

dz0 on uba0 at 0160100
dz1 on uba0 at 0160110
dz2 on uba0 at 0160120
dz3 on uba0 at 0160130

Configuration file complete.

Do you want to edit the configuration file? (y/n) [n]: n

*** PERFORMING SYSTEM CONFIGURATION ***

working ..... Wed Dec 6 02:29:10 EST 1995

*** DEVICE SPECIAL FILE CREATION ***
working ..... Wed Dec 6 02:29:53 EST 1995

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 800985B5
</pre>

Now you might want to take another backup of your disk images, since the ULTRIX installation is now basically complete.

==Adding the unsupported sets==
Now there are some more pieces of software in the CDROM, in a directory called ''unsupported''. We want to install these as well. First, let's boot our system again

<pre>
>>>b dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 747376
data = 125952
bss = 918192
Starting at 0x2c19

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
real mem = 67043328
avail mem = 56455168
using 1638 buffers containing 6712320 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
dz0 at uba0 csr 160100 vec 300, ipl 17
dz1 at uba0 csr 160110 vec 310, ipl 17
dz2 at uba0 csr 160120 vec 320, ipl 17
dz3 at uba0 csr 160130 vec 330, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
Wed Dec 6 11:25:29 MET 1995
Automatic reboot in progress...
/dev/ra0a: 644 files, 6161 used, 9390 free (166 frags, 1153 blocks, 5.0% fragmentation)
/dev/rra0g: umounted cleanly
/dev/rra0h: umounted cleanly
Warning Creating new license database
Warning creating new history file
check quotas: done.
savecore: checking for dump...dump does not exist
local daemons: syslog sendmail.
Removing remnant Opser files
preserving editor files
clearing /tmp
standard daemons: update cron accounting network snmpd printer.
start errlog daemon - elcsd
Wed Dec 6 11:25:48 MET 1995

ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
UWS V4.5 (Rev. 6)

Digital Equipment Corporation
Nashua, New Hampshire

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

#
</pre>

now, we mount the CDROM and use <code>setld</code> to install the unsupported packages. For simplicity's sake, we just (again) install everything.

<pre>
# mount -r /dev/ra2c /mnt
# cd /mnt/VAX/UNSUPPORTED
# ls
DXVUNDEMO450 ULXDOC450 ULXINGRES450 ULXRCS450 ULXUNMAN450
ULXAPL450 ULXEDIT450 ULXLEARN450 ULXSHELLS450 ULXUNMIT450
ULXBASE450 ULXF77450 ULXLISP450 ULXSPMS450 ULXVARIAN450
ULXBIB450 ULXGAMES450 ULXMAN450 ULXTERM450 instctrl
ULXCOURIER450 ULXHYPER450 ULXMOD2450 ULXTOOLS450
ULXCPM450 ULXICON450 ULXNEWS450 ULXUNEXAMP450
ULXDCMT450 ULXINET450 ULXNOTES450 ULXUNFONTS450
# setld -l .

*** Enter Subset Selections ***

The subsets listed below are optional:
1) Base Extension 2) GNU Emacs
3) TCP/IP Networking Util Extension 4) Additional Terminal Drivers
5) Document Preparation Software 6) Games and Diversions
7) Supplementary Documentation 8) Bibliographic Utilities
9) Remote Procedure Call Compiler 10) Aux. Command Line Interpreters
11) USENET News Interface Software 12) Notesfiles Package
13) Revision Control System 14) Misc. User-Contributed Utilities
15) Computer Aided System Tutor 16) Franz Lisp Development Package
17) Modula-2 Development Package 18) Raster Plotter Package
19) APL Development Package 20) CP/M 8in Diskette Utility
21) Hyperchannel Utilities 22) ICON (Language) Development Packag
23) University Ingres QUEL DBMS 24) Software Project Management System
25) Unsupported Fortran Utilities 26) Unsupported On-Line Documentation
27) Unsupported X11 Components 28) Unsupported DECwindows Examples
29) Unsupported MIT Fonts 30) Unsupported X11 Reference Pages
31) Unsupported OSF/Motif Demos

32) All mandatory and all optional subsets
33) Mandatory subsets only
34) Exit without installing subsets

Enter your choice(s): 32
Working....Wed Dec 6 11:29:48 MET 1995
Wed Dec 6 11:30:00 MET 1995

You are installing the following subsets:
Base Extension GNU Emacs
TCP/IP Networking Util Extension Additional Terminal Drivers
Document Preparation Software Games and Diversions
Supplementary Documentation Bibliographic Utilities
Remote Procedure Call Compiler Aux. Command Line Interpreters
USENET News Interface Software Notesfiles Package
Revision Control System Misc. User-Contributed Utilities
Computer Aided System Tutor Franz Lisp Development Package
Modula-2 Development Package Raster Plotter Package
APL Development Package CP/M 8in Diskette Utility
Hyperchannel Utilities ICON (Language) Development Package
University Ingres QUEL DBMS Software Project Management System
Unsupported Fortran Utilities Unsupported On-Line Documentation
Unsupported X11 Components Unsupported DECwindows Examples
Unsupported MIT Fonts Unsupported X11 Reference Pages
Unsupported OSF/Motif Demos

Is this correct? (y/n): y

Base Extension (ULXBASE450)
Copying from . (disk)
Verifying

GNU Emacs (ULXEDIT450)
Copying from . (disk)
Verifying

TCP/IP Networking Util Extension (ULXINET450)
Copying from . (disk)
Verifying
...
</pre>

Note that you could also quickly install only a single package by using for example
# setld -l . ULXINET450

After a few minutes, installation will be completed and we should unmount the CDROM
# cd /
# umount /mnt

==Network configuration==
To configure the network, you have to use a static IPv4 address and put that into the beginning of /etc/rc.local. Note that there is no <code>ifconfig -a</code> in ULTRIX, you have to use <code>netstat -i</code>

<pre>
# netstat -i
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
qe0* 1500 none none 0 0 0 0 0
lo0 1536 loop localhost 1 0 1 0 0
# ifconfig qe0 192.168.1.44 netmask 255.255.255.0 up
# route add default 192.168.1.1 1
add net default: gateway 192.168.1.1
# ping 192.168.1.1
192.168.1.1 is alive
</pre>
Note that it might actually take a while until packets are getting through. I don't know why but in my case it helped to ping ULTRIX from the outside first, e.g. from Windows, and then re-try the ping from the VM. Then it worked. I'm guessing this is some SimH/Windows issue with PCAP or something.

Then put these 2 commands at the start of <code>/etc/rc.local</code> (you'll see where). Note that you can use <code>vi</code> now!
<pre>
# @(#)rc.local 9.4 (ULTRIX) 9/21/95
/bin/hostname yuki
#/etc/ifconfig HDWR `/bin/hostname` broadcast NETNUM.0 netmask 255.0
/etc/ifconfig qe0 192.168.1.44 netmask 255.255.255.0
route add default 192.168.1.1 1
/etc/ifconfig lo0 localhost
#/etc/bscconfig dup0 bsc 1
#/etc/bscconfig dpv0 bsc 1
...
</pre>

==Shutting down cleanly==
As you'd expect, you can use <code>shutdown</code> to shut the system down
<pre>
# shutdown -h now
Shutdown at 11:15 (in 0 minutes) [pid 1500]
#
System shutdown time has arrived
syncing disks... done

?06 HLT INST
PC = 80094CDD
>>>
</pre>

==Enabling serial access==
The SimH config above includes a 16-line serial multiplexer. If you connect via TELNET to port 1005, you are given the first free serial line of the emulated DZ device. However, serial login is disabled by default, so it has to be enabled first. That's what the <code>/etc/ttys</code> file is for. Edit the file and change the ''off'' to ''on'' in the lines for tty00 to tty07, as shown below
<pre>
# @(#)ttys 9.1 (ULTRIX) 4/26/94
#
#
#
# name getty type status comments
#
console "/etc/getty std.9600" vt100 on secure # console terminal
tty00 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty01 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty02 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty03 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty04 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty05 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty06 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty07 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
ttyd0 "/etc/getty std.9600" vt100 off shared secure # modem line
</pre>

If you want to be able to login as root on these terminals, you can also add the <code>secure</code> flag as well. Also note that while it seems tempting to increase the line speed to 19200 or even higher, from my experience that will cause massive lags and emulation hangs in SimH, so do that on your own risk.

After editing the file and saving it, you have to reload init:
# kill -HUP 1

Now try logging in to port 1005 via telnet, and you should be greeted with this:
<pre>
Connected to the MicroVAX 3900 simulator DZ device, line 0

ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:
Requires secure terminal
</pre>

Note that SimH will print out the serial line to which you are connected, in this case line 0 which is /dev/tty00.

==Resources==
Some of the resources I used for creating this guide:
*ULTRIX 4.5 installation ISO [http://musall.de/mirrors/ultrix/ultrix_os/vax/]
*ULTRIX-32 startup and shutdown guide [http://bitsavers.trailing-edge.com/pdf/dec/vax/ultrix-32/3.0/AA-ME91A-TE_ULTRIX-32_Guide_to_System_Shutdown_and_Startup.pdf]
*CERN guide to installing ULTRIX [https://web-docs.gsi.de/~kraemer/COLLECTION/ULTRIX/wwwpdp.web.cern.ch/wwwpdp/as/file/doc/ultrix/ultrix.pdf]
*My old guide for installing ULTRIX [https://docs.google.com/document/d/1ULRhzE0R1twarB5hfJm85yqOdTeoFCGgyPr5AxYEIbE]
*DEC KA655 CPU System Maintenance [http://bitsavers.trailing-edge.com/pdf/dec/vax/655/EK-306A-MG-001_655Mnt_Mar89.pdf]
[[Category:SIMH Tutorials]]

Installing Ultrix 4.5 on SIMH

2015-12-06T10:10:32Z

Darkstar: Network and Shutdown

This WORK-IN-PROGRESS guide will be a simple guide to installing ULTRIX 4.5 for VAX on SimH.

==Requirements==
The following is a list of things required for installation
*A recent version of the [[SIMH]] emulator
**Make sure the binary you're using includes Ethernet support
**I'm using a self-compiled version (git revision 0e8c0aea)
*An ISO image of ULTRIX 4.5 for VAX
**See the "Resources" section for a download link
**It's probably also possible to install it from tape, although I don't know if any installation tapes for ULTRIX 4.5 exist
*Optional stuff (might get added to the guide later):
**Starfish Ultrix Freeware CDs from [http://musall.de/mirrors/ultrix/freeware/ here]

==SimH configuration==
The machine I'm using to run ULTRIX has the following configuration
*DEC MicroVAX 3800
*64mb memory
*DELQA network card (XQ0)
*Two [[RA90]] disk drives (with 1.2gb each) attached to an RQDX3 controller (RQ0 and RQ1)
*CD ROM drive attached to the same RQDX3 controller as unit 2 (RQ2)
*[[TK50]] tape attached as unit 0 on the first TQK50 controller (TQ0)
*DZV11 terminal multiplexer with 16 lines, attached to telnet port 1005 (DZ)
*LPT line printer attached to text file <code>printer_output.txt</code>

Here's my config file (I called it <code>simh.conf</code>)
<pre><nowiki>
;
; SimH 4.0 Configuration file for MicroVAX 3800
;
; Host System : DEC MicroVAX 3800
; Operating System : DEC Ultrix v4.5
; Memory : 64mb
; Network config : XQ: Ethernet, 08:00:2b:04:14:02
; Disks : RQ0: RA90, 1.2gb
; RQ1: RA90, 1.2gb
; CDROMs : RQ2: iso file
; Tape config : TQ0: TK50, 94mb
;

load -r ka655x.bin

; NVRAM
attach NVR nvram.bin

; CPU config
set CPU 64m
set CPU conhalt
set CPU idle=all

; configure console to 7-bit only
set TTO 7b
set TTI 7b

; Disk drives
set RQ0 ra90
attach RQ0 rq0-ra90.dsk
set RQ1 ra90
attach RQ1 rq1-ra90.dsk
set RQ2 CDROM
attach -r RQ2 ultrix-vax-os-v4.5.mode1.ufs.iso
; MD5 sum: 19df0753c27f195e9f1d2f139a3b4629 *ultrix-vax-os-v4.5.mode1.ufs.iso
set RQ3 dis

; Tape
set TQ tk50
;attach tq0 filename-to-tape-file
set TQ1 dis
set TQ2 dis
set TQ3 dis

; serial port, simulated by Telnet to port 1005
set DZ LINES=16
set DZ 8B
attach DZ 1005 NoBuffer

; printer
set LPT enable
attach LPT printer_output.txt

; Disable unused peripherals
set CR dis
set RL dis
set TS dis

; Network interface (08-00-2b is the DEC prefix, the 04-14-02 part is arbitrary)
set XQ MAC=08-00-2b-04-14-02
attach XQ0 eth0

; serial console (launch directly after booting CPU)
set console telnet=1001

; experimental
;set QVSS en

; boot the system
;boot CPU
</nowiki></pre>
Note that I'm using a telnet console (for easier copy/paste on Windows), which means that directly after running this config file (via <code>do simh.conf</code> from Simh) you will need to connect via telnet to localhost:1001 or the boot will abort. If you are on Linux, or just don't want that, remove the <code>set console telnet=1001</code> line.

Also note that you might need to attach XQ0 to a different ethernet device. Use "show ether" in SimH to list all available devices on your system and modify the <code>attach XQ0 eth0</code> line accordingly.

==Running the Emulator==
Either run <code>vax.exe simh.conf</code> from the Windows command line, or just double-click the VAX.EXE executable and type <code>do simh.conf</code>.

On the first launch it might take some time because SimH has to create the disk images (~2.5 gb total). It should look something like this
<pre><nowiki>
MicroVAX 3900 simulator V4.0-0 Beta git commit id: 0e8c0aea
NVR: buffering file in memory
RQ2: unit is read only
Listening on port 1005
WinPcap version 4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008)
Eth: opened OS device \Device\NPF_{A41A1651-DD4D-4735-A4E0-88353165C2EC}
Listening on port 1001
sim>
</nowiki></pre>

Type the following to start the emulation (note: you can also uncomment that line from the end of the config file to have the emulation start right away)
sim> boot cpu
Waiting for console Telnet connection

Now would be a good time to connect your telnet session (I use a batch file for this), otherwise the boot process will timeout.

On your console, you should see something like this:
<pre><nowiki>
Connected to the MicroVAX 3900 simulator CON-TEL device

KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>
</nowiki></pre>

This is the VAX's boot prompt. Normally you just type
>>>boot <device>
where <device> is one of the following
*MUA<num>: TK tape device number <num> (1 to 4)
*DUA<num>: RQ disk device number <num> (1 to 4)

You can use <code>show device</code> to see the installed (and detected) devices you can boot from, and <code>show boot</code> to see which device will be the default if you just type <code>boot</code> (or <code>b</code> for short):
<pre><nowiki>
>>>show device
UQSSP Disk Controller 0 (772150)
-DUA0 (RA90)
-DUA1 (RA90)
-DUA2 (RRD40)

UQSSP Tape Controller 0 (774500)
-MUA0 (TK50)

Ethernet Adapter 0 (774440)
-XQA0 (08-00-2B-04-14-02)
>>>show boot
MUA0
</nowiki></pre>

Since we want to boot from CDROM, which is unit 2, we can use
>>>boot DUA2

Note: You can add flags to boot into single user mode, or to boot in interactive mode (so-called ''conversational boot'', where the system prompts you for a kernel file name to load). For details see the Guide to ULTRIX-32 System Startup and Shutdown, linked to in the ''References'' section. To use it, add the <code>/R5:<flags></code> option to the <code>boot</code> command, where flags is 0 (default multi-user), 1 (conversational multi-user), 2 (single-user) or 3 (conversational single-user). For example
>>>boot/r5:3 dua0

Note: You can also boot from ethernet (<code>boot XQA0</code>) but this requires a DEC-specific boot server in your network (the protocol is called ''MOP'' for ''Maintenance Operations Protocol''), which is beyond the scope of this document. I did get it to work a few years ago though, but it was a bit difficult to set up.

For a list and description of all commands available in the bootloader (hint: there are lots), see the ''KA655 CPU System Maintenance'' guide mentioned in the ''References'' section..

==Bootstrapping ULTRIX==
You will see the following output on the first boot.
<pre>
>>>boot dua2
(BOOT/R5:0 DUA2

2..
-DUA2
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 945424
data = 1290240
bss = 757940
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #2: Wed Oct 18 12:06:55 EDT 1995
real mem = 67043328
avail mem = 61517824
Buffer configuration adjusted to run with small system page table
using 123 buffers containing 1007616 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
WARNING: clock gained 47 days -- CHECK AND RESET THE DATE!

*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice:
</pre>
Now we want to do an ''ADVANCED Installation'', but when we try to, it will take a few seconds until the installation program dumps us to a prompt because it couldn't find a valid device to install from and to:
<pre>
Enter your choice: 2

*** SOFTWARE DISTRIBUTION DEVICE SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of software distribution devices and which installation media you should
load on it:

No valid device is found.
Contact a DIGITAL field service representative.

#
</pre>

The problem seems to be that the hardware SimH emulates is not fully supported by ULTRIX (or is misdetected -- I'm not entirely sure myself). The good thing is that the internet has the correct solution, which is to fix some lines in the installation shell script. The fact that the basic system that is running at this point doesn't have ''vi'', or even ''cat'', makes this a bit harder ;-)

The only option you have is ''ed'', the old UNIX editor. For a quick introduction, see [http://blog.sanctum.geek.nz/actually-using-ed/ here].

To load the file in the editor, use
# '''ed install.1'''
16763

You can see the entire file with
1,$l
but be warned, the output is quite long and it'll take some time to print it all out.

To fix it, use the following commands (the lines in '''bold''' is what you type, everything else is the response from ed)
# '''ed install.1'''
16763
'''173l'''
BTD=`btd`
'''173s/`btd`/ra2/'''
'''173l'''
BTD=ra2
'''193l'''
rz* )
'''193s/rz/ra/'''
'''193l'''
ra* )
'''w'''
16761
'''q'''
#

First, we list line 173, then we change it from <code>BTD=`btd`</code> to <code>BTD=ra2</code>, which happens to be the CDROM device and unit number we're installing from (if you changed that in your config, use the correct name here!)

Then we change line 193 from <code>rz* )</code> to <code>ra* )</code> since we're trying to install on an RA type disk which was apparently not supported in ULTRIX out of the box.

After writing the file with <code>w</code> and quitting ed with <code>q</code>, we're back at the prompt, at which point we can use CTRL+D to retry the installation:

<pre>
# ^D
*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice: 2

*** SYSTEM DISK SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of system disk drives. Select one of the devices below to contain the
root file system:

SYSTEM DISK TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk drive
is on line and write-enabled (if applicable to your disk drive), then
confirm your choice.

Use RA90, ra0, for your system disk? (y/n) []: y

The installation procedure now allocates the root file system on
partition 'a' of the system disk, ra0 RA90.

Making the root file system on ra0 RA90.

The installation procedure is now restoring the root file system to
partition 'a' of the system disk, ra0 RA90.

The installation procedure now checks the root file system on partition 'a'
of the system disk, ra0 RA90.
** /dev/rra0a
** Last Mounted on /mnt
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
226 files, 4547 used, 11004 free (20 frags, 1373 blocks, 1.0% fragmentation)

*** BOOTSTRAP COMMAND SEQUENCE ***

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 8007F799
>>>
</pre>
After this, you will be back at the VAX boot prompt (if you used <code>set CPU CONHALT</code> in your config) or at the SimH emulator prompt (if you used <code>set CPU SIMHALT</code>, which is the default). In the latter case you will have to do <code>boot cpu</code> again to get to the VAX boot prompt.

==First boot==
Now we can boot the installed system from harddisk for the first time.

If you want to, now would be a good time to take a backup copy of your disk files (or just create a btrfs snapshot or something if you have the possibility ;-)

Okay, then let's boot from DUA0
<pre>
>>>boot dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 1153664
data = 281088
bss = 1043548
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #3: Wed Oct 18 11:49:00 EDT 1995
real mem = 67043328
avail mem = 62008320
Buffer configuration adjusted to run with small system page table
using 121 buffers containing 991232 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
</pre>
Here, it will seem to hang for a loooong time. A few minutes. Don't worry, it will eventually continue to boot. I guess it's probing for other devices which are not present.

You ''might'' be able to speed this up a bit by interrupting SimH (press CTRL+E in the SimH console window) and then using <code>set CPU noidle</code> followed by <code>go</code> to resume emulation.

Eventually, you will have to decide on a hostname. Note that if you want to play around with [[DECnet]] at some point, your hostname should be no longer than 6 characters.
<pre>
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)

*** SYSTEM NAME SPECIFICATION ***

Select the name of your system using alphanumeric characters.
The first character must be a letter. For example, tinker.

Enter your system name: yuki

You selected yuki as the name of your system.
Is this correct? (y/n) [y]: y
</pre>

Next up is the time configuration. Since Ultrix 4.5 is not Y2k compliant (AFAIK), I decided to set the clock back a whopping 20 years. Note that the timezone and daylight saving settings are for my location (Germany) and will probably vary for you.

<pre>
*** DATE AND TIME SPECIFICATION ***

The current date and time should be specified using the following
format:

yymmddhhmm

Use two digits for year (yy), month (mm), day (dd), hour (hh), and
minute (mm). Enter the time in 24-hour format. For example, 02:54
p.m. on Feb 2, 1993 would be entered as:

9302021454

Enter the date and time: 9512052336

*** TIME ZONE SELECTION ***

Select the time zone for your area, using the options listed in the
table below. You can also enter the number of hours (-12 to 12) in
time east of Greenwich.

Selection Time Zone
---------------------------------
e Eastern
c Central
m Mountain
p Pacific
g Greenwich
---------------------------------

Enter your choice: 1

Does your area alternate between Daylight Savings and Standard
time? (y/n) [y]: y

Select your geographic area for Daylight Savings Time, using the
options in the table below.

Selection Geographic Area
--------------------------------
u USA
a Australia
e Eastern Europe
c Central Europe
w Western Europe
--------------------------------

Enter your choice [u]: c

The current date and time is Tue Dec 5 23:36:46 EST 1995
</pre>

Next up is the root password. Note that Ultrix will not echo anything here, I added the asterisks just for this guide :)

<pre>
*** SPECIFY THE SUPERUSER PASSWORD ***
The Guide to Installing ULTRIX instructs you on how to enter
the superuser password.
Changing password for root
Enter new password: ******
Verify: ******
</pre>

Next up is the filesystem layout, which is a bit more involved than what you know from more modern systems like MS DOS ;-)

In ULTRIX, partitions are defined for each disk type in a file called <code>/etc/disktab</code>. Note that the partitions overlap, so you shouldn't use them all at the same time. The setup script actually takes care of that for you, but if you later create a new filesystem on the wrong partition you ''WILL'' lose data!

Normally, partition '''c''' is the whole disk, which is useful for add-on disk drives for example. Partitions '''a''' and '''b''' are always available and are traditionally used for the system and the swap-space respectively. The swap partition is also used for crashdumps if no separate crash-dump partition is created. The rest of the disk can be used either as a single partition (which is usually '''g''') or as 3 individual partitions ('''d''' to '''f'''). If the disk is larger than 1 gigabyte, you will get another partition, '''h''', after the g partition, probably because the filesystem cannot cope with partitions >1gig

In our case, we will have the following partitions on the first disk (RA0):
*Partition '''a''' of 32 mb for /root
*Partition '''b''' of 64 mb for swap+crashdump
*Partition '''c''' of 1.2 gig (whole-disk, not used on our setup)
*Partition '''d''' and '''e''' of 200 mb each (not used)
*Partition '''f''' of 400 mb (not used)
*Partition '''g''' of 800 mb (overlaps with d, e and f; will become /usr)
*Partition '''h''' of 256 mb (will become /usr/var)
This way we still have the whole second disk available for later use.

So here it goes:
<pre>
*** FILE SYSTEM DEFAULT OPTION ***

The following table shows the default file system layout on RA90, ra0:

partition bottom top size overlap default
a 0 32767 32768 c root
b 32768 159839 127072 c swap, dump
d 159840 580036 420197 c,g /usr

If you choose the defaults, the var area will be allocated to /usr/var.

Do you want to choose the default file system layout? (y/n): n
</pre>

No, we do not want to use the defaults...

First, we select disk 1, partition '''g''', for the /usr file system:
<pre>
*** /usr FILE SYSTEM ALLOCATION ***

You can allocate the /usr file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

/usr FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for /usr file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the /usr file system:

partition size (Kbytes) overlap
------------------------------------------------
d --- 210098 c,g
e --- 210098 c,g
f --- 420196 c,g
g --- 840393 c,d,e,f
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the /usr file system [d]: g

Making the new file system for /usr on /dev/rra0g RA90
</pre>

Next, we select disk 1, partition '''b''' for swap (only 1 swap partition) and for crashdumps:

<pre>
*** ALLOCATE THE SWAP1 SPACE ***

You can allocate the swap1 space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

SWAP1 SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for swap1 space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the swap1 space:

partition size (Kbytes) overlap
------------------------------------------------
b --- 63536 c
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the swap1 space [b]: b

*** ALLOCATE THE SWAP2 SPACE ***

Do you want to allocate a second swap space? (y/n) [n]: n

*** ALLOCATE THE CRASH DUMP SPACE ***

You can allocate the crash dump space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

CRASH DUMP SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for crash dump space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the crash dump space:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
b --- 63536 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the crash dump space [b]: b
</pre>

Finally we select partiton '''h''' for the /var file system. This might not be large enough later on but then we can always migrate the data away if we need to...

<pre>
*** ALLOCATE THE var FILE SYSTEM ***

You can allocate the var file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

var FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for var file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the var file system:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
g --- 840393 c,d,e,f
------------------------------------------------

Type the letter of the partition on which you want
to allocate the var file system [no default]: h

Making the new file system for var on /dev/rra0h RA90
</pre>

==Installing the distribution files==

Next up we have to decide what ''packages'' we want to install (yes, ULTRIX already had its own package format and corresponding installer called ''setld''. It is very basic, probably most similar to ''pkg_add'' on NetBSD). We simply install everything, since we have enough space :)

<pre>
This distribution media includes subsets for ULTRIX Worksystem
Software (UWS). A UWS license (on a workstation) or a UWS Server
License (on a timesharing machine or server) is required to install
these subsets.

Do you want to install ULTRIX Worksystem Software? y/n []: y

*** SUPPORTED SOFTWARE INSTALLATION ***

*** Select the DECwindows User Interface ***

1) DECwindows for OSF/Motif
2) X11/DECwindows (XUI)

Enter your choice [1]: 2

*** Enter Subset Selections ***

The following subsets are mandatory and will be installed automatically:
* Base System * Kernel Config Files
* TCP/IP Networking Utilities * Network File System Utilities
* Extended (Berkeley) Mailer * X11/DECwindows Servers
* X11/DECwindows User Environment * X11/DECwindows 75dpi Fonts

The subsets listed below are optional:
1) Printer Support Environment 2) RAND Mail Handler
3) Sys. Config. Mgmt. Program (SCAMP) 4) Communications Utilities
5) Unix-to-Unix Copy Facility 6) Maintenance Operations Protocol
7) Accounting Software 8) Kerberos Network Authentication
9) Enhanced Security Features 10) Prestoserve Utilities
11) System Exerciser Package 12) Bisynchronous Communications
13) Doc. Preparation for Ref. Pages 14) Doc. Preparation Extensions
15) Adobe Font Metric Files 16) Software Development Utilities
17) Source Code Control System 18) Internationalization Runtime Env.
19) Internationalization Dev. Env. 20) CDA Base System
21) CDA Software Dev Libraries 22) RPC Runtime Environment
23) RPC Development Environment 24) Pascal Development Package
25) VAX C/ULTRIX 26) Ref. Pages for Sys. Admin. & Users
27) Reference Pages for Programers 28) Programming Examples
29) Ultrix SPDS 30) X11/DECwindows 100dpi Fonts
31) VS35XX X11/DECwindows Fonts 32) Additional DECwindows Applications
33) DECwindows Mail Application 34) Worksystem Development Environment
35) X11/DECwindows System Management T 36) UWS Runtime Reference Pages
37) UWS Development Reference Pages

38) All mandatory and all optional subsets
39) Mandatory subsets only
40) Exit without installing subsets

Enter your choice(s): 38
Working....Wed Dec 6 00:14:12 EST 1995

You are installing the following subsets:
Base System Kernel Config Files
TCP/IP Networking Utilities Network File System Utilities
Extended (Berkeley) Mailer X11/DECwindows Servers
X11/DECwindows User Environment X11/DECwindows 75dpi Fonts
Printer Support Environment RAND Mail Handler
Sys. Config. Mgmt. Program (SCAMP) Communications Utilities
Unix-to-Unix Copy Facility Maintenance Operations Protocol
Accounting Software Kerberos Network Authentication
Enhanced Security Features Prestoserve Utilities
System Exerciser Package Bisynchronous Communications
Doc. Preparation for Ref. Pages Doc. Preparation Extensions
Adobe Font Metric Files Software Development Utilities
Source Code Control System Internationalization Runtime Env.
Internationalization Dev. Env. CDA Base System
CDA Software Dev Libraries RPC Runtime Environment
RPC Development Environment Pascal Development Package
VAX C/ULTRIX Ref. Pages for Sys. Admin. & Users
Reference Pages for Programers Programming Examples
Ultrix SPDS X11/DECwindows 100dpi Fonts
VS35XX X11/DECwindows Fonts Additional DECwindows Applications
DECwindows Mail Application Worksystem Development Environment
X11/DECwindows System Management To UWS Runtime Reference Pages
UWS Development Reference Pages

Is this correct? (y/n): y
</pre>

The installation will take a while (around 15-30 minutes for me), so feel free to let it run in the background for a while now. The installer will periodically print its status so you can see that it's still running...

<pre>
Base System (ULTBASE450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:14:43 EST 1995
Verifying

Kernel Config Files (ULTBIN450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:15:28 EST 1995
Verifying

...
</pre>

At some point you will have to confirm installing the generic kernel and the X11 subsystem:

<pre>
...
UWS Runtime Reference Pages (UWSMAN450)
Copying from /mnt/VAX/BASE (disk)
Verifying

UWS Development Reference Pages (UWSMANPGMR450)
Copying from /mnt/VAX/BASE (disk)
Verifying

The installation software has successfully installed the software
subsets.
Installing Upgrade subsets
The following subsets will be installed:
* X11/DECwindows Servers Upgrade * Generic Kernel
Do you wish to continue? (y/n): y

X11/DECwindows Servers Upgrade (UWSSER451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

Generic Kernel (ULTGENVMUNIX451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

The installation procedure has successfully installed the Upgrade
subsets
</pre>

That's it for the base installation, now we configure our kernel...

==Kernel configuration==
We have to select what features will be in the kernel. For anyone who has ever done a "make menuconfig" on Linux, this is ''slightly'' easier here ;-)
<pre>
*** CONFIGURATION FILE KERNEL OPTION SELECTION ***

Selection Kernel Option
---------------------------------------------------------------
1 Local Area Transport (LAT)
2 Bisynchronous Communication protocol (VAX only)
3 Computer Interconnect (CI) network
4 Diagnostic/Utilities Protocol (DUP)
5 ISO9660 File System Support (CDFS)
6 Ethernet Packet Filter
7 Enhanced Security Features
8 All of the above
9 None of the above
----------------------------------------------------------------

Enter the selection number for each kernel option you want.
For example, 1 3 :
</pre>

In our case, we don't need 2 (it is for 2780/3780 remote terminals), 3 (SimH doesn't emulate any cluster hardware) or 6 (it might cause problems with DECwindows/Motif). Everything else (<code>1 4 5 7</code>) is probably safe. This lets us play around with LAT (maybe connect an emulated Cisco router with LAT routing to it?) and DUP.

<pre>
Enter the selection number for each kernel option you want.
For example, 1 3 : 1 4 5 7

You specified the following kernel options:

Local Area Transport (LAT)
Diagnostic/Utilities Protocol (DUP)
ISO9660 File System Support (CDFS)
Enhanced Security Features

Is this correct? (y/n) [n]: y

*** SYSTEM CONFIGURATION PROCEDURE ***
The installation software found these devices in the floating
address space:

dz0 on uba0 at 0160100
dz1 on uba0 at 0160110
dz2 on uba0 at 0160120
dz3 on uba0 at 0160130

Configuration file complete.

Do you want to edit the configuration file? (y/n) [n]: n

*** PERFORMING SYSTEM CONFIGURATION ***

working ..... Wed Dec 6 02:29:10 EST 1995

*** DEVICE SPECIAL FILE CREATION ***
working ..... Wed Dec 6 02:29:53 EST 1995

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 800985B5
</pre>

Now you might want to take another backup of your disk images, since the ULTRIX installation is now basically complete.

==Adding the unsupported sets==
Now there are some more pieces of software in the CDROM, in a directory called ''unsupported''. We want to install these as well. First, let's boot our system again

<pre>
>>>b dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 747376
data = 125952
bss = 918192
Starting at 0x2c19

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
real mem = 67043328
avail mem = 56455168
using 1638 buffers containing 6712320 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
dz0 at uba0 csr 160100 vec 300, ipl 17
dz1 at uba0 csr 160110 vec 310, ipl 17
dz2 at uba0 csr 160120 vec 320, ipl 17
dz3 at uba0 csr 160130 vec 330, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
Wed Dec 6 11:25:29 MET 1995
Automatic reboot in progress...
/dev/ra0a: 644 files, 6161 used, 9390 free (166 frags, 1153 blocks, 5.0% fragmentation)
/dev/rra0g: umounted cleanly
/dev/rra0h: umounted cleanly
Warning Creating new license database
Warning creating new history file
check quotas: done.
savecore: checking for dump...dump does not exist
local daemons: syslog sendmail.
Removing remnant Opser files
preserving editor files
clearing /tmp
standard daemons: update cron accounting network snmpd printer.
start errlog daemon - elcsd
Wed Dec 6 11:25:48 MET 1995

ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
UWS V4.5 (Rev. 6)

Digital Equipment Corporation
Nashua, New Hampshire

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

#
</pre>

now, we mount the CDROM and use <code>setld</code> to install the unsupported packages. For simplicity's sake, we just (again) install everything.

<pre>
# mount -r /dev/ra2c /mnt
# cd /mnt/VAX/UNSUPPORTED
# ls
DXVUNDEMO450 ULXDOC450 ULXINGRES450 ULXRCS450 ULXUNMAN450
ULXAPL450 ULXEDIT450 ULXLEARN450 ULXSHELLS450 ULXUNMIT450
ULXBASE450 ULXF77450 ULXLISP450 ULXSPMS450 ULXVARIAN450
ULXBIB450 ULXGAMES450 ULXMAN450 ULXTERM450 instctrl
ULXCOURIER450 ULXHYPER450 ULXMOD2450 ULXTOOLS450
ULXCPM450 ULXICON450 ULXNEWS450 ULXUNEXAMP450
ULXDCMT450 ULXINET450 ULXNOTES450 ULXUNFONTS450
# setld -l .

*** Enter Subset Selections ***

The subsets listed below are optional:
1) Base Extension 2) GNU Emacs
3) TCP/IP Networking Util Extension 4) Additional Terminal Drivers
5) Document Preparation Software 6) Games and Diversions
7) Supplementary Documentation 8) Bibliographic Utilities
9) Remote Procedure Call Compiler 10) Aux. Command Line Interpreters
11) USENET News Interface Software 12) Notesfiles Package
13) Revision Control System 14) Misc. User-Contributed Utilities
15) Computer Aided System Tutor 16) Franz Lisp Development Package
17) Modula-2 Development Package 18) Raster Plotter Package
19) APL Development Package 20) CP/M 8in Diskette Utility
21) Hyperchannel Utilities 22) ICON (Language) Development Packag
23) University Ingres QUEL DBMS 24) Software Project Management System
25) Unsupported Fortran Utilities 26) Unsupported On-Line Documentation
27) Unsupported X11 Components 28) Unsupported DECwindows Examples
29) Unsupported MIT Fonts 30) Unsupported X11 Reference Pages
31) Unsupported OSF/Motif Demos

32) All mandatory and all optional subsets
33) Mandatory subsets only
34) Exit without installing subsets

Enter your choice(s): 32
Working....Wed Dec 6 11:29:48 MET 1995
Wed Dec 6 11:30:00 MET 1995

You are installing the following subsets:
Base Extension GNU Emacs
TCP/IP Networking Util Extension Additional Terminal Drivers
Document Preparation Software Games and Diversions
Supplementary Documentation Bibliographic Utilities
Remote Procedure Call Compiler Aux. Command Line Interpreters
USENET News Interface Software Notesfiles Package
Revision Control System Misc. User-Contributed Utilities
Computer Aided System Tutor Franz Lisp Development Package
Modula-2 Development Package Raster Plotter Package
APL Development Package CP/M 8in Diskette Utility
Hyperchannel Utilities ICON (Language) Development Package
University Ingres QUEL DBMS Software Project Management System
Unsupported Fortran Utilities Unsupported On-Line Documentation
Unsupported X11 Components Unsupported DECwindows Examples
Unsupported MIT Fonts Unsupported X11 Reference Pages
Unsupported OSF/Motif Demos

Is this correct? (y/n): y

Base Extension (ULXBASE450)
Copying from . (disk)
Verifying

GNU Emacs (ULXEDIT450)
Copying from . (disk)
Verifying

TCP/IP Networking Util Extension (ULXINET450)
Copying from . (disk)
Verifying
...
</pre>

Note that you could also quickly install only a single package by using for example
# setld -l . ULXINET450

After a few minutes, installation will be completed and we should unmount the CDROM
# cd /
# umount /mnt

==Network configuration==
To configure the network, you have to use a static IPv4 address and put that into the beginning of /etc/rc.local. Note that there is no <code>ifconfig -a</code> in ULTRIX, you have to use <code>netstat -i</code>

<pre>
# netstat -i
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
qe0* 1500 none none 0 0 0 0 0
lo0 1536 loop localhost 1 0 1 0 0
# ifconfig qe0 192.168.1.44 netmask 255.255.255.0 up
# route add default 192.168.1.1 1
add net default: gateway 192.168.1.1
# ping 192.168.1.1
192.168.1.1 is alive
</pre>
Note that it might actually take a while until packets are getting through. I don't know why but in my case it helped to ping ULTRIX from the outside first, e.g. from Windows, and then re-try the ping from the VM. Then it worked. I'm guessing this is some SimH/Windows issue with PCAP or something.

Then put these 2 commands at the start of <code>/etc/rc.local</code> (you'll see where). Note that you can use <code>vi</code> now!
<pre>
# @(#)rc.local 9.4 (ULTRIX) 9/21/95
/bin/hostname yuki
#/etc/ifconfig HDWR `/bin/hostname` broadcast NETNUM.0 netmask 255.0
/etc/ifconfig qe0 192.168.1.44 netmask 255.255.255.0
route add default 192.168.1.1 1
/etc/ifconfig lo0 localhost
#/etc/bscconfig dup0 bsc 1
#/etc/bscconfig dpv0 bsc 1
...
</pre>

==Shutting down cleanly==
As you'd expect, you can use <code>shutdown</code> to shut the system down
<pre>
# shutdown -h now
Shutdown at 11:15 (in 0 minutes) [pid 1500]
#
System shutdown time has arrived
syncing disks... done

?06 HLT INST
PC = 80094CDD
>>>
</pre>

==Resources==
Some of the resources I used for creating this guide:
*ULTRIX 4.5 installation ISO [http://musall.de/mirrors/ultrix/ultrix_os/vax/]
*ULTRIX-32 startup and shutdown guide [http://bitsavers.trailing-edge.com/pdf/dec/vax/ultrix-32/3.0/AA-ME91A-TE_ULTRIX-32_Guide_to_System_Shutdown_and_Startup.pdf]
*CERN guide to installing ULTRIX [https://web-docs.gsi.de/~kraemer/COLLECTION/ULTRIX/wwwpdp.web.cern.ch/wwwpdp/as/file/doc/ultrix/ultrix.pdf]
*My old guide for installing ULTRIX [https://docs.google.com/document/d/1ULRhzE0R1twarB5hfJm85yqOdTeoFCGgyPr5AxYEIbE]
*DEC KA655 CPU System Maintenance [http://bitsavers.trailing-edge.com/pdf/dec/vax/655/EK-306A-MG-001_655Mnt_Mar89.pdf]
[[Category:SIMH Tutorials]]

Installing Ultrix 4.5 on SIMH

2015-12-06T09:34:08Z

Darkstar: /* Adding the unsupported sets */

This WORK-IN-PROGRESS guide will be a simple guide to installing ULTRIX 4.5 for VAX on SimH.

==Requirements==
The following is a list of things required for installation
*A recent version of the [[SIMH]] emulator
**Make sure the binary you're using includes Ethernet support
**I'm using a self-compiled version (git revision 0e8c0aea)
*An ISO image of ULTRIX 4.5 for VAX
**See the "Resources" section for a download link
**It's probably also possible to install it from tape, although I don't know if any installation tapes for ULTRIX 4.5 exist
*Optional stuff (might get added to the guide later):
**Starfish Ultrix Freeware CDs from [http://musall.de/mirrors/ultrix/freeware/ here]

==SimH configuration==
The machine I'm using to run ULTRIX has the following configuration
*DEC MicroVAX 3800
*64mb memory
*DELQA network card (XQ0)
*Two [[RA90]] disk drives (with 1.2gb each) attached to an RQDX3 controller (RQ0 and RQ1)
*CD ROM drive attached to the same RQDX3 controller as unit 2 (RQ2)
*[[TK50]] tape attached as unit 0 on the first TQK50 controller (TQ0)
*DZV11 terminal multiplexer with 16 lines, attached to telnet port 1005 (DZ)
*LPT line printer attached to text file <code>printer_output.txt</code>

Here's my config file (I called it <code>simh.conf</code>)
<pre><nowiki>
;
; SimH 4.0 Configuration file for MicroVAX 3800
;
; Host System : DEC MicroVAX 3800
; Operating System : DEC Ultrix v4.5
; Memory : 64mb
; Network config : XQ: Ethernet, 08:00:2b:04:14:02
; Disks : RQ0: RA90, 1.2gb
; RQ1: RA90, 1.2gb
; CDROMs : RQ2: iso file
; Tape config : TQ0: TK50, 94mb
;

load -r ka655x.bin

; NVRAM
attach NVR nvram.bin

; CPU config
set CPU 64m
set CPU conhalt
set CPU idle=all

; configure console to 7-bit only
set TTO 7b
set TTI 7b

; Disk drives
set RQ0 ra90
attach RQ0 rq0-ra90.dsk
set RQ1 ra90
attach RQ1 rq1-ra90.dsk
set RQ2 CDROM
attach -r RQ2 ultrix-vax-os-v4.5.mode1.ufs.iso
; MD5 sum: 19df0753c27f195e9f1d2f139a3b4629 *ultrix-vax-os-v4.5.mode1.ufs.iso
set RQ3 dis

; Tape
set TQ tk50
;attach tq0 filename-to-tape-file
set TQ1 dis
set TQ2 dis
set TQ3 dis

; serial port, simulated by Telnet to port 1005
set DZ LINES=16
set DZ 8B
attach DZ 1005 NoBuffer

; printer
set LPT enable
attach LPT printer_output.txt

; Disable unused peripherals
set CR dis
set RL dis
set TS dis

; Network interface (08-00-2b is the DEC prefix, the 04-14-02 part is arbitrary)
set XQ MAC=08-00-2b-04-14-02
attach XQ0 eth0

; serial console (launch directly after booting CPU)
set console telnet=1001

; experimental
;set QVSS en

; boot the system
;boot CPU
</nowiki></pre>
Note that I'm using a telnet console (for easier copy/paste on Windows), which means that directly after running this config file (via <code>do simh.conf</code> from Simh) you will need to connect via telnet to localhost:1001 or the boot will abort. If you are on Linux, or just don't want that, remove the <code>set console telnet=1001</code> line.

Also note that you might need to attach XQ0 to a different ethernet device. Use "show ether" in SimH to list all available devices on your system and modify the <code>attach XQ0 eth0</code> line accordingly.

==Running the Emulator==
Either run <code>vax.exe simh.conf</code> from the Windows command line, or just double-click the VAX.EXE executable and type <code>do simh.conf</code>.

On the first launch it might take some time because SimH has to create the disk images (~2.5 gb total). It should look something like this
<pre><nowiki>
MicroVAX 3900 simulator V4.0-0 Beta git commit id: 0e8c0aea
NVR: buffering file in memory
RQ2: unit is read only
Listening on port 1005
WinPcap version 4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008)
Eth: opened OS device \Device\NPF_{A41A1651-DD4D-4735-A4E0-88353165C2EC}
Listening on port 1001
sim>
</nowiki></pre>

Type the following to start the emulation (note: you can also uncomment that line from the end of the config file to have the emulation start right away)
sim> boot cpu
Waiting for console Telnet connection

Now would be a good time to connect your telnet session (I use a batch file for this), otherwise the boot process will timeout.

On your console, you should see something like this:
<pre><nowiki>
Connected to the MicroVAX 3900 simulator CON-TEL device

KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>
</nowiki></pre>

This is the VAX's boot prompt. Normally you just type
>>>boot <device>
where <device> is one of the following
*MUA<num>: TK tape device number <num> (1 to 4)
*DUA<num>: RQ disk device number <num> (1 to 4)

You can use <code>show device</code> to see the installed (and detected) devices you can boot from, and <code>show boot</code> to see which device will be the default if you just type <code>boot</code> (or <code>b</code> for short):
<pre><nowiki>
>>>show device
UQSSP Disk Controller 0 (772150)
-DUA0 (RA90)
-DUA1 (RA90)
-DUA2 (RRD40)

UQSSP Tape Controller 0 (774500)
-MUA0 (TK50)

Ethernet Adapter 0 (774440)
-XQA0 (08-00-2B-04-14-02)
>>>show boot
MUA0
</nowiki></pre>

Since we want to boot from CDROM, which is unit 2, we can use
>>>boot DUA2

Note: You can add flags to boot into single user mode, or to boot in interactive mode (so-called ''conversational boot'', where the system prompts you for a kernel file name to load). For details see the Guide to ULTRIX-32 System Startup and Shutdown, linked to in the ''References'' section. To use it, add the <code>/R5:<flags></code> option to the <code>boot</code> command, where flags is 0 (default multi-user), 1 (conversational multi-user), 2 (single-user) or 3 (conversational single-user). For example
>>>boot/r5:3 dua0

Note: You can also boot from ethernet (<code>boot XQA0</code>) but this requires a DEC-specific boot server in your network (the protocol is called ''MOP'' for ''Maintenance Operations Protocol''), which is beyond the scope of this document. I did get it to work a few years ago though, but it was a bit difficult to set up.

For a list and description of all commands available in the bootloader (hint: there are lots), see the ''KA655 CPU System Maintenance'' guide mentioned in the ''References'' section..

==Bootstrapping ULTRIX==
You will see the following output on the first boot.
<pre>
>>>boot dua2
(BOOT/R5:0 DUA2

2..
-DUA2
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 945424
data = 1290240
bss = 757940
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #2: Wed Oct 18 12:06:55 EDT 1995
real mem = 67043328
avail mem = 61517824
Buffer configuration adjusted to run with small system page table
using 123 buffers containing 1007616 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
WARNING: clock gained 47 days -- CHECK AND RESET THE DATE!

*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice:
</pre>
Now we want to do an ''ADVANCED Installation'', but when we try to, it will take a few seconds until the installation program dumps us to a prompt because it couldn't find a valid device to install from and to:
<pre>
Enter your choice: 2

*** SOFTWARE DISTRIBUTION DEVICE SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of software distribution devices and which installation media you should
load on it:

No valid device is found.
Contact a DIGITAL field service representative.

#
</pre>

The problem seems to be that the hardware SimH emulates is not fully supported by ULTRIX (or is misdetected -- I'm not entirely sure myself). The good thing is that the internet has the correct solution, which is to fix some lines in the installation shell script. The fact that the basic system that is running at this point doesn't have ''vi'', or even ''cat'', makes this a bit harder ;-)

The only option you have is ''ed'', the old UNIX editor. For a quick introduction, see [http://blog.sanctum.geek.nz/actually-using-ed/ here].

To load the file in the editor, use
# '''ed install.1'''
16763

You can see the entire file with
1,$l
but be warned, the output is quite long and it'll take some time to print it all out.

To fix it, use the following commands (the lines in '''bold''' is what you type, everything else is the response from ed)
# '''ed install.1'''
16763
'''173l'''
BTD=`btd`
'''173s/`btd`/ra2/'''
'''173l'''
BTD=ra2
'''193l'''
rz* )
'''193s/rz/ra/'''
'''193l'''
ra* )
'''w'''
16761
'''q'''
#

First, we list line 173, then we change it from <code>BTD=`btd`</code> to <code>BTD=ra2</code>, which happens to be the CDROM device and unit number we're installing from (if you changed that in your config, use the correct name here!)

Then we change line 193 from <code>rz* )</code> to <code>ra* )</code> since we're trying to install on an RA type disk which was apparently not supported in ULTRIX out of the box.

After writing the file with <code>w</code> and quitting ed with <code>q</code>, we're back at the prompt, at which point we can use CTRL+D to retry the installation:

<pre>
# ^D
*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice: 2

*** SYSTEM DISK SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of system disk drives. Select one of the devices below to contain the
root file system:

SYSTEM DISK TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk drive
is on line and write-enabled (if applicable to your disk drive), then
confirm your choice.

Use RA90, ra0, for your system disk? (y/n) []: y

The installation procedure now allocates the root file system on
partition 'a' of the system disk, ra0 RA90.

Making the root file system on ra0 RA90.

The installation procedure is now restoring the root file system to
partition 'a' of the system disk, ra0 RA90.

The installation procedure now checks the root file system on partition 'a'
of the system disk, ra0 RA90.
** /dev/rra0a
** Last Mounted on /mnt
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
226 files, 4547 used, 11004 free (20 frags, 1373 blocks, 1.0% fragmentation)

*** BOOTSTRAP COMMAND SEQUENCE ***

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 8007F799
>>>
</pre>
After this, you will be back at the VAX boot prompt (if you used <code>set CPU CONHALT</code> in your config) or at the SimH emulator prompt (if you used <code>set CPU SIMHALT</code>, which is the default). In the latter case you will have to do <code>boot cpu</code> again to get to the VAX boot prompt.

==First boot==
Now we can boot the installed system from harddisk for the first time.

If you want to, now would be a good time to take a backup copy of your disk files (or just create a btrfs snapshot or something if you have the possibility ;-)

Okay, then let's boot from DUA0
<pre>
>>>boot dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 1153664
data = 281088
bss = 1043548
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #3: Wed Oct 18 11:49:00 EDT 1995
real mem = 67043328
avail mem = 62008320
Buffer configuration adjusted to run with small system page table
using 121 buffers containing 991232 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
</pre>
Here, it will seem to hang for a loooong time. A few minutes. Don't worry, it will eventually continue to boot. I guess it's probing for other devices which are not present.

You ''might'' be able to speed this up a bit by interrupting SimH (press CTRL+E in the SimH console window) and then using <code>set CPU noidle</code> followed by <code>go</code> to resume emulation.

Eventually, you will have to decide on a hostname. Note that if you want to play around with [[DECnet]] at some point, your hostname should be no longer than 6 characters.
<pre>
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)

*** SYSTEM NAME SPECIFICATION ***

Select the name of your system using alphanumeric characters.
The first character must be a letter. For example, tinker.

Enter your system name: yuki

You selected yuki as the name of your system.
Is this correct? (y/n) [y]: y
</pre>

Next up is the time configuration. Since Ultrix 4.5 is not Y2k compliant (AFAIK), I decided to set the clock back a whopping 20 years. Note that the timezone and daylight saving settings are for my location (Germany) and will probably vary for you.

<pre>
*** DATE AND TIME SPECIFICATION ***

The current date and time should be specified using the following
format:

yymmddhhmm

Use two digits for year (yy), month (mm), day (dd), hour (hh), and
minute (mm). Enter the time in 24-hour format. For example, 02:54
p.m. on Feb 2, 1993 would be entered as:

9302021454

Enter the date and time: 9512052336

*** TIME ZONE SELECTION ***

Select the time zone for your area, using the options listed in the
table below. You can also enter the number of hours (-12 to 12) in
time east of Greenwich.

Selection Time Zone
---------------------------------
e Eastern
c Central
m Mountain
p Pacific
g Greenwich
---------------------------------

Enter your choice: 1

Does your area alternate between Daylight Savings and Standard
time? (y/n) [y]: y

Select your geographic area for Daylight Savings Time, using the
options in the table below.

Selection Geographic Area
--------------------------------
u USA
a Australia
e Eastern Europe
c Central Europe
w Western Europe
--------------------------------

Enter your choice [u]: c

The current date and time is Tue Dec 5 23:36:46 EST 1995
</pre>

Next up is the root password. Note that Ultrix will not echo anything here, I added the asterisks just for this guide :)

<pre>
*** SPECIFY THE SUPERUSER PASSWORD ***
The Guide to Installing ULTRIX instructs you on how to enter
the superuser password.
Changing password for root
Enter new password: ******
Verify: ******
</pre>

Next up is the filesystem layout, which is a bit more involved than what you know from more modern systems like MS DOS ;-)

In ULTRIX, partitions are defined for each disk type in a file called <code>/etc/disktab</code>. Note that the partitions overlap, so you shouldn't use them all at the same time. The setup script actually takes care of that for you, but if you later create a new filesystem on the wrong partition you ''WILL'' lose data!

Normally, partition '''c''' is the whole disk, which is useful for add-on disk drives for example. Partitions '''a''' and '''b''' are always available and are traditionally used for the system and the swap-space respectively. The swap partition is also used for crashdumps if no separate crash-dump partition is created. The rest of the disk can be used either as a single partition (which is usually '''g''') or as 3 individual partitions ('''d''' to '''f'''). If the disk is larger than 1 gigabyte, you will get another partition, '''h''', after the g partition, probably because the filesystem cannot cope with partitions >1gig

In our case, we will have the following partitions on the first disk (RA0):
*Partition '''a''' of 32 mb for /root
*Partition '''b''' of 64 mb for swap+crashdump
*Partition '''c''' of 1.2 gig (whole-disk, not used on our setup)
*Partition '''d''' and '''e''' of 200 mb each (not used)
*Partition '''f''' of 400 mb (not used)
*Partition '''g''' of 800 mb (overlaps with d, e and f; will become /usr)
*Partition '''h''' of 256 mb (will become /usr/var)
This way we still have the whole second disk available for later use.

So here it goes:
<pre>
*** FILE SYSTEM DEFAULT OPTION ***

The following table shows the default file system layout on RA90, ra0:

partition bottom top size overlap default
a 0 32767 32768 c root
b 32768 159839 127072 c swap, dump
d 159840 580036 420197 c,g /usr

If you choose the defaults, the var area will be allocated to /usr/var.

Do you want to choose the default file system layout? (y/n): n
</pre>

No, we do not want to use the defaults...

First, we select disk 1, partition '''g''', for the /usr file system:
<pre>
*** /usr FILE SYSTEM ALLOCATION ***

You can allocate the /usr file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

/usr FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for /usr file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the /usr file system:

partition size (Kbytes) overlap
------------------------------------------------
d --- 210098 c,g
e --- 210098 c,g
f --- 420196 c,g
g --- 840393 c,d,e,f
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the /usr file system [d]: g

Making the new file system for /usr on /dev/rra0g RA90
</pre>

Next, we select disk 1, partition '''b''' for swap (only 1 swap partition) and for crashdumps:

<pre>
*** ALLOCATE THE SWAP1 SPACE ***

You can allocate the swap1 space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

SWAP1 SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for swap1 space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the swap1 space:

partition size (Kbytes) overlap
------------------------------------------------
b --- 63536 c
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the swap1 space [b]: b

*** ALLOCATE THE SWAP2 SPACE ***

Do you want to allocate a second swap space? (y/n) [n]: n

*** ALLOCATE THE CRASH DUMP SPACE ***

You can allocate the crash dump space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

CRASH DUMP SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for crash dump space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the crash dump space:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
b --- 63536 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the crash dump space [b]: b
</pre>

Finally we select partiton '''h''' for the /var file system. This might not be large enough later on but then we can always migrate the data away if we need to...

<pre>
*** ALLOCATE THE var FILE SYSTEM ***

You can allocate the var file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

var FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for var file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the var file system:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
g --- 840393 c,d,e,f
------------------------------------------------

Type the letter of the partition on which you want
to allocate the var file system [no default]: h

Making the new file system for var on /dev/rra0h RA90
</pre>

==Installing the distribution files==

Next up we have to decide what ''packages'' we want to install (yes, ULTRIX already had its own package format and corresponding installer called ''setld''. It is very basic, probably most similar to ''pkg_add'' on NetBSD). We simply install everything, since we have enough space :)

<pre>
This distribution media includes subsets for ULTRIX Worksystem
Software (UWS). A UWS license (on a workstation) or a UWS Server
License (on a timesharing machine or server) is required to install
these subsets.

Do you want to install ULTRIX Worksystem Software? y/n []: y

*** SUPPORTED SOFTWARE INSTALLATION ***

*** Select the DECwindows User Interface ***

1) DECwindows for OSF/Motif
2) X11/DECwindows (XUI)

Enter your choice [1]: 2

*** Enter Subset Selections ***

The following subsets are mandatory and will be installed automatically:
* Base System * Kernel Config Files
* TCP/IP Networking Utilities * Network File System Utilities
* Extended (Berkeley) Mailer * X11/DECwindows Servers
* X11/DECwindows User Environment * X11/DECwindows 75dpi Fonts

The subsets listed below are optional:
1) Printer Support Environment 2) RAND Mail Handler
3) Sys. Config. Mgmt. Program (SCAMP) 4) Communications Utilities
5) Unix-to-Unix Copy Facility 6) Maintenance Operations Protocol
7) Accounting Software 8) Kerberos Network Authentication
9) Enhanced Security Features 10) Prestoserve Utilities
11) System Exerciser Package 12) Bisynchronous Communications
13) Doc. Preparation for Ref. Pages 14) Doc. Preparation Extensions
15) Adobe Font Metric Files 16) Software Development Utilities
17) Source Code Control System 18) Internationalization Runtime Env.
19) Internationalization Dev. Env. 20) CDA Base System
21) CDA Software Dev Libraries 22) RPC Runtime Environment
23) RPC Development Environment 24) Pascal Development Package
25) VAX C/ULTRIX 26) Ref. Pages for Sys. Admin. & Users
27) Reference Pages for Programers 28) Programming Examples
29) Ultrix SPDS 30) X11/DECwindows 100dpi Fonts
31) VS35XX X11/DECwindows Fonts 32) Additional DECwindows Applications
33) DECwindows Mail Application 34) Worksystem Development Environment
35) X11/DECwindows System Management T 36) UWS Runtime Reference Pages
37) UWS Development Reference Pages

38) All mandatory and all optional subsets
39) Mandatory subsets only
40) Exit without installing subsets

Enter your choice(s): 38
Working....Wed Dec 6 00:14:12 EST 1995

You are installing the following subsets:
Base System Kernel Config Files
TCP/IP Networking Utilities Network File System Utilities
Extended (Berkeley) Mailer X11/DECwindows Servers
X11/DECwindows User Environment X11/DECwindows 75dpi Fonts
Printer Support Environment RAND Mail Handler
Sys. Config. Mgmt. Program (SCAMP) Communications Utilities
Unix-to-Unix Copy Facility Maintenance Operations Protocol
Accounting Software Kerberos Network Authentication
Enhanced Security Features Prestoserve Utilities
System Exerciser Package Bisynchronous Communications
Doc. Preparation for Ref. Pages Doc. Preparation Extensions
Adobe Font Metric Files Software Development Utilities
Source Code Control System Internationalization Runtime Env.
Internationalization Dev. Env. CDA Base System
CDA Software Dev Libraries RPC Runtime Environment
RPC Development Environment Pascal Development Package
VAX C/ULTRIX Ref. Pages for Sys. Admin. & Users
Reference Pages for Programers Programming Examples
Ultrix SPDS X11/DECwindows 100dpi Fonts
VS35XX X11/DECwindows Fonts Additional DECwindows Applications
DECwindows Mail Application Worksystem Development Environment
X11/DECwindows System Management To UWS Runtime Reference Pages
UWS Development Reference Pages

Is this correct? (y/n): y
</pre>

The installation will take a while (around 15-30 minutes for me), so feel free to let it run in the background for a while now. The installer will periodically print its status so you can see that it's still running...

<pre>
Base System (ULTBASE450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:14:43 EST 1995
Verifying

Kernel Config Files (ULTBIN450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:15:28 EST 1995
Verifying

...
</pre>

At some point you will have to confirm installing the generic kernel and the X11 subsystem:

<pre>
...
UWS Runtime Reference Pages (UWSMAN450)
Copying from /mnt/VAX/BASE (disk)
Verifying

UWS Development Reference Pages (UWSMANPGMR450)
Copying from /mnt/VAX/BASE (disk)
Verifying

The installation software has successfully installed the software
subsets.
Installing Upgrade subsets
The following subsets will be installed:
* X11/DECwindows Servers Upgrade * Generic Kernel
Do you wish to continue? (y/n): y

X11/DECwindows Servers Upgrade (UWSSER451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

Generic Kernel (ULTGENVMUNIX451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

The installation procedure has successfully installed the Upgrade
subsets
</pre>

That's it for the base installation, now we configure our kernel...

==Kernel configuration==
We have to select what features will be in the kernel. For anyone who has ever done a "make menuconfig" on Linux, this is ''slightly'' easier here ;-)
<pre>
*** CONFIGURATION FILE KERNEL OPTION SELECTION ***

Selection Kernel Option
---------------------------------------------------------------
1 Local Area Transport (LAT)
2 Bisynchronous Communication protocol (VAX only)
3 Computer Interconnect (CI) network
4 Diagnostic/Utilities Protocol (DUP)
5 ISO9660 File System Support (CDFS)
6 Ethernet Packet Filter
7 Enhanced Security Features
8 All of the above
9 None of the above
----------------------------------------------------------------

Enter the selection number for each kernel option you want.
For example, 1 3 :
</pre>

In our case, we don't need 2 (it is for 2780/3780 remote terminals), 3 (SimH doesn't emulate any cluster hardware) or 6 (it might cause problems with DECwindows/Motif). Everything else (<code>1 4 5 7</code>) is probably safe. This lets us play around with LAT (maybe connect an emulated Cisco router with LAT routing to it?) and DUP.

<pre>
Enter the selection number for each kernel option you want.
For example, 1 3 : 1 4 5 7

You specified the following kernel options:

Local Area Transport (LAT)
Diagnostic/Utilities Protocol (DUP)
ISO9660 File System Support (CDFS)
Enhanced Security Features

Is this correct? (y/n) [n]: y

*** SYSTEM CONFIGURATION PROCEDURE ***
The installation software found these devices in the floating
address space:

dz0 on uba0 at 0160100
dz1 on uba0 at 0160110
dz2 on uba0 at 0160120
dz3 on uba0 at 0160130

Configuration file complete.

Do you want to edit the configuration file? (y/n) [n]: n

*** PERFORMING SYSTEM CONFIGURATION ***

working ..... Wed Dec 6 02:29:10 EST 1995

*** DEVICE SPECIAL FILE CREATION ***
working ..... Wed Dec 6 02:29:53 EST 1995

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 800985B5
</pre>

Now you might want to take another backup of your disk images, since the ULTRIX installation is now basically complete.

==Adding the unsupported sets==
Now there are some more pieces of software in the CDROM, in a directory called ''unsupported''. We want to install these as well. First, let's boot our system again

<pre>
>>>b dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 747376
data = 125952
bss = 918192
Starting at 0x2c19

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
real mem = 67043328
avail mem = 56455168
using 1638 buffers containing 6712320 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
dz0 at uba0 csr 160100 vec 300, ipl 17
dz1 at uba0 csr 160110 vec 310, ipl 17
dz2 at uba0 csr 160120 vec 320, ipl 17
dz3 at uba0 csr 160130 vec 330, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
Wed Dec 6 11:25:29 MET 1995
Automatic reboot in progress...
/dev/ra0a: 644 files, 6161 used, 9390 free (166 frags, 1153 blocks, 5.0% fragmentation)
/dev/rra0g: umounted cleanly
/dev/rra0h: umounted cleanly
Warning Creating new license database
Warning creating new history file
check quotas: done.
savecore: checking for dump...dump does not exist
local daemons: syslog sendmail.
Removing remnant Opser files
preserving editor files
clearing /tmp
standard daemons: update cron accounting network snmpd printer.
start errlog daemon - elcsd
Wed Dec 6 11:25:48 MET 1995

ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
UWS V4.5 (Rev. 6)

Digital Equipment Corporation
Nashua, New Hampshire

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

#
</pre>

now, we mount the CDROM and use <code>setld</code> to install the unsupported packages. For simplicity's sake, we just (again) install everything.

<pre>
# mount -r /dev/ra2c /mnt
# cd /mnt/VAX/UNSUPPORTED
# ls
DXVUNDEMO450 ULXDOC450 ULXINGRES450 ULXRCS450 ULXUNMAN450
ULXAPL450 ULXEDIT450 ULXLEARN450 ULXSHELLS450 ULXUNMIT450
ULXBASE450 ULXF77450 ULXLISP450 ULXSPMS450 ULXVARIAN450
ULXBIB450 ULXGAMES450 ULXMAN450 ULXTERM450 instctrl
ULXCOURIER450 ULXHYPER450 ULXMOD2450 ULXTOOLS450
ULXCPM450 ULXICON450 ULXNEWS450 ULXUNEXAMP450
ULXDCMT450 ULXINET450 ULXNOTES450 ULXUNFONTS450
# setld -l .

*** Enter Subset Selections ***

The subsets listed below are optional:
1) Base Extension 2) GNU Emacs
3) TCP/IP Networking Util Extension 4) Additional Terminal Drivers
5) Document Preparation Software 6) Games and Diversions
7) Supplementary Documentation 8) Bibliographic Utilities
9) Remote Procedure Call Compiler 10) Aux. Command Line Interpreters
11) USENET News Interface Software 12) Notesfiles Package
13) Revision Control System 14) Misc. User-Contributed Utilities
15) Computer Aided System Tutor 16) Franz Lisp Development Package
17) Modula-2 Development Package 18) Raster Plotter Package
19) APL Development Package 20) CP/M 8in Diskette Utility
21) Hyperchannel Utilities 22) ICON (Language) Development Packag
23) University Ingres QUEL DBMS 24) Software Project Management System
25) Unsupported Fortran Utilities 26) Unsupported On-Line Documentation
27) Unsupported X11 Components 28) Unsupported DECwindows Examples
29) Unsupported MIT Fonts 30) Unsupported X11 Reference Pages
31) Unsupported OSF/Motif Demos

32) All mandatory and all optional subsets
33) Mandatory subsets only
34) Exit without installing subsets

Enter your choice(s): 32
Working....Wed Dec 6 11:29:48 MET 1995
Wed Dec 6 11:30:00 MET 1995

You are installing the following subsets:
Base Extension GNU Emacs
TCP/IP Networking Util Extension Additional Terminal Drivers
Document Preparation Software Games and Diversions
Supplementary Documentation Bibliographic Utilities
Remote Procedure Call Compiler Aux. Command Line Interpreters
USENET News Interface Software Notesfiles Package
Revision Control System Misc. User-Contributed Utilities
Computer Aided System Tutor Franz Lisp Development Package
Modula-2 Development Package Raster Plotter Package
APL Development Package CP/M 8in Diskette Utility
Hyperchannel Utilities ICON (Language) Development Package
University Ingres QUEL DBMS Software Project Management System
Unsupported Fortran Utilities Unsupported On-Line Documentation
Unsupported X11 Components Unsupported DECwindows Examples
Unsupported MIT Fonts Unsupported X11 Reference Pages
Unsupported OSF/Motif Demos

Is this correct? (y/n): y

Base Extension (ULXBASE450)
Copying from . (disk)
Verifying

GNU Emacs (ULXEDIT450)
Copying from . (disk)
Verifying

TCP/IP Networking Util Extension (ULXINET450)
Copying from . (disk)
Verifying
...
</pre>

Note that you could also quickly install only a single package by using for example
# setld -l . ULXINET450

After a few minutes, installation will be completed and we should unmount the CDROM
# cd /
# umount /mnt

==Resources==
Some of the resources I used for creating this guide:
*ULTRIX 4.5 installation ISO [http://musall.de/mirrors/ultrix/ultrix_os/vax/]
*ULTRIX-32 startup and shutdown guide [http://bitsavers.trailing-edge.com/pdf/dec/vax/ultrix-32/3.0/AA-ME91A-TE_ULTRIX-32_Guide_to_System_Shutdown_and_Startup.pdf]
*CERN guide to installing ULTRIX [https://web-docs.gsi.de/~kraemer/COLLECTION/ULTRIX/wwwpdp.web.cern.ch/wwwpdp/as/file/doc/ultrix/ultrix.pdf]
*My old guide for installing ULTRIX [https://docs.google.com/document/d/1ULRhzE0R1twarB5hfJm85yqOdTeoFCGgyPr5AxYEIbE]
*DEC KA655 CPU System Maintenance [http://bitsavers.trailing-edge.com/pdf/dec/vax/655/EK-306A-MG-001_655Mnt_Mar89.pdf]
[[Category:SIMH Tutorials]]

Installing Ultrix 4.5 on SIMH

2015-12-06T09:32:40Z

Darkstar: unsupported packages

This WORK-IN-PROGRESS guide will be a simple guide to installing ULTRIX 4.5 for VAX on SimH.

==Requirements==
The following is a list of things required for installation
*A recent version of the [[SIMH]] emulator
**Make sure the binary you're using includes Ethernet support
**I'm using a self-compiled version (git revision 0e8c0aea)
*An ISO image of ULTRIX 4.5 for VAX
**See the "Resources" section for a download link
**It's probably also possible to install it from tape, although I don't know if any installation tapes for ULTRIX 4.5 exist
*Optional stuff (might get added to the guide later):
**Starfish Ultrix Freeware CDs from [http://musall.de/mirrors/ultrix/freeware/ here]

==SimH configuration==
The machine I'm using to run ULTRIX has the following configuration
*DEC MicroVAX 3800
*64mb memory
*DELQA network card (XQ0)
*Two [[RA90]] disk drives (with 1.2gb each) attached to an RQDX3 controller (RQ0 and RQ1)
*CD ROM drive attached to the same RQDX3 controller as unit 2 (RQ2)
*[[TK50]] tape attached as unit 0 on the first TQK50 controller (TQ0)
*DZV11 terminal multiplexer with 16 lines, attached to telnet port 1005 (DZ)
*LPT line printer attached to text file <code>printer_output.txt</code>

Here's my config file (I called it <code>simh.conf</code>)
<pre><nowiki>
;
; SimH 4.0 Configuration file for MicroVAX 3800
;
; Host System : DEC MicroVAX 3800
; Operating System : DEC Ultrix v4.5
; Memory : 64mb
; Network config : XQ: Ethernet, 08:00:2b:04:14:02
; Disks : RQ0: RA90, 1.2gb
; RQ1: RA90, 1.2gb
; CDROMs : RQ2: iso file
; Tape config : TQ0: TK50, 94mb
;

load -r ka655x.bin

; NVRAM
attach NVR nvram.bin

; CPU config
set CPU 64m
set CPU conhalt
set CPU idle=all

; configure console to 7-bit only
set TTO 7b
set TTI 7b

; Disk drives
set RQ0 ra90
attach RQ0 rq0-ra90.dsk
set RQ1 ra90
attach RQ1 rq1-ra90.dsk
set RQ2 CDROM
attach -r RQ2 ultrix-vax-os-v4.5.mode1.ufs.iso
; MD5 sum: 19df0753c27f195e9f1d2f139a3b4629 *ultrix-vax-os-v4.5.mode1.ufs.iso
set RQ3 dis

; Tape
set TQ tk50
;attach tq0 filename-to-tape-file
set TQ1 dis
set TQ2 dis
set TQ3 dis

; serial port, simulated by Telnet to port 1005
set DZ LINES=16
set DZ 8B
attach DZ 1005 NoBuffer

; printer
set LPT enable
attach LPT printer_output.txt

; Disable unused peripherals
set CR dis
set RL dis
set TS dis

; Network interface (08-00-2b is the DEC prefix, the 04-14-02 part is arbitrary)
set XQ MAC=08-00-2b-04-14-02
attach XQ0 eth0

; serial console (launch directly after booting CPU)
set console telnet=1001

; experimental
;set QVSS en

; boot the system
;boot CPU
</nowiki></pre>
Note that I'm using a telnet console (for easier copy/paste on Windows), which means that directly after running this config file (via <code>do simh.conf</code> from Simh) you will need to connect via telnet to localhost:1001 or the boot will abort. If you are on Linux, or just don't want that, remove the <code>set console telnet=1001</code> line.

Also note that you might need to attach XQ0 to a different ethernet device. Use "show ether" in SimH to list all available devices on your system and modify the <code>attach XQ0 eth0</code> line accordingly.

==Running the Emulator==
Either run <code>vax.exe simh.conf</code> from the Windows command line, or just double-click the VAX.EXE executable and type <code>do simh.conf</code>.

On the first launch it might take some time because SimH has to create the disk images (~2.5 gb total). It should look something like this
<pre><nowiki>
MicroVAX 3900 simulator V4.0-0 Beta git commit id: 0e8c0aea
NVR: buffering file in memory
RQ2: unit is read only
Listening on port 1005
WinPcap version 4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008)
Eth: opened OS device \Device\NPF_{A41A1651-DD4D-4735-A4E0-88353165C2EC}
Listening on port 1001
sim>
</nowiki></pre>

Type the following to start the emulation (note: you can also uncomment that line from the end of the config file to have the emulation start right away)
sim> boot cpu
Waiting for console Telnet connection

Now would be a good time to connect your telnet session (I use a batch file for this), otherwise the boot process will timeout.

On your console, you should see something like this:
<pre><nowiki>
Connected to the MicroVAX 3900 simulator CON-TEL device

KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>
</nowiki></pre>

This is the VAX's boot prompt. Normally you just type
>>>boot <device>
where <device> is one of the following
*MUA<num>: TK tape device number <num> (1 to 4)
*DUA<num>: RQ disk device number <num> (1 to 4)

You can use <code>show device</code> to see the installed (and detected) devices you can boot from, and <code>show boot</code> to see which device will be the default if you just type <code>boot</code> (or <code>b</code> for short):
<pre><nowiki>
>>>show device
UQSSP Disk Controller 0 (772150)
-DUA0 (RA90)
-DUA1 (RA90)
-DUA2 (RRD40)

UQSSP Tape Controller 0 (774500)
-MUA0 (TK50)

Ethernet Adapter 0 (774440)
-XQA0 (08-00-2B-04-14-02)
>>>show boot
MUA0
</nowiki></pre>

Since we want to boot from CDROM, which is unit 2, we can use
>>>boot DUA2

Note: You can add flags to boot into single user mode, or to boot in interactive mode (so-called ''conversational boot'', where the system prompts you for a kernel file name to load). For details see the Guide to ULTRIX-32 System Startup and Shutdown, linked to in the ''References'' section. To use it, add the <code>/R5:<flags></code> option to the <code>boot</code> command, where flags is 0 (default multi-user), 1 (conversational multi-user), 2 (single-user) or 3 (conversational single-user). For example
>>>boot/r5:3 dua0

Note: You can also boot from ethernet (<code>boot XQA0</code>) but this requires a DEC-specific boot server in your network (the protocol is called ''MOP'' for ''Maintenance Operations Protocol''), which is beyond the scope of this document. I did get it to work a few years ago though, but it was a bit difficult to set up.

For a list and description of all commands available in the bootloader (hint: there are lots), see the ''KA655 CPU System Maintenance'' guide mentioned in the ''References'' section..

==Bootstrapping ULTRIX==
You will see the following output on the first boot.
<pre>
>>>boot dua2
(BOOT/R5:0 DUA2

2..
-DUA2
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 945424
data = 1290240
bss = 757940
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #2: Wed Oct 18 12:06:55 EDT 1995
real mem = 67043328
avail mem = 61517824
Buffer configuration adjusted to run with small system page table
using 123 buffers containing 1007616 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
WARNING: clock gained 47 days -- CHECK AND RESET THE DATE!

*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice:
</pre>
Now we want to do an ''ADVANCED Installation'', but when we try to, it will take a few seconds until the installation program dumps us to a prompt because it couldn't find a valid device to install from and to:
<pre>
Enter your choice: 2

*** SOFTWARE DISTRIBUTION DEVICE SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of software distribution devices and which installation media you should
load on it:

No valid device is found.
Contact a DIGITAL field service representative.

#
</pre>

The problem seems to be that the hardware SimH emulates is not fully supported by ULTRIX (or is misdetected -- I'm not entirely sure myself). The good thing is that the internet has the correct solution, which is to fix some lines in the installation shell script. The fact that the basic system that is running at this point doesn't have ''vi'', or even ''cat'', makes this a bit harder ;-)

The only option you have is ''ed'', the old UNIX editor. For a quick introduction, see [http://blog.sanctum.geek.nz/actually-using-ed/ here].

To load the file in the editor, use
# '''ed install.1'''
16763

You can see the entire file with
1,$l
but be warned, the output is quite long and it'll take some time to print it all out.

To fix it, use the following commands (the lines in '''bold''' is what you type, everything else is the response from ed)
# '''ed install.1'''
16763
'''173l'''
BTD=`btd`
'''173s/`btd`/ra2/'''
'''173l'''
BTD=ra2
'''193l'''
rz* )
'''193s/rz/ra/'''
'''193l'''
ra* )
'''w'''
16761
'''q'''
#

First, we list line 173, then we change it from <code>BTD=`btd`</code> to <code>BTD=ra2</code>, which happens to be the CDROM device and unit number we're installing from (if you changed that in your config, use the correct name here!)

Then we change line 193 from <code>rz* )</code> to <code>ra* )</code> since we're trying to install on an RA type disk which was apparently not supported in ULTRIX out of the box.

After writing the file with <code>w</code> and quitting ed with <code>q</code>, we're back at the prompt, at which point we can use CTRL+D to retry the installation:

<pre>
# ^D
*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice: 2

*** SYSTEM DISK SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of system disk drives. Select one of the devices below to contain the
root file system:

SYSTEM DISK TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk drive
is on line and write-enabled (if applicable to your disk drive), then
confirm your choice.

Use RA90, ra0, for your system disk? (y/n) []: y

The installation procedure now allocates the root file system on
partition 'a' of the system disk, ra0 RA90.

Making the root file system on ra0 RA90.

The installation procedure is now restoring the root file system to
partition 'a' of the system disk, ra0 RA90.

The installation procedure now checks the root file system on partition 'a'
of the system disk, ra0 RA90.
** /dev/rra0a
** Last Mounted on /mnt
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
226 files, 4547 used, 11004 free (20 frags, 1373 blocks, 1.0% fragmentation)

*** BOOTSTRAP COMMAND SEQUENCE ***

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 8007F799
>>>
</pre>
After this, you will be back at the VAX boot prompt (if you used <code>set CPU CONHALT</code> in your config) or at the SimH emulator prompt (if you used <code>set CPU SIMHALT</code>, which is the default). In the latter case you will have to do <code>boot cpu</code> again to get to the VAX boot prompt.

==First boot==
Now we can boot the installed system from harddisk for the first time.

If you want to, now would be a good time to take a backup copy of your disk files (or just create a btrfs snapshot or something if you have the possibility ;-)

Okay, then let's boot from DUA0
<pre>
>>>boot dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 1153664
data = 281088
bss = 1043548
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #3: Wed Oct 18 11:49:00 EDT 1995
real mem = 67043328
avail mem = 62008320
Buffer configuration adjusted to run with small system page table
using 121 buffers containing 991232 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
</pre>
Here, it will seem to hang for a loooong time. A few minutes. Don't worry, it will eventually continue to boot. I guess it's probing for other devices which are not present.

You ''might'' be able to speed this up a bit by interrupting SimH (press CTRL+E in the SimH console window) and then using <code>set CPU noidle</code> followed by <code>go</code> to resume emulation.

Eventually, you will have to decide on a hostname. Note that if you want to play around with [[DECnet]] at some point, your hostname should be no longer than 6 characters.
<pre>
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)

*** SYSTEM NAME SPECIFICATION ***

Select the name of your system using alphanumeric characters.
The first character must be a letter. For example, tinker.

Enter your system name: yuki

You selected yuki as the name of your system.
Is this correct? (y/n) [y]: y
</pre>

Next up is the time configuration. Since Ultrix 4.5 is not Y2k compliant (AFAIK), I decided to set the clock back a whopping 20 years. Note that the timezone and daylight saving settings are for my location (Germany) and will probably vary for you.

<pre>
*** DATE AND TIME SPECIFICATION ***

The current date and time should be specified using the following
format:

yymmddhhmm

Use two digits for year (yy), month (mm), day (dd), hour (hh), and
minute (mm). Enter the time in 24-hour format. For example, 02:54
p.m. on Feb 2, 1993 would be entered as:

9302021454

Enter the date and time: 9512052336

*** TIME ZONE SELECTION ***

Select the time zone for your area, using the options listed in the
table below. You can also enter the number of hours (-12 to 12) in
time east of Greenwich.

Selection Time Zone
---------------------------------
e Eastern
c Central
m Mountain
p Pacific
g Greenwich
---------------------------------

Enter your choice: 1

Does your area alternate between Daylight Savings and Standard
time? (y/n) [y]: y

Select your geographic area for Daylight Savings Time, using the
options in the table below.

Selection Geographic Area
--------------------------------
u USA
a Australia
e Eastern Europe
c Central Europe
w Western Europe
--------------------------------

Enter your choice [u]: c

The current date and time is Tue Dec 5 23:36:46 EST 1995
</pre>

Next up is the root password. Note that Ultrix will not echo anything here, I added the asterisks just for this guide :)

<pre>
*** SPECIFY THE SUPERUSER PASSWORD ***
The Guide to Installing ULTRIX instructs you on how to enter
the superuser password.
Changing password for root
Enter new password: ******
Verify: ******
</pre>

Next up is the filesystem layout, which is a bit more involved than what you know from more modern systems like MS DOS ;-)

In ULTRIX, partitions are defined for each disk type in a file called <code>/etc/disktab</code>. Note that the partitions overlap, so you shouldn't use them all at the same time. The setup script actually takes care of that for you, but if you later create a new filesystem on the wrong partition you ''WILL'' lose data!

Normally, partition '''c''' is the whole disk, which is useful for add-on disk drives for example. Partitions '''a''' and '''b''' are always available and are traditionally used for the system and the swap-space respectively. The swap partition is also used for crashdumps if no separate crash-dump partition is created. The rest of the disk can be used either as a single partition (which is usually '''g''') or as 3 individual partitions ('''d''' to '''f'''). If the disk is larger than 1 gigabyte, you will get another partition, '''h''', after the g partition, probably because the filesystem cannot cope with partitions >1gig

In our case, we will have the following partitions on the first disk (RA0):
*Partition '''a''' of 32 mb for /root
*Partition '''b''' of 64 mb for swap+crashdump
*Partition '''c''' of 1.2 gig (whole-disk, not used on our setup)
*Partition '''d''' and '''e''' of 200 mb each (not used)
*Partition '''f''' of 400 mb (not used)
*Partition '''g''' of 800 mb (overlaps with d, e and f; will become /usr)
*Partition '''h''' of 256 mb (will become /usr/var)
This way we still have the whole second disk available for later use.

So here it goes:
<pre>
*** FILE SYSTEM DEFAULT OPTION ***

The following table shows the default file system layout on RA90, ra0:

partition bottom top size overlap default
a 0 32767 32768 c root
b 32768 159839 127072 c swap, dump
d 159840 580036 420197 c,g /usr

If you choose the defaults, the var area will be allocated to /usr/var.

Do you want to choose the default file system layout? (y/n): n
</pre>

No, we do not want to use the defaults...

First, we select disk 1, partition '''g''', for the /usr file system:
<pre>
*** /usr FILE SYSTEM ALLOCATION ***

You can allocate the /usr file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

/usr FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for /usr file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the /usr file system:

partition size (Kbytes) overlap
------------------------------------------------
d --- 210098 c,g
e --- 210098 c,g
f --- 420196 c,g
g --- 840393 c,d,e,f
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the /usr file system [d]: g

Making the new file system for /usr on /dev/rra0g RA90
</pre>

Next, we select disk 1, partition '''b''' for swap (only 1 swap partition) and for crashdumps:

<pre>
*** ALLOCATE THE SWAP1 SPACE ***

You can allocate the swap1 space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

SWAP1 SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for swap1 space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the swap1 space:

partition size (Kbytes) overlap
------------------------------------------------
b --- 63536 c
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the swap1 space [b]: b

*** ALLOCATE THE SWAP2 SPACE ***

Do you want to allocate a second swap space? (y/n) [n]: n

*** ALLOCATE THE CRASH DUMP SPACE ***

You can allocate the crash dump space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

CRASH DUMP SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for crash dump space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the crash dump space:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
b --- 63536 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the crash dump space [b]: b
</pre>

Finally we select partiton '''h''' for the /var file system. This might not be large enough later on but then we can always migrate the data away if we need to...

<pre>
*** ALLOCATE THE var FILE SYSTEM ***

You can allocate the var file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

var FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for var file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the var file system:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
g --- 840393 c,d,e,f
------------------------------------------------

Type the letter of the partition on which you want
to allocate the var file system [no default]: h

Making the new file system for var on /dev/rra0h RA90
</pre>

==Installing the distribution files==

Next up we have to decide what ''packages'' we want to install (yes, ULTRIX already had its own package format and corresponding installer called ''setld''. It is very basic, probably most similar to ''pkg_add'' on NetBSD). We simply install everything, since we have enough space :)

<pre>
This distribution media includes subsets for ULTRIX Worksystem
Software (UWS). A UWS license (on a workstation) or a UWS Server
License (on a timesharing machine or server) is required to install
these subsets.

Do you want to install ULTRIX Worksystem Software? y/n []: y

*** SUPPORTED SOFTWARE INSTALLATION ***

*** Select the DECwindows User Interface ***

1) DECwindows for OSF/Motif
2) X11/DECwindows (XUI)

Enter your choice [1]: 2

*** Enter Subset Selections ***

The following subsets are mandatory and will be installed automatically:
* Base System * Kernel Config Files
* TCP/IP Networking Utilities * Network File System Utilities
* Extended (Berkeley) Mailer * X11/DECwindows Servers
* X11/DECwindows User Environment * X11/DECwindows 75dpi Fonts

The subsets listed below are optional:
1) Printer Support Environment 2) RAND Mail Handler
3) Sys. Config. Mgmt. Program (SCAMP) 4) Communications Utilities
5) Unix-to-Unix Copy Facility 6) Maintenance Operations Protocol
7) Accounting Software 8) Kerberos Network Authentication
9) Enhanced Security Features 10) Prestoserve Utilities
11) System Exerciser Package 12) Bisynchronous Communications
13) Doc. Preparation for Ref. Pages 14) Doc. Preparation Extensions
15) Adobe Font Metric Files 16) Software Development Utilities
17) Source Code Control System 18) Internationalization Runtime Env.
19) Internationalization Dev. Env. 20) CDA Base System
21) CDA Software Dev Libraries 22) RPC Runtime Environment
23) RPC Development Environment 24) Pascal Development Package
25) VAX C/ULTRIX 26) Ref. Pages for Sys. Admin. & Users
27) Reference Pages for Programers 28) Programming Examples
29) Ultrix SPDS 30) X11/DECwindows 100dpi Fonts
31) VS35XX X11/DECwindows Fonts 32) Additional DECwindows Applications
33) DECwindows Mail Application 34) Worksystem Development Environment
35) X11/DECwindows System Management T 36) UWS Runtime Reference Pages
37) UWS Development Reference Pages

38) All mandatory and all optional subsets
39) Mandatory subsets only
40) Exit without installing subsets

Enter your choice(s): 38
Working....Wed Dec 6 00:14:12 EST 1995

You are installing the following subsets:
Base System Kernel Config Files
TCP/IP Networking Utilities Network File System Utilities
Extended (Berkeley) Mailer X11/DECwindows Servers
X11/DECwindows User Environment X11/DECwindows 75dpi Fonts
Printer Support Environment RAND Mail Handler
Sys. Config. Mgmt. Program (SCAMP) Communications Utilities
Unix-to-Unix Copy Facility Maintenance Operations Protocol
Accounting Software Kerberos Network Authentication
Enhanced Security Features Prestoserve Utilities
System Exerciser Package Bisynchronous Communications
Doc. Preparation for Ref. Pages Doc. Preparation Extensions
Adobe Font Metric Files Software Development Utilities
Source Code Control System Internationalization Runtime Env.
Internationalization Dev. Env. CDA Base System
CDA Software Dev Libraries RPC Runtime Environment
RPC Development Environment Pascal Development Package
VAX C/ULTRIX Ref. Pages for Sys. Admin. & Users
Reference Pages for Programers Programming Examples
Ultrix SPDS X11/DECwindows 100dpi Fonts
VS35XX X11/DECwindows Fonts Additional DECwindows Applications
DECwindows Mail Application Worksystem Development Environment
X11/DECwindows System Management To UWS Runtime Reference Pages
UWS Development Reference Pages

Is this correct? (y/n): y
</pre>

The installation will take a while (around 15-30 minutes for me), so feel free to let it run in the background for a while now. The installer will periodically print its status so you can see that it's still running...

<pre>
Base System (ULTBASE450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:14:43 EST 1995
Verifying

Kernel Config Files (ULTBIN450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:15:28 EST 1995
Verifying

...
</pre>

At some point you will have to confirm installing the generic kernel and the X11 subsystem:

<pre>
...
UWS Runtime Reference Pages (UWSMAN450)
Copying from /mnt/VAX/BASE (disk)
Verifying

UWS Development Reference Pages (UWSMANPGMR450)
Copying from /mnt/VAX/BASE (disk)
Verifying

The installation software has successfully installed the software
subsets.
Installing Upgrade subsets
The following subsets will be installed:
* X11/DECwindows Servers Upgrade * Generic Kernel
Do you wish to continue? (y/n): y

X11/DECwindows Servers Upgrade (UWSSER451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

Generic Kernel (ULTGENVMUNIX451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

The installation procedure has successfully installed the Upgrade
subsets
</pre>

That's it for the base installation, now we configure our kernel...

==Kernel configuration==
We have to select what features will be in the kernel. For anyone who has ever done a "make menuconfig" on Linux, this is ''slightly'' easier here ;-)
<pre>
*** CONFIGURATION FILE KERNEL OPTION SELECTION ***

Selection Kernel Option
---------------------------------------------------------------
1 Local Area Transport (LAT)
2 Bisynchronous Communication protocol (VAX only)
3 Computer Interconnect (CI) network
4 Diagnostic/Utilities Protocol (DUP)
5 ISO9660 File System Support (CDFS)
6 Ethernet Packet Filter
7 Enhanced Security Features
8 All of the above
9 None of the above
----------------------------------------------------------------

Enter the selection number for each kernel option you want.
For example, 1 3 :
</pre>

In our case, we don't need 2 (it is for 2780/3780 remote terminals), 3 (SimH doesn't emulate any cluster hardware) or 6 (it might cause problems with DECwindows/Motif). Everything else (<code>1 4 5 7</code>) is probably safe. This lets us play around with LAT (maybe connect an emulated Cisco router with LAT routing to it?) and DUP.

<pre>
Enter the selection number for each kernel option you want.
For example, 1 3 : 1 4 5 7

You specified the following kernel options:

Local Area Transport (LAT)
Diagnostic/Utilities Protocol (DUP)
ISO9660 File System Support (CDFS)
Enhanced Security Features

Is this correct? (y/n) [n]: y

*** SYSTEM CONFIGURATION PROCEDURE ***
The installation software found these devices in the floating
address space:

dz0 on uba0 at 0160100
dz1 on uba0 at 0160110
dz2 on uba0 at 0160120
dz3 on uba0 at 0160130

Configuration file complete.

Do you want to edit the configuration file? (y/n) [n]: n

*** PERFORMING SYSTEM CONFIGURATION ***

working ..... Wed Dec 6 02:29:10 EST 1995

*** DEVICE SPECIAL FILE CREATION ***
working ..... Wed Dec 6 02:29:53 EST 1995

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 800985B5
</pre>

Now you might want to take another backup of your disk images, since the ULTRIX installation is now basically complete.

==Adding the unsupported sets==
Now there are some more pieces of software in the CDROM, in a directory called ''unsupported''. We want to install these as well. First, let's boot our system again

<pre>
>>>b dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 747376
data = 125952
bss = 918192
Starting at 0x2c19

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
real mem = 67043328
avail mem = 56455168
using 1638 buffers containing 6712320 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
dz0 at uba0 csr 160100 vec 300, ipl 17
dz1 at uba0 csr 160110 vec 310, ipl 17
dz2 at uba0 csr 160120 vec 320, ipl 17
dz3 at uba0 csr 160130 vec 330, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
Wed Dec 6 11:25:29 MET 1995
Automatic reboot in progress...
/dev/ra0a: 644 files, 6161 used, 9390 free (166 frags, 1153 blocks, 5.0% fragmentation)
/dev/rra0g: umounted cleanly
/dev/rra0h: umounted cleanly
Warning Creating new license database
Warning creating new history file
check quotas: done.
savecore: checking for dump...dump does not exist
local daemons: syslog sendmail.
Removing remnant Opser files
preserving editor files
clearing /tmp
standard daemons: update cron accounting network snmpd printer.
start errlog daemon - elcsd
Wed Dec 6 11:25:48 MET 1995

ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
UWS V4.5 (Rev. 6)

Digital Equipment Corporation
Nashua, New Hampshire

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

#
</pre>

now, we mount the CDROM and use <code>setld</code> to install the unsupported packages. For simplicity's sake, we just (again) install everything.

<pre>
# mount -r /dev/ra2c /mnt
# cd /mnt/VAX/UNSUPPORTED
# ls
DXVUNDEMO450 ULXDOC450 ULXINGRES450 ULXRCS450 ULXUNMAN450
ULXAPL450 ULXEDIT450 ULXLEARN450 ULXSHELLS450 ULXUNMIT450
ULXBASE450 ULXF77450 ULXLISP450 ULXSPMS450 ULXVARIAN450
ULXBIB450 ULXGAMES450 ULXMAN450 ULXTERM450 instctrl
ULXCOURIER450 ULXHYPER450 ULXMOD2450 ULXTOOLS450
ULXCPM450 ULXICON450 ULXNEWS450 ULXUNEXAMP450
ULXDCMT450 ULXINET450 ULXNOTES450 ULXUNFONTS450
# setld -l .

*** Enter Subset Selections ***

The subsets listed below are optional:
1) Base Extension 2) GNU Emacs
3) TCP/IP Networking Util Extension 4) Additional Terminal Drivers
5) Document Preparation Software 6) Games and Diversions
7) Supplementary Documentation 8) Bibliographic Utilities
9) Remote Procedure Call Compiler 10) Aux. Command Line Interpreters
11) USENET News Interface Software 12) Notesfiles Package
13) Revision Control System 14) Misc. User-Contributed Utilities
15) Computer Aided System Tutor 16) Franz Lisp Development Package
17) Modula-2 Development Package 18) Raster Plotter Package
19) APL Development Package 20) CP/M 8in Diskette Utility
21) Hyperchannel Utilities 22) ICON (Language) Development Packag
23) University Ingres QUEL DBMS 24) Software Project Management System
25) Unsupported Fortran Utilities 26) Unsupported On-Line Documentation
27) Unsupported X11 Components 28) Unsupported DECwindows Examples
29) Unsupported MIT Fonts 30) Unsupported X11 Reference Pages
31) Unsupported OSF/Motif Demos

32) All mandatory and all optional subsets
33) Mandatory subsets only
34) Exit without installing subsets

Enter your choice(s): 32
Working....Wed Dec 6 11:29:48 MET 1995
Wed Dec 6 11:30:00 MET 1995

You are installing the following subsets:
Base Extension GNU Emacs
TCP/IP Networking Util Extension Additional Terminal Drivers
Document Preparation Software Games and Diversions
Supplementary Documentation Bibliographic Utilities
Remote Procedure Call Compiler Aux. Command Line Interpreters
USENET News Interface Software Notesfiles Package
Revision Control System Misc. User-Contributed Utilities
Computer Aided System Tutor Franz Lisp Development Package
Modula-2 Development Package Raster Plotter Package
APL Development Package CP/M 8in Diskette Utility
Hyperchannel Utilities ICON (Language) Development Package
University Ingres QUEL DBMS Software Project Management System
Unsupported Fortran Utilities Unsupported On-Line Documentation
Unsupported X11 Components Unsupported DECwindows Examples
Unsupported MIT Fonts Unsupported X11 Reference Pages
Unsupported OSF/Motif Demos

Is this correct? (y/n): y

Base Extension (ULXBASE450)
Copying from . (disk)
...
</pre>

Note that you could also quickly install only a single package by using for example
# setld -l . ULXINET450

==Resources==
Some of the resources I used for creating this guide:
*ULTRIX 4.5 installation ISO [http://musall.de/mirrors/ultrix/ultrix_os/vax/]
*ULTRIX-32 startup and shutdown guide [http://bitsavers.trailing-edge.com/pdf/dec/vax/ultrix-32/3.0/AA-ME91A-TE_ULTRIX-32_Guide_to_System_Shutdown_and_Startup.pdf]
*CERN guide to installing ULTRIX [https://web-docs.gsi.de/~kraemer/COLLECTION/ULTRIX/wwwpdp.web.cern.ch/wwwpdp/as/file/doc/ultrix/ultrix.pdf]
*My old guide for installing ULTRIX [https://docs.google.com/document/d/1ULRhzE0R1twarB5hfJm85yqOdTeoFCGgyPr5AxYEIbE]
*DEC KA655 CPU System Maintenance [http://bitsavers.trailing-edge.com/pdf/dec/vax/655/EK-306A-MG-001_655Mnt_Mar89.pdf]
[[Category:SIMH Tutorials]]

Installing Ultrix 4.5 on SIMH

2015-12-06T01:34:13Z

Darkstar: /* Kernel configuration */

This WORK-IN-PROGRESS guide will be a simple guide to installing ULTRIX 4.5 for VAX on SimH.

==Requirements==
The following is a list of things required for installation
*A recent version of the [[SIMH]] emulator
**Make sure the binary you're using includes Ethernet support
**I'm using a self-compiled version (git revision 0e8c0aea)
*An ISO image of ULTRIX 4.5 for VAX
**See the "Resources" section for a download link
**It's probably also possible to install it from tape, although I don't know if any installation tapes for ULTRIX 4.5 exist
*Optional stuff (might get added to the guide later):
**Starfish Ultrix Freeware CDs from [http://musall.de/mirrors/ultrix/freeware/ here]

==SimH configuration==
The machine I'm using to run ULTRIX has the following configuration
*DEC MicroVAX 3800
*64mb memory
*DELQA network card (XQ0)
*Two [[RA90]] disk drives (with 1.2gb each) attached to an RQDX3 controller (RQ0 and RQ1)
*CD ROM drive attached to the same RQDX3 controller as unit 2 (RQ2)
*[[TK50]] tape attached as unit 0 on the first TQK50 controller (TQ0)
*DZV11 terminal multiplexer with 16 lines, attached to telnet port 1005 (DZ)
*LPT line printer attached to text file <code>printer_output.txt</code>

Here's my config file (I called it <code>simh.conf</code>)
<pre><nowiki>
;
; SimH 4.0 Configuration file for MicroVAX 3800
;
; Host System : DEC MicroVAX 3800
; Operating System : DEC Ultrix v4.5
; Memory : 64mb
; Network config : XQ: Ethernet, 08:00:2b:04:14:02
; Disks : RQ0: RA90, 1.2gb
; RQ1: RA90, 1.2gb
; CDROMs : RQ2: iso file
; Tape config : TQ0: TK50, 94mb
;

load -r ka655x.bin

; NVRAM
attach NVR nvram.bin

; CPU config
set CPU 64m
set CPU conhalt
set CPU idle=all

; configure console to 7-bit only
set TTO 7b
set TTI 7b

; Disk drives
set RQ0 ra90
attach RQ0 rq0-ra90.dsk
set RQ1 ra90
attach RQ1 rq1-ra90.dsk
set RQ2 CDROM
attach -r RQ2 ultrix-vax-os-v4.5.mode1.ufs.iso
; MD5 sum: 19df0753c27f195e9f1d2f139a3b4629 *ultrix-vax-os-v4.5.mode1.ufs.iso
set RQ3 dis

; Tape
set TQ tk50
;attach tq0 filename-to-tape-file
set TQ1 dis
set TQ2 dis
set TQ3 dis

; serial port, simulated by Telnet to port 1005
set DZ LINES=16
set DZ 8B
attach DZ 1005 NoBuffer

; printer
set LPT enable
attach LPT printer_output.txt

; Disable unused peripherals
set CR dis
set RL dis
set TS dis

; Network interface (08-00-2b is the DEC prefix, the 04-14-02 part is arbitrary)
set XQ MAC=08-00-2b-04-14-02
attach XQ0 eth0

; serial console (launch directly after booting CPU)
set console telnet=1001

; experimental
;set QVSS en

; boot the system
;boot CPU
</nowiki></pre>
Note that I'm using a telnet console (for easier copy/paste on Windows), which means that directly after running this config file (via <code>do simh.conf</code> from Simh) you will need to connect via telnet to localhost:1001 or the boot will abort. If you are on Linux, or just don't want that, remove the <code>set console telnet=1001</code> line.

Also note that you might need to attach XQ0 to a different ethernet device. Use "show ether" in SimH to list all available devices on your system and modify the <code>attach XQ0 eth0</code> line accordingly.

==Running the Emulator==
Either run <code>vax.exe simh.conf</code> from the Windows command line, or just double-click the VAX.EXE executable and type <code>do simh.conf</code>.

On the first launch it might take some time because SimH has to create the disk images (~2.5 gb total). It should look something like this
<pre><nowiki>
MicroVAX 3900 simulator V4.0-0 Beta git commit id: 0e8c0aea
NVR: buffering file in memory
RQ2: unit is read only
Listening on port 1005
WinPcap version 4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008)
Eth: opened OS device \Device\NPF_{A41A1651-DD4D-4735-A4E0-88353165C2EC}
Listening on port 1001
sim>
</nowiki></pre>

Type the following to start the emulation (note: you can also uncomment that line from the end of the config file to have the emulation start right away)
sim> boot cpu
Waiting for console Telnet connection

Now would be a good time to connect your telnet session (I use a batch file for this), otherwise the boot process will timeout.

On your console, you should see something like this:
<pre><nowiki>
Connected to the MicroVAX 3900 simulator CON-TEL device

KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>
</nowiki></pre>

This is the VAX's boot prompt. Normally you just type
>>>boot <device>
where <device> is one of the following
*MUA<num>: TK tape device number <num> (1 to 4)
*DUA<num>: RQ disk device number <num> (1 to 4)

You can use <code>show device</code> to see the installed (and detected) devices you can boot from, and <code>show boot</code> to see which device will be the default if you just type <code>boot</code> (or <code>b</code> for short):
<pre><nowiki>
>>>show device
UQSSP Disk Controller 0 (772150)
-DUA0 (RA90)
-DUA1 (RA90)
-DUA2 (RRD40)

UQSSP Tape Controller 0 (774500)
-MUA0 (TK50)

Ethernet Adapter 0 (774440)
-XQA0 (08-00-2B-04-14-02)
>>>show boot
MUA0
</nowiki></pre>

Since we want to boot from CDROM, which is unit 2, we can use
>>>boot DUA2

Note: You can add flags to boot into single user mode, or to boot in interactive mode (so-called ''conversational boot'', where the system prompts you for a kernel file name to load). For details see the Guide to ULTRIX-32 System Startup and Shutdown, linked to in the ''References'' section. To use it, add the <code>/R5:<flags></code> option to the <code>boot</code> command, where flags is 0 (default multi-user), 1 (conversational multi-user), 2 (single-user) or 3 (conversational single-user). For example
>>>boot/r5:3 dua0

Note: You can also boot from ethernet (<code>boot XQA0</code>) but this requires a DEC-specific boot server in your network (the protocol is called ''MOP'' for ''Maintenance Operations Protocol''), which is beyond the scope of this document. I did get it to work a few years ago though, but it was a bit difficult to set up.

For a list and description of all commands available in the bootloader (hint: there are lots), see the ''KA655 CPU System Maintenance'' guide mentioned in the ''References'' section..

==Bootstrapping ULTRIX==
You will see the following output on the first boot.
<pre>
>>>boot dua2
(BOOT/R5:0 DUA2

2..
-DUA2
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 945424
data = 1290240
bss = 757940
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #2: Wed Oct 18 12:06:55 EDT 1995
real mem = 67043328
avail mem = 61517824
Buffer configuration adjusted to run with small system page table
using 123 buffers containing 1007616 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
WARNING: clock gained 47 days -- CHECK AND RESET THE DATE!

*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice:
</pre>
Now we want to do an ''ADVANCED Installation'', but when we try to, it will take a few seconds until the installation program dumps us to a prompt because it couldn't find a valid device to install from and to:
<pre>
Enter your choice: 2

*** SOFTWARE DISTRIBUTION DEVICE SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of software distribution devices and which installation media you should
load on it:

No valid device is found.
Contact a DIGITAL field service representative.

#
</pre>

The problem seems to be that the hardware SimH emulates is not fully supported by ULTRIX (or is misdetected -- I'm not entirely sure myself). The good thing is that the internet has the correct solution, which is to fix some lines in the installation shell script. The fact that the basic system that is running at this point doesn't have ''vi'', or even ''cat'', makes this a bit harder ;-)

The only option you have is ''ed'', the old UNIX editor. For a quick introduction, see [http://blog.sanctum.geek.nz/actually-using-ed/ here].

To load the file in the editor, use
# '''ed install.1'''
16763

You can see the entire file with
1,$l
but be warned, the output is quite long and it'll take some time to print it all out.

To fix it, use the following commands (the lines in '''bold''' is what you type, everything else is the response from ed)
# '''ed install.1'''
16763
'''173l'''
BTD=`btd`
'''173s/`btd`/ra2/'''
'''173l'''
BTD=ra2
'''193l'''
rz* )
'''193s/rz/ra/'''
'''193l'''
ra* )
'''w'''
16761
'''q'''
#

First, we list line 173, then we change it from <code>BTD=`btd`</code> to <code>BTD=ra2</code>, which happens to be the CDROM device and unit number we're installing from (if you changed that in your config, use the correct name here!)

Then we change line 193 from <code>rz* )</code> to <code>ra* )</code> since we're trying to install on an RA type disk which was apparently not supported in ULTRIX out of the box.

After writing the file with <code>w</code> and quitting ed with <code>q</code>, we're back at the prompt, at which point we can use CTRL+D to retry the installation:

<pre>
# ^D
*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice: 2

*** SYSTEM DISK SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of system disk drives. Select one of the devices below to contain the
root file system:

SYSTEM DISK TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk drive
is on line and write-enabled (if applicable to your disk drive), then
confirm your choice.

Use RA90, ra0, for your system disk? (y/n) []: y

The installation procedure now allocates the root file system on
partition 'a' of the system disk, ra0 RA90.

Making the root file system on ra0 RA90.

The installation procedure is now restoring the root file system to
partition 'a' of the system disk, ra0 RA90.

The installation procedure now checks the root file system on partition 'a'
of the system disk, ra0 RA90.
** /dev/rra0a
** Last Mounted on /mnt
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
226 files, 4547 used, 11004 free (20 frags, 1373 blocks, 1.0% fragmentation)

*** BOOTSTRAP COMMAND SEQUENCE ***

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 8007F799
>>>
</pre>
After this, you will be back at the VAX boot prompt (if you used <code>set CPU CONHALT</code> in your config) or at the SimH emulator prompt (if you used <code>set CPU SIMHALT</code>, which is the default). In the latter case you will have to do <code>boot cpu</code> again to get to the VAX boot prompt.

==First boot==
Now we can boot the installed system from harddisk for the first time.

If you want to, now would be a good time to take a backup copy of your disk files (or just create a btrfs snapshot or something if you have the possibility ;-)

Okay, then let's boot from DUA0
<pre>
>>>boot dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 1153664
data = 281088
bss = 1043548
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #3: Wed Oct 18 11:49:00 EDT 1995
real mem = 67043328
avail mem = 62008320
Buffer configuration adjusted to run with small system page table
using 121 buffers containing 991232 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
</pre>
Here, it will seem to hang for a loooong time. A few minutes. Don't worry, it will eventually continue to boot. I guess it's probing for other devices which are not present.

You ''might'' be able to speed this up a bit by interrupting SimH (press CTRL+E in the SimH console window) and then using <code>set CPU noidle</code> followed by <code>go</code> to resume emulation.

Eventually, you will have to decide on a hostname. Note that if you want to play around with [[DECnet]] at some point, your hostname should be no longer than 6 characters.
<pre>
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)

*** SYSTEM NAME SPECIFICATION ***

Select the name of your system using alphanumeric characters.
The first character must be a letter. For example, tinker.

Enter your system name: yuki

You selected yuki as the name of your system.
Is this correct? (y/n) [y]: y
</pre>

Next up is the time configuration. Since Ultrix 4.5 is not Y2k compliant (AFAIK), I decided to set the clock back a whopping 20 years. Note that the timezone and daylight saving settings are for my location (Germany) and will probably vary for you.

<pre>
*** DATE AND TIME SPECIFICATION ***

The current date and time should be specified using the following
format:

yymmddhhmm

Use two digits for year (yy), month (mm), day (dd), hour (hh), and
minute (mm). Enter the time in 24-hour format. For example, 02:54
p.m. on Feb 2, 1993 would be entered as:

9302021454

Enter the date and time: 9512052336

*** TIME ZONE SELECTION ***

Select the time zone for your area, using the options listed in the
table below. You can also enter the number of hours (-12 to 12) in
time east of Greenwich.

Selection Time Zone
---------------------------------
e Eastern
c Central
m Mountain
p Pacific
g Greenwich
---------------------------------

Enter your choice: 1

Does your area alternate between Daylight Savings and Standard
time? (y/n) [y]: y

Select your geographic area for Daylight Savings Time, using the
options in the table below.

Selection Geographic Area
--------------------------------
u USA
a Australia
e Eastern Europe
c Central Europe
w Western Europe
--------------------------------

Enter your choice [u]: c

The current date and time is Tue Dec 5 23:36:46 EST 1995
</pre>

Next up is the root password. Note that Ultrix will not echo anything here, I added the asterisks just for this guide :)

<pre>
*** SPECIFY THE SUPERUSER PASSWORD ***
The Guide to Installing ULTRIX instructs you on how to enter
the superuser password.
Changing password for root
Enter new password: ******
Verify: ******
</pre>

Next up is the filesystem layout, which is a bit more involved than what you know from more modern systems like MS DOS ;-)

In ULTRIX, partitions are defined for each disk type in a file called <code>/etc/disktab</code>. Note that the partitions overlap, so you shouldn't use them all at the same time. The setup script actually takes care of that for you, but if you later create a new filesystem on the wrong partition you ''WILL'' lose data!

Normally, partition '''c''' is the whole disk, which is useful for add-on disk drives for example. Partitions '''a''' and '''b''' are always available and are traditionally used for the system and the swap-space respectively. The swap partition is also used for crashdumps if no separate crash-dump partition is created. The rest of the disk can be used either as a single partition (which is usually '''g''') or as 3 individual partitions ('''d''' to '''f'''). If the disk is larger than 1 gigabyte, you will get another partition, '''h''', after the g partition, probably because the filesystem cannot cope with partitions >1gig

In our case, we will have the following partitions on the first disk (RA0):
*Partition '''a''' of 32 mb for /root
*Partition '''b''' of 64 mb for swap+crashdump
*Partition '''c''' of 1.2 gig (whole-disk, not used on our setup)
*Partition '''d''' and '''e''' of 200 mb each (not used)
*Partition '''f''' of 400 mb (not used)
*Partition '''g''' of 800 mb (overlaps with d, e and f; will become /usr)
*Partition '''h''' of 256 mb (will become /usr/var)
This way we still have the whole second disk available for later use.

So here it goes:
<pre>
*** FILE SYSTEM DEFAULT OPTION ***

The following table shows the default file system layout on RA90, ra0:

partition bottom top size overlap default
a 0 32767 32768 c root
b 32768 159839 127072 c swap, dump
d 159840 580036 420197 c,g /usr

If you choose the defaults, the var area will be allocated to /usr/var.

Do you want to choose the default file system layout? (y/n): n
</pre>

No, we do not want to use the defaults...

First, we select disk 1, partition '''g''', for the /usr file system:
<pre>
*** /usr FILE SYSTEM ALLOCATION ***

You can allocate the /usr file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

/usr FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for /usr file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the /usr file system:

partition size (Kbytes) overlap
------------------------------------------------
d --- 210098 c,g
e --- 210098 c,g
f --- 420196 c,g
g --- 840393 c,d,e,f
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the /usr file system [d]: g

Making the new file system for /usr on /dev/rra0g RA90
</pre>

Next, we select disk 1, partition '''b''' for swap (only 1 swap partition) and for crashdumps:

<pre>
*** ALLOCATE THE SWAP1 SPACE ***

You can allocate the swap1 space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

SWAP1 SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for swap1 space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the swap1 space:

partition size (Kbytes) overlap
------------------------------------------------
b --- 63536 c
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the swap1 space [b]: b

*** ALLOCATE THE SWAP2 SPACE ***

Do you want to allocate a second swap space? (y/n) [n]: n

*** ALLOCATE THE CRASH DUMP SPACE ***

You can allocate the crash dump space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

CRASH DUMP SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for crash dump space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the crash dump space:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
b --- 63536 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the crash dump space [b]: b
</pre>

Finally we select partiton '''h''' for the /var file system. This might not be large enough later on but then we can always migrate the data away if we need to...

<pre>
*** ALLOCATE THE var FILE SYSTEM ***

You can allocate the var file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

var FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for var file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the var file system:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
g --- 840393 c,d,e,f
------------------------------------------------

Type the letter of the partition on which you want
to allocate the var file system [no default]: h

Making the new file system for var on /dev/rra0h RA90
</pre>

==Installing the distribution files==

Next up we have to decide what ''packages'' we want to install (yes, ULTRIX already had its own package format and corresponding installer called ''setld''. It is very basic, probably most similar to ''pkg_add'' on NetBSD). We simply install everything, since we have enough space :)

<pre>
This distribution media includes subsets for ULTRIX Worksystem
Software (UWS). A UWS license (on a workstation) or a UWS Server
License (on a timesharing machine or server) is required to install
these subsets.

Do you want to install ULTRIX Worksystem Software? y/n []: y

*** SUPPORTED SOFTWARE INSTALLATION ***

*** Select the DECwindows User Interface ***

1) DECwindows for OSF/Motif
2) X11/DECwindows (XUI)

Enter your choice [1]: 2

*** Enter Subset Selections ***

The following subsets are mandatory and will be installed automatically:
* Base System * Kernel Config Files
* TCP/IP Networking Utilities * Network File System Utilities
* Extended (Berkeley) Mailer * X11/DECwindows Servers
* X11/DECwindows User Environment * X11/DECwindows 75dpi Fonts

The subsets listed below are optional:
1) Printer Support Environment 2) RAND Mail Handler
3) Sys. Config. Mgmt. Program (SCAMP) 4) Communications Utilities
5) Unix-to-Unix Copy Facility 6) Maintenance Operations Protocol
7) Accounting Software 8) Kerberos Network Authentication
9) Enhanced Security Features 10) Prestoserve Utilities
11) System Exerciser Package 12) Bisynchronous Communications
13) Doc. Preparation for Ref. Pages 14) Doc. Preparation Extensions
15) Adobe Font Metric Files 16) Software Development Utilities
17) Source Code Control System 18) Internationalization Runtime Env.
19) Internationalization Dev. Env. 20) CDA Base System
21) CDA Software Dev Libraries 22) RPC Runtime Environment
23) RPC Development Environment 24) Pascal Development Package
25) VAX C/ULTRIX 26) Ref. Pages for Sys. Admin. & Users
27) Reference Pages for Programers 28) Programming Examples
29) Ultrix SPDS 30) X11/DECwindows 100dpi Fonts
31) VS35XX X11/DECwindows Fonts 32) Additional DECwindows Applications
33) DECwindows Mail Application 34) Worksystem Development Environment
35) X11/DECwindows System Management T 36) UWS Runtime Reference Pages
37) UWS Development Reference Pages

38) All mandatory and all optional subsets
39) Mandatory subsets only
40) Exit without installing subsets

Enter your choice(s): 38
Working....Wed Dec 6 00:14:12 EST 1995

You are installing the following subsets:
Base System Kernel Config Files
TCP/IP Networking Utilities Network File System Utilities
Extended (Berkeley) Mailer X11/DECwindows Servers
X11/DECwindows User Environment X11/DECwindows 75dpi Fonts
Printer Support Environment RAND Mail Handler
Sys. Config. Mgmt. Program (SCAMP) Communications Utilities
Unix-to-Unix Copy Facility Maintenance Operations Protocol
Accounting Software Kerberos Network Authentication
Enhanced Security Features Prestoserve Utilities
System Exerciser Package Bisynchronous Communications
Doc. Preparation for Ref. Pages Doc. Preparation Extensions
Adobe Font Metric Files Software Development Utilities
Source Code Control System Internationalization Runtime Env.
Internationalization Dev. Env. CDA Base System
CDA Software Dev Libraries RPC Runtime Environment
RPC Development Environment Pascal Development Package
VAX C/ULTRIX Ref. Pages for Sys. Admin. & Users
Reference Pages for Programers Programming Examples
Ultrix SPDS X11/DECwindows 100dpi Fonts
VS35XX X11/DECwindows Fonts Additional DECwindows Applications
DECwindows Mail Application Worksystem Development Environment
X11/DECwindows System Management To UWS Runtime Reference Pages
UWS Development Reference Pages

Is this correct? (y/n): y
</pre>

The installation will take a while (around 15-30 minutes for me), so feel free to let it run in the background for a while now. The installer will periodically print its status so you can see that it's still running...

<pre>
Base System (ULTBASE450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:14:43 EST 1995
Verifying

Kernel Config Files (ULTBIN450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:15:28 EST 1995
Verifying

...
</pre>

At some point you will have to confirm installing the generic kernel and the X11 subsystem:

<pre>
...
UWS Runtime Reference Pages (UWSMAN450)
Copying from /mnt/VAX/BASE (disk)
Verifying

UWS Development Reference Pages (UWSMANPGMR450)
Copying from /mnt/VAX/BASE (disk)
Verifying

The installation software has successfully installed the software
subsets.
Installing Upgrade subsets
The following subsets will be installed:
* X11/DECwindows Servers Upgrade * Generic Kernel
Do you wish to continue? (y/n): y

X11/DECwindows Servers Upgrade (UWSSER451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

Generic Kernel (ULTGENVMUNIX451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

The installation procedure has successfully installed the Upgrade
subsets
</pre>

That's it for the base installation, now we configure our kernel...

==Kernel configuration==
We have to select what features will be in the kernel. For anyone who has ever done a "make menuconfig" on Linux, this is ''slightly'' easier here ;-)
<pre>
*** CONFIGURATION FILE KERNEL OPTION SELECTION ***

Selection Kernel Option
---------------------------------------------------------------
1 Local Area Transport (LAT)
2 Bisynchronous Communication protocol (VAX only)
3 Computer Interconnect (CI) network
4 Diagnostic/Utilities Protocol (DUP)
5 ISO9660 File System Support (CDFS)
6 Ethernet Packet Filter
7 Enhanced Security Features
8 All of the above
9 None of the above
----------------------------------------------------------------

Enter the selection number for each kernel option you want.
For example, 1 3 :
</pre>

In our case, we don't need 2 (it is for 2780/3780 remote terminals), 3 (SimH doesn't emulate any cluster hardware) or 6 (it might cause problems with DECwindows/Motif). Everything else (<code>1 4 5 7</code>) is probably safe. This lets us play around with LAT (maybe connect an emulated Cisco router with LAT routing to it?) and DUP.

<pre>
Enter the selection number for each kernel option you want.
For example, 1 3 : 1 4 5 7

You specified the following kernel options:

Local Area Transport (LAT)
Diagnostic/Utilities Protocol (DUP)
ISO9660 File System Support (CDFS)
Enhanced Security Features

Is this correct? (y/n) [n]: y

*** SYSTEM CONFIGURATION PROCEDURE ***
The installation software found these devices in the floating
address space:

dz0 on uba0 at 0160100
dz1 on uba0 at 0160110
dz2 on uba0 at 0160120
dz3 on uba0 at 0160130

Configuration file complete.

Do you want to edit the configuration file? (y/n) [n]: n

*** PERFORMING SYSTEM CONFIGURATION ***

working ..... Wed Dec 6 02:29:10 EST 1995

*** DEVICE SPECIAL FILE CREATION ***
working ..... Wed Dec 6 02:29:53 EST 1995

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 800985B5
</pre>

Now you might want to take another backup of your disk images, since the ULTRIX installation is now basically complete.

==Resources==
Some of the resources I used for creating this guide:
*ULTRIX 4.5 installation ISO [http://musall.de/mirrors/ultrix/ultrix_os/vax/]
*ULTRIX-32 startup and shutdown guide [http://bitsavers.trailing-edge.com/pdf/dec/vax/ultrix-32/3.0/AA-ME91A-TE_ULTRIX-32_Guide_to_System_Shutdown_and_Startup.pdf]
*CERN guide to installing ULTRIX [https://web-docs.gsi.de/~kraemer/COLLECTION/ULTRIX/wwwpdp.web.cern.ch/wwwpdp/as/file/doc/ultrix/ultrix.pdf]
*My old guide for installing ULTRIX [https://docs.google.com/document/d/1ULRhzE0R1twarB5hfJm85yqOdTeoFCGgyPr5AxYEIbE]
*DEC KA655 CPU System Maintenance [http://bitsavers.trailing-edge.com/pdf/dec/vax/655/EK-306A-MG-001_655Mnt_Mar89.pdf]
[[Category:SIMH Tutorials]]

Installing Ultrix 4.5 on SIMH

2015-12-05T23:48:47Z

Darkstar: /* Installing the distribution files */

Installing Ultrix 4.5 on SIMH

2015-12-05T23:16:52Z

Darkstar: /* Installing the distribution files */

Installing Ultrix 4.5 on SIMH

2015-12-05T23:11:27Z

Darkstar: /* First boot */

Installing Ultrix 4.5 on SIMH

2015-12-05T22:30:10Z

Darkstar: /* First boot */

Installing Ultrix 4.5 on SIMH

2015-12-05T22:07:45Z

Darkstar: add reference

Installing Ultrix 4.5 on SIMH

2015-12-05T22:06:49Z

Darkstar: /* Resources */

Installing Ultrix 4.5 on SIMH

2015-12-05T21:57:15Z

Darkstar: oops

Installing Ultrix 4.5 on SIMH

2015-12-05T21:55:16Z

Darkstar: /* Bootstrapping ULTRIX */

Installing Ultrix 4.5 on SIMH

2015-12-05T21:34:10Z

Darkstar: /* Running the Emulator */

Installing Ultrix 4.5 on SIMH

2015-12-05T21:32:42Z

Darkstar: /* Running the Emulator */

Installing Ultrix 4.5 on SIMH

2015-12-05T21:21:07Z

Darkstar: /* Resources */ link to my old guide

Installing Ultrix 4.5 on SIMH

2015-12-05T21:12:33Z

Darkstar: first version

Zork

2015-12-03T17:35:17Z

Darkstar: /* 6502 (Apple II, Atari, Commodore 64) */ Add Plus/4 version. There's also a C128 native version but I still have to find a "clean" download for it...

[[Image:QuickWin.jpg|200px|thumb|right|Dungeon 2.5.6 on Windows 3.0]]
[[Image:Map of Dungeon.jpg|200px|thumb|right|A map of Dungeon]]

Zork is one of the most popular, and ported games for mini and personal computers. Zork was written in MIT (Marc Blanc, Joel Berez and others) in the [[MDL]] language. It was VERY popular and was ported to various other langauges and systems. The [[FORTRAN]] port by Bob Supnik is perhaps one of the more popular versions.

There is a little confusion as the the name, Zork started out as the original name, but as time went on, it became "Dungeon". However TSR threatened [[Infocom]] that Dungeon sounded too much like Dungeons & Dragons, so the name was changed back to Zork.

A better introduction can be found here:

http://www.csd.uwo.ca/Infocom/dungeon.html

== Introduction ==

Zork started the genre that would be better known as interactive fiction. You simply type in what you would want to do, and the story unfolds..

<pre>
# ./zork
You are in an open field west of a big white house with a boarded
front door.
There is a small mailbox here.
>open mailbox
Opening the mailbox reveals:
A leaflet.
>take leaflet
Taken.
>read leaflet
Welcome to Dungeon!

Dungeon is a game of adventure, danger, and low cunning. In it
you will explore some of the most amazing territory ever seen by mortal
man. Hardened adventurers have run screaming from the terrors contained
within.

In Dungeon, the intrepid explorer delves into the forgotten secrets
of a lost labyrinth deep in the bowels of the earth, searching for
vast treasures long hidden from prying eyes, treasures guarded by
fearsome monsters and diabolical traps!

No DECsystem should be without one!

Dungeon was created at the Programming Technology Division of the MIT
Laboratory for Computer Science by Tim Anderson, Marc Blank, Bruce
Daniels, and Dave Lebling. It was inspired by the Adventure game of
Crowther and Woods, and the Dungeons and Dragons game of Gygax
and Arneson. The original version was written in MDL (alias MUDDLE).
The current version was translated from MDL into FORTRAN IV by
a somewhat paranoid DEC engineer who prefers to remain anonymous.

On-line information may be obtained with the commands HELP and INFO.
>

</pre>

== Source code ==

The MDL source code is available from the SIMH software site [http://simh.trailing-edge.com/games/zork-mdl.zip here]. Likewise, Bob's port to Fortran is available [http://simh.trailing-edge.com/games/dungeon.zip here]. The Fortran version was last updated from 1990.

Various versions can be retrieved from http://ftp.giga.or.at/pub/ifarchive/games/source/ 

{| class="wikitable"
|-
!Source Code
!Description
|-
|[http://ftp.giga.or.at/pub/ifarchive/games/source/Dungeon_source.sit Dungeon_source.sit]
|C source code for Dungeon (the more or less public domain version of the original MIT Zork) for the Macintosh.
|-
|[http://ftp.giga.or.at/pub/ifarchive/games/source/dungeon-2.5.6.tar.gz dungeon-2.5.6.tar.gz]
|FORTRAN source code of Dungeon, the more or less public domain version of the original MIT Zork, version 2.5A, 30-Aug-90. This version is Robert M. Supnik's DECUS version 2.5A (18-Jul-80), ported to Linux with f2c.
|-
|[http://ftp.giga.or.at/pub/ifarchive/games/source/dungeon-3.2A.tar.Z dungeon-3.2A.tar.Z]
|Dungeon version 3.2A, 1-Oct-94; contains all the rooms and puzzles of the original MIT Zork. DEC FORTRAN source code by Robert M. Supnik; see dungn32b.zip for a port to DOS.
|-
|[http://ftp.giga.or.at/pub/ifarchive/games/source/dungeon-3.2B.patch dungeon-3.2B.patch]
|Source code patch by Robert M. Supnik to upgrade Dungeon version 3.2A to version 3.2B.
|-
|[http://ftp.giga.or.at/pub/ifarchive/games/source/dungeon-3.2B.unidiff dungeon-3.2B.unidiff]
|Same patch, converted to Larry Wall's 'patch' utility format (unified diff) by David Bristow.
|-
|[http://ftp.giga.or.at/pub/ifarchive/games/source/dungeon-glk.tar.Z dungeon-glk.tar.Z]
|Dungeon, the more or less public domain version of the original MIT Zork, version 3.2B. Andrew Plotkin ported this version to C |and added the Glk interface.
|-
|[http://ftp.giga.or.at/pub/ifarchive/games/source/dungn26b-src.zip dungn26b-src.zip]
|FORTRAN source code of Dungeon, the more or less public domain version of the original MIT Zork, version 2.6B, 07-Apr-88. This |version is Robert M. Supnik's DECUS version 2.6A (18-Oct-80), ported to MS-DOS by Kevin Black. (an MS-DOS executable of this |version is in games/pc/dungn26b.zip)
|-
|[http://ftp.giga.or.at/pub/ifarchive/games/source/dungn27s.zip dungn27s.zip]
|C source code of Dungeon, the more or less public domain version of the original MIT Zork, version 2.7A, 11-Mar-91. (an MS-DOS |executable of this version is in games/pc/dungn27a.zip, an Amiga port is in games/amiga/Dungeon.lzh, and a port to the Acorn |Archimedes is in games/archimedes/dungeon.spk)
|-
|[http://ftp.giga.or.at/pub/ifarchive/games/source/dungn32b.zip dungn32b.zip]
|Dungeon, the more or less public domain version of the original MIT Zork, version 3.2B, 1-Oct-94. DOS executable for 386+ only and |FORTRAN source code, ported from DEC FORTRAN to GNU G77 FORTRAN by Volker Blasius and David Kinder. The original source code is in |dungeon-32A.tar.Z (file is linked to games/pc/dungn32b.zip)
|}

== Notable Platforms ==

=== Zork running on ITS ===
[[Image:Zork on infoton terminal.jpg|150px|thumb|right|Zork on the PDP-10]]
Zork's [[MDL]] source on [[ITS]] for the [[PDP-10]].

There is a MDL interpreter called [http://ifarchive.org/indexes/if-archiveXprogrammingXmdlXinterpretersXconfusion.html Confusion] that is capable or running a slightly patched version of the original MDL Zork code.

From the US NEWS & DUNGEON REPORT:

<pre>
US NEWS & DUNGEON REPORT
7/22/81 Last G.U.E. Edition

This version of ZORK is no longer being supported on this or any other
machine. In particular, bugs and feature requests will, most likely, be
read and ignored. There are updated versions of ZORK, including some
altogether new problems, available for PDP-11s and various
microcomputers (TRS-80, APPLE, maybe more later). For information, send
a SASE to:

Infocom, Inc.
P.O. Box 120, Kendall Station
Cambridge, Ma. 02142
</pre>

=== Zork on RT-11 ===
[[Image:Zork I for the PDP-11.jpg|thumb|150px|right|The cover for Zork I on the PDP-11]]

I've managed to track back some source & binaries for this [[RT-11]] version. Also the fabled manual was recently found, sold and scanned. It's even autographed.

[http://www.getlamp.com/pdf/Zork_PDP_11.pdf Zork Manual]

[http://pdp11.saracom.com/ Saracom link]

This version can be converted to disk images with [http://www.dbit.com/pub/putr putr], which you can then copy to a larger disk and run it. At the moment this is the oldest known runnable version of Zork.
<pre>
RT-11SJ V04.00C

.D 56=5015

.TYPE V4USER.TXT
Welcome to RT-11 Version 4. RT-11 V04 provides new hardware support
and some major enhancements over Version 3B.

Please use the HELP command; it describes the new options in many
of the utilities.

If you are using a terminal that requires fill characters,
modify location 56 with a Deposit command before proceeding with
system installation. LA36 DECwriter II and VT52 DECscope terminals
do NOT require such modification.

.D 56=0

.RUN DUNGEO
Welcome to Dungeon. This version created 10-AUG-78.
You are in an open field west of a big white house with a boarded
front door.
There is a small mailbox here.
>HISTORY
Revision history:

10-AUG-78 DECUS version.
14-JUL-78 Bug fixes.
6-JUL-78 Multiple system play test version.
28-JUN-78 Complete play test version.
18-JUN-78 Play test public version.
14-JUN-78 Initial public version.
4-MAR-78 Initial version.
</pre>

There is also some rx50 disk images, here [http://www.pdp11.co.uk/2009/05/17/rt-11-rx50-disk-images/ here] dungeon1,dungeon2 & asc are the disks needed for dungeon. This version however is the source code version, Instructions on compiling it can be found in the tutorial [[Compiling Dungeon on RT-11]]. Extracting the strings I see this for the history portion:
<pre>
10-OCT-78 Puzzle Room (V2.1A)
10-SEP-78 Endgame (V2.0A).
10-AUG-78 DECUS version (V1.1B).
14-JUN-78 Public version with parser (V1.1A).
4-MAR-78 Debugging version (V1.0A).
</pre>

I've also managed to track back the source to a newer version, and setup some instructions on how to build it with RT-11 in the tutorial aptly named [[Compiling Dungeon on RT-11]].

=== Zork on TOPS-20 ===
I came across this looking at old UseNIX software, and oddly enough in the [http://tuhs.gcu.info/Applications/Shoppa_Tapes/usenix878889.tar.gz 1987 tape], I found this.. I haven't tried to build it or run it, but it does include source, and in the text files I could extract the following:

<pre>
Welcome to Dungeon.
This version created Sep 21, 1981
</pre>

And the history

<pre>
Revision history:

28-nov-78 Minor cleanups (v2.1a).
10-sep-78 Endgame (V2.0a).
10-AUG-78 DECUS version (V1.1b).
14-JUN-78 Public version with parser (V1.1a).
4-MAR-78 Debugging version (V1.0a).
</pre>

So, while this isn't the oldest one, it's got to be more portable....

=== Zork on the IBM 370 mainframe ===
Recently I've found an [http://web.archive.org/web/20050914173504/http://pucc.princeton.edu/~melinda/ archive of Zork] that includes source that runs on CMS for the IBM [[System/370]] mainframe.. I've run it under [[VM/370]].

<pre>

version
V1. 2C
>
history
Revision history:

V1.0 Appeared fully-formed in someone's VM reader.
>
</pre>

It's scored in 500 points, and the dates all seem to point to 1980 and 1981.

<pre>
US NEWS & DUNGEON REPORT
01-MAR-81 Late Dungeon Edition
This is a version of Zork on VM/370

The problems with it are:
-Lack of an endgame.
-Simple parser (no compound sentences).
-Numerous bugs and spelling errors.
But so what.

If you encounter problems or find logic, spelling, or usage bugs,
keep them to yourself.
</pre>

=== Zork on the PDP-11 running BSD ===

This version of Zork contains the following readme, with some information as to the history of Zork on the mini's:

<pre>
This is a patched up RT-11 binary which ran on an LSI-11.
This program was originally distributed on a Purdue mailing and
was full of bugs. Many bugs in that distribution have been fixed.
This is not a pristine, elegent implemention but it works!

DUNGEON expects following files:

/usr/chris/dungeon/zork UNIX a.out file for Dungeon root
segment and RT-11 Fortran Runtime
/usr/chris/dungeon/dtext.dat Text file in random access-format
/usr/chris/dungeon/dindex.dat Indicies (probably into dtext.dat)
/usr/chris/dungeon/doverlay Original RT-11 DUNGEO.SAV
(reads overlays from here)

If you don't like these pathnames, "dungeon.c" may be modified to
reflect the desired names. Pathnames were originally in "o.s" but
"dungeon.c" was implemented at Purdue as an easier way to change them
than patching binaries. However, we have standardized the d/o.s
interface. It now would be an simple task to put pathnames in o.s
if one so desired.

Other files of interest:

dungeon.c C program with date and UID check and exec of dungeon.

o.s Assembler driver to make dungeon run under UNIX.
Loads overlays, save/restore games, etc. This must
be relocated to 0146000 and stuck on the end of the
dungeon binary file "d". (We don't have sources)

p1 sh file to patch up a.out file "dung" so interface
between "d" and "o.s" works.

1.s kludge file to achive . = .+ 0146000

mkovl sh file to make overlay driver, attach it to "d",
and make a UNIX a.out file by attaching the
proper header.

--ccw
</pre>

=== Zork on BSD/VAX ===

This version is infact the same version that runs on the PDP-11 versions of BSD Unix. What is interesting is that this version uses a PDP/11 emulator to run the above binary. It's also worth noting from the VAX's readme:

<pre>
!cmd (the usual shell escape convention)

> (to save a game)

< (to restore a game)
</pre>

Using the save/restore commands will cause the program to crash.

The following is a quick session of the [[4.2 BSD]] version of zork. I think this was the same under all 4.x BSD vax releases.
<pre>
myname# zork
You are in an open field west of a big white house with a boarded
front door.
There is a small mailbox here.
>history
Revision history:

10-SEP-78 Endgame (V2.0a).
10-AUG-78 DECUS version (V1.1b).
14-JUN-78 Public version with parser (V1.1a).
4-MAR-78 Debugging version (V1.0a).
>
</pre>

=== Zork on micro's ===
Zork was also available on various microprocessors, including z80, 6502, 8086.

From what I can find, here is a list of all the platforms:

*Amiga
*Amstrad CPC
*Apple II
*Apricot
*Atari 8-bit
*Atari ST
*Commodore 128
*Commodore 64
*Commodore Plus/4
*CP/M
*DECmate
*DEC Rainbow
*Epson QX-10
*Kaypro II
*Macintosh
*NEC APC
*PC
*PDP-9 RT-11
*PDP-10
*PDP-11 RT-11
*Tandy
*TI-99/4A
*TI Professional
*TRS-80 [Model I and III.]
*TRS-80 Color

=== TRS-80 ===
[[Image:Zork1 trs80.jpg|thumb|150px|right|Zork 1 for the TRS 80]]
Zork was first available on the [[TRS-80]] requiring 32kb of ram, and a floppy disk drive!

You can download it from here:

http://www.classic-computers.org.nz/system-80/disks/zork1_80sssd_jv1.DSK

----

=== CP/M (8080/8086) ===
[[Image:zork1 CPM kit.jpg|thumb|right|150px|Zork 1 for CP/M]]
Zork was made available on the [[i8080]] running [[CP/M]]. You can run this game on [[SIMH]], and also [[emu8080]].

You can download this version here:
*[http://www.retroarchive.org/cpm/games/zork123_80.zip zork123_80.zip]

Zork was also available for the [[i8086]] running CP/M, and you can find it here:
*[http://www.retroarchive.org/cpm/games/zork123_86.zip zork123_86.zip]

Besides the 8080/8086 versions, I'm unaware of any CP/M 68k, or Z8000 version of Zork for CP/M.

One thing of interest, is that the executable for zork1 for the 8080 is only 8704 bytes!

----

=== 6502 (Apple II, Atari, Commodore 64) ===
[[Image:Commodore OEM Zork 1.jpg|150px|thumb|right|Commodore Zork]]
Of the 6502 based micro's the [[Apple II]], [[Atari 800]], and the [[Commodore 64]] both possesed ports of the interpeter required to run Zork.

*[http://cbmfunet.retro-server.de/plus4/Games/misc/z/Zork%20I.d64.gz Zork] for the Commodore 64.
*[http://plus4world.powweb.com/software/Zork_I Zork] for the Commodore Plus/4

Commodore OEM'd Zork onto their computer, and they had unique artwork done.

=== 8086 ===

The IBM PC was also able to run Zork, as shipped from Infocom.

== History of Zork ==

The [[History of Zork]] can be found here http://www.csd.uwo.ca/Infocom/Articles/NZT/zorkhist.html

=== The GDT command ===
The [[FORTRAN]] version of zork was interesting as it included a built in debugger. Depending how old they are, the question would be different.

For example some of the earlier ones look like this:
<pre>
.RUN DUNGEO
Welcome to Dungeon. This version created 6-JUL-78.
You are in an open field west of a big white house with a boarded
front door.
There is a small mailbox here.
>HISTORY
Revision history:
6-JUL-78 Multiple system play test version.
28-JUN-78 Complete play test version.
18-JUN-78 Play test public version.
14-JUN-78 Initial public version.
4-MAR-78 Initial version.
>GDT
A booming voice calls out, "Who summons the right hand of
the translator? State your name, cat, and serial number!"
SUPNIK,BARNEY,70524
At your service!
GDT>
</pre>

And as Bob put it on a mailing list:
<pre>
Barney was the name of the cat I had when I did the bulk of the porting
work.

I'm fairly sure that 70524 was my DEC badge number.

So I guess my cat was working for DEC, indirectly.

/Bob
</pre>

And more on the nature of GDT:
<pre>
GDT dates from a very early version of the game, in fact, before the
game was actually finished. I realized early on that debugging an
interactive program with the traditional PRINT statements was going to
be very cumbersome, and that the interactive debug tools of the day
(1978) had no semantic understanding of the program. GDT was the
answer. It enabled me to track when things went wrong, and to simulate
parts of the game that hadn't been implemented yet.

Originally, GDT was just a command like any other. Once the game was
released, players quickly realized that it offered a simple way to short
circuit the game and to undo mistakes. Lost something to the thief?
Take it back. Getting killed too often? Turn on immortality mode. So
I implemented a variety of challenges to prevent players from entering
GDT without making the mechanism too difficult for me to remember. I
think the INCANT mechanism might have been the final PDP-11 challenge.

When I did the VAX version, I abandoned all that and went back to GDT as
universally enabled, under control of a run time flag, GDTFLG. I think
I intended to turn GDTFLG off before releasing the VAX version, so that
it would be impossible to get into GDT without patching the binaries;
but in fact the final VAX sources have GDTFLG=1.

/Bob
</pre>

== Interrupters ==

=== InfoTaskForce ===
Started as a side project back in the mid 1980's as first decompiling the 8080 version of Zork. Afterwards they reimplemented it in [[C]], and thus were able to run [[Infocom]] games on any machine that they could compile on. I have been able to track down [http://www.planetemu.net/rom/tandy-radio-shack-trs-80-model-1/infocom-adventure-executor-source-files-1987-infotaskforce-c version 1.0], which included support for various mini-computers & personal computers of 1987. Version 1.0 is only capable of playing [[Infocom Game Versions|version 3]] games. I've been able to get this running on the [[x68000]] platform via emulation. Notes for this port are [http://virtuallyfun.superglobalmegacorp.com/2014/12/15/tracking-down-the-infotaskforce-from-1987/ on my blog]. Also I did a port to the [[cisco]] [[1700]] router platform. Again notes are [http://virtuallyfun.superglobalmegacorp.com/2015/09/27/infotaskforce-running-on-powerpc-dynamips/ on my blog].

The much later [http://www.ifarchive.org/indexes/if-archiveXinfocomXinterpretersXoldXitf.html Version 4.01] build of InfoTaskForce includes support for more platforms, and more versions of Infocom games. This also served as the base for later intpreters

=== Pinfocom ===
Pinfocom is a fork from InfoTaskForce, I'd guess version 3?

== see also ==
[[Zork hints]]

[[Category:Games]]