Sunday, December 27, 2020

ooof. 4 hours and 42 minutes to build 9.99.77!

 mkdir -p -m 0755 /usr/src/obj/releasedir/images

/usr/src/obj/tooldir.NetBSD-9.99.77-amd64/bin/x86_64--netbsd-install -r -p -c -m 444 NetBSD-9.99.77-amd64.iso /usr/src/obj/releasedir/images

iso-image ===> etc

make iso-image-source started at:  Sun Dec 27 07:55:04 AKST 2020

make iso-image-source finished at: Sun Dec 27 07:56:11 AKST 2020

===> Successful make iso-image-source

===> build.sh ended:      Sun Dec 27 07:56:11 AKST 2020

===> Summary of results:

         build.sh command:    ./build.sh -j 4 -u -x -X /usr/xsrc release sets sourcesets iso-image-source

         build.sh started:    Sun Dec 27 03:14:41 AKST 2020

         NetBSD version:      9.99.77

         MACHINE:             amd64

         MACHINE_ARCH:        x86_64

         Build platform:      NetBSD 9.99.77 amd64

         HOST_SH:             /bin/sh

         No $TOOLDIR/bin/nbmake, needs building.

         Bootstrapping nbmake

         MAKECONF file:       /etc/mk.conf

         TOOLDIR path:        /usr/src/obj/tooldir.NetBSD-9.99.77-amd64

         DESTDIR path:        /usr/src/obj/destdir.amd64

         RELEASEDIR path:     /usr/src/obj/releasedir

         Created /usr/src/obj/tooldir.NetBSD-9.99.77-amd64/bin/nbmake

         Updated makewrapper: /usr/src/obj/tooldir.NetBSD-9.99.77-amd64/bin/nbmake-amd64

         Successful make release

         Building sets from pre-populated /usr/src/obj/destdir.amd64

         Built sets to /usr/src/obj/releasedir/amd64/binary/sets

         Successful make sourcesets

         Successful make iso-image-source

         build.sh ended:      Sun Dec 27 07:56:11 AKST 2020

===> .

Command line:  ./build.sh -j 4 -u -x -X /usr/xsrc release sets sourcesets iso-image-source

Virtualbox, 4 cpus, Execution cap 95%, 10248mb of ram

----

Results from 11 Jan 2021:

----

make iso-image-source finished at: Mon Jan 11 03:33:14 AKST 2021

===> Successful make iso-image-source

===> build.sh ended:      Mon Jan 11 03:33:14 AKST 2021

===> Summary of results:

         build.sh command:    ./build.sh -j 4 -u -x -X /usr/xsrc release sets sourcesets iso-image-source

         build.sh started:    Sun Jan 10 23:54:07 AKST 2021

         NetBSD version:      9.99.77

         MACHINE:             amd64

         MACHINE_ARCH:        x86_64

         Build platform:      NetBSD 9.99.77 amd64

         HOST_SH:             /bin/sh

         No $TOOLDIR/bin/nbmake, needs building.

         Bootstrapping nbmake

         MAKECONF file:       /etc/mk.conf

         TOOLDIR path:        /usr/src/obj/tooldir.NetBSD-9.99.77-amd64

         DESTDIR path:        /usr/src/obj/destdir.amd64

         RELEASEDIR path:     /usr/src/obj/releasedir

         Created /usr/src/obj/tooldir.NetBSD-9.99.77-amd64/bin/nbmake

         Updated makewrapper: /usr/src/obj/tooldir.NetBSD-9.99.77-amd64/bin/nbmake-amd64

         Successful make release

         Building sets from pre-populated /usr/src/obj/destdir.amd64

         Built sets to /usr/src/obj/releasedir/amd64/binary/sets

         Successful make sourcesets

         Successful make iso-image-source

         build.sh ended:      Mon Jan 11 03:33:14 AKST 2021

===> .




Sunday, July 19, 2020

386BSD at last!

So, Friday I was looking at the 386BSD repository (as you do) and noticed something quite interesting...

boot.exe

...wtf is a boot.exe? It is a DOS utility that allows you to boot an 386bsd kernel. Similar to (and the basis of?) the utility that used to ship in early FreeBSD cds.

After a brief test in VirtualBox (as you do) I set up an 86Box machine to test it out -and then another, and another, and so on.

