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
done
#
#
for x in obj xsrc src pkgsrc
        do chown -R $USER.$GROUP /usr/$x
done
#
df -h
/bin/echo " "
ls -l /usr/|grep $USER

NetBSD stuff

 mk.conf:

MAKE_JOBS=      4
DEPENDS_TARGET= bin-install

 ---

VBoxManage setextradata "NetBSD-92amd" CustomVideoMode1 1920x1080x32

 vesa list

vesa 0x160

---

 

Hacky tip for Illumos

 This seems to be the weekend to do all the virtualizers -so I've installed OpenIndiana (Hipster 2021-10) which can use UEFI boot now.

I made my hard disk too small so I created another one and then realized that I have no idea how to find out what the name for the disk is. 

Then I remembered -format lists the drives it can see. So:

root@openindiana:~# format -e
Searching for disks...done


AVAILABLE DISK SELECTIONS:
       0. c5t0d0 <VBOX-HARDDISK-1.0-36.00GB>
          /pci@0,0/pci8086,2829@d/disk@0,0
       1. c5t2d0 <VBOX-HARDDISK-1.0-32.00GB>
          /pci@0,0/pci8086,2829@d/disk@2,0
Specify disk (enter its number): ^C
root@openindiana:~#

So now I know I can add c5t2d0 to the end of a zpool create incantation.

As I say; hacky, but it works...

Qemu -hostfwd at last!

 I'm still trying to figure this one out, to be honest

Sparc SS-20 seems to be much improved over the last couple of years; I'm able to boot and install Solaris 7 without much trouble as long as I stick to one cpu and 512megs of ram.

The big big thing is that I've figured out the current (as of 2022) network syntax. 

Sorta.

Now instead of mucking with netdev and vlans I'm able to simply use the "-nic" parameter and put hostfwd directives there.

So here's the complete command for sparc:

qemu-system-sparc -M SS-20 -m 512 -hda (drive) -cdrom  (iso) -boot c -cpu "TI SuperSparc 60" -nic user,hostfwd=tcp::8023-:23

8023 could presumably be anything? to a degree -it didn't work when I tried "80023", though. 

I changed it to "tcp::23-:23" and that worked, but it seems like a bad idea -still, it can be done!

NetBSD on VB - no more hacks! (or at least a lot less)

 Normally doing a NetBSD desktop on VirtualBox involves a convoluted ritual on both host and guest. I still need to do VBoxManage for the host setup, but I've discovered something interesting. For the guest, all I need to do is specify a vesa setting, like this: 

menu=Boot normally:rndseed /var/db/entropy-file;vesa 0x160;boot

...and I get a nice, rich but readable console, and a 1920x180 desktop in X too; without configuring X in any way. This works in VBoxSVGA and VMSVGA. 

Best of all, I get a respectable sized console in full-screen mode -without X. Instead of a tiny 640x480 screen I get a console like this:

 

 

This is a game-changer! No more X (at least, it's optional), no more scaled mode. It's not perfect, but it's a serious improvement!

 

 

A quiet fall

So Windows 11 has dropped -and I've dropped Windows 10. 

I've been using Mint Linux 20.2 with a radeon no-fan (but 2gb) card and it works great for videos; not much else. 

I haven't built (or played with) NetBSD for a while so I set that up last night before I went to sleep; here's the results:

===> Summary of results:
     build.sh command:    ./build.sh -U -j 6 -x -X /home/random/nsrc/92/xsrc -O /home/random/nsrc/92/obj/amd64/ release sourcesets iso-image-source
     build.sh started:    Wed Oct  6 01:26:19 AKDT 2021
     NetBSD version:      9.2
     MACHINE:             amd64
     MACHINE_ARCH:        x86_64
     Build platform:      Linux 4.19.0-17-amd64 x86_64
     HOST_SH:             /usr/bin/sh
     No $TOOLDIR/bin/nbmake, needs building.
     Bootstrapping nbmake
     MAKECONF file:       /etc/mk.conf (File not found)
     TOOLDIR path:        /home/random/nsrc/92/obj/amd64/tooldir.Linux-4.19.0-17-amd64-x86_64
     DESTDIR path:        /home/random/nsrc/92/obj/amd64/destdir.amd64
     RELEASEDIR path:     /home/random/nsrc/92/obj/amd64/releasedir
     Created /home/random/nsrc/92/obj/amd64/tooldir.Linux-4.19.0-17-amd64-x86_64/bin/nbmake
     Updated makewrapper: /home/random/nsrc/92/obj/amd64/tooldir.Linux-4.19.0-17-amd64-x86_64/bin/nbmake-amd64
     Successful make release
     Successful make sourcesets
     Successful make iso-image-source
     build.sh ended:      Wed Oct  6 03:33:21 AKDT 2021
===> .

11 hours to build -current; what the hell?

 I'm not filing a bug because there's too many things that could be problems on my end:

• This is in a virtualbox VM
• I've seen other symptoms of HD failure on my host (I'm replacing the SATA with an SSD)
• This is current compiled on current (9.99.82 compiled on 9.99.81)
• Everything was sent to /usr/obj, which is a zfs volume. 

