Posted by under Honeywell Bull on April 19 2018, 0 comments

These install notes come from a very old website of mine from the early ’90s. I managed to track this down after someone emailed me about my old machine, which they had come into possession of.

I was glad to hear that the old monster was still running. I have no idea who originally wrote this, so don’t blame me for anything…

Don’t forget to run diskinit before install_rt to make sure the disk is properly formatted and the badmap is complete. When you discover extra bad sectors, I don’t know of any workaround other than reformatting and reinstalling.

If the BOOT1INSTALL disk fails (mine did) it can be emulated by starting to boot from BOOT1, interrupting and setting the system disk to be the _root_ slice of the disk you’re setting up, ie probably c0d0s1.

The UK personalisation install script overwrites files in /etc and elsewhere, so don’t bother hacking things around until after stage 8.

Installation Sequence

1. Boot from BOOT1 + KERNEL + COMMANDS

Run diskinit if necessary (see above)
Run /install_rt

2. Boot from BOOT1INSTALL (or see above)

(Automatically runs) install_ud
(Loads from) R/T tape and INST.USR.
(Shuts down)

3. Boot from disk.

4. Run install_ds

(Loads from) D.SYSTEM tape and UPGFULL

Total usage at this juncture should be: (512-blocks)
/       12128        [total 26990 on a Wren3 ESDI]
/usr    35138        [total 238142 -"-]

5. Insert UK.PERS.vol 1 and

cd /; cpio -ivdmuB Switch to vol 2 when prompted, type /dev/rfdsk0 again.
[Don’t run the install prog yet]

6. Insert DOC.ONLINE vol 1 and

cd /usr; cpio -ivdmuB 7. Run /usr/MAN/install

8. Run /usr/uk_pers/install

9. Insert TCP/IP EXOS Vol 1

cd /; cp unix unix.old; cpio -ivdmu Change NCLIST setting in /usr/include/sys/system.h to greater than 200.
(Possibly 1000.)
cd /usr/EXOS; ./laninst

10. Test networking.

/net/netload -a -d -u -h -p 1 /net/net
                 |  |  | ^^^^^^^^^^^^^^^  ^^^
		 |  |  |   |                  Display all trivial errors[A]
		 |  |  |   Replace with your IP
		 |  |  Use a.b.c.255 not a.b.c.0 for broadcast
		 |  Lose this after debugging[A]
		 Use for loopback. Otherwise uses something weird.
    • cd /usr/EXOS; ./lanjob # Modifies /etc/rc /etc/inittab /etc/ttytype
    • Reboot again.
    • Further testing: DIAGLAN floppy. (See [B] before doing this)
    • mount /dev/fdsk0 /mnt && cd /mnt/ins && sh installan
    • cd /; umount /mnt

11. Don’t forget to change the following:

      • – Console entry in /etc/ttytype
      • – netload parameters in /usr/EXOS/lanstart[A]
      • – PASSWORDS!
      • – directory permissions. Removing group and world writeability from most of them is a good start. Kernels also benefit from not being overwriteable by anyone.
      • – umask in /etc/[csh]profile

[A] I use netload -a -u -p 3 Once you’ve poked your IP address in there once it should stay put. -p 3 only displays errors worth seeing. Ethernet On Fire, that sort of thing.

[B] This modifies the diags progs in /usr/DIAG or somesuch. Unfortunately, it seems to turn them Italian. And remember, running uk_pers install again will blat your /etc files (and may not even do any good). So that’s great. If anyone figures out how to get the English version back, do tell. Oh yeah, and diaglan itself seems to be completely useless. Superb.

At the end of all this gubbins, my du reads:
/    14166
/usr 48170
Though by this time, YMMV. Of course.

Further Notes

    Because the networking methods predate the advent of dynamic ptys, EXOS very kindly starts up shedloads of ptys for you. So unless you’re \always\ going to want 64 people to be able to telnet into your Bull, I recommend creating a new runlevel in your inittab which starts up the usual serial gettys but not the network ones. Saves a fair chunk o’ memory.



Leave a Reply

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