Ignoring all of the dead ends and tangents, what I did can be summarized thusly:


  1. I cloned the 386BSD 1.0 repository inside of WSL
  2. I created a tar file (three, actually -a base, X386 and source) and put it on an iso
  3. I created a new 86Box machine, with a 504mb (no larger -or 386BSD's install crashes) drive.
  4. I added a second 504mb drive to that machine.
  5. I attached that drive onto a working FreeBSD 2.0 86Box machine.
  6. Booting into FreeBSD, I mounted the iso I created and the 386BSD drive and untarred all of the archives onto it
  7. After shutting that down, I booted the 386BSD machine and from dos typed boot 386bsd.sma wd1a
  8. I ran through the install process from the secondary hard drive to install 386BSD to the first
  9. I "enjoyed" my new 386BSD 1.0 installation!


...mind the quotes. The install is very rough, and I had to do some things I'm not proud of (ln /usr/bin/true /usr/sbin/sendmail) and some things I shouldn't have had to do (cp /etc/MAKEDEV /mnt/etc/MAKEDEV) (cd /mnt/dev;MAKEDEV

...and the included source does NOT compile, though I can't rule out a fuck-up on my part.

There's quite a few subtleties to all of this; missing directories, odd permissions and at this moment it only seems to work with extremely specific 86Box machines (NEC Pentium, to be exact). Also the TERM variable seems to be set to xterm which is a complete W.T.F. Then there's the question of setting the date (you can, but it doesn't persist)

...but at this point, that's all trivia; the important thing is that I have a "working" configuration.

"Working"



Saturday, July 4, 2020

Turbo Vision resources

Turbo Vision was a DOS "TUI" (text-based user interface) developed by Borland. It was later made open source. 

It's a bugger to track down!

After some searching I did manage to find this page: http://www.sigala.it/sergio/tvision/index.html which has copies of it on the 'resources' link. 

There's also a "public domain lib" out there somewhere -no luck tracking (the sources to) that down yet!

Down a rabbit-hole

Not really related to Unix, but emulation. The 86Box emulator (plus roms) contains a good ps/2 and ps/1 emulator and I've been doing some reading on what different specs were etc.

I wanted to put some links here for future refernce:

Chart of PS/1 specs from https://www.old-computers.com/museum/doc.asp?c=1274
______
There were later many different PS/1 Models released.
Here is a quite complete list of them with main technical differences:
ModelRAM (max.)Hard-diskCPUVideo
2011 n01512 Ko (1MB)none286 at 10MHzVGA
2011 n341MB30MB286 at 10MHzVGA
2011 n411MB40MB286 at 10MHzVGA
2011 n422MB (6MB)40MB386sx at 16MHzVGA
2121 2822MB (6MB)80MB386sx at 16MHzVGA
2121 6422MB (6MB)40MB386sx at 20MHzVGA
2121 6822MB (6MB)80MB386sx at 20MHzVGA
2123 E41 Pro2MB (15MB)40MB386sx at 20MHzVGA
2123 E81 Pro2MB (15MB)80MB386sx at 20MHzVGA
2123 E31 Pro2MB (15MB)130MB386sx at 20MHzVGA
2133 1112MB (15MB)85MB386sx at 25MHzVGA
2133 7112MB (15MB)85MB386sx at 25MHzVGA
2133 8114MB (15MB)85MB386sx at 25MHzVGA
2133 9112MB (15MB)85MB386sx at 25MHzVGA
2133 1144MB (15MB)170MB386sx at 25MHzsVGA
2133 1444MB (32MB)170MB486sx at 20MHzsVGA
2133 1514MB (32MB)85MB486sx at 25MHzsVGA
2133 1544MB (32MB)170MB486sx at 25MHzsVGA
2133 1744MB (32MB)170MB486sx at 33MHzsVGA
2133 4512MB (32MB)85MB486sx at 25MHzsVGA
2133 4614MB (32MB)85MB486sx at 33MHzsVGA
2133 5514MB (32MB)130MB486sx at 25MHzsVGA
2133 5714MB (64MB)130MB486dx at 33MHzsVGA
2155 4714MB (64MB)85MB486dx at 33MHzsVGA
2155 4744MB (64MB)130MB486dx at 33MHzsVGA
2155 4834MB (64MB)130MB486dx2 at 50MHzsVGA
2155 5824MB (64MB)170MB486dx2 at 50MHzsVGA
2155 5934MB (64MB)253MB486dx2 at 66MHzsVGA
2168 4522MB (32MB)85MB486sx at 25MHsVGA
2168 4634MB (64MB)130486sx at 33MHzsVGA
2168 4734MB (64MB)130486dx at 33MHzsVGA
2168 4934MB (64MB)130486dx2 at 66MHzsVGA
2168 5844MB (64MB)253486dx2 at 50MHzsVGA
2168 5944MB (64MB)253486dx2 at 66MHzsVGA
Source : Silicium.org

https://stason.org/TULARC/pc/motherboards/I/IBM-CORPORATION-486-PS-1-TYPE-2133-2155-2168-TYPE.html

https://github.com/86Box/86Box/issues/886

PS/1 Models Spreadsheet on google docs: https://docs.google.com/spreadsheets/d/1gzi99Hd35Doq-tKUGpZZoOIzkGtt43o8dLqlaX-8sYw/edit#gid=969214990

http://www.ibm-pc.org/diagnostic/ibm/ps2/ps2files/index.htm

Saturday, March 28, 2020

Openindiana Static IP

Thanks to a post on the OI mailing list, I finally figured out how to set a static IP.

Actually, setting the static IP hasn't been the problem; that's easy enough to do using network manager. The tricky part has been dns.

The mailing list referred to this guide on the openindiana website. Using those instructions -modified for virtualbox (substituting bge0 with e1000g0), I was able to set my IP to 192.168.1.15 and my router to 192.168.1.1

ifconfig showed the correct information, and my route seemed to be set; but I couldn't ping anything.

I went back to re-read and found this gem:

IF you cannot ping an external IP (e.g. google.com) run this command and try again.
# cp /etc/nsswitch.dns /etc/nsswitch.conf

After that, the net worked just like it was supposed to. In fact, I half suspect I could have skipped all the dinking around and simply set /etc/resolv.conf and nsswitch.conf. I'll have to try that another day!

Other, unrelated notes:
I tried setting up sunstudio 12.3, but it didn't like my installed java version; so it won't run.

I temporarily borked my mate by adding the following to .profile:
$PATH:/opt/solarisstudio12.3/bin
which should have been:
export PATH=$PATH:/opt/solarisstudio12.3/bin

The result being that lightdm would get confused and send me back to the login prompt after successfully logging in.

automating zfs mounts -a quick and very dirty script

 #!/bin/sh for x in obj xsrc src pkgsrc pkgsrc/distfiles pkgsrc/packages pkg         do zfs create ext/$x zfs set mountpoint=/usr/$x ext/$x ...