So -too many moving parts to report, basically. 

That said, here's the summary:

64,no-emul-boot,allow-multidot,bootimage=i386\;efiboot.img,platformid=efi,no-emul-boot NetBSD-9.99.82-amd64.iso cdrom

--- iso_image ---

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

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

iso-image ===> etc

make iso-image-source started at:  Sat May  8 14:02:24 AKDT 2021

make iso-image-source finished at: Sat May  8 14:42:32 AKDT 2021

===> Successful make iso-image-source

===> build.sh ended:      Sat May  8 14:42:32 AKDT 2021

===> Summary of results:

         build.sh command:    ./build.sh -j 5 -m amd64 -x release sourcesets iso-image-source

         build.sh started:    Sat May  8 04:05:23 AKDT 2021

         NetBSD version:      9.99.82

         MACHINE:             amd64

         MACHINE_ARCH:        x86_64

         Build platform:      NetBSD 9.99.81 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.81-amd64

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

         RELEASEDIR path:     /usr/src/obj/releasedir

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

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

         Successful make release

         Successful make sourcesets

         Successful make iso-image-source

         build.sh ended:      Sat May  8 14:42:32 AKDT 2021

===> .

Finding my way

 My last entry was a bunch of compile times with no context.

This post will give the context -hopefully!

First, I want to show why I think I may be on the right track:

iso-image ===> etc
make iso-image started at:  Fri Feb 26 12:57:59 AKST 2021
make iso-image finished at: Fri Feb 26 12:58:01 AKST 2021
===> Successful make iso-image
===> build.sh ended:      Fri Feb 26 12:58:01 AKST 2021
===> Summary of results:
         build.sh command:    ./build.sh -X /home/random/netbsd9/usr/xsrc -x -m sparc -j 5 -U -u -O /home/random/netbsd9/usr/obj -R /home/random/netbsd9/rel/rel-sparc -T /home/random/netbsd9/tooldir/tooldir-sparc release iso-image
         build.sh started:    Fri Feb 26 12:35:41 AKST 2021
         NetBSD version:      9.1_STABLE
         MACHINE:             sparc
         MACHINE_ARCH:        sparc
         Build platform:      Linux 4.19.0-14-amd64 x86_64
         HOST_SH:             /usr/bin/sh
         MAKECONF file:       /etc/mk.conf (File not found)
         TOOLDIR path:        /home/random/netbsd9/tooldir/tooldir-sparc
         DESTDIR path:        /home/random/netbsd9/usr/obj/destdir.sparc
         RELEASEDIR path:     /home/random/netbsd9/rel/rel-sparc
         Updated makewrapper: /home/random/netbsd9/tooldir/tooldir-sparc/bin/nbmake-sparc
         Successful make release
         Successful make iso-image
         build.sh ended:      Fri Feb 26 12:58:01 AKST 2021
===> . 

At this point, it seems as if I'm able to compile sparc/32 ...including X...in 23 minutes. That started at 12:35 and ended at 12:58. 

I haven't tested the iso to confirm that there's X on it, however. 

Even if that has messed up (and I've no reason to think it has) I'm still in the right direction. What I'm referring to is using some of the more advanced(ish) features of buildsh. I have set up a per-arch tools dir and built the tools for several architectures. The quick compile time of sparc32 shows that it's paying off. 

I have a shell script that still has some flaws, but will show you the general idea of what I'm trying to do:

$ cat ../makeit.sh
#!/bin/bash
export TTDR=$HOME/netbsd9/tooldir/tooldir-
export RREL=$HOME/netbsd9/rel/rel-
export OOBJ=$HOME/netbsd9/usr/obj
 for x in i386 sparc64
do
mkdir $RREL$x
./build.sh -X ~/netbsd9/usr/xsrc/ -x -m $x -j 5 -U -u -O $OOBJ -R $RREL$x -T $TTDR$x release iso-image

done

I'm setting up the directories, then the enviromental variables and having mixed results. As I was typing this up, my i386 compile crashed -and now I'm trying with arch-specific obj dirs -a change not reflected in the snippet above.

I also need to research how/what buildsh does with DESTDIR and how to set it, too.

Vax in under an hour...

make iso-image started at:  Thu Feb 25 20:50:56 AKST 2021
make iso-image finished at: Thu Feb 25 20:51:03 AKST 2021
===> Successful make iso-image
===> build.sh ended:      Thu Feb 25 20:51:03 AKST 2021
===> Summary of results:
         build.sh command:    ./build.sh -m vax -U -O /home/random/netbsd9/usr/obj -T /home/random/netbsd9/arch/amd64 -j 5 release iso-image
         build.sh started:    Thu Feb 25 20:08:36 AKST 2021
         NetBSD version:      9.1_STABLE
         MACHINE:             vax
         MACHINE_ARCH:        vax
         Build platform:      Linux 4.19.0-14-amd64 x86_64
         HOST_SH:             /usr/bin/sh
         MAKECONF file:       /etc/mk.conf (File not found)
         TOOLDIR path:        /home/random/netbsd9/arch/amd64
         DESTDIR path:        /home/random/netbsd9/usr/obj/destdir.vax
         RELEASEDIR path:     /home/random/netbsd9/usr/obj/releasedir
         Updated makewrapper: /home/random/netbsd9/arch/amd64/bin/nbmake-vax
         Successful make release
         Successful make iso-image
         build.sh ended:      Thu Feb 25 20:51:03 AKST 2021
===> .

 ...well, hmmph.

I ran a traditional/amd64 build with X and that took about 2 hours -but didn't record the time summary. also the make iso part was messed up because I forgot to put "sourcesets" before "iso-image-source".

Still! It takes half the time to compile NetBSD on a Linux VM than it does on a NetBSD VM. 

Hmmmph. 

This is on Debian 10.8, Virtualbox 6.1.18, 4 cores, for whatever that's worth

---

update

---

i386 in almost 90 minutes (again, no X):

make iso-image started at:  Thu Feb 25 22:26:51 AKST 2021
make iso-image finished at: Thu Feb 25 22:26:58 AKST 2021
===> Successful make iso-image
===> build.sh ended:      Thu Feb 25 22:26:58 AKST 2021
===> Summary of results:
         build.sh command:    ./build.sh -m i386 -U -O /home/random/netbsd9/usr/obj -T /home/random/netbsd9/arch/amd64 -j 5 release iso-image
         build.sh started:    Thu Feb 25 20:58:56 AKST 2021
         NetBSD version:      9.1_STABLE
         MACHINE:             i386
         MACHINE_ARCH:        i386
         Build platform:      Linux 4.19.0-14-amd64 x86_64
         HOST_SH:             /usr/bin/sh
         MAKECONF file:       /etc/mk.conf (File not found)
         TOOLDIR path:        /home/random/netbsd9/arch/amd64
         DESTDIR path:        /home/random/netbsd9/usr/obj/destdir.i386
         RELEASEDIR path:     /home/random/netbsd9/usr/obj/releasedir
         Updated makewrapper: /home/random/netbsd9/arch/amd64/bin/nbmake-i386
         Successful make release
         Successful make iso-image
         build.sh ended:      Thu Feb 25 22:26:58 AKST 2021
===> .

sun2 in ~45 minutes (no X)

---

iso-image ===> etc
make iso-image started at:  Thu Feb 25 23:13:19 AKST 2021
make iso-image finished at: Thu Feb 25 23:13:34 AKST 2021
===> Successful make iso-image
===> build.sh ended:      Thu Feb 25 23:13:34 AKST 2021
===> Summary of results:
         build.sh command:    ./build.sh -m sun2 -U -O /home/random/netbsd9/usr/obj -T /home/random/netbsd9/arch/amd64 -j 5 release iso-image
         build.sh started:    Thu Feb 25 22:38:21 AKST 2021
         NetBSD version:      9.1_STABLE
         MACHINE:             sun2
         MACHINE_ARCH:        m68000
         Build platform:      Linux 4.19.0-14-amd64 x86_64
         HOST_SH:             /usr/bin/sh
         MAKECONF file:       /etc/mk.conf (File not found)
         TOOLDIR path:        /home/random/netbsd9/arch/amd64
         DESTDIR path:        /home/random/netbsd9/usr/obj/destdir.sun2
         RELEASEDIR path:     /home/random/netbsd9/usr/obj/releasedir
         Updated makewrapper: /home/random/netbsd9/arch/amd64/bin/nbmake-sun2
         Successful make release
         Successful make iso-image
         build.sh ended:      Thu Feb 25 23:13:34 AKST 2021
===> .

---

iso-image ===> etc
make iso-image started at:  Fri Feb 26 00:08:14 AKST 2021
make iso-image finished at: Fri Feb 26 00:08:15 AKST 2021
===> Successful make iso-image
===> build.sh ended:      Fri Feb 26 00:08:15 AKST 2021
===> Summary of results:
         build.sh command:    ./build.sh -m sun3 -U -O /home/random/netbsd9/usr/obj -T /home/random/netbsd9/arch/amd64 -j 5 release iso-image
         build.sh started:    Thu Feb 25 23:23:37 AKST 2021
         NetBSD version:      9.1_STABLE
         MACHINE:             sun3
         MACHINE_ARCH:        m68k
         Build platform:      Linux 4.19.0-14-amd64 x86_64
         HOST_SH:             /usr/bin/sh
         MAKECONF file:       /etc/mk.conf (File not found)
         TOOLDIR path:        /home/random/netbsd9/arch/amd64
         DESTDIR path:        /home/random/netbsd9/usr/obj/destdir.sun3
         RELEASEDIR path:     /home/random/netbsd9/usr/obj/releasedir
         Updated makewrapper: /home/random/netbsd9/arch/amd64/bin/nbmake-sun3
         Successful make release
         Successful make iso-image
         build.sh ended:      Fri Feb 26 00:08:15 AKST 2021
===> . 

...time passes... 

iso-image ===> etc
make iso-image started at:  Fri Feb 26 12:57:59 AKST 2021
make iso-image finished at: Fri Feb 26 12:58:01 AKST 2021
===> Successful make iso-image
===> build.sh ended:      Fri Feb 26 12:58:01 AKST 2021
===> Summary of results:
         build.sh command:    ./build.sh -X /home/random/netbsd9/usr/xsrc -x -m sparc -j 5 -U -u -O /home/random/netbsd9/usr/obj -R /home/random/netbsd9/rel/rel-sparc -T /home/random/netbsd9/tooldir/tooldir-sparc release iso-image
         build.sh started:    Fri Feb 26 12:35:41 AKST 2021
         NetBSD version:      9.1_STABLE
         MACHINE:             sparc
         MACHINE_ARCH:        sparc
         Build platform:      Linux 4.19.0-14-amd64 x86_64
         HOST_SH:             /usr/bin/sh
         MAKECONF file:       /etc/mk.conf (File not found)
         TOOLDIR path:        /home/random/netbsd9/tooldir/tooldir-sparc
         DESTDIR path:        /home/random/netbsd9/usr/obj/destdir.sparc
         RELEASEDIR path:     /home/random/netbsd9/rel/rel-sparc
         Updated makewrapper: /home/random/netbsd9/tooldir/tooldir-sparc/bin/nbmake-sparc
         Successful make release
         Successful make iso-image
         build.sh ended:      Fri Feb 26 12:58:01 AKST 2021
===> .

Note to future self, feb 2021

This blog post details a personal workflow experiment. This is for my own use only -if you found this entry because of google, whatever you should be aware that none of this is recommended. It's shit I'm trying for myself.

At least it compiles!

I was able to build CDE on NetBSD 9.1 by following the instructions and then running:

LANG=C make -k World

Four Seventeen...

 ===> build.sh ended:      Fri Feb  5 03:36:39 AKST 2021
===> Summary of results:
         build.sh command:    ./build.sh -j 5 -u -x -X /usr/xsrc release sets sourcesets iso-image-source
         build.sh started:    Thu Feb  4 23:19:31 AKST 2021
         NetBSD version:      9.99.77
         MACHINE:             amd64
         MACHINE_ARCH:        x86_64
         Build platform:      NetBSD 9.99.77 amd64
         HOST_SH:             /bin/sh
         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
         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:      Fri Feb  5 03:36:39 AKST 2021
===> .
beasty2021$

A more prudent decision ...?

 I just, just wrote my previous blogpost 12 hours ago -and I've already got a good deal of 2020Q4 built on Debian 10.

It ought to go without saying I'm doing all of this in Virtualbox, as I do with 9/10ths of the other things I write about (with the exception of 86box stuff). But the Debian VM I was building in was built wrong -the disk space was split and arranged oddly.

So this morning I packed up what I had built and then remade another VM -this time with 80 odd gigs and all on one partition, and splatted it back on there.

Ncurses, gcc-10, libcups and harfbuzz all built just fine -but it was building harfbuzz that I discovered that I'd run out of room. I had things build while I slept:

gcc-10

clang

LLVM

harfbuzz

...it turns out that clang and LLVM didn't build; presumably because of space issues. 

Basically, my strategy is the get the problematic builds (ncurses, libcups) built, then the larger ones (gcc-10, clang) ...after that, I'll tackle widget libraries (gtk,wxwidgets and qt) and hopefully after that I'll be able to build packages such as codeblocks and libreoffice.

The title refers to my move (back) to building on Debian instead of Centos. I know where Debian is going to be and what they'll be doing 5 years from now. IBM -not so much. I might be more interested in riding out the Centos drama if I was invested in the RedHat ecosystem to begin with -but I'm not. I've always preferred Mint, Debian or Ubuntu (in that order).

Mind you, the Centos VM feels cozy as a desktop, and I can see myself possibly setting up a RHEL or a "Rocky" Or a "AlmaLinux" secondary desktop in the future -but for the purposes of learning pkgsrc on Linux I think my time is better spent getting things working on Debian. Like I say, I know where they'll be 5 or 10 years from now.

Crossing the Stream; pkgsrc and Linux Contrarianism

For the last month the Linux world has been in an uproar about IBM Redhat changing CentOS from a RHEL clone to a RHEL beta. 

We have forks and everything -personally speaking, my money is on this one.

In response Redhat's expanded their developer's program -but that's not really interesting to me. At least not at the moment. I've been sitting on a Redhat Developer account since 2015 or 2016 (when they made it free) but I've never really been thrilled with Redhat -going back to when I bought 5.2 in 1998.

But for some reason I'm uncertain about, I'm interested in seeing if I can use pkgsrc on top of Centos/Streams. 

I'm not sure why, except I like the idea of providing a one-and-done newish platform on top of Centos -which, with streams, honestly won't be terribly different than Ubuntu Server (in terms of stability). I also see it in an odd (and possibly incorrect) hedge against low-level breakage on Streams. 

I'm on my 2nd day of building on here and have already worked some things out:

I've learned that post-install I need to add the ncurses-devel and gcc-c++ packages. 

For libcups/cups to compile I've made the following changes to /usr/pkgsrc/share/mk/platform/Linux.mk

[random@deadrat-localdomain ~]$ cat /usr/pkgsrc/mk/platform/Linux.mk |grep ULI

ULIMIT_CMD_datasize?=   /usr/bin/ulimit -d `/usr/bin/ulimit -H -d`

ULIMIT_CMD_stacksize?=  /usr/bin/ulimit -s `/usr/bin/ulimit -H -s`

ULIMIT_CMD_memorysize?= /usr/bin/ulimit -m `/usr/bin/ulimit -H -m`

ULIMIT_CMD_cputime?=    /usr/bin/ulimit -t `/usr/bin/ulimit -H -t`

Then I build (in order): ncurses, gcc10, clang, python27, python38, python39, flex,bison, gdb, screen,sudo,fonts/harfbuzz 

Doing it randomly seems to cause fonts/harfbuzz to break. 

People complain that RHEL/Centos' packages etc are too old, but that might actually be a mark in their favor when it comes to pkgsrc. At least, I haven't gotten this far before on Debian, Ubuntu or Fedora.

Which makes me nervous for when I try to build this on one of those -I suspect their systems may well be too new.

OI on VB; quick note-to-self

 To get proper graphics, the following need to be done: 

C:\Program Files\Oracle\VirtualBox>VBoxManage.exe setextradata OI-2021 CustomVideoMode1 1920x1080x16

C:\Program Files\Oracle\VirtualBox>VBoxManage modifyvm OI-2021 --graphicscontroller vboxvga

The resolution may/may not need to be adjusted in MATE (preferences -> system -> displays).

The text installer (an option from the mate boot disk) allows you to specify an IP and default router, instead of having it handled by Network Manager. 

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

===> .

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"

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:

Model	RAM (max.)	Hard-disk	CPU	Video
2011 n01	512 Ko (1MB)	none	286 at 10MHz	VGA
2011 n34	1MB	30MB	286 at 10MHz	VGA
2011 n41	1MB	40MB	286 at 10MHz	VGA
2011 n42	2MB (6MB)	40MB	386sx at 16MHz	VGA
2121 282	2MB (6MB)	80MB	386sx at 16MHz	VGA
2121 642	2MB (6MB)	40MB	386sx at 20MHz	VGA
2121 682	2MB (6MB)	80MB	386sx at 20MHz	VGA
2123 E41 Pro	2MB (15MB)	40MB	386sx at 20MHz	VGA
2123 E81 Pro	2MB (15MB)	80MB	386sx at 20MHz	VGA
2123 E31 Pro	2MB (15MB)	130MB	386sx at 20MHz	VGA
2133 111	2MB (15MB)	85MB	386sx at 25MHz	VGA
2133 711	2MB (15MB)	85MB	386sx at 25MHz	VGA
2133 811	4MB (15MB)	85MB	386sx at 25MHz	VGA
2133 911	2MB (15MB)	85MB	386sx at 25MHz	VGA
2133 114	4MB (15MB)	170MB	386sx at 25MHz	sVGA
2133 144	4MB (32MB)	170MB	486sx at 20MHz	sVGA
2133 151	4MB (32MB)	85MB	486sx at 25MHz	sVGA
2133 154	4MB (32MB)	170MB	486sx at 25MHz	sVGA
2133 174	4MB (32MB)	170MB	486sx at 33MHz	sVGA
2133 451	2MB (32MB)	85MB	486sx at 25MHz	sVGA
2133 461	4MB (32MB)	85MB	486sx at 33MHz	sVGA
2133 551	4MB (32MB)	130MB	486sx at 25MHz	sVGA
2133 571	4MB (64MB)	130MB	486dx at 33MHz	sVGA
2155 471	4MB (64MB)	85MB	486dx at 33MHz	sVGA
2155 474	4MB (64MB)	130MB	486dx at 33MHz	sVGA
2155 483	4MB (64MB)	130MB	486dx2 at 50MHz	sVGA
2155 582	4MB (64MB)	170MB	486dx2 at 50MHz	sVGA
2155 593	4MB (64MB)	253MB	486dx2 at 66MHz	sVGA
2168 452	2MB (32MB)	85MB	486sx at 25MH	sVGA
2168 463	4MB (64MB)	130	486sx at 33MHz	sVGA
2168 473	4MB (64MB)	130	486dx at 33MHz	sVGA
2168 493	4MB (64MB)	130	486dx2 at 66MHz	sVGA
2168 584	4MB (64MB)	253	486dx2 at 50MHz	sVGA
2168 594	4MB (64MB)	253	486dx2 at 66MHz	sVGA

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

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.